Strategy
How to build a GTM story that investors actually believe
TL;DR
Investors pass on GTM stories that list what a team has been doing. They're scanning for one thing, evidence that the motion repeats. The clearest proof is the same-spot test. If we can name what our motion reliably gets wrong, we have a system. If everything went well and nothing went the same way twice, we have anecdotes. Five layers carry the story, and there are honest stand-ins for every one of them at pre-seed.
Investors are looking for one thing in a go-to-market story. Evidence that the motion repeats.
Most GTM sections are built the same way. Market size, ICP description, channel list, logos, a sales motion overview. It feels complete.
It rarely works, because it describes what we've been doing rather than what our doing it reliably produces. Those are two different conversations, and only one of them is investable.
A partner has minutes with the deck. The GTM section is competing for that attention against the financials and the team slide. There's no time to build to a point.
The same-spot test
There's a car wash near me that misses the same two inches of the back bumper. Every single time.
It's annoying. It's also the most honest thing about the place, because a machine that misses the same spot twice is a machine. Something is happening in there in a fixed order, and that fixed order is what you're buying.
A wash that came out perfect once, and nobody can say why, is a coincidence with a receipt.
That's the same-spot test, and it's the one partners are running whether or not they'd describe it that way. Can we name what our motion reliably gets wrong?
If we can, we have a system with a known flaw, and known flaws get funded. If everything in the deck went beautifully and none of it went the same way twice, we have anecdotes.
What partners scan for
ICP as a pattern
At pitch time, an ideal customer profile has to be a pattern we extracted from deals that already closed. "Mid-market SaaS companies with 50 to 500 employees" is where the work starts.
Compare two sentences a team could say out loud. "We target operations leaders at B2B SaaS companies" is a hypothesis. "Our last twelve closed deals share three traits, and in ten of them the trigger was a CRM migration or a new CFO arriving within ninety days" is a finding.
The second one tells a partner we know who buys and what makes them buy right now. It also tells them we've been watching.
When the ICP is hypothesis-only, everything downstream gets mentally discounted. The channel math, the cycle, the economics all sit on a customer definition nobody has tested. For how to build that pattern out of deal data, see our guide to building an ideal customer profile that converts.
The cycle count
"We use LinkedIn and outbound" names tools. What a partner wants is one channel that produced a comparable result more than once.
A cycle means we ran the motion, measured it, changed something, and ran it again. Three of those is the threshold we use, because three is where "it worked" turns into "it behaves."
Here's the shape that lands. "Our outbound sequence to VP Finance at manufacturing companies produces a consistent 8% reply rate. We've run it five times across different rep books and seen variance under three points."
Imperfect numbers survive that framing easily. A result nobody has reproduced doesn't survive it at all.
Economics you can defend
Nobody expects early unit economics to be clean. They expect us to know what's inside them.
Customer acquisition cost is where teams get caught, because the numerator is a choice. Counting paid media and quietly leaving out rep salaries is the most common version, and it gets found in the first five minutes.
Payback period is the number partners anchor on, and expectations tighten as ARR grows rather than as rounds are named. If ours runs long, the useful move is naming the specific operational change that compresses it and when.
Lifetime value at this stage is a model, so show the model. A number with no assumptions attached is less credible than a rough number a partner can argue with.
The gas light
Some of us drive forty miles past the gas light without a flicker of worry. We've run this car down four times and we know what it has left, roughly, less in the cold.
The person in the passenger seat is quietly terrified. They don't have our four data points.
"It depends" is what someone says about a car they've never watched run out. When a partner asks about sales cycle length, they're not collecting a number. They're testing whether we've watched.
The answer that works names the median across a recent cohort, then names the variable that splits it. Something like a median of forty-seven days, with deals that have a VP-level champion closing in half the time of the ones that don't.
Cycle predictability is what makes a capacity model real. If we can't say how long deals take, we can't project revenue or forecast hiring, and every number after that slide becomes decorative.
A claim that can be wrong
Positioning is credible to an investor when they could call one of our customers and hear it confirmed without prompting.
"We help companies work smarter" survives no such call. "We're the only error-tracking tool built for embedded device fleets rather than web front ends" gets confirmed or denied in thirty seconds, which is exactly what makes it worth something.
The test is falsifiability. A claim no competitor would bother disputing has no edge for a buyer to hold onto. The one a named competitor would push back on hard is a narrative.
Strong positioning doesn't prove product-market fit. It proves we know the market well enough to stake something. Our post on navigating PMF without GTM fit covers what to do when those two are out of sequence.
The verbal version
When a partner says "walk me through your GTM," the instinct is to present the slides. Resist it. A tight spoken version buys more time in the room than a slide-by-slide walk.
Five minutes, six beats. Who we sell to and what makes them buy now, with one closed deal that shows both. The channel that's working, with the specific repeatable result.
What the economics look like, including where they'll be next stage and why. What the cycle looks like, median plus the variable that drives the spread.
Why we win, in one sentence, followed by a deal we took from a named competitor and the reason the customer gave.
Then where this goes with capital, which is where the ask stops being abstract. Hiring against a channel with known payback is an investable sentence. "Scaling GTM" isn't.
The deck version is the same six beats on six slides instead of one dense overview. For the layer underneath all of it, the SaaS GTM guide walks through ICP, channel strategy, and launch sequence outside a fundraising context.
Before you have the data
Pre-seed teams don't have three channel cycles or mature economics, and the investors who fund at that stage know it. What they're reading is whether we know what needs proving.
Structured discovery interviews stand in for closed-deal evidence, as long as we can point to the same problem described in the same words by different people. Verbatim quotes carry weight that summaries never do.
One documented cycle stands in for three. "We ran this to fifty prospects, here's what happened, here's what we changed and why" shows the discipline, which is the actual thing being evaluated.
A labeled model stands in for real unit economics. Mark which assumptions come from data and which are theory, because a partner who can attack a specific assumption is engaged, and one staring at a clean unexplained number is gone.
Stage definitions stand in for cycle predictability. If we know what moves a deal from evaluation to proposal and what signal triggers it, we have the machinery that produces predictable cycles once volume shows up.
Rigor about what we don't know reads better than confidence about what we do. Every partner has been burned by the second one.
Nobody funds a perfect wash that happened once.
Name the spot it misses.
What to do next
If the GTM section describes activity and you can feel it, more slides won't help. Take the last twelve or twenty closed deals, find the traits that repeat, and rebuild the section from the pattern up. Most teams discover they had a motion and were describing a schedule.
If the harder problem is that the positioning claim isn't specific enough for a customer to confirm, that's a positioning audit before it's a deck exercise. If that's where you are, start here. The first conversation is free.
Frequently asked questions
Your ICP with closed-deal evidence, your primary channel with performance across multiple cycles, your unit economics with the CAC calculation spelled out, your sales cycle with the variable that drives its spread, your positioning claim with a competitive alternative named, and what capital does to the motion. Six focused slides beat one dense overview.
Most companies need a year or more of closed-deal data before repeatability and cycle predictability are demonstrable with any confidence. Three cycles with consistent results is the practical threshold. Before that, structured discovery and one well-documented experiment are the honest stand-ins, and by Series A the motion is expected to be running and measurable.
They shift from evaluating a working motion to evaluating how the team thinks. That means the quality of customer discovery, the clarity of the ICP hypothesis and the plan to test it, the read on competitive alternatives, and a channel thesis specific enough to be wrong. Conviction at pre-revenue comes from the questions being asked.
Confusing activity with evidence. Teams describe what they're doing rather than what it consistently produces, and the story sounds busy while telling a partner nothing about how the motion behaves under capital. The repair is to anchor every claim to a measurable outcome that happened more than once.
Related reading
The author
Nick Pham
Founder of Bare Strategy. Twenty years in B2B marketing, the last decade in product marketing inside enterprise software.
More about the operator →If this is where you are
Bring the problem, not a brief, and you'll leave the first conversation with something useful either way.
Start a conversation