The 90-second version
The build objection went from 2.0 to 7.2 percent of deals in a year. Where it lands it cuts win rate by 80 percent.
You named next year’s big motion before hiring the person who owns it. Normal, and also the risk.
Your buyer has had 30+ cold emails selling personalisation. Not one was personalised.
The European read: on a 3-month notice, day 60 is your last honest exit, so the review date must exist before the start date.
The thread: your buyer can generate the system now. They cannot generate the judgment about what it costs to keep it running.
Read time: ~7 min.
This week’s number 1 move
Topline tracked the “we will build it ourselves” objection across their deal panel. 2.0 percent of deals in late 2025, 5.5 percent in the first half of 2026, 7.2 percent now. Above 100k it appears in roughly 9 percent of deals, and where it appears it cuts win rate by 80 percent. That is not an objection. That is a competitor with no salary.
My take: the second you argue against the build, you are arguing against your buyer’s competence in front of their own team, and they pick their competence every time. So stop arguing and start pricing. They costed one thing, the build. Not the person, not the maintenance, not the change management. Those 3 are where builds die, and they are yours to name because you have watched it happen and they have not.
Do first: pull your last 20 losses. Tag every one where the buyer said any version of “we will build it”, and write 3 columns: what they would build, who was building it, what they were measuring.
The rule: you never win the build call by attacking the build. You win it by pricing the 3 costs they left out.
Source: Topline, “The year every buyer tries to build their own software” (August 18)
Hi, it is Koen Stam and welcome to GTMcraft OS: The European GTM Operator. This newsletter is built from 100,000+ GTM signals collected from 100+ operators and founders, combined with 13+ years of my own lessons and failures from the trenches. I write at the intersection of go-to-market practice and AI-powered systems for founders and GTM operators scaling their next 2M, 5M or 10M ARR.
Problem 1: Your buyer costed the build, and nobody costed the person
From my week: I spent last week covering 3 leadership seats that were uncovered at once, running the deal strategy, the workshops and the 1:1s myself. That week is the line your buyer never puts in the build case.
Jen Allen-Knuth gave 30MPC a sequence that works because it starts by conceding. Validate their build case with open questions. Help them succeed at building. Only then move to what kills internal builds: implementation, change management and support. And this is not a phase. Retool found 35 percent of 817 builders had already replaced a SaaS tool, 78 percent expecting to build more.
My take: they budget the build. They budget nothing for the Tuesday the person who built it hands in their notice. I raise it because I have watched that bill land from the inside. In a lean team every departure costs 2 quarters, one to hire and one to rebuild the context that walked out the door.
The European read: in a smaller market their build rests on 1 or 2 engineers they cannot replace locally, from the same pool you hire from. The single-point-of-failure risk is higher than the benchmark suggests.
Do first: on your last 20 losses, write the 1 sentence you did not say on that call. 90 minutes, CRM access, no new tool.
Do this week: add 3 discovery fields: who maintains it, what happens when they leave, who owns the change.
Do this month: make the team’s first response 1 standard line, with nobody freelancing it for a quarter.
The rule: the build is a project cost. Keeping it true is an operating cost, and only one of those is in your buyer’s spreadsheet.
You know it worked when: your win rate on deals carrying a build objection stops sitting far below the rest of your book.
The play: 5 steps to build a discovery question bank your reps actually run (2026 series). For 2-5M and 5-10M teams where every rep answers the same objection differently.
Sources: 30 Minutes to President’s Club, “How to handle the build vs. buy objection” (August 18) · Topline, “The year every buyer tries to build their own software” (August 18)
Problem 2: You named the motion before you hired the person who runs it
From my week: we confirmed a partner motion as one of next year’s big levers, and we are still 2 finalist interviews away from having the person who owns it. Decision inside 2 weeks. That order is normal, and it is exactly where these go wrong.
Jason Lemkin put a 4-part test on it this week, judged at day 60.
Did they make 1 great hire.
Did the 1 metric move.
Did they take real work off your plate.
Does the team believe in them.
Fail any of the 4 and you move on. No partial credit, and all 4 are observable without a spreadsheet. Justin Welsh wrote the other half the same week: delay is not patience, and hard information given early enough to act on is the kindest version of the conversation.
My take: naming a lever before I have the owner is not the mistake. I do it every planning cycle. Naming it and never writing down how I will know by day 60 is the mistake. My rule is that you cannot delegate a number, you build the layer that carries it, and a layer with no owner and no review date is a slide, not a motion.
The European read: on a 3-month notice, day 60 is your last honest exit. Be sure at month 5 and you pay through month 8, in a market where the replacement takes another quarter.
Do first: write the 4 checks on 1 page for the role you are hiring now, before the contract is signed.
Do this week: book the 60-day review on the day they sign, not the week you start worrying.
Do this month: run the same 4 checks on the leader you hired 6 months ago.
The rule: name the exit before the start date, or you will find the answer in month 9 and pay for it through month 12.
You know it worked when: every leadership hire has a review date before their first day. With no sales leader yet, read it as ramp to quota: your first hire is on the curve by day 60 or you know why.
The play: 5 steps to hire GTM bar-raisers on a real work sample (2026 series). For teams opening a motion they have never run before.
Sources: SaaStr, “A simple 4 part test to know if you’ve hired the right VP” (August 22) · Unsubscribe, “People deserve bad news” (August 22)
Problem 3: Your first email claims personal, and your buyer stopped believing it
From my week: my standing rule here has not changed in 2 years, and this week is the first hard evidence I have seen for it. Personalized at scale is not the same as personal. The gap between those 2 things is where reply rates went.
Elric Legloire put the number on it. He has had more than 30 cold emails from vendors selling personalisation, and not 1 was personalised. Which is why “I saw your post about X” now reads as a template. It is one. His fix: build the smallest real piece of your product’s output on that prospect’s own data and put it in the email as visible text. Not an attachment, not a link behind a form. Something they read in the preview pane. He also names where it failed, selling into HR, and that caveat is why I trust the rest.
My take: the reason almost nobody does this is that it does not scale, and that is exactly the point. A sentence claiming you researched someone can be generated 500 times before lunch, which is why it stopped working. A sample built on their data cannot. My test is the 10-minute one: if I cannot build it in 10 minutes I picked the wrong sample, and if it takes an hour I have built a proposal nobody asked for.
The European read: a sample built on the buyer’s own data survives translation in a way a clever opening line never does. In a second-language market it does the work your copy cannot.
Do first: pick 10 accounts and build 1 small real output on each one’s data. A paragraph of context, the sample, 1 question. No meeting ask.
Do this week: track reply rate against your current sequence, same list size, same days.
Do this month: keep whichever wins and delete the other.
The rule: a visible sample beats a personalised sentence, because the sample cannot be faked at scale and the sentence already has been.
You know it worked when: your reply rate on the sample list beats your standing sequence over 2 weeks, and self-sourced pipeline share moves without you adding hours.
The play: 5 steps to run founder-led outbound that books meetings (2026 series). For 2-5M teams where the founder still opens doors reps cannot.
Sources: Outbound Kitchen, “How to show your product in cold outreach” (August 16) · Koen Stam, “Personalized at scale is not the same as personal” (LinkedIn)
Save this. 3 GTM problems from this week’s signal, injected with the sharpest expert thinking, reframed for a European operator, each with a play you can run today and my own take from the trenches.
Send it to 1 founder or GTM operator scaling toward 10M in Europe who reads everything and ships none of it.
Steal this move: make the uncosted 3 a required field, in 4 weeks
Problem 1 is the most urgent one this quarter, and it keeps costing you because it lives in whichever rep takes the call.
Fixes: every rep answering your highest-stakes objection differently, so the deal turns on who picked up the phone.
Best for: 2-5M and 5-10M teams on the upmarket and new-country legs, where the buyer’s build rests on engineers they cannot replace locally.
The 5 steps (over 4 weeks):
Week 1, mine it: pull your last 20 losses and write what was said, not what should have been.
Week 2, cut it: keep only questions that changed a conversation in 3 of the 20. Twice is a preference.
Week 3, field it: make the 3 uncosted items required CRM fields.
Week 3, standardise it: 1 first response to the build objection, same words, for a quarter.
Week 4, practise it: a 20-minute role play, not a document nobody opens.
Template: a 1-5 rubric per rep. Rows: validating question asked, maintainer named, backfill risk named, change owner named, buyer said a number out loud, agreed next step. Under 3 on any row is this week’s coaching.
Paste this into your AI:
Here are notes from my last 20 closed-lost deals: [paste]. Flag every deal where the buyer said any version of “we will build it ourselves”, and extract what they would build, who was building it, and what they were measuring. Then show which questions appear in the deals we won and which were never asked in the ones we lost.
2 questions for the room
How many of your last 20 losses had a build in them, and what did you say when it came up?
Does your most recent leadership hire have a review date in your calendar, or only a start date?
What is your number 1 takeaway this week? Reply or send me a DM.
Go deeper with GTMcraft OS
Scale on plays and skills, not prompts.
You do not need another newsletter, podcast or LinkedIn post.
You need the system under it.
Read the plays. Every single play is free and live in GTMcraft OS on Notion. Click through from any edition.
Build your own. GTMcraft OS members connect the full libraries, 100+ plays plus 100,000+ LinkedIn, newsletter and podcast signals, straight into their own AI or Claude context, so their team builds on the whole corpus instead of one-off prompts.
The single plays are free to read. Wiring the whole corpus into your own operating system, and keeping it current, is what the membership gives you.
Master your human GTM skills AI can’t replace inside GTMcraft,
Koen
Your (human) GTM Coach
—
PS. Co-written by Wispr + 3 GTMcraft Skills + Claude Opus 5; edited & approved by Koen
The Future GTM Operator is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.