The bus factor is a software engineering risk metric: the number of people who need to be hit by a bus before a project collapses. Lower is worse. A bus factor of one means one person's absence breaks everything.
Non-technical solopreneurs have a version of this problem, but instead of a single developer holding all the knowledge, it's their own time and attention that everything depends on.
The typical solo business tech stack:
CRM (half-configured, data quality questionable)
↓ manual export every week
Email platform (doesn't sync with CRM)
↓ Zapier automation (currently broken)
Website (pricing updated 3 months ago, website still shows old pricing)
↓ no monitoring
Client onboarding (Google Doc + Notion + email thread + memory)
Every connection in this chain is manual or fragile. Every failure requires the founder's personal intervention. There's no documentation, no redundancy, and no one else who understands how it all fits together.
This isn't bad luck. It's the predictable result of building a business tech stack without architectural planning, the same way we'd predict problems in a codebase with no documentation, no tests, and tight coupling everywhere.
The solution isn't more tools. It's the same thing that fixes bad codebases: strategic design, simplification, proper documentation, and someone who can see the full picture.
Full breakdown of what that looks like for non-technical solo businesses: → https://foundersbar.com/articles-and-research/how-tech-overwhelm-hurts-solopreneurs (foundersbar.com)
Top comments (0)