Sixty-Day Diagnosis, Three Options
Evaluate a business within a fixed window, then give executives three distinct paths rather than one recommendation: invest and bring in growth leaders, take it private with private equity, or sell to named acquirers.
Let the Incumbent Keep Its Category
When a competitor's brand is too strong to beat head-on, concede the business it is known for and take a larger adjacent pool of spend.
One-to-Many Partnerships
Instead of winning thousands of logos individually, integrate into a handful of key software platforms in the right industries, where you aren't competing against name brands, so each partnership reaches many potential customers.
Pipeline Coverage by Segment
Evaluate pipeline coverage separately for SMB, mid-market and enterprise, and read it alongside each segment's conversion rate rather than in aggregate.
Stage-to-Stage Failure Diagnosis
Know how much pipeline is in each stage and each stage's conversion rate, then ask why deals fail between specific stages, using MEDDPICC gaps to find the cause.
GTM Telemetry as a Gold Mine
Anthony's metaphor: investing in go-to-market without telemetry is like spending tens of millions on mining equipment with no idea what the machines are yielding.
The Founder-Led Snapback
After a raise, a company hires salespeople to replace founder-led selling, the founder's process fails to replicate, conversion falls, and the founder returns to selling to hit the committed number.
Data-Backed Scenario Reset
When the plan is out of reach, tell the CEO and board why you are in this spot and what happens if nothing changes, then lay out scenarios supported by historical data.
The Step-Out-of-the-Room Test
If you had to leave a sales presentation for an emergency, the colleague beside you should be able to run it just as you would, because the message is the same.
Hit the Number, Then Be Right About It
The most important thing in sales is hitting numbers. The second most important is being right about whether you will or won't.
Narrow Sales, Widen CS and Solutions
Give each go-to-market function a different focus mandate: sales narrows on closing, CS expands across clients and products, and solutions sits in the middle.
Play the Character
When a high-energy setting wears you down, decide on a character, which is yourself, and play that character rather than asking what you would do.
Three Messages and a Bridge
Before any interview or important conversation, decide on three things you want to get across, and for every question find a way to bridge back to one of them.
The Leader as Best SDR
With no SDR team, the revenue leader commits to being the team's best SDR, with leader-generated leads ideally covering half of each rep's number and the rep responsible for the rest.
AI Researches and Edits, Humans Decide
AI can do research and help edit, but the story and the ultimate decision should be made by a person.
The Bridge Is Creative
Use AI where the work is bounded by fixed functionality and packaged products, and keep the link between the solution and the client's business with the person who knows the client.
The Four Bets Behind Hathway's Turnaround
Four deliberate changes after the 2016 layoff: narrow to one industry, take only revenue that can be a going concern, invest in proprietary IP, and rebuild the sales narrative around speed to market.
The Going-Concern Revenue Test
Before taking an engagement, ask whether it can become an ongoing investment for the client, ideally one that generates measurable revenue, so the work can stack and scale instead of ending in a cliff.
Reference Architecture With Perpetual Licenses and Retained Customizations
Build a core code library every engagement starts from, license it to each client perpetually without transferring ownership, and keep the rights to client-funded customizations so the IP grows with every engagement.
Sell Speed, Not the Agency
Replace a credentials pitch with a narrative about the buyer's market that makes time to market the deciding criterion, then win on that criterion.
Niche by Where Your Buyers Gather
A niche is narrow enough when your whole marketing budget can reach it through the same events and partners. If a second segment would need different trade shows, wait and expand into it later as an adjacency.
Three-Tier Partner Model
Tier one partners go to market with you and get major conference investment; tier two get quarterly business reviews, account planning and close sales relationships with little investment; tier three are utility tools worth including but not strategic.
Utilization-First Capacity Planning
In a services business, manage to utilization as the master metric and plan capacity from pipeline scenarios, hiring lead time and ramp time so supply matches demand.
Intentionality, Presence and Forcing Functions
Instead of chasing work-life balance, plan the limited time you have at home as deliberately as your work week, be mentally present in it, and use systems and rituals so you don't have to rely on discipline.
Blind, Not Bad: The Finance-Built Forecast
A forecast built by finance without a bottoms-up roll-up from the field may land on the number, but it can't explain churn, downsell, where deals are being won or what is happening with customers.
RevOps as the Interpreter Between Sales and Finance
Revenue operations sits alongside finance and translates sales data into the financial plan that rolls up to the board, and also supplies the metrics leaders use to coach.
Order System vs. Forecasting System
If reps enter opportunities only once they know they have the deal, the CRM is recording orders, not supporting a forecast.
Susan Rothwell's Change Management Playbook
Start with strategy and the outcomes you want, explain the why, write a communication plan and an input plan, give frequent transparent updates, and iterate, including admitting when a call was wrong.
What Is Old Is New Again, With a Twist
There are only so many ways to organize a team. Returning to an earlier model is fine when it carries what you learned from the detour.
The "If You Were in My Role" Question
End every roundtable or listen-and-learn by asking: if you were running sales and CS, what one piece of advice would you give yourself?
The Curated Feedback Loop
For a specific change, pick a cross-functional group with mixed experience and backgrounds, have a neutral leader run it with senior leaders absent, script what you need from it, respond openly, then have members collect feedback from their own teams.
AI Strategy, Training and Governance Before Experiments
Give the organization an overarching AI strategy (purpose, approved tools, intended uses), basic training such as prompting and limiting context, and governance, instead of leaving everyone to work it out.
How Would AI Do This, Not How Would AI Fix This
Before applying AI, ask whether the process is right. Design from the AI lens (how AI would do the work) rather than the current-process lens (how AI could patch it).
Codify Definitions, Name an Owner, Get Agreement
Write down what each term and KPI means, such as new logo, win rate, MQL, bookings and ARR, assign an owner, and get everyone at the table, finance included, to agree, even when the definition is a compromise.
Consultants Advise, Operators Decide and Live With It
Use outside firms for outside thinking, unbiased data analysis and challenge to your org design, but keep the change management plan and the decisions in-house, because the operator lives with the results.
Same Engine, Different Map
Frontier AI models are a Formula One engine every company rents on equal terms. Competitive advantage comes from the map, a company's own definitions, owners and connected data, not from horsepower.
Go-to-Market Yield
Measure the revenue a go-to-market organization produces per unit of what has already been spent on it, and improve it through conversion and cycle time rather than new headcount, pricing or leads.
The Semantic Layer (GTM Brain)
A company's business logic written down in plain English in one place AI can read: what win rate means, how bookings are counted, what qualified means.
The One-Owner Rule
Every metric gets exactly one owner, a named human rather than a team: whoever has to defend the number in the board meeting.
The Context Graph
The connections between a company's data: contracts to the right opportunities, to the right accounts, with the right people on them.
Humans Write the Logic, AI Writes the YAML
Never let the model author business logic. People write definitions in plain language and AI converts them into structured formats such as YAML.
Monday: 20 Definitions, 20 Owners, 20 Sources
A zero-budget start: write down the 20 definitions every reported number depends on, put one name against each, and write down where each number comes from.
The Three Pillars of a Turnaround: Culture, Structure, Operations
A CRO coming in from the outside to turn around a revenue organization has to get three things right, in order: culture first, then structure, then operations.
2X2Y
A north-star vision to double the size of a business (2X) over two years (2Y).
Lead From the Front
Senior leaders go to customer meetings, ask the tough questions and learn the customer and the data firsthand, without overshadowing the account owner.
Outrun the Slowest Camper
You don't need to be a buyer's top priority, only above the line of what they will actually fund this year.
Stop at Yes (There Is No Such Thing as Yes Plus)
Once the buyer says yes, stop selling. Continuing the pitch can only add reasons to reconsider.
"What Would Be the Reason It Doesn't Close? What Else?"
A revenue-call technique: for each deal, imagine looking back at month-end after it failed to close, name the reason, then keep asking "what else?" until every risk is on the table.
The Light Factory
Trying something new and paying attention to the team can lift performance even when the experiment itself fails.
People Respect What You Inspect
The metrics a leader visibly inspects are the ones the team respects and moves.
RevOps: Telemetry First, Then Conversion and Velocity
Anthony Enrico's way of grouping RevOps work: first, GTM telemetry (can you measure what you report to the board?); after that, every project should improve conversion rate or velocity.
Defend and Grow, Plus Greenfield
Split the revenue team to match a keep-grow-add strategy: one team defends and grows the largest and mid-sized customers, another hunts new logos.
The Comp Plan Is the Source of Truth on Strategy
Every behavior the strategy needs should be economically incentivized, so a rep unsure of the strategy can read it from the comp plan: if it pays you, do it.
Align on Contracts, Then Publish One Number Weekly
A two-step fix for competing ARR numbers: get sales, founders, finance and RevOps in a room to decide how real contracts count, then produce that ARR every week from a single trusted source.
Ramping Contracts: Step Up and Call It Expansion
For a multi-year contract with an escalating price, report each year's value as ARR in that year and treat the increases as expansion revenue, rather than averaging or reporting the final-year value up front.
Trailing Three Months Times 12
A starting rule for annualizing uncommitted usage revenue: average the last three months, treat it as MRR, and multiply by 12, then refine using the business's own usage patterns.
Value a Zero-Commit Logo by Precedent
For an enterprise deal closed with no committed spend, estimate ARR by applying the realization rate and rollout time of comparable past customers, then make that number a company-wide delivery commitment.
Pay on Commit, Estimate Variable, True Up
A sales comp structure for variable revenue: pay simply on the committed amount, pay on a data-backed realization rate for the variable portion, and later true up or claw back against actuals.
Three-Out-of-Four-Quarters Kicker
A year-end bonus of an extra 5% for reps who hit quota in at least three of four quarters, designed to reward consistent attainment rather than one big quarter.
The Revenue Engine and Its Check-Engine Lights
Go-to-market as an engine fueled by marketing and SDR dollars: the fuel has to match the engine, and much of RevOps' and finance's work is diagnosing warning lights quickly.
Two Models, Meet in the Middle
Run annual planning with two parties building separate models, one bottoms-up and one top-down, then reconcile the differences and agree a plan with the sales leader in the room.
Count the Pilot, Footnote the Pilot
During a fundraise, a paid pilot can be included in ARR as long as the amount that is pilot and not fully committed is disclosed in a footnote.
The Finance Team of One
Run startup finance as one leader on a trusted, integrated stack, with selective outsourced help and AI handling analysis in the background.
The RevOps Payback Floor
Whatever a company spends on RevOps, the team should at least pay for itself annually — through reduced expense, a more productive sales team, or better decisions from better reporting.
Capability-First Team Design
Size a RevOps team by the capabilities the business is missing, not by a target headcount.
Don't Peanut-Butter Spread the Plan
Aim a finite go-to-market budget at the specific places with the most defensible return instead of spreading it thinly across every product, segment and team.
The Power of One Percent
Small percentage improvements in conversion or retention, applied to a large go-to-market base, are worth more than they look — and small slips cost as much.
Plant Yourself Smack in Between Everything
The route from RevOps to the C-suite: own the reports and the numbers, and be able to explain how A connects to Z across every function, until you are a required seat in executive meetings.
Ask In, Then Debrief the Board Meeting
Two ways a RevOps leader earns a board-meeting invitation: ask to sit in once trust is established, and debrief every board meeting with the CRO to prepare for the next one.
Raise Your Hand When Change Is Occurring
C-level seats tend to open during transitions and turmoil; the people who get them keep doing good work, build relationships, and volunteer when the moment comes.
Carrying the Bag Without a Quota
A strong RevOps leader already carries the number in practice — at the CRO's hip, crossing the T's on every deal — even if the comp plan never had a quota.
RevOps Runs the Cadence (Dress Rehearsal for CRO)
The head of RevOps runs the pipeline and forecast calls in the CRO's stead, asking the questions the CRO would ask and taking the answers as the boss would.
From Your Own Story to Stories With Numbers
Build storytelling by first practicing non-business stories — your own career — with your team and your CRO, then turning that practice into telling stories with numbers.
The Personal Critical Event
In software there is no critical event that ages on its own, as a candidate on the job market does in recruiting. The seller must find one inside the buyer — ideally a personal stake, such as a promotion or the risk of being replaced — and keep every conversation anchored to it.
FOMU: Fear of Messing Up
The reason most enterprise deals are lost to no decision rather than to a competitor: the buyer isn't afraid of missing out, they're afraid of messing up.
Revenue Athletes vs. Chess Players
High-velocity sellers are revenue athletes: many at-bats, fast learning, losses that don't sting. Enterprise sellers are chess players: strategic, but without natural urgency, so they drift.
Diagnosis, Not Prescription
Take fear out of an enterprise deal by acting as an advisor who has seen this situation many times, rather than prescribing urgency or piling on ROI.
Stage Three: Say Three Things, Not Twenty
The pipeline bunches up at the technical deep-dive stage because sellers rush discovery and then hand the buyer everything. Slow down early, earn each stakeholder, and ration information stage by stage.
Mutual Close Plan and Power Chart
Tie the critical event to a date, work backwards through legal and every step to go-live, and turn the buyer's org chart into a power chart of influence and authority.
The Critical-Event Forecast Gate
No deal enters best case or most likely without a credible compelling critical event. If the event can move by weeks, it counts; if it can move by quarters, it isn't a critical event.
Our Forecast, Not the CRO Show
Present the enterprise forecast to the executive team as a shared call, asking for their read on each deal, rather than defending it as the CRO's own.
The Slack Deal Desk and Internal SLAs
RevOps as a systems-thinking force multiplier: replace long deal-desk meetings with a Slack approval flow, and measure the seller's own organization — such as legal request response time — not just the buyer.
Data Plus Story, With Measurement Gates
Data without a story gives people nothing to grab onto, and a story without data isn't relevant. Pair them, form several hypotheses, pick the one with the shortest learning cycle, and agree up front on the metric and the time horizon.
Listener and Scrutinizer Agents
An agent workflow that pairs a listener agent, which proposes updates from recorded calls and messages, with a scrutinizing agent that rejects weak items before anything reaches a human.
The TGI Fridays Menu: Less Is More
Curate choices down to a few. Buyers don't want more information; they want to make the right decision.
Horsepower vs. Context (F1 Car, Einstein, Usain Bolt and the Toddler)
Model intelligence and business context are separate problems. Vendors keep adding horsepower; only the company can supply the map. Anthony's summary: more horsepower won't build the map, more intelligence won't give you the context, and making Usain Bolt faster won't fix the toddler leg.
Every Day Is the Model's First Day
You are effectively hiring your AI models every day, and each day is their first. Without a persistent foundation, teams are stuck re-onboarding them over and over.
Maximize Yield From the GTM Machine
The most effective way to get more out of a go-to-market investment is to raise yield: increase conversion rates and reduce time in stage. Small gains compound, and they are the business case for investing in the data model.
The Context Graph (Start With the CRM)
Connecting the dots across and within systems, so the AI knows which records belong together when it looks at a person or account. The crawl-walk-run starting point is to make the CRM your first context graph.
Tokenomics: Output per Token
Measure AI by output relative to tokens spent, not by volume of usage, and design the data so agents can hop between connected records instead of indexing whole databases.
Never Let AI Author Your Business Logic
Humans write definitions in plain English. AI may format them (Google Doc to YAML to GitHub), but it must never decide what a metric or a good renewal means.
Boardroom-First Metrics and Ownership
Define first the metrics you'll have to defend in the board meeting this quarter, and make the owner of each metric the person who has to speak to it there.
The Data-Model Maturity Curve: Centralized, Resolved, Defined, Retrievable
A four-level progression. (1) Centralized: warehouse and BI layer in place. (2) Resolved: identities deduplicated to one canonical key per account across systems. (3) Defined: 20 to 30 key metrics defined, agreed and version-controlled, each naming the column and filters to use. (4) Retrievable: clean associations and distilled data give quick, cheap retrieval.
Data Model First, Agents Second
Build the data model once so any agent can run on it. Starting with the agent means reverse-engineering a bespoke data model for every agent you build.
The Ten-Week Roadmap and Five Roles
A roughly ten-week deployment staffed by five roles: an executive sponsor (usually the CRO, possibly the CEO), RevOps, an analytics engineer, a platform engineer, and whoever runs the CRM. More than half of the time goes to alignment before engineering and agent building.
Building the Car While It's Going 100 Miles an Hour
Hassan's description of RevOps at an early-stage hypergrowth company: building processes and systems while the foundations underneath keep shifting.
The Small Boat vs. the Cruise Ship
A smaller company is a small boat that is easy to steer, while a larger organization is a cruise ship that takes hours or days to change direction, so RevOps design has to match the vessel.
Ticketing Center vs. Strategic Partner
RevOps that agrees with everything a CRO says and executes is a ticketing center. Strategic RevOps asks why, explains the risks of a bad decision and offers alternatives that still reach the goal.
North-Star Revenue-Share Compensation
A compensation model for a business with no contracts, in which sales, post-sale and solutions engineers all take a percentage of each customer's monthly revenue for a year.
Predicting ARR From 60 Days of Usage
A prediction model that estimates a new customer's annual revenue from roughly their first 60 days of usage, trained on historical customer usage and adjusted for known seasonal patterns.
Top-Down vs. Bottoms-Up Quota Setting
Reconciling the top-down target investors set with a bottoms-up model of how many reps, and how much marketing coverage, are needed to hit it.
The Stage-by-Stage RevOps Org
Hassan's build order for the function: a generalist at Series A, a strategic leader with technical and analyst layers from Series B to D, and a specialized team after IPO.
Structured Chaos
The early-stage goal for RevOps: not to stop the chaos of a startup but to give it a method, so the environment is still chaotic but makes sense.
The Two Hires That Make a RevOps Leader Strategic
At Series B to D, the head of RevOps adds a technical persona and an analyst persona beneath them to absorb tactical work.
The Formula One Pit Crew — and Who Designs the Car
Sales is the driver everyone watches. RevOps is the pit crew doing unseen tire changes in seconds, and truly world-class RevOps also designs the car.
Agents Are Tools, Not the End Goal
AI agents should be evaluated against the same north-star metrics as any other investment, not by asking for the ROI of the agent itself.
The Context Layer
The knowledge of how the go-to-market systems actually work and how metrics are defined, which Hassan calls the most important piece of any AI deployment, and which sits with RevOps.
Confidently Wrong
AI deployed without RevOps governance makes disinformation faster: it returns a wrong answer with confidence, and that answer spreads.
Flip the Question: The Cost of Not Having RevOps
When a CRO asks what the ROI of RevOps is, reverse the question and ask what it costs to run a scaling go-to-market machine with nobody strategically designing, overseeing or managing it.
AI-Native GTM (working definition)
Agents running the work that used to be non-humanly possible — the analysis nobody had time for and the answers that took a data team three sprints — on demand, in plain English.
The Three Agent Plays
ICP analysis cross-referencing deal size, sales cycle and six-month retention; a messaging teardown against recorded sales calls; and a live pipeline diagnostic run inside the forecast meeting.
The Four Missing Things
Shared definitions, identity resolution, the plan, and memory — the four absences that make raw AI on a CRM return confident wrong answers.
Speed Is the New Moat
Competitive advantage comes from constant recalibration during the quarter rather than from headcount or tooling — discovering you were wrong while it can still be changed.
The Capital Clock
The roughly twelve-month window — eighteen at the outside — between a Series A closing and the company being back out raising, in which the outcome of the Series B is determined.
Instrument, Multiply, Prove
The three sequential builds that fill the Capital Clock window: instrument every motion before scaling it, multiply the performance of each motion with technology, then prove the result on a segmented scoreboard.
The GTM Brain
Three layers of context every go-to-market decision runs on: Performance (all GTM data normalised into one semantic layer and tied to goals), Market (ICP, messaging, market conditions), and Process (a living repo of playbooks, hypotheses and decisions).
Effectiveness Over Efficiency
Efficiency saves money by removing effort; effectiveness wins the market by lifting the win rate, conversion and performance of each motion. At this stage, only the second one matters.
The Segmented Scoreboard
CAC, payback, conversion and sales cycle reported by channel, by motion, by customer segment and down to the individual rep and CSM, rather than blended across the business.
The Two Flavors of RevOps
A split between back-office RevOps (systems, process, tickets, quota fixes — never touches the field) and field-operator RevOps (lives between the sales team and the machine, injecting value into forecast calls, campaigns, and programs).
Operating Cadence That Mirrors the Customer Journey
Build your internal operating rhythm around the four phases of how a customer consumes you — awareness, consideration & decision, implementation, and value realization — rather than around your org chart.
Enablement as a Competency Web (Zero-Based)
Staff sales enablement by treating every non-quota role (managers, RevOps, SEs, enablement) as overhead wrapped around a $1–2M-quota AE, and asking what each role gives back. Budget it zero-based and build it as a living sales academy, not a content factory.
The Span-of-Control Trigger for Enablement
Stand up formal enablement once a frontline manager's span of control passes five or six reps — earlier if you sell complex, enterprise, high-consideration products.
Hunter/Farmer in a Consumption Model
Split the field into hunters who acquire new logos (traditional sales path) and farmers who grow the install base aggressively, then engineer the bridge so neither feels the other is interloping.
Acquisition Is a Process, Not an Event
In consumption revenue, the signed PO is where the work starts. Because revenue recognizes on usage, the entire post-signature job is driving adoption and demonstrated value.
Don't Land at Scale (Lawnmower, Not 18-Wheeler)
Land small as a paid pilot, prove value fast, run a ~6-month 'double-tap' true-up, then bridge to the 12-month renewal — which is really the first real deal.
Consumption Quota Design
Acquisition and install reps carry different numbers; acquisition sellers ideally carry no consumption quota. Build a bookings plan for hunters and a consumption plan for farmers, layered with spiffs and target-incentive mixes.
Consumption Forecasting = Centralized Data Science (Owned by Finance)
Go-to-market gathers raw materials (account plans, commercial events, product releases, macro signals); a centralized data-science function owned by finance turns them into a forecast. Sellers cannot predict consumption.
Leverage vs. Trust
Leverage is forcing your way into the room by making leaders unprepared without you. Trust is being invited in because sales leaders want you there. Only trust builds durable influence.
On the Leadership Team, But Annexed From It
RevOps sits in a strange seat: reporting to the CRO but excluded from the CRO's peer conversations, while simultaneously knowing more than most of its peers and hearing things in rooms sales never enters.
AI Makes Humans Superhuman → More Hires, Not Fewer
AI is a productivity multiplier that requires clean data and human oversight. A productivity gain should be reinvested in more capacity to go faster, not banked as headcount reduction.
The First 90 Days: Absorb, Then Find the Truth
Spend the opening months of a new role absorbing information from two sources — the people on the ground doing the selling and implementing, and the available data — then marry those perspectives into a working theory of what's actually happening before setting priorities.
The Honest Plan: Missed Quarters Trace Back to a Planning Lie
When you miss a quarter, an intellectually honest post-mortem usually ties the miss to a planning or strategy assumption you weren't honest about — not to near-term deal execution.
Successful-Transaction (Outcome-Aligned) Pricing
Charge only when the AI agent completes the entire job correctly (e.g., reads and infers every field on a document 100% right), so price tracks roughly one-to-one with the value delivered.
Estimated ACV: Stacking Contracted + Forecasted ARR
Report usage-based revenue to the board by stacking two clearly labeled layers: contracted ARR ('take it to the bank') plus a conservative fraction of the forecasted amount booked as 'estimated ACV' (EACV).
Land Tight-Scope, Earn the Next Project
Start with a small, high-confidence use case you know you can nail, prove value fast, and use that win to earn the right to the next project — becoming the customer's primary consideration for what's next.
Use the POC to Close, Not to Sell
Qualify and sell the deal first, then run the POC only to confirm the solution works and the teams click — never as a desperate Hail Mary to generate intent that isn't there.
The POC Punch List
Before offering a POC, square away the MSA, legal and security, and budget, and get both IT and operations (the business side) at the table and excited. The POC then only validates the solution and the working relationship.
Post-Sales Joins Pre-Sales for Scoping
Have the implementation / agent-PM team scope the work during the sales cycle, so the buyer meets who they'll work with, gains confidence, and sellers can't over-promise.
The Plan as a Diagnostic (NUCO + Channel Model)
Build the revenue plan so every channel has its own win rate and ASP and new-logo ('NUCO') plugs the gap to the number — robust enough that a missed quarter can be traced to a specific assumption that broke, with leading indicators warning you a quarter or two out.
Top-Down Goal, Bottoms-Up Resourcing
Leadership sets a non-negotiable number; what's up for debate is only the resources required to deliver it. The exercise is iterative and cross-functional, and pairs with a proactive 'what would it take to 10x my org' model run before the CEO asks.
The Tripartite Sales Motion
Three sales processes run in parallel and then fused: win the fintech that wants a banking/card product, sign a sponsor bank willing to back the program, and marry the two under a single tri-party agreement.
The Give-and-Get Deal Model
Bake forecasting into qualification as a trade: the customer shares projections (customer counts, average spend) and in return receives a professionally built deal model showing how the program becomes profitable — one shared document both sides work from.
Sales Engineering as the Single Source of Truth
Use the sales engineer's solution document — effectively a statement of work — as the artifact that holds every party accountable to exactly what was scoped and approved.
The Build Order of GTM (RevOps First)
The sequence in which a founder should lay down go-to-market foundations — with RevOps placed effectively first, right after the first salesperson, before scaled AE or BDR headcount.
Segment-Based Planning
Treat each go-to-market segment (enterprise, mid-market, SMB, and their international variants) as its own line of business, with distinct product needs, marketing plan, ACV/LTV, conversion rate, sales cycle, and quotas.
Selling to the Blocker, Not the Champion
Identify and win over the people who can kill a deal — often someone you never meet, like compliance or a bank's board — rather than over-investing only in the enthusiastic champion.
Revenue Insights as a Service (5-Chapter Audit)
A recurring ~50-page audit that connects to the platform in two hours, looks back a year over won and lost deals, and reports across five chapters: sales-efficiency trend, win/loss analysis, live-pipeline risk, rep coaching gaps, and sales-process friction.
The CRO Dilemma
A CRO knows what to fix and even knows candidate strategies, then freezes — either because execution looks like an overwhelming amount of work, or from fear of taking a step back and breaking what already works. RevOps is where that freeze thaws.
Lead With an Opinion (RevOps' Information Edge)
RevOps shows up with a point of view on what the business should do rather than waiting for direction — enabled by an information edge, because the field shares candid feedback with the head of RevOps that it won't share directly with the CRO.
Continuous Planning vs. the Annual Sprint
Keep an annual anchor tied to strategic and fundraising commitments, but plan continuously: evaluate performance to plan monthly, decide on adjustments quarterly, and run a second-half replan as conditions change.
The Bi-Weekly Run-the-Business Meeting
A one-hour, bi-weekly meeting between RevOps and sales leadership, anchored on a fixed dashboard of five to eight initiatives, that serves as the catch-all forum for the business.
Measure Every Initiative in Isolation
Beyond standing metrics, instrument each strategic bet on its own — a spiff's multi-attach rate, deal progression past a stuck stage, or pipe from moved vs. unmoved accounts — so you can prove whether it's working.
What-If Territory Modeling
Data-driven modeling of territories across three lenses — firmographic (segment thresholds), 'smart plan' (balance by priorities like ARR or tier-A account count while minimizing disruption), and geography — layered with coverage, quota, and policy modeling.
The Gold-Mining Metaphor for Territory Planning
Run territory planning like a gold-mining company: first know where the gold is, then decide which miners to send where, and keep the operation flowing when a miner goes down.
Market Map (TAM Valuation per Account)
Survey your total addressable market and assign a potential revenue valuation to every account, then use that field to carve and balance territories so each seller has an equal amount of gold to mine.
Operate as a COO
The most consistent RevOps career path leads to COO; the way to grow toward it is to run RevOps today as if you already held the COO role — operationally minded, program-driven, and confident enough to lead the CRO.
The Three AI Products: Model, Consumer App, Agent Platform
Each major lab (OpenAI, Google, Anthropic) ships three distinct products: the model (baseline infrastructure — GPT-5.2, Gemini 3, Claude Opus 4.5), the consumer app (the browser chatbot for general-population Q&A), and the agent platform (for professionals to get work done).
Agent Platform vs. Consumer App: The Feature Divide
The capabilities that only agent platforms have and consumer apps lack: a persistent internal to-do list (so the agent works 10–40+ minutes autonomously), the ability to launch sub-agents, reading and writing files on your local machine, permission/plan modes, queued messages, and context compaction.
Agentic Prompt Architecture (Think Like a Strategist, Not a Chatbot)
A repeatable structure for building agent prompts: (1) supply context files, (2) instruct it to launch sub-agents, (3) have it maintain a to-do list, (4) tell it to be token-efficient, (5) direct it to write outputs to files, and (6) frame it to think like a strategist / thought partner.
The Token Window & Context Compaction
A token is the atomic unit of how AI thinks (~3–4 characters). The context window is finite working memory holding all inputs and outputs (e.g., 200K for Claude 4.5, 1M for Gemini 3); once full, the agent forgets earlier context. 'Compacting' summarizes the current context and hands it off to a fresh agent with a clean window.
Agent Skills (Download a Capability)
A skill is a folder of files that teaches an agent how to perform a task (make a PowerPoint, an SOP, a PDF, wireframes). The labs adopted a shared skills standard, so you can download skills from the internet or build your own and point the agent at the skill's path to execute it.
The Three-Step Agent Platform Setup
Getting an agent platform running in ~5 minutes: (1) download VS Code, (2) install the official Claude Code extension from Anthropic, (3) log in with a $20/month Claude subscription. Restart, click the orange icon, authorize, and the agent is enabled.
No Commitments / Everyday Renewals
A go-to-market model with no contracts and no renewals — pure pay-as-you-go, even on multi-million-dollar enterprise deals — so the customer can leave at any time and the company effectively re-earns the business every single day.
Big Ship vs. Jet Ski (and Working ON vs. IN the Company)
Anthony's framing for the startup-vs-scale-up choice: a big ship already has a direction and goes far; a jet ski is nimble and yours to steer. Oliver's corollary: at early stage you work ON the company (creating its DNA), and at scale you work IN it (executing).
ARR Without Contracts (Extrapolate + Project)
Define ARR by taking collected revenue and extrapolating it forward twelve months, then stacking disciplined, repeatable consumption projections — derived from a customer's telemetry data or their prior-vendor usage — on top of the extrapolated actuals.
Projected 'Synthetic ACV' Commission
Pay commissions up front on a projected ACV — the customer's estimated one-to-three-year spend — protected by security-margin haircuts, a two-person review of the estimate, a rep-adjustable projection, and a consume-to-earn provision that only fully vests the commission once the customer actually consumes.
The Comp Plan Is a Derivative, Not a Root Cause
A comp plan surfaces problems but rarely causes them. If deals collapse at scale, the root cause is bad hires or a product that isn't doing its job — not the incentive structure, which only mitigates or escalates the underlying issue.
SEALs, Marines, Infantry — Hiring in Waves
Staff a company in waves: SEALs first (operate confidently without supervision in uncharted terrain, mission evolves as they gather intel in the field), then Marines (build the foundation), then infantry (scale once the foundation exists).
Motivation vs. Morale
Motivation is why someone joined your cause — intrinsic, and not the leader's job to install. Morale is how someone feels in a given moment — situational, and squarely the leader's job to manage by supporting people through hardship without removing it.
Knowledge Management as the AI Unlock (Context Engineering)
The real leverage from AI isn't the model — it's the discipline of organizing and maintaining company knowledge so an agent has clean, current context to draw from, turning a one-hour subject-matter meeting into a five-minute prompt that's 95% right (plus a ten-minute human review of the output).
Remove Humans to Enforce Process
Since go-to-market process breaks whenever it depends on human compliance, the fix isn't more enforcement (mandatory fields, stage gates) but removing people from the data-capture loop entirely — letting AI listen and populate the system automatically.
Reps as Consumers of Data, Not Producers
Once AI captures CRM data automatically, the salesperson stops being a producer of data (data entry) and becomes a consumer of it — served a prioritized view of what's healthy, what's slipping, and what to work on next.
Crawl, Walk, Run Rollout
Adopt in stages: crawl (RevOps connects CRM, call recorder, Slack/Teams, and email, sets team structure and field mappings for a two-way sync), walk (auto-create and enrich records, remove humans from data entry), run (deal-health analysis, agents, and cross-functional data products).
The Two-Dimensional Deal-Health Map
Plot every opportunity on two axes: horizontal = how healthy the deal is (likelihood to win), vertical = how likely it is to close when the rep expects. The quadrants surface safe bets, acceleration opportunities (will close but not this quarter), and firm-decision-date deals where you may not be selected.
The Genie Agent (Context-Grounded Execution)
A full-reasoning agent wired to every captured touchpoint plus external research tools that executes deal tasks — building a custom ROI calculator to the prospect's own metrics, pulling industry benchmarks, and drafting the decision-maker email.
Promoter Score
A per-contact score from -10 to +10 that identifies champions and blockers at a glance, with the reasons and specific quotes behind each. Filtering contacts by ICP persona and a high promoter score produces a live, shareable list of advocates.
Listen to the Field, Not Just Customers (Go Where the Puck Is Going)
Product roadmap signal should come from live sales conversations with the market — use cases, friction, competitors mentioned — not primarily from customer success and existing customers, who are biased because their problem already feels solved.
High Complexity, Low Variability
RevOps problems are hard to solve but remarkably consistent across similar-stage companies — a Series B sales-led company has the same problems and the same fixes as its peers — which is why the function outsources well while sales and product must stay in-house.
Sales Velocity
A composite health metric combining the number of deals a rep works, the average deal size (ACV), the win rate, and the length of the sales cycle. Ebsta uses it to quantify the gap between top and average performers.
The Full-Cycle Seller
A seller who influences top of funnel, generates their own opportunities, and continues to own the relationship after the deal is signed — the opposite of the single-purpose-vehicle / hunter-farmer model where customers are handed from one specialist to the next.
Engagement Score (out of 100)
A relationship-health score built from observable transactions — meetings, email traffic (inbound worth more than outbound), and call data (longer calls worth more) — deliberately excluding intent and sentiment analysis.
Shallow vs. Deep ICP
The difference between a firmographic, one-line ICP ('Series A–C startups') and a layered one that adds persona, buyer maturity, investors, and growth rate — and never confuses ICP with TAM.
Written, Scored Qualification with Gates & Triggers
Requiring every opportunity to carry written, scored qualification, with explicit gates and triggers to move from one stage to the next — and not allowing sellers to skip stages or self-score their own qualification.
Qualifying Out (Fail Fast)
The top-performer discipline of converting the fewest opportunities out of discovery on purpose — ruthlessly killing deals that won't close so time and resources flow to deals that will.
The ARR Bridge
Model your target as current ARR + new ARR + expansion − churn/contraction. New ARR is new logos (and new contracts with existing customers); expansion and churn both come from the existing base.
Reverse-Engineered Growth Model (Top-Down + Bottom-Up)
Take the macro ARR goal and reverse-engineer it top-down through funnel metrics (net retention, SQL-to-close, sales cycle, MQL-to-SQL, average ACV) and bottom-up through the resources and team (CS capacity, quota/performance, ramp time, cost per SQL, salaries) required to hit it.
'Which Input Is Wrong?' Alignment Method
When executives challenge the outputs (reps, budget, pipeline required), don't defend the outputs — send them back to the inputs and ask which specific assumption they'd change: conversion rate, sales cycle, MQL-to-SQL, expected performance.
Sales-Cycle-Driven Pipeline Timing
Because deals don't close the month a lead arrives, the length of the sales cycle dictates when pipeline must exist. A two-quarter cycle means the pipeline for Q3 bookings has to be built in Q1.
Ramp Time ≥ Sales Cycle (Hire Ahead)
A rep is 'ramped' only when building pipeline and closing at full productivity — not when training ends. Ramp time should never be shorter than the sales cycle, which forces you to hire ahead of the number.
The Board's Unit-Economics Stress Test
The board evaluates the plan not as a sum of initiatives but as unit economics balanced against growth, judging whether the company can graduate to the next funding stage. If it fails that test, the CEO and CFO reject it back to you.
Grow Progressively Into Your Unit Economics
Because you invest in SaaS before results arrive, unit economics degrade when you invest and improve as ROI lands. Plan a trend that grows into the economics the board wants — not a perfect green line every quarter.
Benchmarks as Depersonalizers
Anchor and stress-test assumptions against VC/PE-published benchmarks (win rate by ARR band and deal size, quota-to-OTE ratios, funnel conversion rates) so the conversation becomes 'you vs. the market' instead of 'you vs. the person.'
The Living Plan: Scenarios, Live Progress-to-Target, Core vs. Bets
Replace the static spreadsheet with scenario modeling for sensitivity analysis, live progress-to-target reporting, a core-vs-new-bets split, and a daily sales-tracker email that becomes the company's single source of truth.
1% Better Every Day
There are no silver bullets. Compounding small, daily improvements — messaging, coverage, demos — is what drives real growth: 1% better every day is roughly 37x over a year, while 1% worse is a ~97% loss.
Zero → Foundational → Sprinting
A staged operating model for taking a company from nothing to a running revenue engine: first establish foundations and first principles, then instrument and stabilize, and only then layer in advanced and modern techniques (including AI) to sprint.
Build First, Then Ask Questions
On joining, learn the existing systems by using and pushing them to their breaking point, then ship a working V0/V1 before soliciting input — collaborating afterward to fill in scope and context.
The Three Pillars of the Modern Revenue System
A CRM-based revenue-intelligence system resting on three pillars: (1) volume/activity — meeting depth and self-sourced pipeline; (2) accounts — tiering and account quality; and (3) accuracy/validation — clean, correctly-tagged data with automated backstops.
The Data Skeleton (One Source of Truth)
A single consolidated system — often an automated spreadsheet with 50-60 metric tiles rather than a visual 10-12-metric dashboard — organized in three levels: North Star KPIs (board/investor), functional KPIs (six to ten per team, in lockstep), and hyper-specific activity metrics.
The Opportunity-Quality Gate
Measure sales on the inverse of marketing's volume: only opportunities that pass a hard gate from discovery into 'prove value' count — deals genuinely closeable, and closeable within the quarter — and marketing's targets are pegged to that same gate.
Hubs and Spokes (Custom Tools + Agent Missions)
Build custom, proprietary 'hubs' from scratch (e.g., in Replit) that solve a precise business problem and eradicate vendor spend; then transform their outputs into an agent-readable format (JSON) so agent 'spokes' (n8n, Manus, computer use) can run the downstream mission — with a human at the tail.
AI-First vs. Human-First (Two-Path Framework)
For any process, first ask whether AI can do the entire thing (path one: hardest but most efficient). If it can't be done cleanly, default to human-first with AI as augmentation (path two).
Salesforce as the Single Source of Truth
Consolidate every revenue signal — email and calendar from the mail server, conversation intelligence from calls, and CRM history — into the Salesforce opportunity, account, lead, and contact records, rather than scattering them across ten systems.
Relationship Score & Trend
A score, tracked over time, that aggregates communication frequency, depth, and stakeholder engagement across an account or opportunity to indicate the strength of the relationship and the likelihood the deal closes.
Benchmarking Against Won/Lost History
Use an organization's own closed-won and closed-lost deals to set benchmarks — time-in-stage, deal age, stakeholders per stage — then flag opportunities that deviate from what winning normally looks like.
AI Qualification Auto-Capture
Analyze call transcripts with AI to auto-populate a qualification framework (e.g., MEDDIC) — recommending a score per element plus supporting notes the rep can accept, edit, or ignore — without the rep manually entering it.
Deal Score (0-100)
A composite score where 0 equals closed-lost and 100 equals closed-won; it should rise as a deal moves through the pipeline and reacts to all positive and negative signals mapped against a 12-month benchmark of won deals.
BAMFAM — Book a Meeting From a Meeting
A selling discipline of always securing the next meeting while you are still in the current one, so an opportunity never sits without a scheduled next step.
Bottoms-Up Forecasting With Manager Override
Reps submit a data-backed forecast (pipeline / upside / commit) weekly; managers then submit their own adjusted view, hedging a rep's commit to upside when qualification is thin. Coverage ratios and pacing roll up by the Salesforce hierarchy.
Required vs. Actual Pipeline Coverage
Compare a rep's actual pipeline coverage (e.g., 6.8x) to the coverage they historically require to hit target (e.g., 3.6x) to decide whether they need more pipeline or should focus on closing what they have.
Data Foundation / Ontology Before AI
Treat the accuracy and structure of your underlying data — the ontology — as the foundation for any AI strategy, because AI is only as good as the data it can access, and swappable models matter less than the data feeding them.
The Morning Coffee Dashboard
A daily operator ritual: wake up and scan a set of dashboards the way a fan checks their sports team — is anything broken in Salesforce, is pipeline building as expected, which reps are up or down — paired with a heavy cadence of one-on-ones.
Sales Velocity & the Velocity Delta
Sales velocity = (number of deals x average deal value x win rate) / time to close, expressed as a normalized dollars-per-day contribution per seller. The velocity delta is the multiple separating top performers from B/C players (11x in the 2025 report).
The Bow Tie — Multi-Thread Both Sides
A view of the revenue motion where the left side is acquisition (lead to close) and the right side is post-sale retention and expansion. The insight: the right side must be multi-threaded and instrumented as deliberately as the left.
Time Kills All Deals (Days-in-Stage)
Compare the average number of days a deal spends in a stage when it wins versus when it loses. Once a deal exceeds ~14 days in a stage, win rate drops sharply; by four weeks it falls to about 5%.
Ruthless Qualification (Disqualify 30% at Discovery)
Top performers close off roughly 30% of opportunities at the discovery stage, refusing to advance deals that were never properly qualified on budget, stakeholders, timeline, mutual close plan, and security/legal review.
Benchmarks as Gates and Triggers
Quantify what top performers do (e.g., six engaged stakeholders and a finance persona above a set engagement score by stage two), visualize it simply, and enforce those benchmarks as gates a deal must clear and triggers that prompt sellers and managers inside the CRM opportunity record.
The People-Graph Data Engine
A machine that connects to email, calendar, and phone systems to reconstruct every customer relationship, create and maintain CRM contacts, score engagement out of 100 (with trend and relationship-owner), and write it all back to Salesforce automatically.
Expected (Estimated) Value
Sum, across all possible outcomes, of each outcome's probability times its value: EV = P(outcome1) x V(outcome1) + P(outcome2) x V(outcome2) + ... . A positive EV is a good bet; a negative EV is a bad one.
Thinking in Bets (Decision Quality vs. Outcome)
From Annie Duke's book: judge choices by the quality of the bet given what you knew, not by whether the single outcome was good or bad. A good decision can lose and a bad decision can win.
Kaizen (Continuous Decision Improvement)
A core value of Spencer's company: constant, incremental self-improvement — applied here to decision-making, by reviewing whether a choice had positive expected value regardless of how it turned out.
Pot Odds
The ratio of the amount you must call to the total pot you stand to win, expressed as the minimum win probability that justifies calling. Call $100 into a pot that becomes $400 and you have 25% pot odds.
EV-Weighted Segment Selection (Enterprise vs. Mid-Market vs. SMB)
Model each go-to-market segment as a bet: win rate (probability) times ACV (value) gives per-deal EV; then layer in deal volume, fully-loaded rep cost, and marketing cost to get the true expected value of investing in that segment.
White Space Scoring in the CRM
A calculated field in Salesforce or HubSpot — built from custom properties and workflows — that outputs how much a given account or open deal is 'worth' by expected value, so reps can filter to the highest-EV deals.
EV-Weighted Territories, TAM & Quotas
Build territories and quotas from expected value — TAM and account valuation weighted by expected conversion rate — rather than gross dollar value.
The 5 Things Every CS Ops Org Needs (plus a bonus step zero)
A build-from-scratch playbook for customer success operations: (0) Breathe and triage for impact; (1) Learn the lay of the land — roles, journey, and where time goes; (2) Bring in the right tech once the process is aligned; (3) Build KPIs and a customer health index; (4) Use the data to drive decisions; (5) Stay connected to the customer.
Adoption Is Not Health
High product adoption and green dashboards do not guarantee a healthy customer. A single metric (logins, courses created, items assigned) measures activity, not the value the customer is actually extracting.
Renewal Early-Warning Alerts (6 / 3 / 1)
Automated Salesforce alerts that fire at six, three, and one month before a renewal date, pinging the right people to confirm conversations have started, questions have been asked, and adoption is on track.
The CSP-Readiness Test
Three gates that determine when a company is ready to buy a Customer Success Platform: (1) established processes for outreach, QBRs, and handling at-risk vs. healthy accounts; (2) trackable product-usage data (e.g., via Snowflake or a BI tool); and (3) an inability to stay proactive by hand at leadership's bar.
The Customer Health Index
A composite health score that aggregates multiple signals — support (first-response and resolution times), satisfaction (NPS/CSAT), adoption, and usage — rather than relying on any single isolated metric.
The Three Partnership Metrics
A minimal scorecard for any partnerships team: (1) production to goal — pipeline sourced and revenue won, segmented by partner; (2) cost-to-carry ratio — fixed overhead plus variable cost per partner; and (3) cannibalization rate — direct deals that moved to a partner channel and what that cost.
Partner Production Goals (Reseller vs. Referral)
Set production goals both overall and segmented by partner, and match the goal type to the partner type: a channel reseller carries a closed-won production number, while a referral partner (or one that risks cannibalization) carries a sales-qualified-lead goal for leads handed to the sales team.
Cost-to-Carry Ratio
The cost of running the partnerships motion, broken into operational overhead you can't easily influence and the variable cost per partner — events, sales, marketing, and partner-manager resources — that you can, expressed against the production that spend generates.
Cannibalization Rate
The share of deals that would likely have closed direct but moved to a partner channel — tracked by counting opportunities already registered in the direct channel that shifted to a partner, and the discount or referral fee paid to do so.
The Integrated Operating Plan
The cross-functional plan RevOps builds and owns, tying sales, marketing, customer success, and partnerships to one set of goals — and the first thing you measure RevOps against by asking whether the teams are actually achieving it.
RevOps as a Service Team (Voice of Customer)
A structured feedback loop that treats the departments and individual contributors RevOps serves as its customers: weekly one-on-ones with functional leaders, an IC 'champion' for day-to-day signal, and a formal RevOps satisfaction survey sent to everyone served.
Funnel Metrics as the Objective Scorecard
The data-driven half of measuring RevOps: every operational initiative should show up as improving funnel metrics — rising conversion rates (e.g., SQL to closed-won) and falling cycle times — as a direct correlation to the work completed.
Marginal Gains (1% Compounding)
The idea that small adjustments to conversion-rate or cycle-time assumptions in a capacity plan or growth model compound into outsized, exponential gains as the business scales.
Risk Prevention: Days Since a P0
A defensive dimension of the RevOps scorecard that measures the issues the team prevents — for example, how many days you've gone without a serious priority-zero tech-stack incident or a serious data error in a board meeting.
On-Time, Under-Budget Project Delivery
Measuring RevOps's tactical and operational projects on budget and expected completion time — staying under budget and on schedule for work like a CRM implementation or a new set of board/offsite metrics.
Created Pipeline to Plan
Marketing carries a quota of sales-qualified leads and created pipeline, set jointly with sales and interlocked with the bookings and revenue plan on both volume and timing, then tracked per channel.
Channel Productivity & Efficiency
Judge every marketing channel by concrete dollar efficiency — cost to create an SQL and cost to create a closed-won deal — alongside the differences in deal size, conversion rate, and sales cycle by channel.
The Lead Impact Matrix
A 2x2 visualization that matrixes two channel metrics — most usefully conversion rate against production (volume) — to gauge the efficiency of each lead source and rank high- versus low-performers.
Weighted Pipeline Coverage
Coverage of pipeline to quota where each deal is discounted by a stage-based probability weight (ideally drawn from your own historical closed-won rates) plus a deal-health or subjective adjustment for finish-line risk.
SQL-to-Closed-Won Conversion Rate
The rate at which sales-qualified opportunities become closed-won, calculated only on closed deals (never open ones) and segmented by product, business unit, region, and firmographic segment.
Win/Loss Reason Analysis
Systematic review of why deals are won and lost, using close reasons that are relevant and actionable, then hunting for overall trends and anomalies that fail a common-sense check.
The Strategic–Tactical Toggle
The defining skill of a great RevOps leader: stepping in to get tactical for a specific business outcome when needed, then expanding back out to the overall strategy — while prioritizing the big-picture work.
RevOps as the Conductor (the Glue)
The VP of RevOps is the cross-functional glue — a conductor who plays no single instrument but keeps sales, marketing, CS, partnerships, finance, and product aligned and producing one coherent strategy.
The Annual Operating Plan (the Ops Super Bowl)
The VP of RevOps' single most important deliverable: a data-driven go-to-market operating plan — goals, assumptions, capacity planning — that is then monitored against actuals through the quarter and year.
The RevOps Operating Cadence (Annual → Daily)
A nested rhythm: annual planning; monthly plan/forecast tracking and internal board dry runs; weekly 1:1s with every functional leader; and a daily 'morning coffee dashboard.'
The VP-vs-Director Test
A blunt litmus test for the role: if you are not leading (not merely attending) the annual planning process and not in the board room, you're operating at a director level, not VP.
RevOps 1.0 vs. RevOps 2.0
A maturity model for the function. RevOps 1.0 is the tactical, reactive service center — implementing the tech stack, formatting sales calls, planning territories, comp plans, and CS playbooks, and managing requests. RevOps 2.0 is an internal management consultant that participates in corporate planning, sits shoulder-to-shoulder with finance on the board plan, and leads with insights and recommendations.
Closed-Loop Planning
A planning discipline in which the analyses behind each metric, the plan assumptions themselves, and actual performance against those assumptions are all kept visible and updated in real time — rather than being computed once for the annual plan and filed away until the next board meeting.
The Revenue Waterfall as a Living Input
The set of five or six drivers a well-built revenue waterfall contains — normalized prospect volume, sales cycle, time-based conversion distributions, close-won production, SQLs and MQLs — that you should have a pulse on at all times and be able to segment 20–30 ways (enterprise vs. SMB, region, product line, service center).
The Five Salesforce Foundations
A five-part checklist for a trustworthy CRM: (1) enable field history tracking, (2) timestamp critical stage and status changes with custom fields, (3) freeze closed-won data, (4) flow lead data into every object on conversion, and (5) put validation rules in place.
Field History Tracking
Turning on Salesforce field history tracking to record how data evolves over time, providing an audit trail for diagnosing issues and a historical snapshot for admins, users, and downstream tools.
Stage-Change Timestamps
Dedicated custom fields that capture the date each important status or stage changed — lead status, lead lifecycle stage, opportunity stage, customer stage, or proof-of-concept stage — so change data is directly reportable.
Freeze Closed-Won Data
Locking closed opportunity data so it can't be edited after the deal closes — restricting changes to a super admin and reinforcing it with validation rules, automation, and weekly backups.
Lead-to-Object Data Flow
Ensuring that when a lead converts, its important fields — lead source, lead source detail, owner/SDR, and lifecycle timestamps — carry across to the account, contact, and opportunity records.
Validation Rules That Match the Process
Rules that block records from saving unless they meet your business process — from simple checks (required amount, no past close dates) to methodology-driven requirements that ask for the right data at each stage.
The Two Flavors of Lying with Data
Misleading data comes in two forms: the deliberately or maliciously wrong (rare in business), and the unintentional kind, where someone tried to convey something reasonable but introduced biases in how they approached it.
The Chart Crime
A chart crime is a visualization designed to evoke a certain emotion — most often by manipulating the axes (a truncated y-axis, mismatched scales) so real data tells a dramatically different story than it should.
The Four Data-Literacy Checks
Anthony's closing checklist for reading any chart honestly: (1) look for cherry-picking and get a holistic view, (2) inspect the axes for alignment and scale, (3) widen the time series, and (4) layer in real business context tied to operating plans and outcomes.
The Two-Sided Cost of a Wrong Forecast
Forecasting too high pushes you to over-invest ahead of actuals; forecasting too low leads you to over-promise to the market and under-build the infrastructure to support the customers you win. Both directions carry catastrophic downside.
One Step Closer to the Truth
A forecasting philosophy that treats the forecast as an iterative pursuit of directional accuracy rather than penny-perfect precision — each cycle you layer on new information and methodologies to get one step closer to reality.
The Three Forecast Milestones
The three deal milestones that most reliably indicate forecast health: (1) entering the pipeline after real pre-qualification (confirmed intent and budget), (2) proposal/negotiation once commercials are being discussed, and (3) legal or executive approval once the deal leaves the champion for compliance and sign-off.
Completed-State Sales Staging (the LeanScale Method)
Name every pipeline stage after the action that has been completed — 'Negotiation Completed,' 'Proposal Sent,' 'Marketing Qualified Lead' — rather than an ambiguous noun like 'Negotiation' or 'Proposal,' so an opportunity's exact position is never in doubt.
Segment Before You Forecast
Break the pipeline into meaningful segments — deal size/tier (enterprise, mid-market, SMB), geography, product/use case, industry — and measure conversion rates and sales cycle within each segment instead of using one blended rate for the whole business.
Process Before Technology
Don't layer forecasting technology — including AI forecasting tools — until the underlying process (stages, entry/exit criteria, segmentation) is ready. Once the foundation is set, tooling can enhance accuracy; before that, it just automates a broken input.
ChatGPT as an Always-Available Pair Partner
Use ChatGPT as the technical collaborator you turn to when a human peer is unavailable — paste a broken formula or a stuck problem and get an immediate diagnosis and a testable fix.
Plain-English In, Working Config Out
Describe a Salesforce business rule in ordinary human language and let ChatGPT translate it into the validation rule or formula, then review the output for business context before saving.
Ask It What This Does (Translation Layer)
Paste an existing, complex formula and ask ChatGPT 'what does this formula do?' to get a plain-English explanation you can understand and pass on to others.
History Rhymes: The Email-vs-Paper Precedent
A mental model for reacting to disruptive technology: history doesn't repeat but it rhymes, and past waves (like email) augmented and grew work rather than eliminating it.
Expected Annual Contract Value / Expected Annual Recurring Revenue (EACV / EARR)
An informed estimate of what a usage-based deal will be worth over its first 12 months (or a chosen period), assigned even when zero dollars are contractually committed, so the deal can be reported, forecast, and managed.
Track Expected Value Against Actuals
A closed-loop discipline of tracking each deal's real consumption against its assigned expected value — daily, monthly, or otherwise, but at least through the first year — to see where estimates over- or under-called.
Data Baseline + Rep Judgment
A method for estimating expected value that starts from a data baseline — usage trends of similar companies and of a customer's first three, six, and nine months — then layers in rep discovery, safeguards, and discounts to land a defensible number.
The Commitment-for-Discount Trap
The anti-pattern of forcing usage into a committed contract by discounting the per-unit price — e.g., committing 25% of expected volume for a 10% price cut — to buy reporting predictability.