Support Debt: The Hidden Tax on Solo Founders
Type: media · article
Stage: Stage 7: Support Proof
Difficulty: advanced
Support debt is what happens when every new customer increases the founder's workload. Track: support hours per active customer, per new customer, repeated-question percentage, first-response time, time to resolution, self-service rate. If support time rises linearly with customer count, growth will eventually break the founder. Set a support budget: at 100 customers, support must stay below 5 founder-hours per week.
Overview
Support debt is what happens when every new customer increases the founder's workload. At first, this looks harmless. Ten customers create a few messages. Twenty customers create a few more. Then the founder crosses a threshold where support becomes the default workday. That is the Stage 7 failure mode.
What support debt looks like
The founder answers the same questions repeatedly. Customers need hand-holding to activate. Bugs require manual fixes. Billing issues are handled one by one. Feature requests arrive through scattered channels. The founder cannot build because the product keeps asking to be explained.
If a micro-SaaS requires constant hand-holding, it has not yet been validated as scalable software.
The support debt calculation
Track founder support time for one week. Then calculate:
- Support hours per active customer
- Support hours per new customer
- Repeated-question percentage
- First-response time
- Time to resolution
- Self-service resolution rate
If support time rises linearly with every new customer, growth will eventually break the founder.
The advanced action
Set a support budget. For example: "At 100 customers, support must stay below 5 founder-hours per week."
Then redesign onboarding, docs, automations, and product UX until the business fits inside that budget.
Stage 7 rule
A product is not operationally scalable until support time grows slower than customer count.