Expansion · From experience
Demand you can't see
Demand was growing, but invisible from the outside, and the core ICP couldn't reach the goal alone.
Module 04 of 5 · GTM engineering · What the plan runs on
The stack keeps growing, but the data doesn't connect and too much still runs on manual work.
What changed in the GTM stack this year, and what to do about it in 2027.
AI can now connect your stack, read buyer signals and give the GTM team better tools. New tools also arrive faster than any team can absorb them.
Start from the job to be done and stay with the problem, then choose the tool. Every tool should do a real job, with an owner.
One story from Nick's career: where this part of the plan broke, the early sign, and what fixed it.
Expansion · From experience
Demand was growing, but invisible from the outside, and the core ICP couldn't reach the goal alone.
What breaks · Module 04 · Expansion
At CircleCI in EMEA, demand for DevOps was growing but unevenly spread and hard to spot. There were fewer large tech companies than in the US, and cloud adoption was slower. Bottom-up sizing showed our core ICP, software teams at VC-backed tech companies, couldn't reach the regional goal at expected deal sizes. I believed the same traits existed in companies outside our target segments, and any single user conversation confirmed it. We had no data or tooling to find them at scale.
Usage and spend growth from retained customers, new MRR and pipeline at established conversion rates didn't add up to the net MRR growth the goal needed.
We mapped internal and external data across the customer journey to find the traits of accounts that signed up, engaged, retained and expanded. A signal-based trigger system flagged when a company moved onto the target list, outbound scaled programmatically, and we had a live view of our SAM and SOM.
Can you name the signals that put a company on your list, and does anything tell a rep the day one fires?
From Nick Buckley-Mills, founder of Ascent.
What the module asks of your plan. Score them in the assessment.
What the plan has to decide, and what you should be able to show once it has.
Seed
Series A
Series B
Treat the stack the way a product team treats its roadmap. Start with the job the team needs done and the outcome in the GTM plan that it serves. Then weigh the alternatives, which include changing a process, giving the work to a person, or leaving it alone. Buy or build a tool only where it improves an outcome the plan measures. Get modules 01 to 03 decided first. The tools serve those decisions.
It's Clayton Christensen's jobs-to-be-done idea, applied to the go-to-market stack.
Judge each use case by the plan outcome it moves.
Ask these before you sign the plan off.
Seed
Series A
Series B
What good looks like at your stage, with a published figure where there is one.
Every customer conversation and deal sits in one CRM, every new customer can be traced to the channel that found them, and nobody rebuilds a report by hand.
Pipeline, ARR and churn each have one definition agreed with finance, and the board report comes straight from the CRM.
Product usage, CRM and finance data are joined, and each tool and AI use case has an owner and a measured outcome.
None of the three benchmark sources publishes a stage figure for this module.
More red than you expected? We can help fix it, working inside the business with your team. We'll reply within one working day.
Let's talkInvesting in a company that needs this? See how we work with VC and PE funds.
Readiness score
Each question is a provocation, the kind a sharp board member would ask before backing the plan. The score is a readiness score. It shows how far the plan's answer is made, agreed, written down and backed by data you trust. A low score marks where to dig before you commit. A question your team scores differently marks an argument to have now, in the planning meeting, before it comes up in front of the board.
Score each question from 1 to 4 using these definitions. There's no middle score, so you have to pick a side. Have each leader score alone, then compare.
A module's score is the average of its questions. Look at any 1 whatever the average says, because one undecided question can undo the rest of the module. At Seed, a 3 is a strong result on most questions, since a 4 needs data that most Seed companies don't have yet. 1 shows as red and 4 as green.
Nobody needs an account. Each person's answers stay in their own browser until they choose to send their link.
Each module's design ends with a "Good looks like" line for each stage, with a published benchmark where one exists. The figures come from High Alpha's 2025 SaaS Benchmarks Report, which groups companies by ARR. As a guide, the toolkit reads under $1M ARR as Seed, $1M to $5M as Series A and $5M to $20M as Series B. Funding rounds and ARR don't line up neatly, so read each figure as a rough guide.
ICONIQ's 2026 State of GTM reports across all its respondents without a split by stage. Meritech's benchmarks cover public and late-stage companies and sit behind a login, so this version doesn't use them. None of the three publishes stage figures for win rate, pipeline coverage, quota attainment, ramp time, burn multiple or the magic number, so those questions have no benchmark here.