Module 04 of 5 · GTM engineering · What the plan runs on

04

Connect your stack and data

The stack keeps growing, but the data doesn't connect and too much still runs on manual work.

2026 to 2027

What changed in the GTM stack this year, and what to do about it in 2027.

What changed in 2026

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.

1,488marketing technology tools were added in a single year, and 1,367 removed, out of 15,505 in 2026 (chiefmartec)

What breaks

One story from Nick's career: where this part of the plan broke, the early sign, and what fixed it.

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.

The questions

What the module asks of your plan. Score them in the assessment.

  1. SeedCould anyone on the team find every customer conversation, and what was learned, without asking a founder?
  2. SeedWhat's the simplest stack that lets the founders sell and learn? What have you decided not to build yet?
  3. Seed, Series ACan you trace each new customer back to the channel that found them? Do sales and marketing accept the same answer?
  4. All stagesHow do product usage data and customer records come together today? Which decisions has that changed this quarter?
  5. All stagesWhich manual tasks will you automate or hand to AI this year? Where would that add risk?
  6. Seed, Series AIs the CRM set up for the sales hires joining this year? What would force a rebuild, and when?
  7. Seed, Series AHow is the board's pipeline report produced, and how much of it is done by hand? Would the board trust it without a founder explaining it?
  8. All stagesFor each tool in the stack, including AI tools, what's its job and which plan outcome has it moved?
  9. Series A, BDo finance, sales and marketing use one definition of pipeline, ARR, churn and net revenue retention? Who signs off a change?
  10. Series A, BIs customer and deal data clean enough to act on AI output? How do you know?
  11. Series BWho owns RevOps and the systems roadmap? Is it resourced for the motions and regions you run?
  12. Series BHow many hours a week do reps spend selling? Which systems or tasks take the rest, and what does the plan change?
  13. Series BWhat would the stack need to support the next country or product? Who has scoped it, and is it in the budget?

Design

What the plan has to decide, and what you should be able to show once it has.

Seed

The plan decidesOutput
Process ownership: where customer learning lives and who keeps it currentOne shared place holding every customer conversation, deal and lesson, set up so the first sales hire can use it
Metric definitions: one definition per measure the plan usesA short list of the numbers the board sees, each with one definition and its source
Tools and automation: CRM, analytics and reportingA one-page stack list giving each tool's job, owner and the outcome it moves, plus what you've chosen not to build yet
Where AI saves time or helps make a call, with each use case tied to a plan outcomeA short list of AI and automation use cases, each with the outcome it should move and the risk it adds
Leading indicators from modules 01 to 03, tracked without manual workSource channel recorded for every new customer, and product usage linked to customer records for the decisions it informs

Series A

The plan decidesOutput
Metric definitions: one definition per measure the plan usesA metric dictionary agreed with finance, with a named person who signs off changes
The CRM and attributionA CRM set-up ready for this year's sales hires, with the source channel recorded for every new customer
Product usage dataUsage data joined to CRM accounts, with a list of the decisions it feeds
Leading indicators from modules 01 to 03, tracked without manual workA dashboard specification, and a board pipeline report taken straight from the CRM
Tools, automation and AI, tied to plan outcomesA stack map with an owner, a cost and a purpose for each tool, plus a short list of AI use cases, each with its outcome, how it's measured and the data it relies on

Series B

The plan decidesOutput
Process ownership: who owns each GTM process, and how a change gets madeA RevOps charter with a named owner, a change process, and resourcing set against the motions and regions
Metric definitions: one definition per measure the plan usesA metric dictionary signed off by finance, with a named owner for changes
Tools and automation: CRM, sales engagement, data enrichment, analytics and reportingA stack map with an owner, a cost, a job and the plan outcome for each tool, plus a one-page case for each new tool, reviewed after a quarter
Where AI saves time or helps make a call, with each use case tied to a plan outcomeA list of AI and automation use cases, each with its outcome, how it's measured, a data-quality check and the risk it adds
Leading indicators from modules 01 to 03, tracked without manual workA dashboard specification joining product usage, CRM and finance data, including a report of rep time spent selling
Training on the tools, and how stack changes are run as projectsA roadmap of stack changes for the year, including what the next country or product needs, scoped and in the budget
How we'd approach the stack

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.

Where AI and automation are worth paying for

Judge each use case by the plan outcome it moves.

  • Rep productivity: account research, call preparation, notes, follow-up and CRM updates, so more of the week goes on selling.
  • Pipeline: enrichment, intent signals and account prioritisation, so reps work the accounts most likely to buy.
  • Insight: call analysis, deal inspection and forecast risk. Managers should see a deal slipping before the forecast call.
  • Decisions: scenario, territory and capacity modelling. The leadership team can test the plan before it commits.
  • Automation: handoffs, routing and reporting that someone still does by hand.

Pressure test

Ask these before you sign the plan off.

Seed

  • Which decisions in this plan depend on data we can't produce today?
  • If a founder left tomorrow, which customer insights would we lose?
  • If the board asked for the pipeline number today, how long would it take? Would two of us get the same figure?
  • What does the stack cost a year? Which tools could we drop without losing anything?
  • Which AI or automation spend is tied to an outcome we can measure within a quarter?

Series A

  • Which decisions in this plan depend on data we can't produce today?
  • Could a new sales hire trust the CRM on day one? What would they find wrong first?
  • Who owns data quality before there's a RevOps hire, and who checks it?
  • What does the stack cost a year? Which tools would we cut first?
  • Which AI or automation spend is tied to a measured outcome? How will we know within a quarter if it worked?

Series B

  • Which decisions in this plan depend on data we can't produce today?
  • What does the stack cost a year per rep? Which tools would we cut first?
  • If we launched the next country or product on today's stack, what would break first?
  • Which AI or automation spend is tied to a measured outcome? How will we know within a quarter if it worked?
  • When did a metric definition last change without sign-off, and what did it do to the board numbers?

Good looks like

What good looks like at your stage, with a published figure where there is one.

Seedtypically under $1M ARR

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.

Series Atypically $1M to $5M ARR

Pipeline, ARR and churn each have one definition agreed with finance, and the board report comes straight from the CRM.

Series Btypically $5M to $20M ARR

Product usage, CRM and finance data are joined, and each tool and AI use case has an owner and a measured outcome.

Sources

None of the three benchmark sources publishes a stage figure for this module.

Want a second view
on next year's plan?

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 talk

Investing in a company that needs this? See how we work with VC and PE funds.