The 1 test that strips dead deals from your forecast
Any open deal older than twice your sales cycle is already gone. Run the truth test, then fix the base before you scale it.
The 90-second version
The loud move this week was bolting an agent onto everything. The teams that grew fixed the base first, starting with the pipeline truth test: any open deal older than twice your sales cycle is effectively dead, so strip it and look at the real number.
Your outbound is volume, not a sequence. A four-part first touch aimed at accounts with a real trigger beats more sends to the wrong list.
Your worst-fit accounts eat the capacity you keep trying to hire your way out of. Total the cost to serve next to the ACV, then make the exit, contain, or invest call.
Your targeting runs on triggers that do not predict closed-won. Of 1.6 million datasets tested for outbound signal, only 12 survived. A bigger list is more noise, not more pipeline.
The European read: fundamentals are the only thing that carries across a fragmented, multi-language market. The forecast discipline, the sequence, and the account math you build at home port to the next country. A tool or a price does not travel.
The thread: you cannot amplify your way out of a broken base. Fix it first, because the base is the only part that compounds across quarters and countries.
Read time: ~7 min.
This week’s number 1 move: Run the pipeline truth test before you scale anything.
Eddie Reynolds laid out a GTM efficiency pyramid on the GTM AI Podcast this week: fundamentals, then adoption, then optimization, then amplification. The top rung, where more firepower lives, only pays off if the base under it is real. Most teams skip the bottom three, point their firepower at a broken process, and it breaks faster. His fastest fundamentals check is the pipeline truth test. Any open deal sitting longer than twice your average sales cycle is effectively dead. Strip those deals, look at what is left, and that is your real pipeline. It is the quiet theme of the whole week. The operators who grew did not add more firepower. They fixed the thing the firepower would have amplified.
My take: This is the one I would run first, because it costs nothing and it exposes the truth about your number in an afternoon. My own sharpening: measure against your win cycle, the median days your won deals actually take, not your average sales cycle, because losses drag the average long. When I joined Personio to scale Benelux I normalized every quarter across every motion, hunting where growth was real, and the same pattern showed up everywhere. A deal sits past twice its win cycle and nobody pulls it, because green feels safer than a smaller honest number. If I cannot name the next step and the date, it is not pipeline. Strip it, then re-engage the few with a live champion, we turned 500K in written-off deals back into revenue that way.
Do first: Pull median days-to-close on your won deals over the last 2 quarters. Double it. Pull every open deal older than that line out of your committed number, and total what you stripped. That gap is your real exposure.
The rule: Age beats stage. An honest smaller number beats a comfortable padded one. The payoff is not cosmetic: operators who re-age and re-weight the forecast this way routinely find close to a fifth of pipeline has quietly aged out, and forecast accuracy climbs around 20 percent in two quarters.
Source: GTM AI Podcast, “Your Pipeline Is Lying to You. AI Won’t Fix It.” (July 30)
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.
100,000+ GTM relevant signals from LinkedIn, Newsletters and Podcasts indexed. Translated into 100+ GTM plays, skills and training for you to implement today.
13+ years over 3 GTM operator jobs across 3 GTM motions (SMB, MM, ENT). Scaling from 2-10M+ ARR multiple times. Same recipe. Different motions.
Now all part of the GTMcraft Operator System.
Problem 1: Your outbound is volume, and volume is not a sequence
Outbound is a craft with a structure, and more sends do not fix a broken one. Two signals made the same point from opposite ends. 30MPC published the anatomy of their cold sequence: a four-sentence first email, one line of real personalization, the problem, the solution, a low-friction test-drive ask, then a same-thread nudge that now out-replies the first email, 5 percent against 4, then a case-study bump. Pierre Herubel named the other half. Most teams pour everything into demand capture, chasing the roughly 5 percent of the market in-market today, and spray it wide, while they neglect the 95 percent they could be teaching. So the fix is not more sends. It is a structured sequence aimed only at accounts with a real trigger. Point more volume at a bad sequence and the wrong list, and you scale ignored email.
My take: More volume is the most expensive way to hide a weak sequence. I make my teams read step one out loud: if that first line could go to any account on the list, it is not a sequence, it is spam with better grammar. The structure is the craft, and the same-thread nudge out-replying the first email, 5 against 4, is the proof that follow-through beats reach. Get the four parts right on a small, triggered list before you scale anything. On a lean team the specific human line is what earns the reply, not the send count.
The European read: In smaller, fragmented markets your account count is lower and word travels fast, so a wide generic blast burns names you cannot afford to burn and reads even flatter in a buyer’s second language. A tight, triggered sequence in each market is how a lean team lands where volume bounces.
Do first: Pull your live outbound sequence and read step one against the four parts, personalization, problem, solution, low-friction ask. Every part missing is your rewrite list.
Do this week: Cut your send list to only the accounts with a real trigger this week, a funding round, a hire, a launch, a product change, and add the same-thread nudge if your sequence has no bump in it.
Do this month: Rebuild the first touch around one specific detail per account, and set the trigger rule your list is built on, so specific and triggered is the default, not the exception a top rep makes by hand.
The rule: If the first line could go to any account on your list, you have volume, not a sequence.
You know it worked when: Reply rate on the reworked sequence climbs, and the same-thread nudge starts out-replying the first email.
The play: 5 steps to build a cold outbound sequence that earns replies (2026 series). Rebuilds the first touch around structure and a real trigger, so more sends stop being the only lever. Best for 2-5M teams scaling outbound across markets.
Sources: 30MPC, “The 30MPC Outbound Sequence Part One: The First 3 Emails” (July 28) · Pierre’s Content Guides, “7 Infographics for your 2026 marketing strategy” (July 30)
Problem 2: Your worst-fit accounts eat the capacity you keep trying to hire
Hakan Ozturk named the account every CS org privately knows should be cut but never formally decides to: the chronic bad-fit customer whose true cost hides across four budgets. The CSM hours, the custom eng builds, the escalations, the roadmap slots it displaces. None of it is ever totaled next to the ACV, so the account survives review after review. Eddie Reynolds supplied the other half of the math. Rep and CSM capacity is finite, roughly 200 accounts per person per year, so every hour spent on a money-loser is an hour stolen from an account that would grow. Put the two together and the move is clear. Total the cost to serve next to ACV, build the list of your 3 most expensive accounts rather than your 3 biggest, and make the exit, contain, or invest call. That frees the capacity you keep trying to buy with another hire.
My take: Headcount is not capacity. Before you add a seat to cover the load, prove the team you already have is aimed at the revenue you already own. Customer success is a growth engine, not a cost center, so an account that drains it is a growth problem, not a service ticket. Here is the honest exception, because I run this at sub-5M too: you can keep one money-loser on purpose, but only against a named reason, a marquee logo, a reference you can quote, a case study you are actively building, and only with an expiry date on that grace. What you cannot do is let it survive review after review because nobody put the cost next to the ACV.
The European read: In a smaller market your logo count is lower, so one chronic money-loser is a bigger share of a CSM’s book and a bigger drag on the quarter. You cannot out-hire the drain either, because hiring is slower and more expensive here. Protecting finite capacity for the accounts that expand is the operating model, not a nice-to-have.
Do first: List your 3 most expensive-to-serve accounts, CSM hours plus eng asks plus escalations, next to their ACV. The ones costing more than they pay are your list.
Do this week: For each of the 3, make the call in writing, exit, contain, or invest, and if you keep a money-loser, name the logo or reference reason and the expiry date on it.
Do this month: Build cost to serve next to ACV into your account review, so a money-loser gets flagged on structure, not on whoever complains loudest.
The rule: Capacity is finite. An account that costs more than it pays is stealing from one that would grow, unless you keep it on purpose, with a named reason and an expiry date.
You know it worked when: Your CSMs get hours back and point them at the accounts with real expansion, and no chronic money-loser survives another review unnamed.
The play: 5 steps to cut the accounts that cost more than they pay (2026 series). Totals cost to serve against ACV and forces the exit, contain, or invest call, so capacity moves to accounts that grow. Best for 2-5M and 5-10M teams tightening retention economics.
Sources: The CS Cafe, “The account everyone knows is already gone (cost to serve)” (July 26) · GTM AI Podcast, “Your Pipeline Is Lying to You. AI Won’t Fix It.” (July 30)
Problem 3: Your targeting runs on triggers that do not predict closed-won
The base your outbound stands on is not the email, it is the list and the trigger behind it. Jordan Crawford put a hard number on how bad most of that base is: of 1.6 million datasets tested for outbound signal, only 12 survived as useful. Almost every trigger teams build lists on is noise that does not correlate with anything that closes. A bigger list, or a smarter tool that finds more triggers, just scales the noise. The fix is a human-craft one: treat your ICP as a filter, not a slide, and validate every trigger against your own closed-won before it earns a place in the sequence. The teams that grow rank accounts on signal, not size, and the signal has to be one that actually predicts a deal.
My take: I have watched teams build a 5,000-account list and call it pipeline. A list is not pipeline. A ranked list built on a trigger that correlates with your closed-won is. My rule is simple: no trigger enters the sequence until someone has checked it against last year’s won deals. Most do not survive that check, and cutting them is the cheapest lift in outbound, because you stop paying to send to accounts that were never going to buy. Signal, not size, and the signal has to earn its place.
The European read: The trigger 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. If you import one trigger set across your countries you scale the noise faster. Validate the trigger against closed-won per market, not once for the whole region.
Do first: Take your top 5 outbound triggers and check each against last year’s closed-won. The ones that do not correlate are your cut list.
Do this week: Rebuild this week’s list on the 2 or 3 triggers that actually correlate, and drop the rest, even if it shrinks the list.
Do this month: Set the standing rule that no trigger enters the sequence until it is validated against closed-won, and validate it per market, not once for the region.
The rule: A bigger list is not more pipeline. A trigger that does not predict closed-won is noise you are paying to send.
You know it worked when: Reply and meeting rates climb on a smaller, triggered list, and you can name why each account is on it.
The play: 5 steps to raise win rate by ranking accounts on signal, not size (2026 series). Ranks accounts on a trigger validated against closed-won, so the sequence runs on signal instead of a bigger list. Best for 2-5M teams tightening targeting across markets.
Sources: On the Edge by Blueprint, “1.6 Million Datasets, 12 Survived” (July 25)
Save this. 3 GTM execution problems from this week’s signal, injected with the sharpest expert thinking, reframed for a European operator, each with a move you can run today and my own take from the trenches.
Send it to 1 founder or GTM operator scaling toward 10M in Europe who reads everything and ships none of it.
Steal this move: Fix the base in 4 weeks
The number 1 move is the pipeline truth test, so here is the hero play in full. It fixes your forecast first, then builds the other 3 competencies, outbound, retention, and targeting, on the same 4-week arc.
Play: 5 steps to cut the dead deals your forecast still counts, “5 steps to cut the dead deals your forecast still counts (2026 series)”
Fixes: A forecast padded with deals that died in place months ago, so the number misses and nobody saw it coming.
Best for: 2-5M and 5-10M, any motion, and the European reality of a lower account count where one misread deal is a real dent in the quarter.
The 5 steps (over 4 weeks):
Week 1, set the line: compute your win cycle from 2 quarters of closed-won, the median days-to-close, then set the death line at twice it, per segment.
Week 2, strip it: age every open deal against its segment line, pull each one past it out of the commit, and total the stripped value as your real exposure.
Week 3, fix the next base: rebuild one weak fundamental, the outbound sequence, the worst-fit accounts, or the targeting triggers, on the same honest read.
Week 4, route and repeat: move stripped deals to a dated re-engage lane, keep only the ones with a live champion, and set the Monday ritual that re-ages the pipeline.
Standing: report the stripped total next to the committed number every week, so a padded forecast never hides again.
Template: A 1-5 forecast-health rubric. Rows: aged against win cycle not stage, no deal past twice the cycle in commit, stripped total named, re-engage lane dated, re-aged weekly. Score your pipeline 1-5. Anything under 3 is this week’s work.
Paste this into your AI:
Here is my closed-won export and my open pipeline: [paste]. Compute my win cycle as median days-to-close by segment, set the death line at twice it, and age every open deal against it. Strip every deal past the line, total the stripped value, and re-forecast the survivors weighted by stage age times velocity. Then show me the gap between my padded number and my honest one.
Full play, template and workbook inside GTMcraft OS. Reply or DM me to get access.
Also on the radar
Elena’s Growth Scoop, “So, you want to be a content creator?” (July 28). External voice is real pipeline, and Elena Verna is honest about the cost too, the harassment, the burnout, the loss of narrative control. Name the 1 ICP problem you could credibly own in public, and write one post on it this week.
Lenny’s Newsletter, “11 products I love, free for a year” (July 28). The biggest Product Pass expansion in 2 years added 11 tools, useful as a stack-refresh sourcing list. Audit 1 gap in your lifecycle stack against it.
Kieran Flanagan, “Use AI to Craft Slop Free Content” (July 31). A Bynder blind test found 56 percent preferred AI copy until told it was AI-written, then engagement dropped. Before you scale any drafting, blind-test your last published post on 3 colleagues.
Three questions for the room
What is your real pipeline after you strip every deal older than twice your win cycle?
If you totaled cost to serve next to ACV, which 3 accounts are costing you more than they pay?
Which of your outbound triggers actually correlate with closed-won, and which are noise you pay to send?
What is your number 1 takeaway this week? Reply or send me a DM.
Go deeper with GTMcraft OS
Scale on plays and skills, not prompts.
You do not need another newsletter, podcast or LinkedIn post.
You need the system under it.
Read the plays. Every single play is free and live in GTMcraft OS on Notion. Click through from any edition.
Build your own. GTMcraft OS members connect the full libraries, 100+ plays plus 100,000+ LinkedIn, newsletter and podcast signals, straight into their own AI or Claude context, so their team builds on the whole corpus instead of one-off prompts.
The single plays are free to read. Wiring the whole corpus into your own operating system, and keeping it current, is what the membership gives you.
Master your human GTM skills AI can’t replace inside GTMcraft,
Koen
Your (human) GTM Agent
PS. Co-written by Wispr & 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.