Evidence beats assertion. At every stage, the question is: what proof do you have?
Every investor and accelerator conversation is stage-gated. The questions an investor asks — and whether they take you seriously — are directly determined by the traction stage your venture is at. A founder at Stage 0 (concept only) who presents with the confidence of a Stage 4 founder (paying pilots, LOIs in hand) does not get a better meeting. They get a worse one, because the disconnect between claim and evidence damages credibility faster than any individual answer can repair it.
This is why being honest about your current stage — and ruthlessly focused on the evidence required to move to the next stage — is more valuable than overstating progress. Accelerators like KEPSA Jiinue explicitly assess stage readiness as part of their selection process. They are not looking for finished businesses — many of their cohort companies are pre-revenue. They are looking for founders who understand where they are and have a credible plan to advance.
The Product and Traction dimension carries 15% of the VRS because it captures something that no other dimension can: whether you have tested your venture against reality. A great team with a clear problem and sound economics is still a hypothesis. The moment you have real users — non-friends, non-family, people with no obligation to be kind — testing your product and reporting their experience, you have evidence. The moment one of those users pays you money, you have proof. Every stage above Stage 3 represents a qualitatively different level of de-risking.
"If you're not embarrassed by the first version of your product, you've launched too late."
— Reid Hoffman, Co-founder, LinkedIn
"If you are not embarrassed by the first version of your product, you've launched too late."
— Reid Hoffman, Co-founder, LinkedIn
The Milestone Ladder has 6 stages. Each stage requires specific evidence before you can claim to occupy it. You cannot skip stages — you can move through them quickly, but claiming Stage 4 without the evidence for Stage 3 is a position that will not survive the first question in an investor conversation.
The Ladder also tells you what to do next. Each stage has a clear "next step" — the single action most likely to advance you to the stage above. Focus all effort on that action until you have the evidence for the next stage.
What it looks like: You have identified a problem you want to solve and have begun thinking about a solution. You may have initial research, a slide deck, or a written description.
Next step: Conduct customer interviews to validate that the problem is real, frequent, and costly (see Module 2).
What it looks like: You have spoken to real potential customers using a structured interview process. You can state the problem at Level 3 precision (see Module 2). You have a document or spreadsheet recording the interviews.
Next step: Design and build a prototype or MVP that addresses the specific pain identified in interviews.
What it looks like: You have built something — a prototype, a no-code MVP, a service delivered manually — and tested it with people who are genuine representatives of your target customer. You have their feedback in writing or recorded. At least some feedback is critical (positive-only feedback from obliging testers is not real validation).
Next step: Build an MVP with enough functionality to support a structured beta programme with 5–10 real users.
What it looks like: Real users are using the product independently (not being walked through it). You have usage data — logins, feature usage, time-on-platform. You have structured feedback from a beta cohort of at least 5 real users. You know your top 3 product friction points.
Next step: Convert 2–3 of your strongest beta users to a paid pilot or signed Letter of Intent (LOI).
What it looks like: Real organisations or individuals are paying you money (or have committed to pay via LOI) for your product. You can name them, describe their use case, and report on their early results. You know whether they are getting value from the product.
Next step: Retain your pilot customers through their first renewal or commitment period. Document the results they have achieved. Use their outcomes as case studies for subsequent sales conversations.
What it looks like: You have a customer base that is growing and renewing. You have MRR that is predictable. You have case studies showing specific outcomes. Churn is below 5% monthly. You have a repeatable sales process.
Next step: Systematise acquisition, document the sales process, and begin building the operational infrastructure to support growth.
Most early-stage accelerators (including KEPSA Jiinue) require a minimum of Stage 3 (MVP built and tested with real users) for application consideration, and strongly prefer Stage 4 (pilot customers). Stage 5 ventures typically qualify for later-stage programmes. Knowing your stage allows you to target the right opportunities — and to work urgently on the specific evidence gap preventing you from applying to the right programme.
The Traction Evidence Card forces you to document what evidence you actually have for your current stage — not what you believe to be true, but what you can show to an investor or programme manager if they ask. Complete columns 3 and 4 for every stage, not just the one you think you are at. The gaps in earlier stages are as important as progress in later ones.
| Stage | Evidence required | Your current evidence | Gap |
|---|---|---|---|
| Stage 0 Concept |
Idea documented, founding team in place | [What do you have?] | [What is missing?] |
| Stage 1 Problem Validated |
10+ customer interviews, Level 3 problem statement with quantified cost | [Interviews done? Notes available?] | [# of interviews remaining] |
| Stage 2 Solution Validated |
Prototype or MVP tested with 5+ real non-friend users, written feedback documented | [Who tested it? What did they say?] | [What feedback is missing?] |
| Stage 3 MVP Built |
Functional product used independently by real users, usage data available | [Users, usage stats, feedback recorded?] | [What usage data is missing?] |
| Stage 4 Pilot Customers |
2+ paying customers or signed LOIs, named, with documented use case | [Customer names, amounts, dates?] | [How many pilots needed?] |
| Stage 5 Live Customers |
Multiple paying customers, renewal data, documented outcomes, MRR trend | [MRR, churn rate, outcomes?] | [What data does not yet exist?] |
Your current confirmed stage is the highest stage where you can answer all "evidence required" criteria with specific, documentable facts. Aspirational stages do not count.
The transition from Stage 3 to Stage 4 is the most consequential step in early-stage validation — and the one most founders delay too long. The typical reason for delay is fear of asking for money from someone who has been using the product for free. But the ask is what generates the real signal: a user who has been receiving value and will not pay for it is not a customer, they are a user. A user who pays is evidence that the value proposition is real.
The most effective conversion approach: schedule a specific conversation (call it a "review" or "check-in", not a "sales call"), lead with the outcomes they have achieved while using the product, then present the paid tier as the next step in a relationship that is already working. Make the offer specific: a named price, a defined term, a clear start date. Ambiguity in the offer produces ambiguity in the response.
As you build traction, the biggest risk is that your delivery process doesn't scale — you add customers but also add proportional time and cost. Value Stream Mapping your delivery workflow now, before scaling, prevents this. Every step that a customer does not pay for is a cost that erodes your gross margin as you grow.
AI & No-Code Tip: Use no-code tools (Bubble, Glide, Notion) to automate the non-value-adding steps in your delivery process. Use Zapier or Make to connect your tools without engineering cost. The goal: reduce the founder-hours required per customer by 50% before your next funding conversation.
WhatsApp launched with one feature: reliable cross-platform messaging with no ads. Rather than building more features, the founding team obsessively optimised delivery speed and reliability — the core job-to-be-done. They tracked one metric: messages sent and delivered. By the time Facebook acquired them for $19 billion, they had 450 million users and a team of 55.
The lesson: Traction is not about features — it is about relentlessly improving the one thing your early users actually need.
After completing Module 3, Amara reviews her Traction Evidence Card honestly. Her Stage 2 evidence is weak: she and Kofi tested the TrackFlow prototype with 4 people — 2 former DHL colleagues (friends) and 2 family members of Kofi's. This is not Stage 2 validation. It is testing within a social network that has no incentive to be critical.
Her KEPSA Jiinue Growth Programme application is due in 10 weeks. The programme's selection criteria require a minimum of Stage 3 (real users, non-friends). KEPSA strongly prefers Stage 4 (paying or LOI). Amara is functionally at Stage 1 (problem validated from Module 2 interviews, but no real-user product testing).
She and Kofi design a 5-person structured beta programme. They recruit participants from Amara's DHL operations network — 5 e-commerce SMEs who met the criteria in the Module 2 customer interviews and scored 8+ on the urgency scale. All 5 agree to a 4-week free beta in exchange for structured weekly feedback calls.
In Week 4 of the beta, Amara reviews feedback: 3 of the 5 businesses report that TrackFlow has reduced their manual tracking time by an average of 11 hours per week. Two report that they have been able to resolve customer delivery disputes faster. No major product failures. Kofi fixes 3 friction points identified in beta feedback sessions.
In Week 5, Amara runs conversion conversations with all 5 beta users. She leads each conversation with the outcome data ("you've saved approximately 11 hours of staff time over the last 4 weeks — that's about £180 at your team's hourly cost"). She offers a 6-month pilot at £200/month. Three of the five sign within 7 days. Two decline (both citing cash flow timing, not value). TrackFlow reaches Stage 4 with 3 paying pilots: £600 MRR.
VRS Dimension 4 score moves from 35 to 70. KEPSA grants TrackFlow an interview slot. The application is noted for: documented beta programme with non-friend participants, usage data from 5 businesses, and 3 named paying pilots with specific outcomes. Amara reports this in 3 sentences on the application form. It is more compelling than most 10-page applications.
Complete the Traction Evidence Card. For each stage, write down specifically what you have — not what you are planning to get. Be strict: evidence means documented, shareable facts. If you could not attach a file or send a link to support the claim, it does not count as evidence yet. Your confirmed stage is the honest foundation for everything else in this action plan.
Look at the stage above your confirmed stage. What evidence is required? Who are the specific people you need to engage to generate that evidence — named potential beta users, named potential pilot customers? Write their names and a specific outreach plan. The 30-day deadline is not aspirational — it is the constraint that forces action. Stage advancement does not happen without a deadline.
Identify the 2 users or prospects in your current network who have the strongest signals of intent — they have engaged with the product, given positive feedback, and asked questions about pricing or next steps. Schedule specific conversations (not emails — calls or in-person meetings) and make a specific offer: a named price, a defined term, a clear start date. The goal is a signature or a payment before your next investor or accelerator conversation.
Now that you understand this dimension, see how your venture actually scores. The free Venture Readiness Assessment takes 15 minutes and gives you a score across all 8 dimensions.
Take the Free Assessment →