At Seed, validation doesn’t mean applause — it means behavior. Compliments are cheap. Clicks, logins, referrals, and repeat use are the proof that what you built is actually working.
This is where you stop guessing and start measuring real pull.
“If users aren’t coming back, you don’t have validation — you have polite rejection.”
Purpose
- Demonstrate traction through user actions, not opinions.
- Identify behavioral proof of value (activation, engagement, referrals).
- Tie product refinement to observed usage, not founder instinct.
- Signal early demand beyond your immediate network.
When to Complete
- After MVP is in users’ hands and producing measurable activity.
- Before asking investors to fund “early traction” or go-to-market.
- Once at least 10–20 users/customers show repeatable engagement.
Proof Sections
Engaged User Feedback
- Who’s using it — and how often?
- What actions confirm your intended value?
- B2B SaaS – “12 users activated MVP; 5 reached ‘Aha’; 3 invited teammates unprompted.”
- B2C CPG – “20 sample packs delivered; 30 inbound referrals within 2 weeks; re-order requests from early testers.”
- Services – “3 pilot clients onboarded; 2 added scope of work within first month.”
Data-Driven Insight
- What behaviors are you tracking?
- Where do users succeed or fail?
- Are you analyzing trends, not anecdotes?
- B2B SaaS – “50% completed onboarding; drop-off at step 3; fixed with in-app tooltips.”
- B2C CPG – “70% finished sample pack within 48 hours; 25% reordered in <2 weeks.”
- Services – “80% of tasks completed by deadline; client feedback loop showed confusion on reporting cadence.”
Refinement Loops
- How is feedback collected and reviewed?
- Are you iterating based on usage?
- Is the team aligned around fixing what matters most?
- B2B SaaS – “Weekly Notion triage; Jira tickets linked to behavior tags.”
- B2C CPG – “Survey after each pilot batch; product tweaks prioritized by repeat order rate.”
- Services – “Post-project client interviews feed directly into updated onboarding doc.”
Signals of Early Demand
- Are users asking to share, pay, or expand?
- Have you seen pull beyond your initial reach?
- B2B SaaS – “Beta user referred friend who signed up next day and asked about pricing.”
- B2C CPG – “Retailer inquired after seeing Instagram posts from early testers.”
- Services – “Pilot client introduced us to two partner orgs without being asked.”
Execution Requirements
- Live MVP in real users’ hands.
- Measured user activity beyond “vanity” sign-ups.
- Documented iteration loop (feedback → change → re-test).
- At least one external signal of pull (referrals, re-orders, expansion).
Domain Adaptability – Moderate
Universal Goal: Show that behavioral proof exists, not just verbal interest. Execution varies by domain.
Quick How-to by Domain:
- B2B SaaS / Software – Track activation → engagement → referral funnel; run weekly product/UX triage.
- B2C CPG – Deliver test batches; track reorder rate and organic referrals; capture demand from outside your direct outreach.
- Services / Ops-Heavy Models – Secure repeat work; track client scope expansions; measure referral introductions.
Expected Output
- Behavior-based user insights (activation, engagement, retention).
- Optional UX funnel chart, usage snapshot, or reorder data.
- Documented refinement process tied to actual user activity.
Linked Asset
View
Edit
Optional Enhancements (Pro-Level Execution)
- Cohort Analysis — Track retention curves across different user groups.
- Behavioral Triggers — Use in-app nudges, re-order prompts, or follow-ups triggered by user activity.
- Referral Mechanism — Build an easy, frictionless referral loop directly into MVP.
- Third-Party Validation — Early reviews, retailer inquiries, or analyst notes as external proof points.
- North Star Metric — Define and track a single metric that proves core value (e.g., active teams, reorder rate, repeat project scope).