The 90-second version
On Friday I walked in to read out next year’s plan and walked out of a brainstorm. The markers were questions asked to someone other than me, like: where do you see constraints?
A mentor showed me his weekly room per key account, with marketing at the table. I do not have it yet.
A new country leader gave me his first-month read. My job now is to ask what he will change, and by when.
The European read: across several markets the constraint usually sits in 1 country, and only its local lead can name it.
The thread: a plan, a key account and a new leader all get better when the room answers first.
Read time: ~8 min
6 quarters of data, 3 working days, 1 month in a new seat, 1 question asked out loud
In the next 3 weeks, most leadership teams see next year’s plan in draft. Soon after, it meets the people who have to run it.
My week had 3 working days, after a family wedding. 3 conversations in it taught me what to do before a plan meets a room.
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: my plan readout turned into a brainstorm
On Friday I walked into a session to read out next year’s plan for my part of the business.
I had prepared for a readout. I got a brainstorm.
The plan asks more of us than this year did. We do invest, but most of the growth has to come from the productivity of the team we have.
The questions were not about the target. Current state. Constraints. Mitigations. Opportunity.
Then the most senior leader in the room turned to our head of RevOps. What do you think? Where do you see constraints? Where do you see opportunity?
Questions like that were the markers. It stopped being only my plan.
The groundwork mattered. On Wednesday my RevOps partner and I built a simple bottoms-up model. Every country lead got the last 6 quarters of data by source and motion, and is building their own. On Thursday I went through every constraint, risk and dependency with my head of marketing.
My take: I will own this plan and I will be accountable for it. But on Friday it did not feel like carrying it alone. It really felt like our plan. What made that happen was not a better deck. It was a question asked out loud to someone other than me. A readout asks the room to approve. A brainstorm asks the room to find the break. A stretch plan needs the second, because the people who hit the constraints first are rarely the person presenting.
The European read: a plan across several markets is built from several local truths. The country lead who knows why 1 market converts slower can name that constraint. A model from the centre cannot. Give each country its own data and model before you add them up.
Do first: write down the 3 constraints most likely to break next year’s plan, and next to each, the person who would see it first. Founder fallback: no leadership team? Your best seller, your marketer and whoever runs customer success each name 1.
Do this week: send the plan to those people before you present it, with 1 question: where does this break? Founder fallback: your co-founder and your best seller, 30 minutes each.
Do this month: give each team lead their last 4 to 6 quarters by source and motion, and ask for their number bottoms-up before you show them yours. Founder fallback: 1 spreadsheet, conversion by source, per seller.
The rule: present the constraints before the target. A plan the room has questioned is a plan the room will own.
You know it worked when: your plan review spends more time on constraints than on the headline, and bottoms-up and top-down land within a gap you can explain. Founder read: 2 people other than you can name the plan’s biggest risk.
The play: 5 steps to build next quarter’s number bottoms-up. A per-seller capacity model, so the number your leads build starts from what they can actually do.
Lesson 2: my regional room does not cover the key account
On Wednesday I had dinner with a commercial leader I see as a mentor, a couple of steps ahead of where I want to be.
Those dinners start with life and family and end deep in go-to-market. For me they are priceless. This time I left with a room he built.
Every week, marketing, his AEs, their leaders, his VP and he sit together on their key accounts. Each AE answers the same questions. What did you do this week? Who are the stakeholders? How did they move? Marketing brings the campaigns it runs into those accounts. Claude keeps the digest short enough for the AEs to read.
I run a room too. Every other Friday my regional leaders walk through pipeline, implementation, renewals and the problems nobody wants to raise. It works for the region.
It does not cover the account. Nobody in it answers, account by account, which stakeholder moved this week.
That is exactly the piece missing in how we build mid-market and enterprise pipeline.
My take: a regional room makes problems visible. A key-account room makes people accountable. They are different jobs. 1 room cannot do both. On a mid-market deal the stakeholders move every week, and marketing is running campaigns into the same accounts. If those 2 things never meet in 1 room, they stay 2 motions pointed at 1 buyer. What I will steal first is the question, not the tool. Who moved, and what did you do about it.
The European read: in a smaller market your key account list is short and it does not refill. 1 stakeholder you lost track of is a real share of the segment. Across 2 or 3 countries the campaigns run in 2 or 3 languages, which is 1 more reason marketing and the AE need the same page.
Do first: pick your 10 key accounts and list every stakeholder you know, with the last date anyone on your side spoke to them. Founder fallback: 1 sheet, 30 minutes.
Do this week: hold 30 minutes with your AEs and whoever runs marketing on those accounts. Each AE answers 3 questions per account: what did I do, who moved, what runs into it next. Founder fallback: no marketer? You and your sellers, same 3 questions.
Do this month: run it 4 weeks in a row, with an AI-drafted 1-page digest from notes and CRM activity before each session. Founder fallback: paste the week’s notes into Claude, 1 line per account.
The rule: the region gets a room every 2 weeks. The key account gets a room every week. Do not ask one to do the other’s job.
You know it worked when: known stakeholders per key account rise, and every key account shows at least 1 dated touch a week. Founder read: you can name who moved in each of your 10 accounts without opening the CRM.
The play: 5 steps to run a weekly sales meeting that decides, not reports. A pre-read carries the status, so the live half of the room only decides.
Lesson 3: a new leader’s first month is a readout you ask for
On Thursday I had lunch with a country leader who is 1 month into the seat.
He brought his first read: how he wants to structure his organization, where he sees potential, where he sees threats.
The first month is for reading the room. You need to understand what you are taking over before you change it.
Then comes the push, and it is the one I always got in my own career. What are the key things you really need to change or adjust? Do not wait too long. Just do it, because otherwise it drags.
My take: a new leader can fail in 2 directions. Change everything before they understand it, or understand everything and change nothing. The first month protects against the first. The question at the end of it protects against the second. A first-month readout forces a view while the eyes are still fresh. I push on the changes because that push is what I always got in my career. A first read that is never acted on slowly becomes the old organization’s read.
The European read: a new country leader inherits a market with its own buyers, partners and history. The first-month read is where you learn which parts of your standard system travel there, and which conversations need to be local.
Do first: book a 60-minute first-month readout with your newest leader and send 3 prompts ahead: structure, potential, threats. Founder fallback: your newest hire at any level, 30 minutes, same 3 prompts.
Do this week: end the readout with 1 question: which 2 things will you change, and by when? Write both down with dates.
Do this month: put a day-60 check in both calendars now, and decide together whether each change goes on or stops. Founder fallback: a 15-minute check-in, booked today.
The rule: give a new leader a month to read the room, then ask what they will change and by when. A first read that waits becomes the old organization’s opinion.
You know it worked when: your new leader has 2 dated changes in flight by day 45 and a go or no-go on each by day 60. Founder read: your newest hire changed 1 thing in their first 2 months that you would not have.
The play: 5 steps to know by day 60 whether your leadership hire is working. A 4-check test at day 60, so the go or no-go comes long before month 9.
Save this. 3 lessons from my week as a European operator, each with a play you can run today.
Send it to 1 founder or GTM operator about to present next year’s plan.
This week’s play to steal
All 3 lessons are the same move at 3 sizes: ask the question before you give the answer. The smallest version runs every week, in every 1:1 you hold.
Fixes: 1:1s that decay into a deal walk you could have read in the CRM.
Best for: 2-10M and 10-25M teams where 1 manager runs 4 to 10 direct reports, often across more than 1 market.
The 5 steps (over 4 weeks):
Week 1, send every direct report the same 3 questions 24 hours ahead: what decision do you need from me, what is blocked, what did you learn that I should know. Answer them yourself too.
Week 2, name 1 input metric per person, taken from their last 90 days. Never their quota.
Week 3, watch 2 calls per person and name 1 behaviour to drill on a live deal. No recordings? Sit in on 1 live call.
Week 3, close every slot with a decision, an owner and a date, or park it with a review date.
Week 4, keep 1 page per person that both sides write in, and hold the slot when the week gets heavy.
Template: 1 page per person, appended weekly. They bring: decision needed, blocked on, learned. You bring: decision you need, what you owe them. Then the metric against last week, and decisions out with owner and date. Score it 1 to 5 before each slot: 1 means only you wrote in it, 5 means both sides did and last week’s commitments are marked done or not.
Paste this into your AI:
Here are my direct report’s answers to 3 questions (decision needed, blocked, learned): [paste]. Here are their open deals: [paste]. Write a 5-line pre-read: what changed since last week, which answer has a deal behind it, and the 1 question I have not asked. Then list the decisions this 1:1 should end with.
Why this matters now
In the next 3 weeks, next year’s plan goes to your leadership in draft, then to your team. The default is a readout: the plan is finished, and the room is asked to believe it.
Run it the other way. Bring the constraints first and let the room find the break while it is cheap. Then give your key accounts a weekly room, and your newest leader a question with a date on it.
3 questions for the room
Before you present next year’s plan, who other than you has told you where it breaks?
Which of your key accounts had a stakeholder move last week that nobody in marketing heard about?
What did your newest leader say they would change after their first month, and has it happened?
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
