This week’s number 1 move

Name the 2 things that must be signed off before December, and book those conversations next week.

Not 10. Two. The 2 decisions that, if they slip past October, become a constraint you carry for 4 quarters instead of a choice you make in 1.

From my week: I had a call with finance last Monday about next year’s expectations, and a session on Thursday night that was booked for 30 minutes and ran far past it, going through next year’s plan line by line. Neither meeting was about the quarter I am actually running.

My take: the reflex when the quarter gets tight is to put everything else down. I feel it every year, and it is how a good operator quietly loses one. What I have learned running this at multiple legs of scale is that the forward conversations are not competing with the sprint for importance. They are competing for a calendar slot, and the sprint wins a fair fight every time. So I do not give it a fair fight. I book next year’s conversations first, in September, while other functions are still willing to have them. I wrote the discipline down last week: rank the asks by size, cost, impact and likelihood, open the cross-functional conversation in Q3, and accept that you will cede some of them to a peer whose payback is faster. That layer gets funded in autumn or not at all.

The rule: the plan is not written in the planning meeting. It is written in whichever month you still had other people’s attention.

Sources: Koen Stam, “A first look at next year, and why the investment conversation starts in Q3” (LinkedIn, August 22); SaaStr, “The best VPs of sales make their B team shine” (August 25)

Problem 1: your Q4 sprint is spending the window where next year gets decided

From my week: the visible calendar was 5 pipeline meetings and 2 late-stage deals. The invisible half was 2 forward conversations, one with finance and one with the person I report to. Nobody on my team saw the forward half happen.

This is not just a busy autumn. Your next-year number is usually built on an attainment assumption your team has never hit. SaaStr put this year’s bands on it from the ICONIQ data. Top orgs run 85 to 90 percent of reps at quota. Average orgs run 65 to 75. Build next year on every rep at 100 and you have lost the difference before January.

The Revenue Formula makes the harder point. In the spreadsheet, everyone hits quota. Most misses are baked into the plan months before anyone underperforms.

My take: I split every line of a plan into 2 piles before anyone else sees it. Core is what I have 4 quarters of evidence for. Experimental is a bet that has not paid yet. Both belong in a plan. Mixing them is how a good ask gets cut wholesale in the room. The harder discipline is the second one: never commit to a number your capacity model cannot carry. If the maths does not work at your real attainment distribution, the honest answer is a smaller number or a different lever, said in September, not discovered in March.

The European read: in a second, smaller market pipeline does not scale with spend the way it does at home. The addressable account count is a hard ceiling, so a plan for country 2 has to name where the volume comes from before it names the budget.

The rule: build the number on the attainment you have, in the month people are still willing to talk about next year.

You know it worked when: your next-year pipeline coverage is a multiple you computed from your own distribution, not a number you hope for. Founder read: your forecast accuracy for Q4 is inside 15 percent before the quarter starts.

The play: 5 steps to build next quarter’s number bottoms-up (2026 series). Inlined in full below.

Access this GTMcraft Play [HERE]

Sources: SaaStr, “The best VPs of sales make their B team shine” (August 25); The Revenue Formula, “In Excel, everyone hits quota” (Podcast DB)

Problem 2: your 1:1s report, because nobody walks in with a question

From my week: I had a 1:1 booked for 30 minutes. I arrived late because the meeting before it ran over, and I was already deciding which 3 things to cut. It ran past 75 minutes instead, and it was the most useful hour of my week. The only reason it worked is that both of us walked in with a written list.

That is a preparation insight, not a scheduling one, and the cost of skipping it now compounds. GTMnow, with Ross Rich, made the sharpest version this week. AI is widening the gap between your top performers and your middle 60, because the tools reward taste. The middle has not built taste yet. His fix is not another tool. It is picking 1 skill your best reps do instinctively and running a recurring session on it with your middle 3.

Hakan Ozturk at The CS Cafe supplies the test. If 2 people prepared the same review for the same account, would the customer’s CFO see the same number. If not, preparation was never the problem. The standard was.

My take: I hold my leaders to 30 minutes a week each, ideally 45, and it eats a large part of my calendar. I keep paying it because a prepared 1:1 is the only meeting in the business where the agenda belongs to the person doing the work. The failure mode I watch for is the drift into a pipeline review, which is a status meeting wearing a coaching label. My test is on me, not on them. If I could have got it from the CRM, we wasted the slot. And we document both sides every time, topics and next steps, so nothing gets rebuilt from memory next week.

The European read: across smaller markets your team is often spread over 3 or 4 countries and 2 or 3 languages, and the corridor conversation that patches a bad 1:1 at head office does not exist. The written next step is the only thing that survives the distance.

The rule: a 1:1 without a written question from the other side is a status update, and you can read status in the CRM for free.

You know it worked when: the share of your team hitting quota moves because the middle improved, not because your top 2 carried the number. Founder read: your self-sourced pipeline share rises while your own selling hours fall.

The play: 5 steps to make your 1:1s produce decisions, not updates (2026 series). Built this week off exactly this lesson. Sets the 3-question input standard, 1 named metric per person, and the decision log both sides write in, plus the AI layer that drafts the pre-read so your calendar stops being the ceiling on coaching.

Access this GTMcraft Play [HERE]

Sources: GTMnow, “What the top 1 percent of sellers do differently” with Ross Rich, Accord (August 25); The CS Cafe, “Value realization at scale, executive reviews” (August 26)

Problem 3: your marketing team and your sales team are running on different clocks

From my week: I hosted a room of European operators this week on the bridge between marketing and sales. Different companies, different sizes, and the same conclusion from everyone. The tools were never the problem, and neither was the reporting line of the BDR team. The break is that demand is measured on this month and sales is measured on a buying cycle that takes 3.

Full-Funnel published the counter-example and the numbers are the argument. 46 accounts. A team of 3. A stack under 1,000 euros a month. One quarter, 3 enterprise opportunities, and their biggest deal closed. What made it work was not budget. Demand and sales held 1 shared list and 1 shared definition of progress. Their leading metric was a 43 percent account engagement rate, not week-one closed-won. That is the clock correction.

Pierre Herubel puts the same discipline on the content side. One clear front-end offer beats a full content calendar, because every post finally has 1 door to point at.

My take: the marketing-to-sales bridge is not an alignment problem, and I have stopped running alignment workshops to fix it. It is a measurement problem. Two teams pointed at the same accounts on different time horizons will always fight, and no shared Slack channel changes that. What I have seen work is boring and takes a week. One named account list both teams sign. One leading indicator both accept before revenue arrives. One offer both point at. On low ACV the economics only close if you extend term length. That was the sharpest thing said in the room this week, and it is the piece most teams never model.

The European read: in fragmented markets your named list is small enough to write down by hand, and the same 200 buyers see your ads, your posts and your outbound in the same week. That is an advantage. Run 1 list across all 3, and stop paying capture prices for accounts that cannot buy this year.

The rule: marketing and sales do not need to report to the same person. They need to be measured on the same clock and the same list.

You know it worked when: account engagement rate rises before pipeline does, and your marketing-sourced opportunity acceptance rate stops being an argument. Founder read: your named-account meetings booked rises without your own hours rising.

The play: 5 steps to split demand budget between brand and capture, and cut the middle (2026 series). Splits the budget by what it is actually buying, so the middle spend that serves neither team gets cut and both clocks get funded properly.

Access this GTMcraft Play [HERE]

Sources: Full-Funnel B2B, “Our ABM program breakdown, case study” (August 28); Pierre’s Content Guides, “6 revenue mechanisms to sell with content in 2026” (August 27); Koen Stam, “Alignment is not the fix, every account needs 4 named owners” (LinkedIn, August 19); Exit Five, Mason Cosby on how to simplify ABM (Podcast DB)

Also on the radar

• A churned logo talks to 20 to 30 prospects and partners, and most teams have no exit process. Action: write the 1-page exit standard this month, so a human handles the goodbye instead of a cancel form. SaaStr, “You’ll lose customers, don’t let them become angry ex-customers” (refreshed August 29)

• If your team rebuilds the value story from a blank slide every quarter, renewal odds depend on who holds the pen. Action: write a 1-page value record with 6 fixed fields for your top 20 accounts. The CS Cafe, “Value realization at scale, executive reviews” (August 26)

Steal this move: build next quarter’s number bottoms-up in 4 weeks

Fixes: the plan handed down as a target, then reverse-engineered into a pipeline requirement nobody can actually produce.

Best for: 2-5M and 5-10M teams on the new-country or upmarket leg, going into a planning cycle with 1 or 2 markets and a capped account count in each.

Template: a 1-5 rubric scored before the plan goes to the room. Rows: real attainment distribution used, ramp subtracted, core lines evidenced, experimental lines have kill dates, market ceiling stated, 2 decisions booked. Under 3 on any row is where the plan breaks.

Paste this into your AI:

Here are the last 4 quarters per rep, with attainment, win rate, average deal size and cycle length: [paste]. Build next quarter’s number bottom-up on the band we actually hit, not 100 percent. Subtract ramp for anyone starting after October. Then tell me the opportunity count the plan requires, and whether our account list can produce it.

Access this GTMcraft Play [HERE]

PS. 200+ plays, templates and workbooks inside GTMcraft OS. Reply or DM me to get access.

Why this matters now

All 3 problems this week are the same problem at different distances.

Your Q4 sprint eats the planning window. Your 1:1 eats the coaching window. Your demand clock eats the account list. The urgent work is not stealing your attention. It is stealing your slot, and it wins because it has a deadline attached and the important work does not.

The fix is not discipline. Discipline is what you spend when the system does not hold. It is a booked date, a written question and a shared list. Three cheap things, all doable this week.

September decides more of next year than December does.

3 questions for the room

1. What are the 2 decisions that have to be signed off before December, and are they on a calendar yet?

2. When did your last 1:1 produce a decision rather than an update?

3. If marketing and sales had to agree 1 leading indicator by Friday, which one would survive the argument?

Reply or send me a DM.

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.

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.

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.

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.

Access this GTMcraft Play [HERE]

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.

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.

Access this GTMcraft Play [HERE]

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.

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.

Access this GTMcraft Play [HERE]

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.

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.

Access this GTMcraft Play [HERE]

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.

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.

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)

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.

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.

Access this GTMcraft Play [HERE]

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.

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.

Access this GTMcraft Play [HERE]

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.

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.

Access this GTMcraft Play [HERE]

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)

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.

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.

Access this GTMcraft Play [HERE]

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.

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.

The set-up

First full week back after 2 weeks fully off. 25 meetings, mostly 30 minutes, stacked around a 12-hour leadership offsite on next year’s plan. Underneath it, 3 leadership seats uncovered at once, so I ran the deal strategy, the workshops and the 1:1s myself while a room upstairs asked what I need to fund the next leg of growth.

Nothing in that week was optional. That is why the important thing slipped.

Lesson 1: a rep called me out on the conversation I had moved

Mid-week, in a normal 1:1, one of my reps told me we still had not run his mid-year development check-in.

He was right. It should belonged to the manager who had left, the replacement starts next month, and the gap landed on me in the week with the least room in it. Past 15 people in the department, that conversation is the only place the middle of the team gets better. So it moved. I have said repeatedly that development is the highest-return leadership work there is, and a busy fortnight proved I treat it as the flexible item.

My take: this was not a discipline failure, it was a design failure, and it was mine. Every other block in my week had a counterparty who would notice a cancellation: a forecast call, a deal review, a candidate. The development conversation had nobody with standing to push back, so it absorbed the pressure of the whole week, until a rep gave it one. That is the block where the person who loses out has the least power to protest, and it decides whether next year’s plan has anyone left to run it.

The European read: in a smaller market the talent pool is tight and word travels fast, so an undeveloped rep costs you more than a seat. It costs the next 2 candidates you try to hire there.

The rule: the recurring block whose only stakeholder is the person with the least power to complain is the first thing your calendar eats.

You know it worked when: the share of your team hitting quota moves because the middle improved, not because your top 2 carried the number. With 3 sellers, read it as your founder-led deal share falling while the number holds.

The play: 5 steps to keep your best closer without making them a manager (2026 series). Builds the senior seat you can offer in that conversation, at real comp parity, so the only way up is not out of the job they are best at.

Access this GTMcraft Play [HERE]

Lesson 2: the bottom-up math said the gap cannot come from win rate

The offsite was a bottom-up planning exercise. Take next year’s target, work backwards, show what it costs.

I built it with marketing off current conversion, win rate and average deal size. The output was blunt. Most of the gap had to arrive as incremental pipeline, because our win rate is already near the top of what this motion produces. You cannot plan on winning a higher percentage of pipeline you do not have. And the ask that math produced is bigger than what I will get, so the skill is the ranking, not the ask.

My take: I split every line into 2 piles before the room sees it. Core is what I have proof for: money in, results back, 4 quarters of evidence. Experimental is a bet that has not yielded. Both belong in a plan, and mixing them is how a good ask gets cut wholesale. The discipline underneath: never commit to a number the capacity model cannot carry. If the math does not work at your current conversion, the honest answer is a smaller number or a different lever.

The European read: in a second, smaller market pipeline does not scale with spend the way it does at home. The addressable account count is a hard ceiling, so the plan for country 2 must name where the volume comes from before it names the budget.

The rule: when your win rate is already near its ceiling, the growth lever is pipeline volume and efficiency, never conversion.

You know it worked when: your pipeline coverage for next year is a multiple you computed, not a number you hope for.

The play: 5 steps to build next year’s plan early enough to hit it (2026 series). Turns the bottom-up build into a ranked, evidence-scored plan instead of a wish list that gets cut in the room.

Access this GTMcraft Play [HERE]

Lesson 3: I let a late-stage meeting move and it cost nothing

One late-stage deal touched my week 3 separate times. The one that mattered was a pricing and budget-fit conversation with the customer’s IT director, the kind of committee deal where the buying decision is not the rep’s counterpart to make. However busy the week, a senior leader stays available for that. It is not doing the rep’s job, it is opening a door only the title opens.

Then it moved, Friday to Monday, on the customer’s side. Usually that is where momentum dies. It did not, for an ordinary reason: both sides had already agreed the next step and what each would bring. The date changed, the commitment did not.

My take: I stopped counting meetings as progress years ago. A meeting is a container. What advances a deal is the agreement inside it, written down and held by both sides. If you cannot name the next step and the date, it is not pipeline, it is optimism with a calendar invite attached. My test in every review: can the rep tell me what the buyer committed to do next, in the buyer’s words.

The European read: when your AE and your buyer sit in different countries, often in a second language, the agreed next step is the only part of the call that survives a reschedule and a translation. Write it in the buyer’s language, in the thread, before anyone leaves.

The rule: a pre-agreed next step is what lets a deal survive a calendar shock, so test the book on that, not on meeting count.

You know it worked when: your win rate on late-stage deals holds through a week where half the calendar moves.

The play: 5 steps to advance deals on agreements, not meetings (2026 series). Replaces meeting-count progress with a buyer-committed next step your reps run on every open deal.

Access this GTMcraft Play [HERE]

This week’s play to steal

Lesson 2 ended with a gap I cannot fund with budget and headcount. It is the play I am taking into my own next 4 weeks.

Fixes: the reflex hire. You add a seat when output stalls, without knowing where the hours you already pay for go.

Best for: 2-5M and 5-10M teams building next year’s plan, on the new-country or upmarket leg. A second market adds fixed cost before revenue, so the hours you reclaim at home fund the entry.

Template: a 1-5 readiness rubric scored before any seat is approved. Rows: 2 full weeks captured, every hour bucketed, selling share stated in 1 sentence, reclaimable hours sized, morning block guarded, re-audit scheduled. Under 3 on any row is why the seat will not pay for itself.

Paste this into your AI:

Here are 2 weeks of calendars and CRM activity per person: [paste]. Tag every hour into 5 buckets: selling, prospecting, admin, internal, coordination. Show me selling share against admin share per person, then mark each bucket keep, cut or redirect and rank the hours I can reclaim fastest.

Full play, template and workbook inside GTMcraft OS. Reply or DM me to get full access.

Access this GTMcraft Play [HERE]

One question for the room

Which recurring block in your calendar has no counterparty who would notice if you moved it, and what does that cost you a year from now?

Reply or send me a DM.

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.

The set-up

I came back from 2 weeks off, worked 2 days and took 2 meetings on purpose. The rest I spent in the room with people.

That constraint was the point. All I could look at were the numbers on the board and the faces in front of me, and both said something different from what I expected.

Lesson 1: Coverage is a comfort number. Access to the economic buyer is the real one.

Coverage sat at a multiple of the monthly number and it meant nothing, because the coverage gap always shows up too late to fix.

One question sorted the healthy deals from the sick ones. Do we have the economic buyer, or a fan. Several were carried at full value with no line to anyone who owns budget.

My take: my rule has been that if you cannot name the next step and the date, it is not pipeline. The harder half: if you cannot name who signs and when you last spoke, it is not a deal. Coverage feels good because it moves without you doing anything hard.

The European read: with a lower account count per market you cannot outrun a bad qualification call with volume.

The rule: coverage tells you how much you have. Access tells you how much is real.

You know it worked when: forecast accuracy lands inside 10 percent 2 quarters running, because the committed number stopped moving after week 4.

The play: 5 steps to engage the economic buyer before the deal stalls. Fixes the deal that looks healthy and has never met anyone who can say yes.

Access this GTMcraft Play [HERE]

Sources: Koen Stam, “We missed our pipeline number in Q1” (August 14) · Outbound Squad, “AdRoll VP of Revenue on pipegen” (August 10)

Lesson 2: When the energy is gone, stop selling the stay and start advising the exit.

Days earlier I wrote that tenure is the asset founders underestimate. Then I walked with someone from that same group and it was not a retention conversation. It was already done.

She saw the energy the new people brought and knew she could not bring it any more. So I stopped. No counter-offer. I helped her think about a good next step, including outside the company.

My take: I hold that offboarding matters more than onboarding, and this week tested it, because I had named her publicly as an asset 3 days before. Trying to save something already gone is not loyalty. It is delay, and when the number rides on 2 or 3 carrier reps it is delay you cannot afford.

The European read: the talent pool here is tight. Someone who leaves well becomes a referral source, someone who leaves badly becomes your next hire’s reference check.

The rule: if the energy is gone you can fix the package, the scope and the manager, and none of it holds.

You know it worked when: the exit is planned early enough that their pipeline is reassigned before it ages, and team pipeline coverage does not dip the quarter after.

The play: 5 steps to turn every GTM exit into a culture asset. Builds on July’s offboarding edition, which covered the exit itself.

Access this GTMcraft Play [HERE]

Sources: Koen Stam, “Nobody cheered when someone else hit their number” (LinkedIn) · Matt Green, “The exit interview asks the great questions too late” (August 12)

Lesson 3: The team that got you here is not automatically the team that gets you to the next increment.

The comfortable version is “retention matters, but you need balance.” True and useless.

Going 3 to 5, or 5 to 10, or 10 to 20, you cannot do it the way you got here. The process changes, or the product line, or the territory. Your team is on that list too.

My take: headcount is not capacity and tenure is not capability. What I watch is whether the experience in the room is used to go faster or to explain why something will not work. The second one is how the number ends up riding on 2 or 3 carrier reps while everyone else sells differently. If you cannot carry a 150 to 250k leadership hire on your runway, the bar-raiser is not a VP. It is the next IC, held to the standard of the leg you are going to.

The European read: adding a country or moving upmarket is a new motion, and a new motion is where the team’s pattern-matching stops helping.

The rule: keep the context, raise the bar, and never let tenure become the argument.

You know it worked when: your next hire ramps to quota inside your ramp target, and the percent of reps at quota goes up while your top 2 carry less.

The play: 5 steps to hire GTM bar-raisers on a real work sample. Fixes the hire who interviews well and cannot run the motion you are moving to.

Access this GTMcraft Play [HERE]

Sources: Koen Stam, “I stopped recommending founders hire a Head of Sales” (LinkedIn) · SaaStr, “Gamma scaled to 100M ARR without a sales team” (July 29)

This week’s play: audit the hour before you add a seat

Before you decide you need more capacity, check whether the hours you have point at revenue.

Play: 5 steps to audit the hour before you add a seat

Fixes: the capacity gap you are about to close with headcount, when the real problem is where the hours go.

Best for: 2-5M and 5-10M, any motion. It bites hardest when you are opening a second market.

Paste this into your AI:

Here is my team’s calendar for next week. Tag every block revenue-generating (in front of a buyer, or producing pipeline) or not. Return a per-person table with total hours, RGA hours, RGA percentage and the 3 largest non-RGA blocks, then which 3 to cut first and what I lose.

Access this GTMcraft Play [HERE]

One question for the room

Look at your top 10 open deals. On how many can you name who signs and the date you last spoke to them?

Reply or send me a DM.

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.

This week’s number 1 move

Score last month’s triggers against your recent wins, and rank the accounts, before anyone sends a thing.

For 2 years the pitch was to add AI to outbound. This week the market raced to point an agent at every trigger feed it could buy. Jordan Crawford framed the counter-move on the signal-based selling discourse: most triggers are noise, so run them through the filter of your own closed-won deals and almost none survive. Florin Tatulea’s number lands on the same point. Signal-based plays convert several times better than cold, but only the scored ones do. Put the two together. The gap is not how many signals you can buy or how fast an agent can act on them. It is whether you score them against your own win pattern before a human reaches out. An agent can weight a live trigger feed against your last 20 wins in minutes, which no rep can do by hand. So build the scoring step, then let your people work the top of the ranked list.

My take: Here is the part most people skip. As the leader I do not just buy the signal tool. I set the standard for what a real signal is worth, because I own the number and I build the layer that carries it. You cannot delegate a number, and you cannot delegate the judgment underneath it either. The agent scores; the rep decides and reaches out, because personalized at scale is still not the same as personal. Monday morning, I would score last month’s triggers against my recent wins and rank the accounts before a single sequence goes out. The tool is not the edge. The standard you set for what earns a human touch is.

The rule: A single trigger is noise. A scored stack is intent. Score the signal before anyone reaches out.

Run it at your stage:

• Founder-led, no agent yet: score your last 10 to 20 wins in a sheet by hand, rank this week’s accounts against them, and work the top. No agent, no new tool, no new spend.

• At scale: point your AI-SDR layer at the scored base, let RevOps own the monthly retrain, and report the reply-rate lift to the board as the ROI on the tools you already pay for.

Sources: Jordan Crawford, “Signal vs insight based selling and the future of AI in GTM” (July 25) · Florin Tatulea, “How to use intent-based selling for sales development success” (30MPC, 2026)

Problem 1: Your outbound agent sprays a list nobody scored, so it scales the wrong accounts faster

You bought a signal tool and wired it into your outbound agent. Now the agent fires on every trigger the feed produces. A hire here, a funding round there, a page visit somewhere else, and it reaches out to all of them at machine speed. The problem is that most of those triggers never preceded a deal, so the agent does not fix a weak list, it scales it. Your reps chase alerts that mean nothing, and the account with real intent gets the same generic first touch as the rest. Todd Busler’s warning this week is blunt: the market is hot on signal-based outbound, and most of the firing is noise, so score before you act. The move on your pipeline motion is to put a gate in front of the agent. Before it sends, weight each trigger by how often that signal appeared before your recent wins, rank the accounts, set a threshold, and let the agent draft only for the top. Everything below the line goes to nurture, not to a rep.

My take: An agent pointed at an unscored list is the most expensive spray you can run, because it burns machine speed and rep hours at the same time. Personalized at scale is not the same as personal, and a generic first touch fired at 500 accounts is neither. Point a rep at an unscored feed and the week goes to a funding alert that meant nothing, while the account with 3 stacked signals sits untouched. That trade is why I do not let the agent decide who is worth a human. I set the gate, the agent ranks against it, and my people work the top. On a lean team that gate is the difference between outbound that compounds and a faster way to get filtered.

The European read: In smaller markets your account list is finite and word travels, so a wide unscored blast burns names you cannot get back and reads even flatter in a second language. A gated agent that only touches the scored top is how a lean team stays precise across countries instead of spraying every market at once.

The rule: If your agent acts on every trigger, it is a faster spray. Gate on the score, then send.

You know it worked when: Your reps work a short ranked list instead of a long raw feed, and reply rate on the touched accounts climbs.

The play: 5 steps to set the trigger-gated outbound sequence your agent runs (2026 series). Puts a scoring gate in front of the agent so it only drafts for accounts above your threshold, and the rest go to nurture. Best for 2-5M teams running signal-based outbound across markets.

Access this GTMcraft Play [HERE]

Sources: Todd Busler, “The market is hot on signal-based outbound” (2026) · Florin Tatulea, “How to use intent-based selling for sales development success” (30MPC, 2026)

Problem 2: You treat one trigger as intent, so a stacked account and a random alert look the same

A single trigger tells you almost nothing. A company hired a role. A company raised money. On its own, each fires for hundreds of accounts that will never buy. Yet most setups treat every trigger as equal, so a random alert and an account with 3 stacked signals land in the same queue. Your best-fit account gets buried, and your rep spends the day on whichever alert popped up first. Kyle Poyar’s read on the intent revival is that automated signal plays convert several times better than cold, but the lift comes from the stack, not from any one trigger. The move is to score the base your agent runs on, not the trigger. Weight the signals, add a bonus when 2 or more fire on the same account, add a bonus for freshness, and down-weight signals that also preceded your losses. Now a stacked, recent account rises to the top and the lone alert sinks. The agent does the weighting across the whole feed in minutes. You decide the threshold and who gets a human touch.

My take: Winning in 2026 is not about more outreach. It is about mastering ICP, demand, and timing, and a stack of signals is timing you can actually see. One trigger is a coincidence dressed up as intent. I do not let reps guess which alert matters, because guessing is how the loud trigger beats the right one. I score the base: which signals, stacked how, actually preceded a buy. That base is the judgment I refuse to hand to a tool blind. The agent applies it at speed across the feed, but the definition of a real signal is mine, and it is the part that decides where my scarce selling time lands.

The European read: The stack that predicts a deal is not the same in every market. A hiring surge that signals intent in DACH can be noise in France, where the buying pattern is different. Import one signal base across your countries and you scale the noise faster. Score the base per market, so the ranked list reflects how each country actually buys, not how your home market does.

The rule: One trigger is a coincidence. A recent stack is a reason to call.

You know it worked when: Your top-ranked accounts are the stacked, recent ones, and your reps stop working alerts in the order they arrived.

The play: 5 steps to fix the base before you point an agent at it (2026 series). Turns your win pattern into the scored base the agent ranks on, so a stacked account beats a lone alert every time. Best for 2-5M and 5-10M teams tightening targeting across markets.

Access this GTMcraft Play [HERE]

Sources: Kyle Poyar, “An outbound playbook for 2025” (2025) · Florin Tatulea, “How to use intent-based selling for sales development success” (30MPC, 2026)

Problem 3: Your scoring model never learns, so it keeps ranking signals that stopped predicting wins

Say you build the scoring base once. You weight the signals, rank the accounts, and ship it. 6 months on, the market has moved, and 2 of your top-weighted signals no longer precede deals. But the model never learned, so it keeps sending your reps to accounts that fit last year’s pattern. A scoring agent that never retrains decays into the same noise it was meant to cut. The edge in signal-based selling is not the base you build once. It is the loop that keeps it honest. The move on your pipeline motion is to schedule the retrain. Every month, feed the agent your new closed-won and closed-lost deals. Raise the weight on signals that keep predicting wins, cut the ones that now precede losses, and re-score the live feed against the updated pattern. Review the model quarterly, so the standard your team runs on stays tied to what is actually closing, not to what closed a year ago.

My take: The model stopped being the moat a while ago. The loop around it is. A scoring base you set once and never revisit is just yesterday’s judgment on autopilot, and yesterday’s judgment quietly stops matching the market. I treat the retrain like a forecast review: a standing ritual with one named owner, not a project someone gets to when they can. The agent does the re-scoring in minutes, but the decision to trust it again this quarter is mine, because I own the number it feeds. Kept honest, the loop is what makes a scored list keep beating a raw feed instead of slowly becoming one.

The European read: Each market moves at its own pace, so a signal that predicts in one country can decay first in another. A single global retrain hides that. Run the loop per market, so the ranked list in each country tracks how that market is buying now, which is also how you catch a new motion opening before your competitors do.

The rule: A scoring model you never retrain becomes the noise you built it to cut.

You know it worked when: Your signal weights shift each quarter to match what is closing now, and the ranked list keeps beating a raw feed.

The play: 5 steps to truth-test your pipeline before an agent forecasts on it (2026 series). Builds the recurring honesty check that keeps your scored feed tied to what is actually closing, so the agent never ranks on a stale pattern. Best for 2-5M and 5-10M teams running an agent on their pipeline.

Access this GTMcraft Play [HERE]

Sources: Todd Busler, “The market is hot on signal-based outbound” (2026) · Jordan Crawford, “Signal vs insight based selling and the future of AI in GTM” (July 25)

Steal this move: Build a signal-scoring agent under your outbound motion in 4 weeks

The number 1 move is to score the signal before anyone reaches out, so here is the hero play in full. It moves your outbound off a raw trigger feed and onto a scored, ranked list your reps work top-down.

Play: 5 steps to turn outbound trigger noise into a signal-scoring agent

Access this GTMcraft Play [HERE]

Fixes: An outbound agent firing on every trigger, so it scales a bad list faster and your reps chase noise.

Best for: 2-5M and 5-10M, any pipeline motion, and the European reality of a finite account list where a wide unscored blast burns names you cannot get back.

Lean version (founder-led, no agent yet): do steps 1 and 2 in a spreadsheet against your last 20 wins, rank by hand, and work the top 20 this week. Add the agent in phase 2, once the pattern is proven and the manual version is already earning replies.

Template: A 1-5 signal-scoring rubric. Rows: win pattern pulled from real closed-won, signals weighted not equal, stack bonus set, recency bonus set, losses down-weighted, monthly retrain owned. Score your setup 1-5. Anything under 3 is this week’s work.

Paste this into your AI:

Here is my closed-won and closed-lost export and my live trigger feed: [paste]. Find the signals that showed up in the weeks before my wins, weight each by how often it preceded a buy, add a bonus for stacked and recent signals, and down-weight any that preceded losses as often as wins. Then score and rank my live feed against that pattern and show me the top 20 accounts, with the driving signal for each.

Also on the radar

• Jordan Crawford, “Signal vs insight based selling and the future of AI in GTM” (July 25). Run your triggers through the filter of your own closed-won deals and almost none survive. Before you buy another signal source, test the ones you have against your last 20 wins.

• Florin Tatulea, “How to use intent-based selling for sales development success” (30MPC, 2026). Signal-based plays convert several times better than cold, driven by stacked signals, not any one trigger. Pick the 2 signals that stack most on your wins and start there.

• Kyle Poyar, “An outbound playbook for 2025” (2025). Most accounts are not in-market at any moment, so scoring is the case, not reacting to every alert. Score so scarce human time lands on the few that are ready.

Why this matters now

For 2 years the outbound advantage was access to more signals. This week the market showed the next line. Point an agent at a raw trigger feed and you scale a bad list faster. Point it at a scored list and scarce human time lands on the accounts most likely to buy. The edge is not the number of signals you can buy or the speed of the agent. It is whether you score them against your own win pattern before anyone reaches out, and whether you keep that pattern honest as the market moves. A scored stack compounds. A raw feed just gets louder. This builds on last week, where the move was to own the layer that runs your revenue instead of renting it. This week is the upstream beat: own the standard for what a real signal is worth, so the right accounts reach a human at all.

What is your number 1 takeaway from this week’s signal: which of your outbound triggers actually predicts a win, and which are you paying to send to?

Reply or send me a DM.

Master your human GTM skills AI can’t replace inside GTMcraft,

Koen

Your (human) GTM Agent

PS. Co-written by Wispr + 3 GTMcraft Skills + Claude Opus 5; edited & approved by Koen

This week’s number 1 move: Rewrite your homepage hero to name one buyer, one problem, and one outcome no competitor can honestly claim.

Dave Gerhardt broke down how one B2B brand stood out among 200 competitors this week on Exit Five. The answer was not a bigger budget. It was a sharper edge. They stopped selling to everyone and named the one buyer they were built for. Most founders do the opposite. They widen the message to catch more of the market, and the message goes gray. A gray message competes on price, because price is the only thing left to compare. So the move is subtraction, not addition. Take your homepage hero line and your last 3 closed-lost notes. Rewrite the hero to name one buyer, one problem, one outcome only you can own. Then read it against those 3 losses and ask whether it would have changed them.

My take: I am a GTM operator carrying a number too, so I read this one as a job on my own desk, not just a move to pass on. Focus is not a mood, it is a number you can point to. I will run the same on my own markets in the coming week, ranking them by real revenue instead of ambition, and run this paste test on our message the same way. Positioning is that call, aimed at your message instead of your map. The pitch to be for everyone always sounds bigger than the pitch to be undeniable for one buyer. Broad commoditizes. Undeniable compounds. I would rather own a narrow room than rent a seat in a crowded one, because in a crowded room the only question left is your price. If you are the founder still writing the motion yourself, this is the highest-return hour you spend this month, because you are the pitch and the map at once.

The rule: If widening the message is your growth plan, price is your real positioning. Narrow until the comparison disappears.

Run it at your stage:

• Founder-operator: you own the message, so rewrite the hero and your outbound first line yourself this week. You are the whole decision unit, so there is nothing to align but your own nerve to cut.

• GTM leader: you may not own the homepage, but you own the claim your reps say in the room. Gate the one undeniable version in your deck and your call reviews, so 20 reps sell one claim, not 20 versions of a gray one.

Source: Exit Five, “How this B2B brand stands out among 200 competitors” (August 4)

Problem 1: Your message could be pasted onto a competitor’s site and still read true

Run the test now. Copy your homepage headline onto a rival’s site. If it still reads true, you do not have positioning, you have wallpaper, and the buyer cannot pick you on a difference they cannot see. Peep Laja put the root cause plainly: most teams think they have a pipeline problem, when they actually have a messaging and differentiation problem. Weak positioning starves the top of the funnel, then the whole team blames volume and pours budget on a message that was never sharp. The fix is not more words. It is a sharper claim: name the specific buyer, the specific problem, and the outcome only you can stand behind. A claim a competitor can copy word for word was never a claim.

My take: I keep coming back to the same 4 fundamentals when a number stalls: simplicity, clarity, belief, and alignment. Positioning is where clarity gets tested first, because the market hears your message before it ever meets your product. When I cannot say in one line who we are for and who we are not for, the problem is never the ad spend. It is that I have not made the call yet. Making the call is the work, and no campaign budget substitutes for it. On a lean team you feel this fastest, because you do not have the volume to paper over a gray message with more sends.

The European read: In smaller, fragmented markets a gray headline reads even flatter in a buyer’s second language, where nuance drops and only the plain claim survives. If your one line could go on any rival’s site, it lands as noise in every market you translate it into. A claim built around one specific buyer is the only kind that keeps its edge country to country.

The rule: If your competitor could paste your message and it still reads true, it is not positioning, it is wallpaper.

You know it worked when: Buyers start repeating your claim back in discovery, and your win reasons shift from price to the specific outcome you named.

The play: 5 steps to turn customer calls into a VOC engine that sharpens messaging (2026 series).

Mines your own customer calls for the exact words that make your claim yours, so the message stops reading like everyone else’s. Best for 2-5M teams sharpening positioning across markets.

Access this GTMcraft Play [HERE]

Sources: Peep Laja, “You don’t have a pipeline problem, you have a messaging and differentiation problem” (LinkedIn) · Exit Five, “How this B2B brand stands out among 200 competitors” (August 4)

Problem 2: You claim “no one else does this” and the buyer hears risk

Here is the trap on the other side of differentiation. You finally name a real edge, you say no one else does it, and the deal cools. The buyer did not hear proof. They heard a reason to be careful. Kyle Asay named the mechanic this week: a buyer who hears “no one else does this” thinks “then why should I trust it?” An undefended differentiator reads as risk, not value, and buyers avoid risk before they chase upside. So defend every claim 2 ways. First, the unique resource that lets only you do it: more time in the market, a specific data set, an engineering choice. Second, a point of view backed by a customer story that proves the benefit is real. A differentiator you cannot defend is worse than no differentiator, because it plants doubt at the exact moment you need trust.

My take: Belief is one of my 4 fundamentals, and this is where it gets tested on the buyer’s side, not yours. A claim you cannot back does not build belief, it drains it. My rule is that no differentiator goes in the deck until it has a resource and a proof story behind it: here is why only we can do this, and here is the customer it already worked for. If I cannot produce both, the claim is a liability, so I cut it or I go earn the proof. The undefended version does not read as bold, it reads as unproven, and unproven is the fastest way to lose a careful buyer.

The European read: In a smaller market your logo count is lower and references are scarcer, so an undefended claim has nowhere to land and the doubt sticks. Word travels fast here too, so one buyer who read your edge as risk tells the next. A local proof story, a customer in their market and their language, does more to defend a claim than any amount of confidence in the pitch.

The rule: An undefended differentiator reads as risk, so back every claim with a reason only you can give and a proof the buyer can check.

You know it worked when: The “how do I know that is real” objection stops showing up late, because you answered it the moment you made the claim.

The play: 5 steps to run a discovery call that earns the second meeting (2026 series). Surfaces the buyer’s risk early and arms your reps to defend the claim with a resource and a proof story, so a real edge stops cooling deals. Best for 2-5M and 5-10M teams selling a genuine differentiator.

Access this GTMcraft Play [HERE]

Sources: Kyle Asay, “Why ‘no one else does this’ backfires” (August 7) · Exit Five, “How this B2B brand stands out among 200 competitors” (August 4)

Problem 3: You explain your edge in tech speak, and the buyer never feels it

A sharp claim still dies if you say it in jargon. Frictionless. Low-touch. Seamless. The buyer nods and forgets, because words that sound like every vendor make your edge invisible again. Krysten Conner showed the fix on a coaching call this week. A seller kept saying frictionless implementation, and prospects glazed over. They swapped it for one analogy everyone knows: competitors are IKEA, months of assembly, we are Wayfair, delivered assembled, usable the same day. The discovery calls got better immediately, because the buyer finally pictured the difference. A concrete image beats a category buzzword every time. The point of positioning is not to be understood by your team. It is to be felt by the buyer, so translate your edge into a picture they can repeat to a colleague who was not in the room.

The European read: An analogy has to survive translation. IKEA and Wayfair may land in one market and mean nothing in the next, so the picture is not one line you write once, it is one you localize per country. In a new market where your voice is unknown, a concrete image the local buyer already understands is how you get remembered instead of filed under generic vendor.

The rule: A buyer champions what they can picture and repeat, so trade the buzzword for the image.

You know it worked when: Buyers repeat your analogy back unprompted, and your reps hear it quoted in the room they were not in.

The play: 5 steps to run a demo that advances the deal (2026 series). Turns your edge into a moment the buyer feels and can retell, so the difference lands instead of getting filed under generic vendor. Best for 2-5M teams whose product is better than their pitch makes it sound.

Access this GTMcraft Play [HERE]

Sources: Krysten Conner, “Explain differentiation with an everyday analogy” (August 4)

Steal this move: Become the category of one in 4 weeks

The number 1 move is to narrow until the comparison disappears, so here is the hero play in full. It rebuilds your positioning around the one buyer you are undeniable for, then defends and translates the claim so it holds up in the room.

Fixes: A message so broad that every deal commoditizes to a price comparison, because you never named the one buyer you are built for.

Best for: 2-5M and 5-10M, any motion, and the European reality of a lower account count where a gray message burns names you cannot afford to burn.

Template: A 1-5 positioning-clarity rubric. Rows: one buyer named, one problem named, one outcome only you own, claim survives the paste test, each differentiator has a resource and a proof, the edge has a picture a buyer repeats. Score your positioning 1-5. Anything under 3 is this week’s work.

Paste this into your AI:

Here is my homepage hero, my last 20 closed-won deals, and my last 3 closed-lost notes: [paste]. Find the one buyer, one problem, one outcome I win on most often. Draft a hero line only I could honestly claim. Then read it back as each of my 3 top competitors and flag every phrase they could also sign, so I know what to cut.

Access this GTMcraft Play [HERE]

Also on the radar

• April Dunford, “Positioning jujitsu” (LinkedIn). Positioning is as much about placing your competitors as carving your own space. You win by choosing the frame the comparison happens in. Name the alternative you want to be compared against, then position against it on purpose.

• Chris Walker, “Category creation” (LinkedIn). For a category creator the future feels inevitable, but you still have to teach the market the new frame before it buys. If you are creating a category, budget for education, not just demand capture.

• Todd Busler on Peep Laja, “Pipeline pain is usually a positioning symptom” (LinkedIn). Before you raise spend, pressure-test whether the message is the real bottleneck, not the volume.

Three questions for the room

• Could a competitor paste your homepage headline onto their site and have it still read true?

• Which of your top 3 differentiators can you defend with both a unique resource and a customer proof story, and which are you just asserting?

• What is the one everyday analogy your buyer repeats back, and does it survive translation into your next market?

What is your number 1 takeaway this week? Reply or send me a DM.

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.

This week’s number 1 move

Before you buy the next tool that runs a revenue motion, run the portability test.

The tool that builds your pipeline, drives your renewals, or drafts your demand is where your GTM logic actually lives. This week the market raced to bolt an agent onto every pricing page. PricingSaaS pulled the numbers across 4,060 companies: 14.6 percent now show an AI agent on the pricing page, 54 percent of second-quarter agent pricing changes were brand-new launches, and 70 percent are bundled into existing plans, a feature you rent inside a screen you cannot open up. Brendan Short in The Signal covered the move that cuts the other way. Clay shipped a public API, a CLI, and a one-line agent plugin, draining its own interface lock-in on purpose, because its heaviest users build in code, not the UI. His call: programmatic access becomes a first-order buying criterion within 12 months. So the question on any revenue tool is not which agent looks best in the demo. It is whether you can build your own context and workflow on it, or you rent a screen.

My take: Here is where I land after 3 years of testing AI in GTM. You cannot delegate a number, you build the layer that carries it, and a closed UI cannot carry my number because I cannot feed it my context or wire it into my motion. AI is a multiplier, not a corrector, so bolt it onto a system with no owner and it scales the mess at machine speed. That is why I slow founders down on tooling: not because I doubt AI, but because the layer underneath usually has no owner. So I run the portability test before the demo dazzles me. If I cannot build on it, I do not buy it, whatever the agent on the pricing page promises.

The rule: A shiny agent on the pricing page is not an edge. An endpoint you can build on is. Buy the tool you can own.

Sources: The Signal, “Clay Just Drained Its Own Moat (On Purpose)” (July 28) · PricingSaaS, “The State of Agent Monetization” (July 31)

Problem 1: Your pipeline logic lives in a closed screen, so your best account research never compounds

The tool that builds your list and drafts your first touch runs your pipeline, and most of them are closed screens. You log in, click, export a CSV, and every bit of ICP logic you tuned stays trapped in the vendor’s UI. Brendan Short’s piece on Clay names why that is about to hurt. Clay shipped an open API, a CLI, and a one-line agent plugin, because its power users already build their list logic in code. They wire it into their own workflow, so their enrichment and scoring rules become an asset they keep, not a screen they revisit. His forecast lands straight on your pipeline motion: within 12 months, programmatic access is a first-order buying criterion. So the move is to buy the list-build tool you can call from your own code or agent, so your account research, your triggers, and your scoring compound into something you own, instead of resetting every time you switch vendors.

The European read: Your ICP shifts by market, so the account logic that works in your home country is not the one that works in the next language. If that logic lives in your own workflow, you fork it per market and it compounds. If it lives in a vendor screen, you rebuild it from zero in every country you open.

The rule: If your account research only lives inside a vendor’s screen, you are renting your pipeline, not building it.

You know it worked when: Your list-build logic runs from your own code or agent, and a vendor swap costs you a config change, not a rebuild.

The play: 5 steps to set the targeting standard your outbound agent runs on (2026 series). Turns your ICP and trigger logic into a portable standard an agent runs, so your pipeline research compounds instead of resetting. Best for 2-5M teams scaling outbound across markets.

Access this GTMcraft Play [HERE]

Sources: The Signal, “Clay Just Drained Its Own Moat (On Purpose)” (July 28) · PricingSaaS, “The State of Agent Monetization” (July 31)

Problem 2: You are buying a renewals agent you cannot feed your own account context

Your customer success and renewals tool probably grew an AI agent this quarter. PricingSaaS counted the pattern across 4,060 companies: 14.6 percent now show an AI agent on the pricing page, and 70 percent of those agents are bundled into existing plans rather than sold on their own. Bundled and closed means the agent runs on the vendor’s logic, not yours. It cannot read your health signals, your win notes, or your account history, because you cannot feed it your context, so it drafts a generic renewal email any competitor’s agent would also draft. The move on your retention motion is to buy the tool whose agent you can load. Give it your account context, your churn signals, and your playbook as files it reads every time, so the renewal draft carries what only you know.

My take: Personalized at scale is not the same as personal, and a renewals agent running on vendor defaults is the fastest way to sound like everyone else on the account that pays you most. Customer success is a growth engine, not a cost center, so I will not let its highest-stakes moment run on generic. The fix is context, not a smarter model: load the agent your health signals, your win notes, and how that account actually measures value. AI does the first draft, a human does the second and sends it, because the renewal is a relationship and the biggest ones are still won human to human.

The European read: Your renewal motion runs in the customer’s language and against their local sense of value, not a translated template. A context file per top account, written in how that market measures value, is how a lean team makes every renewal sound local instead of shipping the same generic draft across every country.

The rule: An agent you cannot feed your context is a template with a chat box, not a renewals engine.

You know it worked when: Your renewal and QBR drafts read like your best CSM wrote them, because the agent runs on your account context, not the vendor’s defaults.

The play: 5 steps to feed your renewals agent the account context it needs (2026 series). Turns your health signals and account history into context files an owned agent reads, so every renewal draft carries what only you know. Best for 2-5M and 5-10M teams defending NRR.

Access this GTMcraft Play [HERE]

Sources: PricingSaaS, “The State of Agent Monetization” (July 31) · The Signal, “Clay Just Drained Its Own Moat (On Purpose)” (July 28)

Problem 3: Your content agent is a rented screen, so your demand reads like everyone else’s

The tool that drafts your demand content runs on the vendor’s model and prompt, not your voice or your workflow. Kieran Flanagan surfaced the cost this week: a Bynder blind test found 56 percent of readers preferred AI copy, until they were told it was AI-written, and then engagement dropped. Generic AI content is now a measurable risk to the demand it is supposed to build. A closed content UI cannot hold your foundation files, your best posts, or your rubric, so it regresses to the same generic draft every rival’s tool produces. The move is to own the content engine, not rent it. Build or buy a content agent you can load your voice files and your scoring rubric into, and wire into your own publish workflow, so your demand engine scales on an asset you own and the output still sounds like you.

My take: Feed it your best work and keep the last 20 percent, because that is the part you get paid for. I spent 3 years explaining who I am to a model and still got the internet average back, until I dropped in 20 of my own posts and a couple of playbooks, and only then did it read like me. AI amplifies what you feed it, so feed a rented UI nothing of yours and it amplifies the average. I would rather ship 3 posts that could only have come from us than 10 that could have come from anyone.

The European read: In your home market your audience knows your voice, so generic content reads as a step down. In a new market you are building that voice from zero, and generic AI content is how you stay invisible. A voice-loaded engine is how you sound like a local operator in each market instead of a translation of everyone else.

The rule: If your content tool cannot read your best work, it will keep producing everyone else’s average.

You know it worked when: Your content agent drafts from your voice files, a human approves the last 20 percent, and engagement holds when readers know it is AI-assisted.

The play: 5 steps to build a measurable loop that scores its own output (2026 series). Wires your voice files and rubric into an owned content engine that scores every draft before a human ships it, so scale and sounding like you stop being a trade-off. Best for 0-5M founder-led demand engines.

Access this GTMcraft Play [HERE]

Sources: Kieran Flanagan, “Use AI to Craft Slop Free Content” (July 31) · PricingSaaS, “The State of Agent Monetization” (July 31)

Steal this move: Own the agent layer under one revenue motion in 4 weeks

The number 1 move is the portability test, so here is the hero play in full. It moves one revenue motion, pipeline, renewals, or demand, onto a layer you own.

Fixes: A stack filling with seat-locked screens, where the logic that runs your revenue motion is trapped in a UI you rent.

Best for: 2-5M and 5-10M, any motion, and the European reality of running one stack across fragmented, multi-language markets from the background, not a person in every vendor tab.

Template: A 1-5 portability rubric. Rows: API, CLI, or MCP endpoint present, clean data export tested, core logic written as a portable file, 1 step running from your own workflow, offboarding terms read. Score each tool 1-5. Anything under 3 is a screen you rent.

Paste this into your AI:

Here is the tool that runs my [pipeline / renewals / demand] motion and a link to its docs: [paste]. Fill the portability score: does it expose an API, CLI, or MCP endpoint, and can I export my data cleanly. Then draft the 1 real test call I should run in the trial, and list the logic I need to pull out into a portable file so it survives a vendor switch.

Full database of GTM plays, templates and workbooks inside GTMcraft OS. Reply or DM me to get access.

Access this GTMcraft Play [HERE]

Also on the radar

• PricingSaaS, “The State of Agent Monetization” (July 31). 54 percent of second-quarter agent pricing changes were brand-new launches, and few are metered on their own. Before you pay for an agent add-on, check whether it is metered or just bundled to lift your renewal.

• The Signal, “Clay Just Drained Its Own Moat (On Purpose)” (July 28). Brendan Short’s call: programmatic access becomes a first-order buying criterion within 12 months. Add 1 line to your tool eval scorecard, does it expose an API, CLI, or MCP endpoint.

• GTM AI Podcast, “Your Pipeline Is Lying to You. AI Won’t Fix It.” (July 30). Eddie Reynolds puts AI on the top rung of the GTM pyramid, above fundamentals. Buy an agent for a broken motion and you amplify the break. Name the rung that is actually weak before you buy.

Why this matters now

For 2 years the AI advantage was access to a better model. This week the market showed the next line. When a vendor bolts a closed agent onto its pricing page, you rent a screen. When Clay opens an API, its power users build an asset they keep. The edge is not the agent in the demo, it is whether you can build your own context, skills, and workflow on top of it. The layer you own compounds, one revenue motion at a time, in every market you sell into. A rented UI resets every renewal. This builds on Fix The Base from this week: repair the fundamentals, then own the layer you amplify them on.

What is your number 1 takeaway from this week’s signal: which revenue motion is running on a layer you rent instead of one you own?

Reply or send me a DM.

Master your human GTM skills AI can’t replace inside GTMcraft,

Koen

Your (human) GTM Agent

PS. Co-written by Wispr + 3 GTMcraft Skills + Claude Opus 5; edited & approved by Koen

Read more