The 90-second version
A customer who had left us for a cheaper competitor came back to buy again. In the final meeting we spent 55 of 90 minutes on trust and 35 on price.
On a second late-stage deal I was certain the blocker was budget. Two deeper questions in, the real constraint was whether they had the people to implement it at all. A discount would have bought a failure at a lower price.
I ran a promotion round where not everyone got promoted. Not ready was the stated reason every time, and it was never the real one.
The European read: in smaller markets your buyer will meet you in person and will talk to 3 peers before they sign, so a transparent no about what you cannot do buys more than a discount does.
The thread: the stated objection is almost never the real constraint, in a deal room or a calibration room.
Read time: ~8 min
5 pipeline reviews, 3 interviews, 2 late-stage deals, 1 promotion round
The last week of August, and nothing in it read like August.
Underneath the visible calendar was the work nobody saw: a call with finance on Monday and a long session on Thursday night, both about next year’s investment rather than this quarter’s number.
Two of those deals taught the same lesson from opposite ends. So did the promotion round.
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.
Lesson 1: we spent 55 of 90 minutes on trust, and only 35 on price
A customer that had left us came back. They had switched to a cheaper competitor, found out cheaper was not better, and their own employees asked to come back.
We met at their office for what was booked as the best and final proposal. Budget holder in the room, plus the director who would own the rollout. I went in person, at late stage, for a meeting that could have been a call.
We booked 60 minutes and used 90. Only 35 of those went on pricing and next steps. The other 55 went on the tooling, the edge cases, what we do well, what we do badly, and what we may never build.
My take: I did not go to that meeting to negotiate, and I would not have travelled for a pricing call. I went because a buyer who has already been wrong once is not pricing the product, they are pricing the risk of being wrong twice. They had bought a promise before and it did not hold. So the 55 minutes were the deal and the 35 were the paperwork. My rule at that stage: we name the 3 things we cannot do before they find them. A seller who volunteers the gap is the only kind a burned buyer believes. And a senior leader in the room is not there to run the rep’s deal, it is there to make the promise carry a name.
The European read: in a smaller market your buyer will drive an hour to meet you, and will call 2 or 3 peers who already use you before they sign. Word travels faster than any case study, so what you admit is worth more than what you claim.
Do first: open your 3 largest open deals and write the 3 things your product does not do well for that account. If you cannot fill 3 lines, you have not had the honest conversation yet.
Do this week: on the deal closest to signature, put those 3 lines in front of the buyer yourself, with what you would do instead in each case. Watch whether the conversation gets shorter or longer. Longer is the good outcome.
Do this month: for every win-back or competitive replacement in your pipeline, add a required question to the deal review. What did the last vendor promise that did not hold, and what is our version of that promise.
The rule: at late stage a buyer is no longer pricing the product, they are pricing the risk of being wrong twice. Cut the risk and the price argument shrinks on its own.
You know it worked when: your late-stage discount rate falls while your win rate holds. With a small team, read it as the share of deals that close at list.
The play: 5 steps to decide when an in-person meeting is worth the trip (2026 series). Gives you a rule for which meetings earn the travel, so senior time goes to the rooms where trust is the actual constraint.
Lesson 2: I thought it was the price, it was the capacity
Second late-stage deal, same week. We were the preferred vendor and the only one still in the conversation, and it still would not close.
We had offered every shape we could: start small, start bigger, start later. All of it aimed at budget, because we were talking to the budget holder and budget is what budget holders talk about.
Then we asked a duller question. What is actually holding you.
The answer was not money. The company was mid-way through acquisitions, and the team that would own the rollout did not have the people to implement and adopt it. Buying it in that quarter meant buying a project nobody could run. Which meant the same conversation again in 12 or 24 months, and no impact for anyone.
My take: I stopped treating the budget holder as the answer years ago. In mid-market and up there is no single counterparty, there are at least 3 functions with 3 different risks, and the one who says no last is rarely the one who was blocking. What I have seen work is boring: ask what happens in the 90 days after signature, and ask it of the person who has to live those 90 days. Half the deals I have watched stall on price were stalling on capacity, sequencing, or a competing internal project nobody named. Discounting those deals does not close them. It just makes the failure cheaper for you.
The European read: across smaller European markets your buying committee is usually 3 people wearing 5 hats, and the one who has to run the rollout often has no budget line at all. They will not raise their hand. You have to go and ask them.
Do first: take your 5 largest open deals and write, per deal, the name of the person who will own the rollout after signature. Mark every deal where you cannot.
Do this week: on each marked deal, book 20 minutes with that person. One question: what would have to be true in your team for this to work in the first 90 days.
Do this month: add the implementation owner as a required contact on every deal above your average deal size, before it can be called late stage.
The rule: when a late-stage deal stalls, do not re-price it. Re-map the room, then ask what happens after signature.
You know it worked when: your late-stage slip rate drops and your onboarding start dates hold. If you do not run a formal forecast yet, read it as deals that close in the month the rep first called.
The play: 5 steps to run team selling that multi-threads every deal (2026 series). Builds the multi-threading standard so the implementation owner and the finance owner are both in the deal before the negotiation, not after it.
Lesson 3: not ready is not a reason, it is where I stopped thinking
The priority block of my week was a promotion calibration across the wider business. Every leader in the room, every candidate on the table.
Not everyone gets promoted. That is the part of the job nobody puts on a slide. What you owe the person is not the promotion. It is a real reason, a real path, and a date.
My take: this is the same diagnostic as the 2 deal rooms, which is why it sits in the same edition. Not ready is the stated objection, and it is almost never the real constraint. The real one has a name: they have never carried a forecast, they close well and cannot build pipeline, they have never had a hard conversation with a peer. If I cannot say which, I have not done the work, and not ready is just where I stopped thinking. The second failure mode I watch for in myself is speed. A no delivered the same hour is a no about my calendar. A no delivered 2 days later, with the gap and the next milestone written down, is coaching. And I do not pitch for my own team in that room, because the day I do, everything I say about anyone else stops being worth anything.
The European read: in a market where your senior talent pool is 200 people and they all know each other, a badly delivered no does not stay inside your company. It reaches your next 2 candidates before your recruiter does.
Do first: name the 1 person who thinks they are next, and write their gap in a sentence they would recognise. No promotion cycle yet? Do it for whoever would leave first if a better title landed in their inbox.
Do this week: say it to them, at least 24 hours after you decide, with the gap, the path and a date to review it. Send the same 3 things in writing.
Do this month: write the bar for the next level in observable behaviour. On a team of 4, that is a shared doc, not a framework.
The rule: you cannot promote everyone, so the thing you scale is the quality of the no. That is what decides whether they stay.
You know it worked when: the people you did not promote are still on your team at the next cycle, and 1 of them clears the bar. With a small team, read it as regretted attrition at zero.
The play: 5 steps to give your team hard news early enough to act on it (2026 series). Turns the no into a documented conversation with a gap, a path and a date, so the message lands as coaching rather than a verdict.
Save this. 3 lessons from my week as 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 is about to discount a deal that was never about price.
This week’s play to steal
Lesson 3 ends where most leadership teams stop looking. You promoted 1 or 2 people. Everyone else went back to their desk. That group is where your number actually lives, and it is the play I am taking into my own next 4 weeks.
Fixes: the number that rides on 2 or 3 carrier reps while the middle sits flat and the average hides both.
Best for: 2-5M and 5-10M teams on the upmarket or new-country leg. In a smaller market you cannot hire your way past a flat middle, because the senior talent pool is not there to buy from.
The 5 steps (over 4 weeks):
Week 1, split it: plot attainment as a distribution, not an average. Count the reps above 100 percent, between 70 and 100, and below 70.
Week 1, name it: pick the 3 people in the middle band with the most pipeline and the least coaching hours in the last quarter.
Week 2, isolate it: watch 2 calls each and name the 1 behaviour your top rep does instinctively that they do not do at all.
Weeks 2 to 4, drill it: run 1 bi-weekly 45-minute session on that single behaviour, with a live deal on the table, not a slide.
Week 4, gate it: re-score the same behaviour on a new call. No movement in 4 weeks means the gap is the plan, not the person.
Template: a 1-5 rubric scored per rep before and after. Rows: attainment band, pipeline held, coaching hours last quarter, the named behaviour, the observed change. Under 3 on the named behaviour after 4 weeks is a plan problem, not a coaching problem.
Paste this into your AI:
Here is per-rep quota attainment, pipeline held and closed-won for the last 2 quarters: [paste]. Show attainment as a distribution in 3 bands, not an average. Name the reps carrying the plan, name the middle band, and tell me how much of next quarter’s number disappears if the top 2 reps leave.
One question for the room
Take your last deal that stalled on price. If you had to name the real constraint instead, what would it be, and who in the room would have told you? 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.