← Contents01 / 20

Module 1 — Orientation: What GTM/RevOps Actually Is

"Sales, Marketing, and Customer Success are three drunks fighting over one goddamn steering wheel, and RevOps is the sober, shaking bastard wedged in the back seat screaming directions nobody asked for into an abyss. Buckle up or get the fuck out." — overheard from an operator, parking garage, 2:14 a.m., smelling of cold coffee and moral collapse

We were somewhere around the third board deck when the dread took hold — really got its claws in, somewhere between the "hockey-stick growth" slide and the "conservative scenario" that assumed seven miracles and a strategic act of God. The slides said hypergrowth. The CRM said nothing real had closed in nine days. The VP of Sales said trust me — which in this business is a full fucking confession. And somewhere in a Slack channel nobody monitored, a $40,000 deal was quietly dying of neglect: unrouted, unloved, composting in a queue named Leads_New_FINAL_v2 like a corpse in a bureaucratic swamp. That deal didn't have to die. Nothing in that room had to happen the way it happened. That is why this manual exists — so you stop making the same stupid, expensive, avoidable mistakes that every goddamn SaaS org has made since 2009 and will keep making until the machines take over and do it worse.

HOW TO USE THIS THING (Terms of Engagement Before We Proceed)

This is a field manual. Not a memoir. Not a TED talk. Not a fucking LinkedIn carousel with a "dropped this framework on my CEO and she cried 🙌" caption. It is an operational handbook for building, staffing, and running a B2B SaaS revenue machine — for real, with real math — narrated by someone who has survived a dozen go-to-market death marches and emerged on the other side: paranoid, overcaffeinated, and, crucially, correct.

  • Who this is for: The first-time VP of Sales who just got handed a Number and no plan and a 90-day runway before the board gets nervous. The founder who refuses to stop selling because he genuinely believes no one else on earth can do it. The Head of RevOps drowning in a Frankenstack of thirteen tools that all claim to be the source of truth and are all lying. The CRO who suspects — correctly, always correctly — that the forecast is a hallucination built from hope and Excel macros. Anyone who has to make revenue happen on purpose instead of by accident or force of cosmic personality.
  • How to read it: Modules are sequenced to build a revenue org from zero. Read them in order the first time. After that, raid it like a tactical field library. The module on forecasting is Module 13. Do not skip to Module 13 before understanding why your funnel is a crime scene. The modules build on each other like load-bearing walls. Knock one out and the building falls on someone.
  • What the voice is: Profane. Paranoid. Occasionally savage. Genuinely afraid of the board and of the machines and of the $300,000 mis-hire in Month 4. Ignore the cursing if you must. Do not ignore the frameworks. Every numbered list in here is correct. I checked. My attorney checked the parts that could get us sued. He billed $4,200 for the privilege and then told me the clawback language was still too soft. He was right.
  • My attorney appears throughout this manual to dispense legal and financial guidance that is either deranged or disturbingly accurate. You will not always be able to tell which. Neither can I. This is part of what makes B2B SaaS so goddamn frightening.

RULE No. 1: The plan you write down beats the genius you keep in your head, because the genius quits, gets poached, has a breakdown, or simply relapses — and the plan stays on the shared drive, patient and indifferent.

THE JOB — What GTM and RevOps Actually Are (the unvarnished shit)

Go-To-Market (GTM) is the entire apparatus by which your company locates human beings who have money and problems, convinces them to trade that money for some relief from those problems, and keeps them pacified long enough to do it again next year. That is it. Strip away the Patagonia vests, the standing desks, the kombucha on tap, the "customer journey mapping workshops," and the guy in Product who keeps calling sales calls "learnings" — and what you have is: find them, win them, keep them, grow them. Four verbs. Every other word in your GTM strategy document is furniture.

The machine that executes those four verbs is the revenue engine, and it has three combustion chambers that are perpetually on fire in slightly different ways:

  1. Marketing — manufactures attention and demand. Feeds the top of the funnel with humans who might buy. Is constantly fighting about whether a "Marketing Qualified Lead" is a lead at all or a warm body who clicked on a webinar invite by accident.
  2. Sales — converts attention into signed contracts and cash. Closes. Is constantly fighting about whether Marketing's leads are garbage (they often are) and whether the CRM is someone else's problem (it isn't).
  3. Customer Success (CS) — keeps the money from leaving and convinces it to bring friends. Retains and expands. Is constantly fighting about whether Sales lied to the customer during the deal (they sometimes did) and why everyone else treats CS like the complaint department.

In a healthy org, these three hand the customer down a single continuous assembly line: a stranger becomes a lead, becomes an opportunity, becomes a customer, becomes a renewal, becomes an expansion. One smooth, humming motion. One bloodstream.

In an unhealthy org — which is to say, every org you will ever fucking work in — these three become warring tribes who do not speak the same language, do not share the same scoreboard, and would each, privately, prefer to watch the others humiliated at the all-hands. This is not a personality problem. This is not a "culture problem" you can fix with an offsite and a trust fall. It is a systems problem and it has a specific, identifiable, fixable cause.

Why the tribes fracture (the original sin — you caused this)

They fracture because you paid them to. Each tribe is measured on a different Number, and those numbers conflict by design, and then you act surprised when the tribes are at war. Let me walk you through the crime:

  • Marketing is paid on volume and cost — MQLs generated, pipeline sourced, cost-per-lead. So Marketing optimizes for quantity, fires a fire hose of half-qualified garbage over the fence, calls it "strong top-of-funnel momentum," and goes back to designing the next campaign.
  • Sales is paid on closed revenue, right fucking now. So Sales cherry-picks the three leads that look good, ignores the other 900 as "not ready," and screams into Slack that Marketing leads are a joke and also can someone please fix the routing in Salesforce because three deals just fell into a black hole.
  • CS is paid on retention and renewal. So CS resents Sales for closing a customer at the wrong price point with features that don't exist yet, resents Marketing for calling it a "partnership," and quietly starts a document titled "Deals Sales Should Not Have Closed — 2024 Edition" that is now 47 pages long.

Now add the definitional schism and you've got a full catastrophe. Ask three tribes what a "qualified lead" means and you get three answers, four arguments, a cross-functional Jira ticket, and a meeting to schedule the meeting where they'll disagree about it. Marketing's MQL is Sales's spam. Sales's "committed deal" is CS's "lawsuit waiting to happen." Nobody agrees on what a Stage 3 opportunity actually means, so the funnel is measuring vapor and calling it data. When definitions diverge, the data becomes fiction, and you are now forecasting fiction to a board that will fire you for it. They won't fire you for the fiction — they'll fire you when the fiction stops matching reality, which it always does, and always at the worst possible time.

THE PLAYBOOK — What Alignment Means and What RevOps Actually Owns

Let's be very clear about what alignment is, because every conference speaker and every guru selling a $3,500 course has turned it into mush. Alignment is not a feeling. It is not the vibe at your revenue kickoff. It is not the emoji-filled Slack message after the ski trip where Marketing and Sales "finally got on the same page." Alignment is mechanical: the three tribes share one funnel, one set of written definitions, one dataset, and one set of mutually-reinforcing incentives, so the customer experiences one company — not three feuding departments who've been cc'ing each other on complaints.

You build alignment with four hard artifacts. Build them or stay fractured forever:

Step 1 — Write the goddamn funnel definitions. Every stage — Lead, MQL, SQL, SAL, Opportunity, Closed-Won — gets a written, enforced definition with exit criteria: the specific, verifiable thing that must be true for a deal to advance. "I feel good about this one" is not an exit criterion. "The economic buyer attended a demo and verbally confirmed budget before Q3" is an exit criterion. This is not bureaucracy. This is your company's immune system against bullshit.

Step 2 — Write the SLAs between the tribes and make them hurt. Marketing commits to deliver N qualified leads of defined quality per month. Sales commits to work every routed lead within a defined window — because speed-to-lead is not a preference, it's a religion, and the data on response decay will horrify you (Module 10 is the wake-up call on this). Sales commits to a clean handoff packet to CS at close, because dumping a confused, over-promised customer on CS with a "good luck!" is not a handoff, it's an act of aggression. These SLAs are written. They are inspected. They have consequences. An SLA without teeth is a polite suggestion, and polite suggestions do not close revenue gaps.

Step 3 — One source of truth, or die arguing. A single CRM-and-warehouse stack where every tribe reads from the same numbers. Yes, this is partly a myth — the single-source-of-truth is always under construction, always partly wrong, always three schema migrations away from coherent. You fight for it anyway. You fight for it because the alternative is three disconnected dashboards, a board meeting where Marketing and Sales present different pipeline numbers with equal confidence, and a RevOps analyst crying quietly into her laptop at 11 p.m. trying to reconcile the gap. That analyst is the RevOps Martyr. You've met her. She's holding the whole operation together with VLOOKUP and spite. (Modules 5 and 19 are her bible.)

Step 4 — Make the incentives stop making the tribes enemies. Pay Marketing partly on pipeline that actually closes, not raw MQL volume — otherwise you're subsidizing spam. Pay Sales something on first-year retention, not just bookings, or they'll sell anything to anyone and leave CS to clean up the wreckage. Pay CS on net expansion. Compensation is culture wearing a spreadsheet, and if your comp plan says "I don't care about anything except this one metric," your people will optimize for that one metric and burn the rest of the building down. (Module 8 goes deep on this. It will make you uncomfortable. Good.)

So what the hell does RevOps actually own?

Revenue Operations (RevOps) is the unified operational function that runs the plumbing under all three tribes so the engine fires as one goddamn machine instead of three separate machines that occasionally crash into each other. It exists because somebody has to own the system — the whole system — instead of arguing about whose silo is most important. RevOps owns five things. Memorize them or tattoo them somewhere you'll see them on bad days:

  1. PROCESS — The documented workflows of revenue: lead routing, deal stages, approval chains, forecast cadence, handoffs, renewals, offboarding, everything. RevOps designs these, writes them down (they must exist as documents, not as tribal knowledge in one analyst's head), and enforces them with teeth. If a process is not written, it does not exist. If it is not enforced, it does not work.

  2. SYSTEMS — The tech stack. CRM administration, the tool sprawl, integrations, automation, the cursed Salesforce custom fields nobody remembers creating (Stage_REAL__c, Close_Date_ACTUAL__c, IsThisARealDeal__c). RevOps is the architect and the janitor of the Frankenstack simultaneously. Every "quick tool" added without RevOps approval is a debt accruing interest in the dark. Module 5 is the reckoning.

  3. DATA — Definitions, hygiene, dashboards, the warehouse, reporting, the endless, Sisyphean project of making numbers mean the same thing in every room. RevOps decides what an MQL is and then defends that definition against a Marketing team that wants to lower the bar and a Sales team that wants to raise it. Somebody has to hold the line. (Module 19 is about the tarpit under all of this.)

  4. PLANNING — The quantitative spine of the whole operation: quota and capacity modeling, territory carves, comp design, headcount math, the forecast, the scenarios the CEO needs for the board. RevOps does the arithmetic that the leaders are too busy to do correctly, and then RevOps gets blamed when the arithmetic predicts something inconvenient. This is the job. Do not be surprised by it. (Modules 6, 7, 8, and 13 cover this in the detail it deserves.)

  5. ENABLEMENT — Equipping the reps to actually execute the motion: onboarding, methodology rollout, playbooks, training, tooling adoption. Sometimes this lives in a sibling function. It is always a RevOps concern, because a beautiful process that reps don't follow is not a process, it's a decoration.

RULE No. 2: If two functions are fighting over a seam between them, the seam belongs to RevOps. Stop refereeing the people. Fix the fucking machine.

HOW IT GOES TO HELL (it will; know the patterns)

The Founder Who Still Thinks He's the Best Salesperson In The Building refuses to define a process because "process slows us down and kills the hunter instinct" — and also, privately, because a defined process would reveal that his gut-feeling deals take four times longer and discount twice as deep as the ones he's not personally involved in. He built the first ten logos on force of personality and a refusal to sleep. His gut does not scale to forty reps across three time zones. When he finally hires RevOps, eighteen months too late, the CRM is a crime scene with three duplicate contact records for every account and close dates set in months that have already passed. We will charge him accordingly.

The VP of Vibes — a sales leader who manages entirely by adrenaline, hope, and a Patagonia vest with a startup logo nobody recognizes — runs the revenue org on feel. Ask him for the source-of-truth pipeline number and he opens three dashboards that disagree, picks the highest one, forwards it to the board with a cheerful subject line, and then vanishes before the questions start. This is how careers end, publicly and expensively. The board does not forget. The board is a long-memory creature in a nice blazer and it is always, always watching.

The RevOps Martyr silently holds the entire machine together with MASTER_do_not_touch_v7.xlsx and the kind of institutional knowledge that lives only in one person's head and disappears when that person finally breaks down and takes a vacation. Nobody thanked her. Nobody gave her a seat in the strategy meeting. She is the single point of failure for the company's ability to know whether it is making money, and the company treats her like a spreadsheet. When she quits — and she will quit — the forecast ceases to exist for two weeks. She will be replaced by a contractor who charges three times as much and knows nothing. You did this.

The Guru — say, Chip Brennan, three million LinkedIn followers, $4,000 online course, author of Align and Thrive: The Revenue Mindset Playbook — tells you that "alignment is a mindset, and the mindset is the mission." Chip has never written an SLA. Chip has never configured a lead routing rule. Chip has never sat in a pipeline review where Marketing and Sales had different numbers and a board meeting in 48 hours. Chip is a content business wearing a sales-leadership costume, and his course is going to cost you six months of misaligned metrics and a lot of arguments that could have been resolved by writing a three-sentence definition of what a fucking MQL is.

FIELD RULES

  1. You don't have a Sales problem, a Marketing problem, or a CS problem. You have a revenue-engine problem. Diagnose the whole machine or you'll fix the wrong part forever.

  2. Whatever you reward, you get more of — including the dysfunction. Conflicting metrics manufacture warring tribes. Fix the metrics, not the morale. No offsite has ever fixed a misaligned comp plan.

  3. A definition everyone disputes is worse than no definition at all. Because it produces confident, false data that everyone presents to the board as if it means something. Define the funnel in writing. Enforce it. Fight for it at every QBR.

  4. RevOps owns the seams: process, systems, data, planning, enablement. Give it teeth, a seat at the strategy table, and a budget, or watch the engine seize and your best operators burn out holding it together with duct tape and resentment.

  5. Alignment is mechanical, not emotional. Off-sites don't align orgs. Shared funnels, written SLAs, and incentives that don't make the tribes enemies — those align orgs. The kumbaya comes after the systems work. Not before.

It is 4 a.m. and I am staring at a dashboard that says we are at 142% of pipeline coverage and a CRM that says half those deals have close dates in a month that ended six weeks ago. Both files are, according to their respective owners, "the source of truth." Somebody is going to present one of them to the board on Tuesday. I have poured the coffee. There is no one else in the building. The machines are running. Pour yours. We start at Module 2.