The Investor Who Stopped Funding Headcount - And Started Funding Delivery Systems

I approved the headcount increase on a Tuesday. Twelve engineers. $2.4 million annual burn. The CEO was confident: 'We just need more hands.'

Fourteen months later, the team was 40% bigger and shipping 10% less.

This wasn't an anomaly. Across my portfolio of eleven companies, I was watching the same pattern repeat with eerie consistency: more people, more money, same output. Sometimes less.

The portfolio pattern I couldn't explain

I ran the numbers across all eleven companies. What I found was disturbing:

• Companies that grew engineering from 10 to 30 people saw output increase by maybe 50%, not 200%.
• The fastest-shipping company in my portfolio had 14 engineers. The slowest had 45.
• Every company that missed product milestones blamed the same thing: 'We need more senior people.'
• Every company that hired more senior people still missed the next set of milestones.

I kept approving the same solution to the same problem, getting the same result, and calling it 'execution risk.'

The due diligence question I never asked

My due diligence process for engineering was: How many engineers do you have? What's your tech stack? How fast is your deployment cycle? Do you have CI/CD?

Surface-level questions that every company could answer positively regardless of whether their delivery system actually worked.

I never asked the question that actually matters:

Show me how a feature goes from idea to production. Not the diagram. The actual trail. Show me the decisions, the constraints, the approvals, and the evidence that what shipped is what was intended.

I never asked because I didn't know that question existed. I'd spent my career treating engineering as a black box you fuel with capital and hope it produces output.

The company that broke the pattern

Company number twelve was different. Not because the founders were smarter - they were. But specifically because of something the CTO said during our first meeting:

We don't need more engineers. We need a better delivery system. If you fund headcount, we'll grow linearly. If you fund the system, we'll grow exponentially.

I almost passed. It sounded like a CTO trying to avoid scaling the team. But something made me dig deeper.

She showed me their delivery system. Not a slide deck. The actual system.

• Every architecture decision had a record: what was decided, why, what alternatives were considered, what constraints applied.
• Every deployment had a governance trail: what changed, what tests passed, what approvals were given.
• Every priority shift had a decision record: what moved, what it displaced, who approved the change.
• Any person - engineer, PM, or board member - could trace any feature from intent to production.

What I learned about delivery economics

After investing in company twelve, I went back and audited my portfolio through a new lens. The results were painful but clarifying:

1) The coordination tax is the real burn rate

At 10 engineers, the coordination tax was manageable. At 30, it consumed more capacity than the new hires added. I was literally funding negative marginal returns.

2) Ungoverned speed is a liability, not an asset

Three of my portfolio companies had enterprise deals stall because they couldn't demonstrate auditability. I'd optimized for shipping speed. The market was demanding shipping credibility.

3) Delivery predictability is a valuation driver

The companies with predictable delivery - the ones where the board deck matched reality - commanded better terms, closed enterprise deals faster, and retained engineering talent longer. Predictability wasn't a process metric. It was a financial asset.

How I changed my playbook

I rewrote my due diligence framework. Three new non-negotiables:

• Show me the delivery trail. Not a dashboard. The actual path a feature takes from decision to production, with every constraint and approval visible.
• Show me how the system handles priority changes. Not 'we're agile.' Show me the decision record when something gets bumped.
• Show me what happens when someone leaves. Can a new engineer understand why the system was built this way without asking the person who built it?

Companies that can answer these questions get funded. Companies that can't get a recommendation to fix their delivery system before their next round.

Cards on the table

There wasn't a specific portfolio review. There wasn't one CTO who said the magic words. There wasn't a clean moment where venture math and delivery science clicked together.

But the pattern is real. Investors routinely fund headcount as the solution to delivery problems - and routinely watch that investment produce diminishing returns.