Founder skill
Skill: doing customer support well
Customer support at indie SaaS scale is the founder's responsibility for a long time. Done well, it produces the highest-trust customers in the cohort; done badly, it burns out the founder and burns trust with customers. The skill is to set rules, communicate them clearly, and execute consistently.
Time to functional: 30-90 days from first paying customer to a sustainable support cadence. Faster for founders who set expectations up front; slower for founders trying to be 'always available'.
Verified · editorial policy
Why this skill matters
Founders who do support well in months 1-12 retain customers at 2-3x the rate of those who treat it as a chore. The support relationship is part of the product at indie scale; replacing it with automation too early is the most common premature-scale mistake.
What “good” looks like
Response within 24 hours during work days; clear off-hours expectations posted publicly; one escalation path for urgent issues; a public help center for self-serve; customer feels heard even when the answer is 'no'.
The practice plan
Step 1
Set explicit response-time expectations
Post your support hours on the website. 'Mon-Fri response within 24 hours' is honest and reasonable. Setting unreachable expectations (instant) produces resentment when you cannot meet them.
Cadence: One-time setup; revisit when load changes.
Step 2
Build a self-serve help center
Document the top 20 questions you get. Customers self-serve before they email you; founder time is preserved for the conversations that need it.
Cadence: Build initially in 1-2 weekends; expand monthly.
Step 3
Reply to every email yourself for the first 50 customers
Even when it takes longer. The patterns you absorb in customer #1-50 support shape the product. Outsourcing too early skips the lesson.
Cadence: Daily, during support hours.
Step 4
Build templates for the recurring 5-10 questions
Save and reuse responses to the questions you answer most. Template starting point + 30 seconds of personalization beats a fresh write every time.
Cadence: After every 10 support emails, evaluate which became repeats.
Step 5
Audit churned customers monthly
Read the support history of every customer who churned. The pattern of unanswered or poorly-handled questions is the easiest churn-fix you have.
Cadence: Monthly.
Failure modes when self-teaching
- Replying instantly to everything. Trains customers to expect 24/7 availability the founder cannot sustain.
- Defensive responses. Tone matters; even correct answers delivered defensively lose trust.
- Skipping the help center because 'I will just answer emails'. The help center is what makes the email volume sustainable.
- Outsourcing support before product-fit. Outsourced support cannot make the product decisions inbound questions reveal.
- Treating support as separate from product. Every support question is product feedback.
Related Brunson terms
Frequently asked
- When should I hire support help?
- When you cross 200-500 active customers AND support is genuinely the bottleneck on founder time. Earlier hiring is premature; the founder still needs the pattern-recognition from support volume.
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.