Revenue Executive Officer cheat sheet
Revenue Executive Officer · Keep the key ideas within reach.
Revenue Strategy and Business Model Design
Recurring revenue model value = ARR x gross margin multiple; one-time revenue is valued at a far lower multiple, so model choice drives enterprise value as much as volume.
Rule of 40: revenue growth rate (%) + profit margin (%) ≥ 40 signals a healthy SaaS balance; below 40 forces a trade-off decision between growth spend and margin.
LTV:CAC ratio target is ≥3:1; below 1:1 means each acquired customer destroys value, above ~5:1 usually signals underinvestment in go-to-market.
CAC payback months = CAC / (monthly ARPA x gross margin %); sub-12-month payback is strong, beyond 24 months strains cash unless capital is cheap.
TAM/SAM/SOM must be built bottom-up (accounts x ACV) rather than top-down percentages; top-down sizing hides segment-level viability.
Business model canvas dependencies: pricing model, contract term, expansion mechanism, and delivery cost structure must be internally consistent; a usage model with high fixed delivery cost creates margin risk.
Land-and-expand requires a defined expansion lever (seats, usage, modules, or price uplift) with a measurable attach rate; expansion without a lever is just hope.
Annuity vs transactional mix: shifting from perpetual to subscription lowers near-term revenue but raises retention and predictability; model transitions require a bridge plan for cash and comp.
Revenue Operations and Go-to-Market Alignment
Single source of truth for account, opportunity, and territory data is a precondition for RevOps; duplicate or conflicting CRM records invalidate every downstream metric.
Lead-to-cash handoff map should name an owner and SLA for each stage: marketing qualified lead, sales accepted lead, opportunity, closed-won, onboarding, renewal.
Territory design rules: balance total addressable opportunity within ±10-15% across reps, align to segment or geography, and avoid splitting named accounts across owners.
SLA example: MQL-to-first-touch within 24 hours; SAL acceptance or rejection within 2 business days with a documented reason code.
Pipeline coverage rule: 3x-4x qualified pipeline to quota for stable win rates; coverage below 3x predicts a miss unless win rate or deal size rises.
GTM alignment metric: marketing-sourced vs sales-sourced pipeline split, plus influence attribution, to avoid double counting and credit disputes.
Quarterly business review cadence with shared funnel metrics (conversion by stage, cycle time, win rate) prevents finger-pointing between marketing, sales, and CS.
Channel and partner conflict rules must be written: deal registration, margin protection, and rules of engagement for direct vs partner-led opportunities.
Pricing, Packaging, and Monetization
Value-based pricing anchors price to quantified customer outcome (cost saved, revenue gained, risk avoided); cost-plus pricing leaves value on the table and invites disruption.
Good-better-best packaging: three tiers with a clear value metric and a defined upgrade path; the middle tier is usually the designed target and should carry the best margin.
Value metric selection test: the metric must scale with customer value, be easy to understand and forecast, and be hard to game; seats, usage, and outcomes are common choices.
Price increase playbook: grandfather existing customers for a defined period, give notice per contract terms, and pair increases with added value or a migration offer.
Discount governance: approval thresholds by discount band, deal desk review above a set percentage, and no discount without a documented give-get (term, volume, case study).
Usage-based pricing requires a spend cap, alerting, and predictability features; bill shock is the top churn driver in consumption models.
Price testing should use cohort or geo-based tests with holdout groups; comparing sequential periods confounds price effect with seasonality.
Net price realization = list price minus discounts, rebates, and concessions; track it by segment because average discount often hides deep outliers.
Revenue Forecasting, Analytics, and KPIs
Forecast categories: commit, best case, and pipeline; accuracy is measured as forecast vs actual within a tolerance band (commonly ±5-10% for commit).
Weighted pipeline forecast = sum of (deal value x stage probability); calibrate stage probabilities from historical conversion, not intuition.
ARR = sum of annualized recurring contract value; MRR x 12 only if no contract mix distortion; exclude one-time and services revenue.
Net revenue retention (NRR) = (starting ARR + expansion - contraction - churn) / starting ARR; gross retention excludes expansion and isolates churn.
Magic number = net new ARR in quarter / prior-quarter sales and marketing spend; above 0.75-1.0 signals efficient go-to-market spend.
Cohort analysis separates acquisition quality from later behavior; blending cohorts hides deteriorating retention in newer vintages.
Leading vs lagging KPIs: pipeline creation, MQL volume, and demo bookings lead; revenue, churn, and NRR lag; dashboards should pair both.
Forecast hygiene: require close-date and amount change history, flag slipped deals, and review sandbagging by comparing rep commit to historical close rates.
Sales Performance Management and Compensation
OTE = base salary + target variable; typical split is 50/50 or 60/40 for account executives, with more variable weight as the role becomes more transactional.
Pay mix and leverage: variable pay should scale with controllable outcomes; paying commission on revenue a rep cannot influence (e.g., renewals of accounts they never owned) erodes trust.
Quota setting: sum of rep quotas typically exceeds company target by 10-20% to absorb attrition and ramp; quota attainment distribution should show 60-70% of reps at or above quota.
Ramp model: new reps get a ramped quota and guaranteed minimum or draw for a defined period; unramped quotas predict early failure and attrition.
Commission accelerators above 100% of quota and decelerators below threshold; caps are rare in enterprise sales and damage motivation when applied retroactively.
SPIFFs are short-term incentives for specific behaviors (new product, strategic segment); they must expire and be measured against incremental behavior, not existing pipeline.
Clawbacks for churned or unpaid deals must be defined in the plan document with a lookback window; ambiguous clawback language is a legal and morale risk.
Plan governance: publish plan documents before the period starts, calculate from a single data source, and run a dispute process with a defined resolution SLA.
Customer Retention, Expansion, and Lifecycle Revenue
Churn types: logo churn (customer count), gross revenue churn (lost MRR), and net revenue churn (after expansion); each answers a different question and must be reported separately.
Health score inputs: product usage depth, support ticket sentiment, executive engagement, invoice payment behavior, and renewal proximity; weights should be validated against actual churn.
Expansion levers: seat growth, usage growth, cross-sell of adjacent modules, upsell to higher tier, and price uplift at renewal; each needs an owner and a trigger.
Renewal playbook timeline: start 90-120 days before expiry for enterprise, confirm value delivered, identify stakeholders, then negotiate; late starts compress leverage.
Onboarding time-to-value is the strongest early predictor of retention; define a first-value milestone and measure days to reach it by cohort.
Save play for at-risk accounts: root-cause diagnosis, executive sponsor involvement, and a documented remediation plan with a success metric and review date.
Customer lifetime value should use gross margin and a discount rate for long horizons; undiscounted LTV overstates value in multi-year contracts.
Advocacy loop: satisfied customers feed references, case studies, and referrals; track referral-sourced pipeline as a retention-quality signal.
Revenue Technology Stack and Data Governance
CRM is the system of record for account, contact, opportunity, and activity; any tool that writes revenue data back must conform to CRM object and field standards.
Integration pattern: prefer event-driven or scheduled sync with idempotent keys and error queues; point-to-point scripts without monitoring create silent data loss.
Data governance roles: data owner (business accountability), data steward (quality operations), and system owner (tool administration); without named owners, quality decays.
Field hygiene rules: picklist-controlled stages, required close date and amount, no free-text for segment or source, and validation rules that block stage skips.
Deduplication: match on domain plus normalized company name; merge rules must preserve the surviving record's history and reassign open opportunities.
CPQ-to-CRM-to-billing lineage must be traceable end to end; a mismatch between booked and billed ARR is a governance failure, not a finance quirk.
Security and compliance: role-based access, field-level encryption for sensitive data, audit logs, and data retention policy aligned to contract and regulation.
Stack rationalization test: every tool must have a named owner, a defined use case, and a measured adoption rate; unused licenses are pure margin leakage.
Leadership, Ethics, and Executive Communication
Executive communication structure: lead with the answer, then evidence, then ask; a one-page memo beats a slide deck for decisions and forces clarity.
Board reporting cadence: revenue vs plan, NRR, pipeline coverage, CAC payback, and cash runway; variance explanations should state cause, impact, and corrective action.
Ethical revenue recognition: never pull forward or misclassify revenue to hit a target; side letters and undisclosed terms are fraud risk, not sales creativity.
Compensation ethics: no retroactive plan changes without legal review and clear communication; retroactive clawbacks of earned commission invite disputes and attrition.
Data ethics: customer data used for targeting or pricing must respect consent and contract terms; differential pricing based on protected attributes is unlawful in many jurisdictions.
Difficult message protocol: state the fact, own the impact, give the plan and timeline, and commit to a follow-up date; ambiguity amplifies rumor.
Decision rights: define who decides, who consults, and who is informed for pricing exceptions, discount approvals, and headcount; unclear rights slow revenue.
Culture of dissent: reward early bad-news escalation; teams that hide risk produce forecast surprises and ethical shortcuts.