Indie Hacker Playbook: Building SaaS Products Around Twitter
A developer with more than ten years of experience can still be surprised by what a launch reveals. In this account, Luca Restagno describes two products — Hivoe and Inboxs — and the sequence that connected them: a quiet Product Hunt launch, a shift toward audience building on Twitter, a first paying customer at five euros per month, and later a pre-sale that sold twenty lifetime deals at fifty dollars in a week. The useful lesson is not the specific numbers. It is the order of operations: find where people already talk, build a small tool for a real friction point, and let paying interest decide what to build next.
From employee to solo builder
After years of working inside other companies, the decision to build independently came from a simple calculation: enough technical knowledge had accumulated to create and scale a product rather than keep doing it for an employer. What was underestimated was the marketing side. Trading a fixed salary for a hoped-for MRR also meant accepting factors outside personal control, which made the traditional career path feel less appealing.
A first product was built on the side over two years and launched on Product Hunt. It received only 70 upvotes. That result was the turning point: an audience matters as much as the build when a SaaS product launches and grows. Six months later that first product was sold with a former colleague, and the solo indie hacker path began.
Hivoe: a tool born from Twitter conversations
Hivoe started because of active Twitter use and an audience-building effort. Large accounts were recommending Twitter Direct Messages as a way to create new relationships. That observation led to a small product around the feature. An early user found on Twitter tried Hivoe at a very early stage and wanted to pay — a surprise that prompted a quick payment-processor integration and a first subscription at 5 euros a month.
Over time, a limitation became clear: the native Twitter DM experience is not powerful enough for people running a business there. Conversations cannot be marked unread, saved for later, or tagged. That gap became the reason to build Inboxs.
Inboxs: validating with a pre-sale instead of a finished product
Inboxs used a different method. A landing page described the planned features and a clear call to action — lock your price forever, a lifetime deal at $50. Visitors could not try the product before buying. Twenty people purchased within a week, and that became the validation signal.
This is a useful pattern to examine carefully. The pre-sale tests willingness to pay before the build is complete, but it also creates an obligation to deliver the described features. The landing page carried three essential elements: a feature description, a clear call to action, and a price-lock offer. Nothing in the account suggests the price or the buyer count should be treated as a benchmark for other products.
Splitting time between a job and two products
Eight hours a day go to a full-time job, which remains the main income source. The rest goes to the two products and to Twitter activity, described as the main traffic source. There are no strict rules. Time goes to whichever product needs it — at the time of the account, Inboxs was the focus, with the goal of consolidating it around user feedback and moving to a recurring subscription.
Productivity is not guaranteed. The approach is to spend a lot of time deeply focused on work that is enjoyable, accept that context switching is overwhelming but familiar to a software engineer, and recognize that not every desired task will get done. The practical rule: pick the most important task and give it the time. No special system — hard work and consistency.
Marketing as observation, with Twitter as the channel
Marketing is described as a skill still being learned, with observation of others as the current method. The working definition: put the product out in an appealing way and generate traffic so the product reaches an audience. Twitter is the platform of choice, and the indie hacker and solopreneur community there is described as supportive. Daily activity grows the audience a little at a time, and Twitter is named as the main traffic source.
Advice for two different stages
For people already growing a business, the emphasis is on customer experience: timely support and happy customers. Listening matters even when revenue is already coming in, because it reveals how people actually use the product. Content and SEO are framed as a long-term game.
For people just starting, the advice is blunt: pause development and spend six months growing an audience on a preferred social platform or a newsletter. With a large enough audience, a launch is more likely to produce people who try the product, give feedback, and pay.
Decision checklist: audience-first or pre-sale-first?
Use this checklist to choose a starting path. It is a reading aid built from the two product stories, not a guarantee of outcomes.
- Do you already have a place where people listen to you? If yes, an audience-first launch is the lower-friction path.
- Is the friction point visible in an existing platform? Hivoe came from a feature people were already recommending to each other.
- Can you describe the product clearly enough for someone to buy without trying it? Inboxs was validated that way.
- Are you prepared to deliver every feature named on the pre-sale page? A pre-sale is a promise, not just a test.
- Is the price-lock offer time-bound and clearly stated? The described offer was a $50 lifetime deal.
- Can you protect focused time for the product that needs it most? The account describes choosing one priority at a time.
- Are you measuring interest in paying customers, not just upvotes? The first launch's 70 upvotes did not translate into traction.
Worked example: reading the Inboxs pre-sale signal
The Inboxs pre-sale produced 20 purchases at $50 each within one week, before anyone could try the product. As a validation signal, that means 20 people accepted the described feature set and the price-lock terms on the strength of the landing page alone. It does not establish retention, satisfaction, or whether the final product matched expectations. A careful reader would treat it as evidence of demand for the described offer, and would then track delivery against the promised features.
A simple way to record the signal: note the offer, the price, the time window, the number of buyers, and the features promised. Compare the delivered product against that list before drawing conclusions about product-market fit.
Two different failure signals
The account contains two distinct setbacks that are easy to conflate. The first was a launch that reached few people: 70 upvotes on Product Hunt. The diagnosis was an audience gap, not a product flaw. The second was a product limitation: native Twitter DMs lacked unread marking, saving for later, and tags. The diagnosis there was a feature gap that justified a new product. Keeping these separate matters — one calls for distribution work, the other for product work.
Learning resources named in the account
The recommended podcast is Wannabe Entrepreneur by Tiago Ferreira. The first book read on building in public and building an audience was "The Embedded Entrepreneur" by Arvid Kahl, which is strongly recommended. Luca can be found on Twitter as @ikoichi, and the products are at hivoe.com and inboxs.io.
Frequently asked questions
What is pre-sale validation?
It is selling access to a product before it is finished, using a landing page that describes the features and a clear call to action. In the Inboxs case, the offer was a $50 lifetime deal described as locking the price forever, and 20 people bought within a week without being able to try the product first.
Why did the first Product Hunt launch underperform?
The account attributes the 70-upvote result to a lack of audience rather than a product problem. The lesson drawn was that an audience is crucial for launching and growing a SaaS product.
What problem does Inboxs solve?
It addresses limitations in the native Twitter Direct Messages experience for business use: conversations cannot be marked unread, saved for later, or tagged. Inboxs was created to improve that workflow.
How is time divided between a full-time job and two products?
Eight hours a day go to the full-time job as the main income source. The remaining time goes to the two products and to Twitter activity. There are no strict rules; time goes to whichever product needs it, with one priority chosen at a time.
What advice is given to people just starting out?
Pause development and spend six months growing an audience on a preferred social platform or a newsletter. The reasoning is that a large enough audience makes a launch more likely to produce people who try the product, give feedback, and pay.