101% NRR and a 6-figure true-up
What a comp leader, a founder, a CFO, and a CS operator all said this week about paying for the behavior you actually want.
Save this. 3 GTM 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, the play behind it, 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.
Applied GTM: Pay For Behavior - Wednesday July 15, 2026
People do what you pay them to do, not what your strategy deck says. That is the whole edition.
11 signals from 41 GTM newsletters and the signal databases. 3 problems. 1 playbook. Covers July 5 to 11. Read time ~7 min.
The 90-second version
Comp is the operating system for your GTM. Most teams build it last and blame it first. Show me the incentive and I will show you the outcome.
No one is paid to save the base, so it walks. Median private B2B net revenue retention has slipped to about 101%, barely above break-even.
A mis-hire and a slow ramp burn capacity you already bought. Every hire has 1 number that is their job. If it has not moved in 1 cycle, it will not.
The European read: one comp plan has to work across several markets with different deal sizes, and the base you already won in a country is your cheapest growth, so leaving the save unpaid is expensive twice over.
The thread: point the incentive at the behavior you want, or it quietly stops happening.
Read time: 7 min
This week’s number 1 move
Treat comp as the operating system for your GTM.
Brian Le scaled Notion’s sales comp from 80 people to over 400, and his framing is worth stealing: comp is the operating system for go-to-market. Most teams build it last and blame it first. It is the thing that turns your strategy into what a rep actually does. Jason Lemkin made the same point from the opposite end this week. He is churning off a vendor he was a founding reference account for, and the reason is the incentive, not the product. A discount would have kept him, but no one there is comped to save the account, so no one picks up the phone.
My take: I just spent a week where comp and ownership decided everything, the rep who owns his number versus the one who waits on my calendar. Your comp plan is the quietest instruction you give a team, and they follow it far more closely than any kickoff speech.
Start here: open your own comp plan and, line by line, name the single behavior each component pays a rep to do. Any line that does not map to a real priority this half is a leak, quietly teaching your team to do the wrong thing.
The rule: your plan is not a spreadsheet you true-up at quarter-end. It is the machine that decides what the whole team does all quarter.
Sources: GTMnow, “The Compensation Blueprint for a High-Performing Sales Team” (Jul 10) · SaaStr, “Should You Discount to Save a Renewal” (Jul 8)
Hi, it is Koen Stam and welcome to GTMcraft: The Future 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 scaling 0 to 10M+ ARR.
100,000+ GTM relevant signals from LinkedIn, Newsletters and Podcasts indexed. Translated into 100+ GTM plays 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 Room.
Problem 1: You run comp on a spreadsheet, and it is quietly degrading
Brian Le ran Notion’s commissions by hand across stitched-together spreadsheets before he automated them, and he is blunt that every comp plan lives on 3 inputs: pay mix, quotas and pay curves, and governance. When one stops talking to the others, the plan degrades. You see it first in the pacing, deals bunching at the end of the quarter, then in the distribution. CJ Gustafson tells the finance half. At a company going from 10M to 150M ARR, commissions ran out of 1 Excel tab, and it worked fine right until they hired into the plan. A few hundred reps on custom deals turned that tab into a 6-figure true-up that blew up the quarterly projection. Solve the manual thing before it gets huge, because “that will be a good problem to have” is how you pay for the mistake twice.
My take: I read pacing and distribution across markets every quarter before I read the payout. When deals bunch in the last 2 weeks or everyone is over 100%, the plan is talking, not the team, and I diagnose by segment before I touch anything.
The European read: one comp plan has to work across several markets with different deal sizes and norms, so it degrades faster than a single-country plan. Read the pacing and distribution per market, and fix by segment, not with a blanket change that breaks a country that was fine.
Start here: pull your last 2 quarters of attainment by rep and check 2 things: whether deals bunch in the final 2 weeks, and whether everyone is over 100%. Either one means the plan is off, not the team.
Do this week: map every line of your plan to the 1 behavior it pays for, and flag any line that no longer maps to a real priority this half.
Do this month: diagnose by segment and market before any change, and move the most fragile part of the plan off the manual spreadsheet before it becomes a grenade.
The rule: if everyone hits quota, the quota is wrong. If no one does, the plan is broken. Read the pacing and the distribution before the payout.
You know it worked when: you can name the behavior every comp line pays for, and deals stop bunching at quarter-end.
The play: 5 steps to pay for the behavior you actually want (2026 series). Wire each comp component to a named behavior, then read pacing and distribution before the payout. Get full access below ↓
Sources: GTMnow, “The Compensation Blueprint” (Jul 10) · Mostly Metrics, “Tactics for Budgeting at Hyperscale” (Jul 7)
Problem 2: No one is paid to save the base, so it walks
Jason Lemkin is churning off a vendor he championed for years, and his point is the incentive, not the product. Move your whole customer success team into sales, comp everyone on new logos and expansion, and the quiet work of pulling a wavering customer back belongs to no one. The number backs him up. Median private B2B net revenue retention has slipped to about 101%, barely above break-even, while companies above 120% trade at roughly a 63% premium. Hakan Ozturk shows where the save is actually decided, and it is at kickoff, not the renewal call. Most account plans get filled in once and never reopened, so the 500K renewal gets the same attention as the 20K one, and the exposure surfaces at T-14, the one week there is no room left to fix it.
My take: EB just hit 100% NRR for a full quarter on my team, and it happened because someone owns the base, not because the product got better. The renewal nobody is paid to save is the one you lose, and you lose it quietly.
The European read: in fragmented markets the base you already won in a country is your cheapest growth, cheaper than opening the next market. If no one in that country is comped to save it, it churns while you are busy chasing the new logo elsewhere.
Start here: list your 5 largest renewals in the next 90 days and, next to each, name the 1 person whose comp changes if it is saved. Every blank is unowned revenue.
Do this week: score every account plan and tier it by weight, so you see the dollars at risk before renewal season, not at T-14.
Do this month: put a real incentive on the save, so defending the base is someone’s paid job, not a task that belongs to no one.
The rule: if no one is paid to save the renewal, it is not being managed, it is just scheduled. Score the risk at kickoff, not at T-14.
You know it worked when: every top renewal has a named owner whose paycheck moves with it, and exposure shows up in week 1, not week 50.
The play: 5 steps to defend your NRR before renewal day (2026 series). Build a T-120 renewal board, score each account on hard signals, and trigger weekly saves before the base walks. Get full access below ↓
Sources: SaaStr, “Should You Discount to Save a Renewal” (Jul 8) · The CS Cafe, “The Success Plan That Survives a CFO Question” (Jul 5)
Problem 3: A mis-hire and a slow ramp burn capacity you already bought
Brian Le’s sharpest line is that a rep who quits over a broken plan is a capacity problem, not a payroll line. You lose every dollar you spent ramping them, then pay it again on the backfill. Jason Lemkin shows how to spot a mis-hire fast: every VP has 1 number that is their job. Revenue per lead and velocity for a VP of Sales, qualified leads for marketing, net retention for CS. If that number does not move in 1 cycle, it is not going to. Nick Cegelski shows how to protect the ramp: onboard in the order industry, then product, then sales, because under stress reps fall back on what they learned first, and they need the prospect’s world before the pitch. Pair every classroom hour with a doing hour so reps build real pipeline during ramp.
My take: I just closed a hire on exactly this logic, hire on the 1 number, verify with real work, ramp on doing. A mis-hire on a lean team is not a payroll line, it is a capacity hole you feel immediately and pay for twice.
The European read: a lean team spread across markets feels a mis-hire the week it happens, because there is no bench to absorb it. Ramp in the order industry, then product, then sales, so a new rep in a new country reaches real pipeline faster and you stop paying twice for one seat.
Start here: take your most recent leadership or rep hire and write the single number that is their job. Then check whether it moved in their first full cycle. If it did not, you have your answer.
Do this week: rebuild your onboarding in the order industry, then product, then sales, and pair every classroom hour with a doing hour on real pipeline.
Do this month: run 20-80 training after ramp: 1 skill taught in visceral detail each month, reinforced weekly with 4 real call or deal reviews, instead of front-loading 8 topics no one remembers by day 30.
The rule: every hire has 1 number that is their job. If it has not moved in 1 cycle, it is a mis-hire, and every week you wait burns capacity you already bought.
You know it worked when: your last hire’s 1 number moved in cycle 1, and new reps build real pipeline during ramp, not after it.
The play: 5 steps to ramp a new rep to real pipeline (2026 series). Onboard industry then product then sales, pair every classroom hour with a doing hour, and hire on the 1 number. Get full access below ↓
Sources: SaaStr, “What Happens When You Hire the Wrong VP” (Jul 6) · 30MPC, “How to Build a World-Class Onboarding Plan” (Jul 7)
Steal this move: wire your comp to the behavior in 4 weeks
Play: 5 steps to pay for the behavior you actually want (2026 series)
Fixes: a comp plan that quietly rewards activity you did not actually want, so the team does the wrong thing on Monday.
Best for: operators at 0 to 10M+ ARR running 1 plan across several European markets, where a blanket change breaks a country that was working.
The 4-week move:
Week 1, audit the plan. Map every component to the 1 behavior it pays for. Flag any line that does not map to a real priority this half.
Week 2, read the degradation. Pull 2 quarters of attainment by segment and market. Check for end-of-quarter bunching and everyone over 100%.
Week 3, own the base. Name the person whose comp moves for each of your top renewals, and put a real incentive on the save.
Week 4, protect the ramp. Write the 1 number for every recent hire and check it moved in cycle 1. Fix onboarding to industry, product, sales.
Template: a 1-line-per-component table: component, the behavior it pays for, the priority it maps to this half, keep or fix. Any component with no real priority is a leak.
Paste this into your AI:
Here is my comp plan by component and 2 quarters of attainment by rep and segment [paste]. For each component, name the single behavior it pays for and whether it maps to a priority this half. Then flag end-of-quarter bunching and any segment where everyone is over 100%, and list the 3 changes that would most cleanly point the plan at the behavior I want.
Full play, template and workbook inside GTMcraft OS. Reply to this email or DM me to get access.
Also on the radar
SaaStr, “5 Learnings from ServiceTitan at 1B ARR” (Jul 10): revenue grew 25% while sales and marketing spend rose 5.6%, and margin doubled. Put your revenue growth rate next to your sales-spend growth rate, and if spend is outpacing revenue, that is your leak.
PricingSaaS, “Inside Docusign’s Enterprise Credit Model” (Jul 10): Docusign moved enterprise pricing off seats to a credit model, charging nothing for search. Check whether your biggest account would pay more or less on usage than on seats.
3 questions for the room
Read your own comp plan line by line. Is there a single line paying for a behavior you do not actually want?
List your 5 biggest renewals. For how many can you name the person whose paycheck moves if the account is saved?
Name the 1 number that is the job for every person you hired this year. Any blanks?
What is your number 1 takeaway this week? Reply or send me a DM.
Go deeper with GTMcraft OS
Scale on plays, not prompts.
You do not need another newsletter, podcast or LinkedIn post. You need the system under it.
Read the plays. Every play, live and current, inside GTMcraft OS.
Download for your archive. Take the PDF or workbook offline.
Get the markdown. Drop the raw play into your own stack or AI tool.
Build your own. Use the GTMcraft Notion databases (100,000+ signals) to spin up a play for your exact motion.
The full Plays database is over 100 plays and growing every week.
Curious to see a sneak peek of GTMcraft OS, DM me or reply on this email.
See you inside GTMcraft OS, your GTM co-operator. Not another community.
Koen
Your (human) GTM Agent
