Founder skill
Skill: customer development
Customer development is the practice of having structured, regular conversations with real customers and prospects to learn what they actually need. It is the highest-leverage skill in pre-revenue indie SaaS and the one founders most often skip. The practice is simple in structure and hard in execution.
Time to functional: 30-90 days from start of practice to functional skill. 'Functional' means: founder can run a conversation without falling into pitch mode, takes structured notes, and identifies patterns. Mastery is 12-24 months of sustained practice.
Verified · editorial policy
Why this skill matters
Almost every Brunson Wrong Person diagnosis traces back to insufficient customer development. The founder is guessing what the customer wants instead of asking. Five hours per week of structured customer conversations produces more product-direction signal than 50 hours of building.
What “good” looks like
Five customer-development conversations per week, each 20-30 minutes, with named real prospects or customers. The founder takes structured notes, identifies patterns across conversations, and adjusts positioning or product based on what is consistently heard. The founder can name the top 3 themes from the last 30 conversations.
The practice plan
Step 1
Build the conversation list
List 30 named real people in your target audience — past customers, churned customers, signed-up-but-did-not-buy, dream-100 prospects. Tag each with status and last contact date.
Cadence: One-time setup; refresh monthly.
Step 2
Reach out for 30-minute conversations
Personal email or DM offering 20-30 minutes. No agenda template; just 'I am building X, I would value your perspective on it'. Aim for 5 conversations per week.
Cadence: 5 outreach asks per week, ongoing.
Step 3
Run the conversation with one structural rule
Talk less than 30% of the time. The prospect talks 70%+. Open-ended questions, no pitch, no demo unless asked. The single rule that distinguishes customer development from sales calls.
Cadence: Per conversation.
Step 4
Document the conversation immediately
Within 60 minutes after the call: write down 3 things the prospect said verbatim, 1 surprise, and what changed in your understanding. Store in a system you will re-read (Notion, Airtable, a doc).
Cadence: Per conversation, within 60 minutes.
Step 5
Weekly pattern review
Re-read the last 5 conversations. Note recurring themes, contradictions, and surprises. Decide one thing to change (positioning, product, target) based on the pattern, not a single conversation.
Cadence: Weekly, 30-60 minutes.
Failure modes when self-teaching
- Talking too much. The founder explains the product instead of letting the prospect describe their world.
- Treating conversations as demos in disguise. The prospect feels pitched and shuts down.
- Skipping documentation. Memory is unreliable; patterns require written record.
- Acting on single conversations. Customer development is pattern-based; one strong opinion is data, not direction.
- Stopping after the first 10 conversations because 'I have enough now'. Customer development is ongoing — the next 10 conversations have new patterns.
Related Brunson terms
Frequently asked
- How many conversations are 'enough' to make a product decision?
- At least 10 conversations from the same target cohort showing the same pattern, ideally across a 2-3 week window. Single conversations are anecdotes; consistent patterns across cohorts are signal.
- Should I record customer-development calls?
- Ask permission; some do, some don't. Real-time notes are usually more valuable than recordings because they force you to identify what mattered. Recordings without re-listening are not useful.
Other founder skills
Apply the skill to a live page
The free 90-second Launch Diagnostic labels which Brunson failure mode your page hits — and tells you which founder skill is most directly on the critical path.