Updated recently
Last updated:
Quick Answer: from idea to revenue startup guide: The path is six stages, and each one has a gate you must pass before the next. Validate the problem with thirty to forty conversations about the past, not the future. Size the market from the bottom up, by counting buyers you can name. Build the minimum that produces the outcome, not a smaller version of the full product. Set the price on value before you need the money. Sell directly — the founder sells the first ten. Close the loop by making those ten successful. Most startups fail because a gate was skipped rather than because an idea was bad.
Key takeaways
- Each stage has a gate, and the gate is objective. A stage ends when a number is hit, not when the work feels finished.
- Validation is about the past. Ask what people currently do and what it costs them; nobody can predict their own future behaviour accurately.
- Size the market bottom-up. Multiply the number of buyers you can name by what they would pay; the top-down number is a mood, not a plan.
- Build the minimum that produces the outcome. A working solution to one problem, delivered to one customer, beats a polished product for nobody.
- Price before you need revenue. A price set under pressure becomes the anchor, and escaping it takes years.
What this guide covers
- The six stages and the gate at each one
- How to run validation conversations that produce evidence
- Bottom-up market sizing with real numbers
- Building the minimum and setting the price
- The founder’s role in the first ten sales
- What to do once revenue starts, and what not to do
The gates
The reason startups fail is rarely a bad idea. It is that a stage got skipped, or passed without its gate being met, and the problem was discovered several stages later when it was expensive.
Each stage below has a gate — a specific, checkable condition. If the gate is not met, the correct action is to go back, not to push forward and hope. Most founders’ instinct is the opposite, because forward motion feels like progress and going back feels like failure.
Stage 1: validate the problem (gate: 10 unprompted buying signals)
The work. Thirty to forty conversations with people who have the problem. Ask about the past and the present: walk me through the last time this happened, what do you do about it now, what does that cost, what have you tried before and why did you stop.
Why it matters. The purpose is not to get agreement. It is to learn the buyer’s vocabulary, their actual priority, what they currently pay for the workaround, and who decides. People are poor at predicting their own future behaviour and generous with hypothetical yeses.
The gate. Ten “unprompted buying signals” — and the word unprompted is the whole test. Someone says “how much does it cost?” without being led. Someone asks when it will be available. Someone describes the workaround in detail and asks whether you would do it properly. Someone asks if you work with their size of organisation. Someone introduces you to a colleague.
Ten of those, across at least three different buyer types, and the problem is real. If you get five polite maybes and no unprompted signals, the problem is not validated, whatever the conversations felt like.
The trap. Counting “I would use that” as a signal. It is not. It is the politest possible sentence, and it carries no information about willingness to pay.
Stage 2: size the market (gate: a bottom-up number you can defend)
The work. Ignore the reports that say your market is worth a certain number. Instead count: how many buyers fit your definition, in your geography, of your size, that you can name or list? Multiply by what each would pay per year.
Why it matters. Top-down sizing multiplies two guesses — a total market estimate and your assumed share — and the result is unfalsifiable. Bottom-up sizing produces a number you can argue with, and it is usually much smaller than the top-down figure, which is information rather than discouragement: a small enough market means you can dominate it, and a market of 400 serious buyers is a real business.
The gate. You can state the number, show the arithmetic, and name a way of reaching the first 100 of them. If you cannot name how you would find them, the market size is decorative.
The useful secondary question. Is this market growing? A small growing market is usually a better target than a large static one, because the growth creates awareness work for you rather than only for your competitors.
Stage 3: build the minimum (gate: one customer gets the outcome)
The work. Build the smallest thing that produces the outcome for one customer. Not a smaller version of the full product — the minimum that delivers the result, with everything else removed.
Why it matters. The distinction matters more than it sounds. A smaller version of the full product still contains all the complexity, all the assumptions and all the work that turns out to be unnecessary once the first customer uses it. The minimum forces you to find the shortest path to the outcome, which is often where the real product insight is.
The gate. One real customer has used it and got the outcome they came for. Not signed up, not trialled — used it and got the result. This gate is where most startups are skipping ahead, and it is why they end up with software nobody uses.
The discipline. Do not add a feature because a prospective customer mentioned it in a conversation. That is a list of hypotheticals, and each addition costs weeks. Take payment for the next thing instead — a paying customer tells you what to build, and a free request does not.
Stage 4: set the price (gate: a price you can say without flinching)
The work. Calculate the real cost of delivering, add the margin you need, and quote it. Attach it to the outcome and the cost of the problem rather than presenting it bare.
Why it matters. The first price becomes the anchor for every later negotiation, and the team believes it thereafter. A price set to win the first customer — discounted, or set low out of nervousness — permanently lowers the business. Raising it back requires a multi-year programme of segmentation and renewal-time increases.
The gate. You can say the number to a stranger without apologising, and you know your delivery cost well enough to know the margin at three times volume.
The practical test. Ask three early customers what they would pay and why. If the answers cluster far below your cost-plus number, either the pricing is wrong or the positioning is wrong — and both are cheaper to fix now than later. The framing that works without discounting is covered in winning more customers without lowering prices.
Stage 5: sell directly (gate: ten paying customers)
The work. The founder sells the first ten. Not a sales team, not a marketing campaign — the founder, personally, to people they have spoken to.
Why it matters. Ten direct sales teach you the entire business: what buyers actually ask, what language they use, which objections are real, what they will pay, and how long the cycle is. It also builds a set of relationships that will carry the first reference, the first referral and the first hard-won insight about the product.
The gate. Ten customers who have paid. Not trials, not waitlist signups, not “interested when we launch”. Payments, from ten real organisations.
The founder’s advantage. At this stage you are better than any salesperson you could hire, because you can ask naive questions and you understand the product completely. The first ten customers are also the best source of the specification, because they will tell you what they will actually accept by accepting it.
The trap. Scaling acquisition before this gate. Ten thousand visitors and zero payments produce learning about marketing, which is usually the wrong lever at this stage.
Stage 6: close the loop (gate: the first ten are successful and referring)
The work. Make the first ten customers genuinely successful. Onboard them properly, deliver the outcome, and ask for introductions when the result lands.
Why it matters. This is the stage most startups skip, because the revenue has arrived and it feels like the job is done. In fact it is the beginning. Ten satisfied customers produce references, a true specification, a real conversion rate, a real churn rate and a real acquisition cost — and every one of those numbers changes what you should do next.
The gate. The first ten have renewed or expanded, at least a few have introduced others, and you can state your actual conversion rate, actual churn and actual acquisition cost rather than estimates.
What comes next. Now, and only now, the growth questions become answerable: what channel brought these customers, what does it cost, and what happens when you double it. Until you have real numbers from real customers, any growth plan is a hypothesis about a business that does not exist yet.
What to avoid in the middle
Do not add features because a prospective customer asked. Collect the requests, and count how often each appears. Build the one that appears in a third of conversations. The rest are individual preferences.
Do not hire a sales team before you have sold ten yourself. You do not yet know what works, and a team will scale the wrong thing efficiently.
Do not build a brand before you have a product people use. Marketing amplifies what exists; it does not create it.
Do not take the feedback of your friends. People are loyal to people, and a friend saying yes tells you about the friendship.
Do not let the idea get more polished than the evidence. A deck that grows while the customer count stays at zero is a comfortable way to avoid the hard part. The failure patterns are described in why most startups fail, and the founder-level advice is in what every first-time founder should know.
Related reading
- What Every First-Time Founder Should Know
- Why Most Startups Fail and How to Avoid It
- How to Win More Customers Without Lowering Prices
Frequently asked questions
How long does it take to go from idea to first revenue?
For a business serving an existing market, three to six months is typical, and most of that is spent in stage one rather than stage three. The variable is not the build — it is how long it takes to find ten people with an urgent enough problem and a budget. Businesses entering genuinely new markets take longer because they have to educate buyers, which is why the pre-sale test in stage one is so valuable: it compresses the discovery period dramatically.
What is the fastest way to validate a startup idea?
Conversations about the past rather than the future, and a pre-sale. Ask thirty to forty people who have the problem what they currently do, what it costs and what they have already tried. Then attempt to take money — for something you have not built. Payment is the only unambiguous signal, and a pre-sale also often reveals the specification you need, because a customer who has committed has told you what they will actually accept.
How do I price a new product when I have no customers yet?
Calculate the real cost of delivering — including the founder’s time at a market rate, support and rework — then add the margin you need and quote it with the value framing attached. The trap is discounting to win the first customer: that price becomes the anchor for every later negotiation and takes years to reverse. So test the price early. Ask three early customers what they would pay and why; if the answers sit far below your number, the pricing or the positioning is wrong, and both are cheaper to fix now.
Should I build the full product before launching?
No. Build the smallest thing that produces the outcome for one customer, and get one real customer to use it and get the result they came for. A smaller version of the full product still contains all the complexity and all the assumptions that turn out to be unnecessary once someone uses it. The minimum forces the shortest path to the outcome, which is usually where the real product insight is. Add features only when a paying customer asks for them — a free request is a hypothesis, and a payment is evidence.
How many customers do I need before hiring or scaling marketing?
Ten paying customers who are successful, ideally including a few who have introduced others. At that point you have a true conversion rate, a real churn figure, a real acquisition cost and a set of references — numbers rather than estimates. Before that, marketing spend produces learning about marketing, which is usually the wrong lever, and a sales team scales a motion that has not been proven. The build phase is covered in what every first-time founder should know.
What should a founder do while waiting for revenue?
Run the loop that produces revenue, not one that produces comfort: keep talking to buyers, improve the thing that is closest to being usable, and get the first paying customer rather than the first hundred visitors. Track the activity number that should move before revenue does — conversations held, trials started, proposals sent — because slow revenue and absent revenue look identical without it. And keep the cash buffer intact, since the most common cause of failure here is not the product but a set of individually reasonable commitments that outran the money.
