The Spec That Saved Our Series A

“Come back when you have a plan”

The meeting was going well. Two cofounders, a lead investor, and a partner at a mid-tier VC in London. The product demo was solid. Metrics were good: 400 paying customers, 15% month-over-month growth, low churn. The team was strong.

Then the investor asked the question: “Walk me through your product roadmap for the next 12 months.”

The CEO started talking. He mentioned a few features. Enterprise tier. API. Some kind of marketplace. The CTO added context, but contradicted the CEO on timing. They went back and forth for a minute, clearly thinking out loud rather than presenting a plan.

The investor nodded politely and said: “Sounds like you have a lot of ideas. Why don’t you come back when you can show me the plan in writing?”

The meeting ended. The deal didn’t.

What they had wrong

This team wasn’t incompetent. They were busy. They’d spent the last year building a product, acquiring customers, and keeping the servers running. Documentation felt like a luxury they’d get to “someday.”

The problem wasn’t that they didn’t have a strategy. They did, roughly. The CEO thought about it constantly. The CTO had a mental model of the technical evolution. But none of it was written down, organized, or stress-tested against reality.

In a pitch meeting, that gap is fatal. Investors aren’t just evaluating your product. They’re evaluating your ability to think clearly and execute deliberately. If you can’t articulate your plan, they’ll assume you don’t have one.

The week that changed everything

After the meeting, the cofounders blocked out a full week. No customer calls, no feature work. Just planning and writing.

Here’s what they produced.

The product roadmap

Not a feature list. A structured document with three time horizons:

Q1 (immediate): Ship self-serve onboarding and usage-based billing. Goal: reduce sales-assisted signups from 80% to 40%.

Q2 to Q3 (medium-term): Launch API and integration marketplace. Goal: increase average contract value by 30% through platform stickiness.

Q4 (end of year): Enterprise tier with SSO, audit logs, and dedicated support. Goal: land 10 enterprise accounts at 5x the standard price.

Each initiative had a clear rationale tied to a business outcome. Not “we think an API would be cool” but “our top 20 accounts have asked for API access, and 3 have said it’s a blocker for expanding their usage.”

Dependencies and risks

They mapped out what each initiative required. The API needed a dedicated backend developer they hadn’t hired yet. Enterprise features required SOC 2 compliance, which would take 3 to 4 months. They were honest about what they didn’t know: whether the marketplace would gain traction was an open question.

This section impressed the investor more than anything else. It showed they understood the difference between a plan and a wish list.

Success metrics

For each quarter, they defined how they’d measure progress. Not vanity metrics. Specific, falsifiable targets.

• Q1: Self-serve signups reach 60% of total. Activation rate above 40%.
• Q2 to Q3: 15 active API integrations. ACV increases to £X.
• Q4: 5 enterprise contracts signed. Net revenue retention above 120%.

These numbers gave the investor something to check in on. They also gave the cofounders something to hold themselves accountable to.

The second meeting

They went back to the same investor two weeks later with the document. Printed copies, because some investors still prefer paper.

The conversation was completely different. Instead of “tell me about your roadmap,” the investor said “I see you’re planning to launch the API in Q2. What’s your go-to-market for the marketplace?”

They’d moved from defending the existence of a plan to discussing the details of the plan. That’s a fundamentally different conversation. It’s the one investors want to have.

They closed the round six weeks later. The same investor led it.

Why this matters beyond fundraising

The cofounders told me something interesting afterward. Writing the spec didn’t just help with the raise. It changed how they made decisions day-to-day.

Before, every new idea got debated in isolation. “Should we build X?” “I don’t know, maybe?” Now they had a framework: does this move us toward Q1 targets? If not, it goes on the backlog.

The engineering team noticed too. For the first time, they understood why they were building certain things and could push back when requests didn’t align with the roadmap.

One document changed the operating rhythm of the entire company.

The lesson

Documentation isn’t busywork. When you’re raising money, it’s proof that you know what you’re doing. When you’re not raising money, it’s how you make better decisions.

You don’t need a 50-page strategy doc. You need a clear, structured roadmap that answers: what are we building, why, in what order, and how will we know it’s working?

If that document doesn’t exist for your company, write it this week. You’ll be surprised how much clarity comes from the act of writing it down.

And if an investor ever tells you to “come back with a plan,” know that it’s not a rejection. It’s an invitation. Take it seriously, put in the work, and go back with something worth reading.