How I Build
Revenue Machines
A systematic framework for diagnosing, designing and executing scalable GTM operations — from first principles to full-stack deployment.
One question runs underneath all of it, and it is the one that survives every framework on this page: who owns this? Not who reports it. Not whose name is on the objective. Who owns the definition, the threshold, the handoff — and who owns the question of whether the thing should still exist at all. Almost every failure I have been called in to fix was an organization where the answer was nobody, and nobody had noticed, because a metric was green and a person was busy.
Which question have you
not answered yet?
A company’s stage is defined by the question it cannot yet answer, and by nothing else — not headcount, not funding, not revenue. Seven questions follow, in order, each with a test it is possible to fail. The first one you cannot clear is where the work is, and it tells you which two or three chapters below to read — whether or not we ever speak.
The Enterprise Journey
A company’s stage is defined by the question it has not yet answered, and by nothing else — not size, not headcount, not funding. A four-hundred-person manufacturer can be stuck on question two; a thirty-person software company can be genuinely working on question four. Mismatching the playbook to the question is the single most common reason GTM investment fails.
Demands: segmentation, value articulation
Demands: repeatable process, stage discipline
Demands: commercial planning, capacity design, forecasting
Demands: governance, data integrity, adaptability
The capability each phase demands has to be built during the phase before it, out of a surplus that is always already committed to something more urgent. That is the whole difficulty, and it is why sequence is harder to get right than strategy. Below, the seven questions in order — each with the test that closes it.
| Stage | The question | You have answered it when |
|---|---|---|
| Ideation | Is this worth solving? | You can name the reachable, monetizable, retainable, winnable population and its size — bottom-up, without a penetration percentage. |
| Product-market fit | Do customers care? | You can produce a fit table by segment, and at least one segment passes every test — for a reason someone other than the founder can state. |
| Early growth | Can we sell repeatably? | A median seller, following a written process, produces a result within 20% of their peers. |
| Scaling | Can we grow predictably? | Your week-four forecast error is under 10%, and every variance has a named cause. |
| Pre-public | Can we operate durably? | The machine survives a departure, a reorganization, a bad quarter and an acquisition. |
| Scrutiny | Can we withstand examination? | Any reported number is reproducible by two people from source, and every definition change is documented. |
| Public enterprise | Can we stay adaptive? | Your loop time is shorter than your market's rate of change, and someone owns the question of whether each control should still exist. |
The questions are a loop, not a ladder. A mature company re-enters at question one for some part of itself while answering question seven for the rest. Hold both — and do not collapse them into one speed.
Flying the Rocket Ship
While Upgrading Its Boosters
High-growth companies face a paradox: the momentum that creates opportunity also makes operational transformation dangerous. You cannot shut down to rebuild.
Core Challenges
- Revenue systems don't scale with business growth, creating hidden drag on performance
- Marketing, Sales, and CS operate in silos — data lives in disconnected islands, handoffs break
- Tech stack grows organically rather than architecturally, creating compounding technical debt
- Leadership makes decisions on incomplete or conflicting data, driving inconsistent strategy
Consequences If Left Unaddressed
- Forecast accuracy degrades — deals slip, quarters miss, credibility erodes
- Reps spend 40%+ of time on non-selling activities; productivity plateaus despite headcount growth
- Customer experience breaks at handoff points — churn creeps up silently
- Competitive disadvantage compounds as nimbler operators build the infrastructure you're still designing
"The solution isn't to stop flying. It's to build a methodology that upgrades systems in flight — isolating, testing, and deploying changes without disrupting the revenue motion already running."
Strategies for Growth
Revenue growth reduces to a single equation. Every operational intervention maps back to one or more of its variables — making prioritization rigorous rather than intuitive.
Increase Average Price
Pricing architecture, bundling strategy, upsell/cross-sell playbooks, expansion revenue motion. A 1% price improvement yields 10× the profit impact of 1% volume growth.
Reduce Average Costs
Process automation, tool consolidation, AI-augmented workflows. Cost reduction without capability reduction is the RevOps mandate.
Increase Quantity
TAM expansion, ICP precision, demand architecture, conversion rate optimization, retention and NRR programs.
Improve Conversion Rates
Funnel analytics, sales process reengineering, content/enablement alignment with buyer stages, deal inspection disciplines.
Accelerate Sales Velocity
Cycle time compression, proposal automation, CPQ, decision-maker mapping. Time kills deals — velocity is survival.
Retain & Expand
Onboarding, health scoring, QBR cadence, expansion triggers, churn prevention. Acquiring a customer costs 5–7× more than retaining one.
Operational Charter Kickoff
Every transformation starts with structured diagnosis. A 12-week charter gives leadership clarity on what exists, what's broken, and what to build — before a single tool is purchased or headcount added.
| Phase | Weeks 1–2 | Weeks 3–5 | Weeks 6–9 | Weeks 10–12 |
|---|---|---|---|---|
| Preparation | Stakeholder interviews (C-suite, Sales, Marketing, CS) Document current-state processes & org chart Audit tech stack & data architecture |
|||
| Assessments | Process scorecard (Awareness → Purchase → Use) Automation gap analysis Data quality & pipeline hygiene audit Benchmark vs. peer companies |
|||
| Opportunity Refining | Identify top 15–20 improvement opportunities Build ROI models for each initiative 2×2 prioritization: Effort vs. Impact Sequence quick wins vs. foundational builds |
|||
| Roadmap Development | Finalize 18-month implementation roadmap Resource plan & team design KPI framework & measurement plan Executive alignment & board presentation |
Tech-Enabled Improvement Journey
Process improvement without technology is theory. Technology without process is waste. Eight stages connect diagnosis to measurable outcome — each is a gate, not a milestone.
Key Principle: If the pilot doesn't validate the hypothesis, we return to ideation — not push to build. This prevents the most expensive failure mode in enterprise technology: building the wrong thing at full scale.
Process & Automation Scorecards
Scorecards translate subjective operational feel into prioritization data — surfacing where effort and investment will have the highest return. The value is not in any single cell. It is in imposing the same lenses on every area, so that “which of these is worst?” becomes a question you can actually ask.
Process Scorecard — Customer Journey
| Process Area | Awareness | Consideration | Purchase | Use / Expand |
|---|---|---|---|---|
| Lead Generation | 🔴 High Opp | 🟡 OK | 🟢 Good | 🟢 Good |
| Routing & Handoffs | 🟢 Good | 🔴 High Opp | 🔴 High Opp | 🟡 OK |
| Conversion Tracking | 🔴 High Opp | 🔴 High Opp | 🟡 OK | 🟢 Good |
| Content & Enablement | 🟡 OK | 🔴 High Opp | 🔴 High Opp | 🟡 OK |
| Reporting & Analytics | 🔴 High Opp | 🔴 High Opp | 🟡 OK | 🔴 High Opp |
Automation Scorecard — Revenue Stack
Show the full table — 6 rows
| Domain | Data Entry | Alerts & Routing | Reporting | AI / ML Assist |
|---|---|---|---|---|
| Lead Qualification | 🟡 OK | 🔴 High Opp | 🟢 Good | 🔴 High Opp |
| Opportunity Management | 🟢 Good | 🟡 OK | 🟡 OK | 🔴 High Opp |
| CPQ / Deal Config | 🔴 High Opp | 🔴 High Opp | 🟡 OK | 🟡 OK |
| Order Management | 🔴 High Opp | 🟡 OK | 🔴 High Opp | 🟢 Good |
| Post-Sales / CS | 🟡 OK | 🔴 High Opp | 🔴 High Opp | 🔴 High Opp |
| Structural Ops Support | 🔴 High Opp | 🟡 OK | 🔴 High Opp | 🟡 OK |
The Funnel Is Not a Funnel
A funnel implies buyers descend under gravity, and that your job is volume at the top and less friction below. They do not descend. They climb, and climbing costs them energy — so the job is to reduce the steepness of each step. That is a different job from the one most demand budgets are built to fund, and it is measured differently.
Market Sizing Hierarchy
Built bottom-up, with a named channel attached to the reachable layer. A top-down number with a penetration percentage on the end is a hope with arithmetic attached, and every plan built on it inherits the error.
Parallel Demand Tracks
The Climb — Five Buyer States
Most of the market sits at steps one and two, permanently. Most demand budgets are spent at step three, where every competitor is also bidding for the small share already in process.
Two models, two different jobs
| Funnel model | Ascent model | |
|---|---|---|
| Implicit physics | Buyers descend under gravity | Buyers climb, and climbing costs energy |
| Your job | Volume at the top, less friction below | Reduce the steepness of each step |
| What you optimize | Conversion between bands | Step transitions, and the cost of each |
| Failure mode | Buy more of the small share already in market | — |
Build the step table for your own company: what percentage of your target accounts sits at each step, and what percentage of your demand spend. It takes an afternoon and it is usually the most uncomfortable exhibit in the business. If more than half the spend sits at step three, cost per acquisition will rise every year regardless of how well the team executes.
The first-touch analysis
The single highest-return marketing analysis available to most companies, and almost nobody has run it. It costs a query and an afternoon.
- For every deal won in the last two years, find the earliest recorded engagement of any kind from that account, in any system
- Compute the time from that first engagement to the first sales conversation
- Report the distribution and the median — not the mean
- Compare the median against your attribution window
If your median is long and your attribution window is short, you are systematically defunding the activity that produces your revenue — and you will not find out for two years.
Holistic Customer Journey Blueprint
End-to-end visibility requires mapping every touchpoint across all GTM functions. The blueprint creates shared language and the foundation for multi-touch attribution.
| Layer | Pre-Sales | Awareness | Consideration | Decision | Onboarding | Adoption | Expansion | Re-engage |
|---|---|---|---|---|---|---|---|---|
| Buyer Actions | Problem recognition |
Search & discover Consume content |
Evaluate options Shortlist |
Champion internally Negotiate |
Implement Train |
Integrate Measure value |
New use cases |
Renewal decision |
| Marketing | ABM / ICP targeting |
SEO / Paid Thought leadership |
Case studies Webinars |
ROI calculators Battle cards |
Adoption content |
Upsell nurture |
Win-back campaigns |
|
| Sales | Sequence launch |
Discovery / Demo |
Multi-thread Proposal / POC |
CS handoff |
EBR / QBR |
Expansion proposal |
Renewal negotiation |
|
| CS | Success plan Kickoff |
Health monitoring Office hours |
Expansion CSM |
Renewal strategy |
||||
| Key Metrics | TAM coverage % |
MQL vol · CPL |
MQL→SQL · Pipeline $ |
Win rate · ACV |
Time-to-value |
CSAT · License util. |
NRR · Expansion ARR |
Gross retention |
Project Prioritization Framework
A 2×2 matrix plotting Business Impact against Implementation Effort separates quick wins from transformational rebuilds. With 20+ concurrent opportunities, sequencing is strategy.
Lead routing fix, pipeline hygiene, forecast templates, MQL definitions, KPI dashboards, rep scorecards
CRM rebuild, CPQ, revenue data lake, AI forecasting, CS platform, partner portal, pricing engine, territory model, comp redesign, onboarding automation, attribution model
Report cleanup, data enrichment, field standardization, documentation, QBR templates
Project ROI Model
Every initiative gets a business case before a single line of code is written. What follows is a worked example of that model — how an investment case is constructed, sequenced and defended when Finance asks where each number came from.
Impact by Program
- ↑ Win rate +8 pts → $22M
- ↓ Sales cycle −23 days → $14M
- ↑ ACV expansion +15% → $9.5M
- ↑ Rep productivity +30% → $5M
- ↓ CPL −35% → $4.2M
- ↑ MQL→SQL conv. +20 pts → $5.1M
- ↑ Attribution accuracy → $3.5M reallocated
- ↑ GRR +4 pts → $1.8M
- ↑ NRR expansion → $1.2M
- ↓ Churn → $0.7M saved CAC
Implementation Phasing
Transformation happens in waves. Each phase builds on the previous, with natural checkpoints to validate ROI before continued investment. Phasing also reduces change fatigue — critical for adoption.
Months 1–4
Months 4–8
Months 8–14
Months 14+
Discovery to Execution
Tool selection follows process design — not the reverse. The plan maps each initiative to a timeline and an enabling technology. Tools are assembled to the process, not the other way around.
Show the full table — 12 rows
| Initiative / Tool | Q1 | Q2 | Q3 | Q4 | Q5 | Q6 |
|---|---|---|---|---|---|---|
| Revenue Intelligence (Clari) | Deploy | Train | ||||
| CRM Rebuild (Revenue Cloud) | Design | Build | Migrate | Opt. | ||
| Integration Layer (MuleSoft) | Arch. | Build | Deploy | |||
| Outbound Engine (Apollo) | Config | Launch | ||||
| AI Productivity (Salesforce AI) | Pilot | Scale | ||||
| Lead Management (LeanData) | Deploy | |||||
| Marketing Analytics (Infinigrow) | Integrate | Model | ||||
| Social B2B (Oktopost) | Launch | |||||
| Gifting / ABM (Sendoso) | Activate | |||||
| Proposal Automation (Loopio) | Build | Deploy | ||||
| AI Conversational (Conversica) | Pilot | Scale | ||||
| Competitive Intel (Crayon) | Config |
Full Revenue Tech Stack by Domain
Revenue Operations Objectives
Eight core objectives that define world-class RevOps. These aren't aspirational statements — they are measurable commitments backed by systems, processes, and KPIs.
Customer Centric
Every process decision evaluated through the lens of buyer and customer experience, not internal convenience.
Personalization at Scale
Segment-of-one messaging powered by data infrastructure and automation, not manual effort.
Agile & Adaptive
Operating cadences that respond to market signals in weeks, not quarters. OKRs over annual plans.
GTM Collaboration
Structural elimination of Sales / Marketing / CS silos through shared data, goals, and rituals.
Automate Repetitive Tasks
Target >70% automation for data entry, routing, alerts, and reporting. Humans focus on judgment calls.
Data-Driven Decisions
No strategy meeting without a data slide. No investment without a model. No quarter-end surprise without a leading indicator that was ignored.
Integrated Technologies
Tools talk to each other. No data islands. Single source of truth for pipeline, revenue, and customer health.
Unified Analytics
One revenue dashboard that Marketing, Sales, CS, and Finance trust equally. Reconciled numbers, not competing spreadsheets.
Six Pillars of Revenue Operations
The connective tissue that holds a revenue organization together. Each pillar has its own processes, tools, and KPIs — but they only create compounding value when designed to integrate.
Analytics & Data
Unified data architecture, attribution modeling, forecasting frameworks, self-serve dashboards. The foundation everything else is built on — teams that can't trust their data can't make good decisions.
Process Engineering
Documented playbooks, SLAs at every handoff, stage-entry criteria, deal inspection frameworks. Process is the instruction manual for your revenue motion — without it, every rep invents their own game.
Technology & Tooling
Architecture-first stack design, vendor evaluation, implementation governance, integration management, tech debt reduction. Tools amplify process — they don't replace it.
Go-to-Market Strategy
ICP definition, territory design, segmentation, pricing strategy, competitive positioning. Strategy without execution is fiction — execution without strategy is chaos.
People & Org Design
Org structure, compensation design, hiring frameworks, onboarding programs, performance management. The best process run by the wrong people still fails.
Governance & Cadence
Operating rhythms (daily / weekly / monthly / quarterly), decision rights, change management, project governance, OKR frameworks. Governance is how strategy becomes reality at scale.
Functional Organization Models
There is no universal RevOps structure. The right model depends on company stage, revenue complexity, and executive alignment. These three models represent the evolution from coordination to full integration.
"The sum of the whole is greater than the sum of its parts — but only when the parts are designed to connect."
Model 1: Commercial Ops Committee
Federated. Each function owns its ops. Committee provides cross-functional coordination.
Mktg Ops
Sales Ops
CS Ops
Best for: $20M–$80M ARR. Strong functional leaders who resist centralization.
Model 2: General RevOrg ★
Centralized RevOps under CRO or COO. Shared services model. My most deployed architecture.
Best for: $80M–$500M ARR. Creates shared truth without over-centralizing.
Model 3: Fully Integrated RevOps
RevOps as a P&L-level function alongside Sales, Marketing, and CS.
Best for: $500M+ ARR where RevOps is a board-level strategic priority.
The next question is usually whether this is a hire, a project, or nothing yet.
That’s a twenty-minute conversation and it costs nothing. If it’s nothing yet, I’ll tell you that — the zones above are there so you can work it out without me.