Headcount alone did not tell me whether our team could sustain the business.
Editorial update, October 11, 2026: Repeated team-size taxonomies and career prescriptions were condensed around the original layoff and enterprise case. Original section links remain: The Historical Logic (That Made Perfect Sense); When Everything Changed; What AI Replaced (And What It Didn't); What AI Successfully Replaced; What AI Couldn't Replace; The Counterfactual Problem; The Questions I Can't Answer; The Modern Team Composition Challenge; Option 1: Stay Ultra-Lean + Advisory Network; Option 2: Strategic Selective Hiring; Option 3: Hybrid Model; What I Would Do Now; The Broader Implications; For Founders and Leaders; For Investors; For Employees; The Uncomfortable Questions; For Your Own Team; For Industry Leaders; The Lessons Learned; What the Layoff Taught Me; The Right Answer (For Now).
We got from 14 people down to 5 people in 2023. For the next two years, we basically have not hired.
One of the most painful moments in my career. Also one of the most instructive.
The reduction helped our costs, but I underestimated the perspectives we would lose. One enterprise-product decision made that cost clearer.
The Painful Personal Experience
The Context Leading Up
By late 2022, we had 14 people:
- 6 developers (full-stack, front-end, back-end specialists)
- 2 designers (product design, marketing design)
- 2 marketers (content, campaigns)
- 2 customer success (support, onboarding)
- 1 operations (HR, finance, coordination)
- 1 analyst (data, reporting)
The team felt right: Everyone had clear roles, good chemistry, meaningful contribution.
The problem: Revenue wasn't scaling with team size. Customer acquisition costs were high. Profit margins were thin.
The AI factor: Throughout 2022, AI tools kept getting better. ChatGPT launched. Code generation improved dramatically. Design automation advanced rapidly.
By Q4 2022, I started noticing: Tasks that required full-time people were increasingly handled by AI tools in minutes or hours, not days or weeks.
The Painful Decision
The moment of truth came in early 2023:
Editorial update, October 11, 2026: The 14-month runway, 15%/25% growth and 60–70% task estimates are figures from this account. Payroll, cash/burn definitions, task acceptance criteria and contemporaneous logs are unavailable here; the AI share is not a verified causal measurement. The listed original roles total fourteen, while the retained five explicitly include me; the payroll roster needed to reconcile that counting boundary is also unavailable. No new roster or figures have been invented.
- Runway was 14 months with current burn rate
- Revenue growth was 15% quarterly but expenses were growing 25%
- AI tools could handle 60-70% of what we were hiring people to do
The options:
- Raise more capital to extend runway (dilute equity for inefficient operations)
- Reduce headcount to sustainable levels and use AI for execution
- Continue burning cash and hope revenue would catch up
We chose option 2. Got from 14 people down to 5 people.
The Human Cost
This wasn't a "big tech layoff" with severance packages and outplacement services.
This was a small company where:
- We knew each other's families
- Had worked together for 2-3 years
- Shared meals, celebrated wins, struggled through problems together
- Everyone had joined believing in the long-term vision
The conversations were brutal:
- "We can't afford to keep the team at this size"
- "It's not about performance, it's about economic reality"
- "AI can handle most of what we need, but we can't afford both AI tools and full team"
One of the most painful moments in my career. These weren't numbers on a spreadsheet. They were people whose careers and livelihoods I was affecting.
The guilt was overwhelming: Did I hire too fast? Should I have seen this coming? Was I a bad leader for not figuring out sustainable growth?
The Immediate Aftermath
What we kept (5 people):
- 2 developers (senior full-stack developers who could direct AI tools)
- 1 designer (senior product designer with strategic thinking)
- 1 customer success (who understood our customers deeply)
- 1 founder (me, handling strategy, sales, operations)
The work we moved toward AI and automation:
- Marketing content creation (ChatGPT, Claude, specialized tools)
- Customer support (AI chatbot handling 80% of inquiries)
- Data analysis and reporting (automated dashboards, AI insights)
- Routine development tasks (AI code generation, testing, documentation)
- Design asset creation (AI design tools for marketing materials)
The financial figures I reported after the reduction:
Editorial update, October 11, 2026: The reported monthly expenses fall from $180K to $65K, a $115K or about 64% reduction. That does not by itself verify a 36+ month runway or 68% profit margin: those require cash, net-burn, revenue and margin-period records, which are unavailable here. The reported 80% support figure is likewise an unverified reported estimate, with no ticket denominator or acceptance/review log supplied.
- Monthly expenses: $180K → $65K
- Runway extension: 14 months → 36+ months
- Profit margins: 15% → 68%
The operational impact was mixed:
- Faster decisions: 5 people align quicker than 14
- Less coordination overhead: Fewer meetings, simpler processes
- Higher individual responsibility: Each person's impact more visible
- AI amplification: Small team achieving output of much larger team
The Echo Chamber Risk
The enterprise-product decision is the case I keep returning to.
Real example from our experience:
Product direction decision (5-person team): We decided to focus on enterprise features because the data suggested enterprise customers had higher lifetime value.
What we considered:
- Customer analytics showing enterprise usage patterns
- Revenue per customer analysis
- Market research on enterprise vs. SMB segments
What we missed:
- SMB customers were easier to acquire and scale
- Enterprise sales cycles were much longer than we anticipated
- Product complexity increased dramatically for enterprise features
- SMB market was larger and growing faster
A larger team might have included:
- Someone who worked at a company that tried enterprise pivot and failed
- Someone with SMB market experience who could have provided alternative perspective
- Someone with enterprise sales experience who understood the real timeline and costs
Result: We spent 8 months building enterprise features before realizing SMB focus would have been better strategy.
Editorial update, October 11, 2026: This preserves the author’s reported eight-month enterprise detour. A dated roadmap, customer research and outcome comparison are unavailable here; it is not evidence that every enterprise pivot or five-person team fails.
The lesson: AI helped us carry out the enterprise decision. It did not remove my responsibility to test the strategy or seek perspectives we were missing.
What I Would Do Differently
The Decision I Got Right
Reducing headcount to sustainable levels: At the time, reducing costs looked necessary to sustain the company. That does not establish that the exact reduction to five was the only workable choice.
Using AI for execution: We used AI and automation for routine execution. The account here does not isolate their productivity gains from the other changes.
Maintaining quality standards: I believed we were maintaining product quality with the smaller team. The customer-satisfaction measurements needed to verify improvement are unavailable here.
The Decision I Got Wrong
Not replacing strategic thinking capacity: I optimized for execution efficiency and cost savings without considering strategic thinking diversity.
Focusing only on measurable benefits: Cost reduction and productivity gains are easy to measure. Strategic insights and creative breakthrough potential are harder to quantify but may be more valuable.
Underestimating compound effects: Small team with limited perspectives makes incremental improvements efficiently but may miss major pivots or innovations.
The key insight: My lesson was to use AI while making room for people who could challenge our assumptions. The enterprise case made that trade-off concrete for me.
The goal: I still want the efficiency of a small team without treating missing perspectives as a free saving.
The reality: I do not know what the larger team would have built or whether a different reduction would have worked better.
But the 14 → 5 layoff taught me this: The immediate savings mattered; the perspectives we lost mattered too.
Now I ask whose perspective a decision is missing, as well as what it costs.