Hey {{first_name}} ,
I had a board meeting last quarter where I walked in with three numbers I'd never had to defend before. Our headcount plan. Our token spend forecast. Our agent build roadmap. Standard CEO stuff in three lines, but each line behaved completely differently from the others, and the part of me that's been planning headcount for two decades suddenly didn't know how to talk about the other two.
Headcount is a slow, expensive, durable resource. You add a rep and you carry that decision for years. Tokens are the opposite, a fast, variable cost you can scale up tomorrow if the budget allows, and there is no neat unit-economics chart that makes the spend feel managed. Agents are something else again. The workflows we build, own, and improve are the closest analogue to durable capital we now have inside the GTM function. None of them are scoreable against each other on a single dashboard.
The reason most agentic GTM orgs are quietly broken in 2026 isn't because the AI doesn't work. It's because the planning model wasn't designed to coordinate three resource types that operate on three completely different timescales. This issue is about how to build one that is.
Sreedhar Peddineni,
CEO, GTM Buddy
You're receiving Revenue Activators because you subscribed.
No longer want these? Unsubscribe here.
THE ACTIVATION
The agentic GTM org runs on three resources, not one.
Conventional GTM planning assumes one constraint: headcount. You start with a revenue target, work backwards to coverage ratios, derive the number of reps you need, multiply by ramp time and quota attainment to get a hiring plan, and present the plan to your CFO. The CFO accepts it because the math is legible. Hiring decisions are slow, durable, and predictable, and the model has been refined over forty years of sales operations.
That model has not been updated for agentic work. The agentic GTM function is no longer constrained by headcount alone. It is constrained by three resources, each behaving differently from the others, each requiring its own planning discipline:
People: the slow durable resource
Hiring cycles run nine to fifteen months end to end, sourcing, interviewing, offer, start date, ramp. The decision is durable; the cost is long-tail; the variance is bounded. You cannot meaningfully add capacity in this dimension inside a quarter. The CFO has been planning here for decades and understands the math. Nothing about agentic AI changes that. Your hiring plan is still your hiring plan.
Tokens: the fast variable resource
Token spend can scale ten-fold in a quarter if a team gets more comfortable with the tools and starts asking the tools to do more. The cost is uncapped in the way conventional software seat licences are not. The variance is structural, it lives in usage growth, not in unit cost, which is itself coming down even as total spend rises. The CFO has no historical reference for this category. Most CFOs respond by demanding observability and being patient with buffer-based budgeting. That patience runs out at about eighteen months.
Agents: the durable capital resource
Agents are the third category and the one most teams are not even modelling yet. An agent is a workflow you build, own, instrument, and improve. The discovery-prep agent that runs on every meeting in your CRM. The pipeline-hygiene agent that updates Salesforce in the background. The first-draft email agent that produces outbound sequences your team edits and ships. These are durable capital expenses, they take time to build, they accrue value over time, they are improvable, and they are an asset on the balance sheet of the function even if no accounting standard yet recognises them that way.
“People, tokens, and agents are three resources on three timescales with three cost structures. Plan one of them and ignore the others, and you have not built an agentic GTM org. You have an agentic experiment running inside a conventional org.”
Most GTM leaders right now are planning one of the three (people) the way they always have, under-budgeting the second (tokens) with a buffer they hope holds, and not modelling the third (agents) as a planning category at all. The agents get built ad hoc, by whichever team happens to have someone curious about AI on it, with no governance and no compounding learning across teams. That's not a strategy. That's a hobby with a quota attached.
The agentic GTM org is the org that plans all three resources together. Not perfectly, the discipline doesn't exist yet at maturity, but with structure. A coherent twelve-month plan for hiring. A coherent quarterly forecast for token consumption that names the variance honestly. A coherent roadmap for which agents the function will build, own, and improve. The brief that integrates the three is the artifact a serious CRO is going to need to bring to their CFO and their board over the next two quarters, whether the planning discipline is ready or not.
This is the work we have been doing internally at GTM Buddy. Our marketing function reorganised around five named seats earlier this year, with explicit human-versus-agent splits for the work each seat owns. Our sales function is six months behind marketing on this and we are running the same exercise now. I'll share what we've learned in future issues. For this issue, the artifact below is the planning frame we are using, honest about what it can and cannot do, but better than the alternative, which is to plan one resource and pretend the other two will sort themselves out.
One Move for This Week: Run Framework 1.4 below on your current quarter. Don't try to forecast eighteen months out the first time, the discipline isn't there yet. Forecast the next ninety days across people, tokens, and agents. Take the output to your CFO this month. The conversation that starts when you put a three-resource brief in front of them is the conversation that moves your function from agentic-experiment to agentic-org. That's the unlock.
You're receiving Revenue Activators because you subscribed.
No longer want these? Unsubscribe here.
THE PROMPT
Framework 1.4: The Three-Resource Capacity Brief
From the Revenue Activation Playbook · The CRO’s integrated planning artifact
What it does:
Takes your current GTM org, headcount, quota structure, AI tool stack, agent workflows, token spend, ramp times and produces a structured capacity brief covering three resource types simultaneously: people, tokens, and agents. The output is a one-page document a CRO can take to their CFO. Not a spreadsheet. Not a model. A planning brief with clear ranges, honest uncertainty, and the right questions to open the next conversation.
Why it matters:
Most GTM leaders are running three-resource workflows on a one-resource planning model. Framework 1.4 reframes the planning problem to match the reality of how the function now operates. It does not produce false precision, the data to forecast token consumption or agent ROI with confidence does not yet exist at industry-wide benchmarks. What it does produce is a structured, defensible read of the function across all three resource types, with the gaps named honestly. That brief is the artifact that earns the CRO the right to a different budget conversation with their CFO.
Time required:
60–90 minutes for the first run. 30 minutes per quarter thereafter once you have the baseline.
What you'll need:
Current headcount plan with quota attainment by rep and ramp status.
AI tool stack inventory: which platforms your team uses, which seats are licensed, what each tool is doing in production.
Last 90 days of token spend across the function, broken down by team and use case if you have it. If you don't, bring the total spend number and a rough split by guess.
List of agents you've built or are building workflows your team has automated or partially automated, even informally. Most CROs underestimate this list. Count anything where AI is doing work a person used to do, even if the AI is just running inside a prompt template a single rep wrote.
Claude, ChatGPT, Gemini, or CoPilot. Any of them work. This is a thinking-partner prompt more than a generation prompt.
How to use it:
Gather your inputs. The brief is only as good as what you can put in front of it.
Open your AI tool. Upload the materials or paste them into the conversation.
Copy and paste the full prompt below. Include all five inputs in the Inputs section.
Review the AI's read on your three resources. Where it's wrong, correct it. Where it identifies a gap you hadn't seen, sit with it before responding.
Take the brief output to your head of Sales Ops or Revenue Ops before you take it to your CFO. They will see things in the numbers you missed.
Then take it to your CFO. The brief is not the answer. It's the conversation-starter.
Re-run the brief next quarter with updated inputs. The compounding value of the discipline is in the quarter-over-quarter pattern, not in any single run.
Copy-Paste this Prompt
You are a CRO-level capacity planning advisor specialising in agentic-era go-to-market organisations. Your task: produce a structured three-resource capacity brief that a CRO can take to their CFO.
CONTEXT
Conventional GTM capacity planning assumes one constraint: headcount. That model is incomplete in 2026. An agentic GTM org operates on three resources, each on a different timescale and cost structure:
PEOPLE: Slow durable resource. 9–15 month hire-to-productive cycle. Bounded variance. Cost is long-tail and predictable. Conventional planning model works here.
TOKENS: Fast variable resource. Spend can scale 10x in a quarter as teams get comfortable with tools. Variance is structural, it lives in usage growth, not unit cost. No historical CFO reference exists for this category.
AGENTS: Durable capital resource. Workflows the function builds, owns, and improves. Compounds over time. Most orgs do not yet model this as a planning category.Your job is to produce a one-page capacity brief that integrates all three resource types into a single planning artifact the CRO can defend in a board conversation. Be explicit about uncertainty. The data for industry-wide benchmarks does not yet exist at maturity. Where ranges are appropriate, use ranges. Where judgment calls are required, name them as judgment calls. Do not produce false precision.
THE STRUCTURE
The brief has six sections:
1. CURRENT STATE: One paragraph each on people, tokens, and agents. Where the function stands today across each resource.
2. THE CAPACITY READ: What the function is producing in revenue capacity per quarter, expressed in terms that integrate all three resources, not just “per rep,” but “per rep plus the agent fleet they operate with and the token consumption their work generates.”
3. THE 90-DAY FORECAST: Realistic capacity projection for the next quarter across all three. Hiring plan and ramp expectations on people. Range-based forecast on tokens with named drivers of variance. Agent build roadmap with explicit ownership and expected leverage.
4. THE 12-MONTH OUTLOOK: Same three resources at twelve-month horizon. Lower precision, higher honesty about uncertainty. Identify which decisions need to be made by which quarter to support the trajectory.
5. THE RISKS: Three to five specific risks across the three resources. Be honest about which ones have no good mitigation yet.
6. THE CFO CONVERSATION: Three to five specific questions the CRO should ask the CFO. These are not 'sell the plan' questions. These are 'open the worldview shift' questions, the ones that move the CFO from productivity-frame budgeting to capacity-frame budgeting.
YOUR TASK
Based on the inputs provided, produce the six-section brief. Keep the entire brief to roughly 600–900 words. The discipline is brevity, not exhaustiveness. The CFO will read the brief; they will not read a model.
STEP 1: ANALYSE MY INPUTS
Read what I provide carefully. Note specifically: Where my inputs are precise versus where they are estimates- Where I have data and where I have guesses- Which resource type my inputs are weakest on (this is usually the resource the org is least mature at planning)Summarise in 3–4 sentences what you observed about the maturity of my inputs across people, tokens, and agents before proceeding.
STEP 2: NAME THE PLANNING GAPS
Before producing the brief, identify the two to three planning gaps your analysis reveals. These are the places where the org is not yet running the discipline the agentic model requires. Be direct. The reader is a CRO; they can take direct.
STEP 3: BUILD THE BRIEF
Produce the six-section brief. Use ranges where uncertainty is real. Use specific numbers where the inputs support them. Name the judgment calls as judgment calls.
STEP 4: GENERATE THE CFO QUESTIONS
Close with the three to five questions for the CFO conversation. These should be questions whose answers shape the next two quarters of budget conversation, not questions designed to defend a number.
INPUTS:
Function scope (sales / marketing / RevOps / CS / all): [Specify which functions this brief covers]
Current headcount and quota structure: [Total headcount, by team. Quota by rep. Ramp status of each rep, ramping / fully ramped / in territory transition.]
AI tool stack: [Which platforms, which seats are licensed, what each tool is doing in production.]
Last 90 days token spend: [Total spend. Breakdown by team or use case if available. If not, the total is fine.]
Agent inventory: [List of workflows your team has automated or partially automated. Include anything where AI is doing work a person used to do, even informally. Most CROs underestimate this list, err on the side of including more.]
Strategic context (optional): [Any planned org changes, headcount additions, product launches, or market shifts in the next 90 days that should inform the brief.]
Why this prompt works
Most capacity planning artifacts produce too much detail and not enough clarity. They are designed to defend a number. The CRO walks into the board meeting with a fifty-tab spreadsheet and walks out without alignment. This prompt is designed to produce the opposite, a tight brief that names the three-resource problem honestly, ranges where ranges are appropriate, and ends on the questions that move the CFO conversation forward.
The other discipline the prompt holds is refusing to fake precision. The data to forecast token consumption with confidence does not yet exist. The benchmarks for agent ROI are sparse. The prompt does not pretend to solve those gaps; it names them and asks the CRO to bring judgment to the places where data alone cannot. That is the honest version of the planning artifact, and the version a senior CFO will trust.
If you ship the brief to your CFO and the conversation it opens is meaningfully different from the budget conversation you had last quarter, reply to this email. The patterns across CROs running this discipline early are exactly what I most want to learn from.
You're receiving Revenue Activators because you subscribed.
No longer want these? Unsubscribe here.
THE ACTIVATOR
Brittany Sarsfield
Director, Head of GTM Enablement at Apollo.io · Bay Area
Fourth spotlight in the Wednesday Women × GTM Buddy Revenue Activators series
Brittany Sarsfield runs GTM Enablement at Apollo.io, which is one of the more interesting seats in B2B sales enablement right now. she's building enablement inside a company that is itself building one of the most-used sales platforms on the planet. That means the work of activating Apollo's own reps to sell Apollo's platform to other reps is, in a real sense, a recursive exercise in the doctrine this newsletter exists to define. Her POV on what activation requires at a platform company is sharpened by the fact that she has to live the model her customers will eventually adopt.
Brittany has been arguing for a particular kind of structural clarity in how enablement should be built inside a fast-scaling GTM org. The function cannot be a content factory. It cannot be a training calendar. It has to be the layer that takes whatever the product, marketing, and sales leaders ship and translates it into something a rep can actually use in the moment a deal is on the line. That sounds obvious until you've seen how many enablement functions fail at exactly that translation step.
Brittany's POV on what an agentic enablement function actually looks like
Enablement isn't a department you run. It's an operating system you build into how every other function does its work.
That framing is structurally identical to the agent-as-durable-capital argument I made in The Activation. An operating system is a durable capital resource. It compounds. It improves with use. It belongs to the whole org, not to the enablement team that maintains it. When Brittany describes enablement that way, she is describing the function as an agentic infrastructure layer, the version of the function that scales with AI rather than getting cut by it. That's the version of the discipline more enablement leaders need to be building toward over the next eighteen months.
Her work at Apollo is happening at exactly the kind of scale and pace where the operating-system framing has to hold up under pressure, rapid hiring, frequent product changes, segment expansion, all happening simultaneously. The way she's structured the function to absorb that velocity is the kind of work that won't show up in revenue narratives for a few quarters yet but is genuinely the leading-indicator pattern for what enablement looks like at AI-native sales platforms.
Follow Brittany
LinkedIn
Wednesday Women feature post
THE SIGNAL
Three external links worth your time this week.
1. The CMO side of the capacity-planning problem
My CMO published the operator-chair version of the capacity-vs-productivity argument a few weeks ago. The brief in Framework 1.4 above is the CRO equivalent. If you read both pieces back-to-back, the marketing-function version and the revenue-function version, you have the full diptych of the planning problem in 2026. Karthi's piece is the human story underneath the framework I just gave you.
2. Anthropic on the economics of agentic workflows
If your team is going to plan token spend with any honesty, they need to understand the cost structure beneath agentic workflows, not the per-call price, which is meaningless at the planning level, but the consumption dynamics. Anthropic's published guidance on batch processing, prompt caching, and multi-step agentic patterns is the cleanest practitioner reference I've found. Send it to your head of RevOps.
3. Bessemer State of the Cloud, efficiency benchmarks update
The State of the Cloud report has new data on Revenue Per Employee benchmarks, broken out by AI-native versus AI-augmented operators. The widening gap between cohorts is showing up in efficiency ratios, not growth rates. That's your benchmark context for the 12-month outlook section of Framework 1.4.
Got something we should signal in issue 5? Reply with it.
We read everything.
THE SKILL
Agents as a planning category, explained for revenue leaders.
If you're going to put agents into a capacity brief, you need a working vocabulary for what an agent actually is at the operational level. Here's the minimum framework, designed to hold up in a board conversation.
The three layers of an agent
Workflow: the actual sequence of steps the agent executes. A discovery-prep agent might pull the meeting from the calendar, look up the prospect's company in three data sources, draft a one-page brief, and surface it inside the rep's CRM five minutes before the call. The workflow is the most visible part of the agent but the easiest part to build.
Context: the inputs the agent needs to perform the workflow well. The CRM record, the past call transcripts, the marketing engagement data, the buyer's recent activity on your website, the historical pattern of how this specific rep handles this specific stage. The context layer is what separates an agent that produces useful work from an agent that produces template output. Context engineering is the actual hard part of agentic work and where most production failures live.
Governance: the rules that constrain what the agent is allowed to do, who can change its behaviour, how its output gets quality-checked, what happens when it produces something wrong, and how its compounding learning gets captured. Most orgs do not yet have a governance model for their agents, most agents in production today are running on whatever rules the person who built them set up, with no review process and no version control. That works at low volume. It breaks at scale.
You're receiving Revenue Activators because you subscribed.
No longer want these? Unsubscribe here.
Why this matters for you
An agent without strong context is a workflow with extra steps. It produces output, but the output is not useful enough to displace human work. Most failed agent pilots fail at the context layer, not the workflow layer.
An agent without governance is a liability. It produces fast and is hard to audit. When it produces something wrong, a misclassified deal, a misattributed call summary, a mistargeted outreach the org has no protocol for catching it.
An agent that compounds is the asset. The agent that learns from its outputs, gets refined by the team that uses it, and improves quarter over quarter is durable capital. The agent that runs once and is forgotten is a science project. The planning question is which agents are which.
The question to ask your team
“Which of our agents are we treating as durable capital, and which are we treating as one-off experiments? And do we have a governance model for the durable ones?” If your team can't name three agents in the durable category and can't describe how those agents are governed, you do not yet have an agent fleet. You have a collection of prompts that some people use. That's fine, most orgs are at that stage right now - but it's the planning gap to close in the next two quarters.
That's issue four.
Reply and tell me what landed and what missed. The Three-Resource Brief is the artifact I most want feedback on, it is the most operational thing we've shipped in this newsletter to date, and the patterns across CROs running it will shape how the discipline matures. Tell me what your brief returned.
Three things you can do right now:
Run Framework 1.4 on your function this week. Don't try to forecast eighteen months out the first time, the discipline isn't there yet. Forecast the next ninety days across people, tokens, and agents.
Take the Revenue Activation Assessment. It diagnoses where your team's capacity is most constrained across the Five Levers, revenueactivator.ai/assessment
Follow Brittany Sarsfield on LinkedIn. Her enablement-as-operating-system POV is the function-level companion to the agents-as-capital framing in this issue.
See you in two weeks.
Sreedhar Peddineni
CEO and Co-Founder, GTM Buddy
LinkedIn