Startup Stages: A Practical Roadmap for Indie Hackers and Solo Founders

Nov 6, 2026

The main startup stages are problem discovery, idea validation, minimum viable product development, launch, traction, and sustainable growth. For indie hackers and solo founders, there is also an important possible outcome: shutting down a product and applying its lessons to the next launch.

These stages describe changes in evidence, not company size or fundraising status. A startup moves forward when its founder learns something meaningful about the problem, the product, or the business.

For a solo founder building in public, understanding the startup stages helps answer three practical questions:

What deserves attention now?
What evidence would justify the next investment of time?
What progress is worth sharing publicly?

This guide explains each stage, the signals that matter, and how a public maker story can connect individual launches into a coherent track record.

Startup Stages at a Glance

A bootstrapped product does not need to follow a venture-backed funding timeline. Pre-seed, seed, and Series A describe financing events, not necessarily product maturity.

A more useful framework for an independent maker looks like this:

Startup stage	Main question	Most useful evidence	Public update
Problem discovery	Does a specific problem exist?	Recent examples, recurring frustration, existing workarounds	The problem being investigated
Idea validation	Will people commit to a solution?	Trial commitments, pilot participation, payments where appropriate	Tests, findings, and assumptions
MVP development	Can the product deliver its core outcome?	Successful completion of the main user task	Working demos and product decisions
Launch	Can relevant people discover and try it?	Qualified visitors, signups, and activated users	Launch story and early feedback
Traction and retention	Do users return and receive ongoing value?	Repeat use, retention, renewals, referrals	Improvements and usage lessons
Sustainable growth	Can the business grow without overwhelming its founder?	Repeatable acquisition, manageable costs, operational capacity	Milestones and strategic trade-offs
Shutdown or renewal	Is continued investment justified?	Product economics, customer needs, opportunity cost	Closure details and lessons learned

The stages overlap. A launched product may still need problem discovery, while an established product may return to validation before serving a new audience.

Stage 1: Problem Discovery

Problem discovery begins with a specific person and a specific difficulty, not a feature list.

An indie hacker might notice that freelance designers struggle to collect client feedback, or that newsletter writers repeatedly assemble reports by hand. The opportunity becomes clearer when the founder understands the situation, the existing workaround, and the consequences of leaving the problem unsolved.

What matters at this stage

Useful research focuses on actual behavior:

When did the problem last occur?
What did the person do about it?
Which tools or manual processes were involved?
What time, money, or opportunities did the problem cost?
Who has the authority and motivation to adopt a solution?

Questions about recent experiences are generally more informative than questions about hypothetical future use.

What to share publicly

A founder can share the problem being explored, patterns from conversations, and assumptions that changed. Customer identities and sensitive details should remain private unless permission has been given.

The goal is not to announce certainty. It is to make the investigation understandable.

Signal to move forward: A defined group describes a recurring problem and already spends effort trying to solve it.

Common mistake: Treating enthusiasm for an idea as proof that the underlying problem is important.

Stage 2: Idea Validation

Validation tests whether the proposed solution deserves a larger investment.

A landing page, prototype, manual service, or small pilot can reveal more than weeks of isolated development. The appropriate test depends on what remains uncertain.

If the uncertainty concerns demand, a polished interface is unlikely to resolve it. If the uncertainty concerns usability, a waitlist alone provides limited evidence.

Commitment matters more than compliments

Different actions carry different levels of commitment:

Liking a social post requires little effort.
Joining a relevant waitlist suggests interest.
Attending a product walkthrough requires time.
Providing data or changing a workflow requires effort and trust.
Paying for a clearly described offer tests willingness to pay.

None of these guarantees a viable business. Together, they help a founder distinguish polite encouragement from meaningful demand.

Preorders and paid pilots require transparent terms, realistic delivery expectations, and clarity about what exists today.

What to share publicly

Useful validation updates explain:

The assumption being tested
The experiment used
What participants actually did
What changed as a result

Signal to move forward: Target users make a meaningful commitment, and the founder understands which outcome they expect.

Common mistake: Counting every email signup as an equally qualified future customer.

Stage 3: Minimum Viable Product Development

The minimum viable product, or MVP, is the smallest usable version that can deliver the core promised outcome and test important assumptions.

For a solo founder, this stage is largely an exercise in scope control. Every extra integration, setting, or dashboard creates development and maintenance work.

Define one complete user journey

A useful MVP supports a clear path:

A target user arrives with a known problem.
The user completes the essential setup.
The product performs its main function.
The user receives an understandable result.

The interface can be simple, and some work can happen manually behind the scenes. However, essential privacy, security, and reliability requirements should not be dismissed as optional polish.

Measure completed outcomes

Feature count is a weak measure of progress. More useful questions include:

Can a target user finish the main task?
Where does the user become confused or stop?
How much help is required?
Does the result solve the problem identified earlier?

Building in public can make these decisions visible through short demos, shipping notes, and explanations of what was deliberately excluded.

Signal to move forward: Early users can reach the product’s core outcome with an acceptable level of assistance.

Common mistake: Expanding the MVP whenever a new feature idea appears.

Stage 4: Launch

A launch makes a product discoverable and gives a relevant audience a reason to try it.

For indie hackers, launch channels may include Product Hunt, niche communities, an existing audience, direct outreach, and a public maker page. The right channel depends on where potential users already spend attention.

A launch is a distribution event, not proof of product-market fit.

Prepare the path from attention to value

Before promoting the product, a founder should check that:

The product description identifies the intended user.
The main benefit is clear.
Signup and onboarding work.
New users can reach the core outcome.
Feedback and support channels are available.
Basic measurement distinguishes visits, signups, and activation.

Activation means reaching an event that indicates initial value. Its definition should match the product, such as completing a report or publishing a first project, rather than simply creating an account.

Evaluate more than launch-day traffic

A busy launch can produce attention without lasting demand. A smaller launch can be valuable if it attracts well-matched users who continue using the product.

Public launch updates are most useful when they explain what happened after the announcement, including onboarding problems, unexpected use cases, and subsequent improvements.

Signal to move forward: The launch produces enough relevant usage and feedback to support focused iteration.

Common mistake: Treating rankings, votes, or traffic as substitutes for users receiving value.

Stage 5: Traction and Retention

Traction means there is evidence of demand. Retention shows whether that demand continues after initial curiosity fades.

At this stage, a founder’s attention shifts from getting people through the door to understanding why they stay, leave, or recommend the product.

Choose metrics that match the product

Useful measures may include:

Activation rate
Repeat use at the product’s natural frequency
Retention by signup cohort
Trial-to-paid conversion, when applicable
Subscription cancellations and renewals
Support needs and recurring friction
Referrals from existing users

A daily-use tool and an occasional-use utility should not be judged by the same usage schedule. Retention needs to reflect the problem’s actual rhythm.

Use public feedback without surrendering direction

A public backlog and feature voting can help reveal what followers and users want. However, votes are inputs, not automatic instructions.

A frequently requested feature may come from people outside the target audience. A less popular improvement may remove a serious obstacle for active customers.

A solo founder can weigh requests against:

Relevance to the core user
Impact on activation or retention
Development and support cost
Strategic fit
Evidence behind the request

Signal to move forward: A defined audience repeatedly receives value, and some acquisition or referral activity can be reproduced.

Common mistake: Attracting more users before understanding why existing users leave.

Stage 6: Sustainable Growth

For a solo founder, growth should improve the business without making it impossible to operate.

That may mean increasing revenue, reducing churn, improving margins, or serving the same customers with less manual work. Hiring a team or pursuing rapid expansion is not a requirement.

Examine the whole operating model

Growth decisions should account for:

Acquisition effort and cost
Revenue quality and customer concentration
Hosting and service costs
Support workload
Reliability and maintenance
Founder capacity
Dependence on a single platform or channel

A product can grow in signups while becoming less sustainable. For example, support demands may rise faster than the founder’s ability to handle them.

Public updates can explain strategic choices, such as improving onboarding instead of adding features or strengthening reliability before another promotion.

Signal of a healthier business: The product has repeatable demand, manageable obligations, and enough operating capacity to serve users consistently.

Common mistake: Assuming every successful small product must become a large company.

Stage 7: Shutdown, Maintenance, or a New Direction

Not every product should keep growing. A founder may choose maintenance mode, a sale, a major change in direction, or a shutdown.

These are legitimate outcomes, not stages that must be hidden from a maker’s history.

When reassessment becomes necessary

Reasons to reconsider a product include:

Weak demand despite several well-designed tests
Persistent retention problems
Costs or support needs that outweigh its value
A mismatch with the founder’s goals
A stronger opportunity elsewhere

No single metric settles every decision. The founder needs to consider both customer obligations and the opportunity cost of continuing.

Close products responsibly

A shutdown plan should address notice, billing changes, data exports, access deadlines, and data handling. Applicable contractual and legal obligations still matter.

An honest public retrospective can document:

What the product attempted to solve
What was launched
What evidence influenced the decision
What customers need to do
What the founder learned

A project graveyard gives those lessons a lasting place instead of allowing unsuccessful launches to disappear from the record.

How to Identify the Current Startup Stage

The most useful stage is the one that describes the product’s biggest unresolved question.

Unclear problem: return to discovery.
Interest without commitment: focus on validation.
Commitment without a usable solution: build the MVP.
A working product with little exposure: prepare a focused launch.
Signups without repeat value: investigate activation and retention.
Repeat demand with operational strain: improve sustainability.
Persistent weak evidence or poor fit: reassess continued investment.

A founder with several products may occupy several startup stages at once. One product might be growing, another validating demand, and a third closing down.

The goal is not to progress through labels as quickly as possible. It is to make the next decision with better evidence.

Make Every Startup Stage Part of the Maker Story

A founder’s public record can show more than launch announcements. Weekly progress, product decisions, follower feedback, and honest shutdowns all help explain how the work develops.

25launches gives indie hackers and solo founders one free public page for every product they have launched, their progress this week, a backlog followers can vote on, and a graveyard of shut-down projects.

Founders can use 25launches to give every startup stage a place in their maker story.