HubSpot RevOps cheat sheet

Course definition: RevOps is presented as the cross-functional alignment of sales, marketing, and customer success operations into a single revenue-focused function.

Curriculum sequence: fundamentals of RevOps, flywheel application, SLA design, sales process mapping, systems management, executive communication, team structure, hiring, and iterative evaluation.

Flywheel framing: every domain is tied back to reducing friction and increasing momentum across the attract, engage, and delight stages.

Accountability mechanism: SLAs are the course's primary tool for holding marketing, sales, and customer success to shared commitments.

Process artifact: sales process mapping connects buyer journey steps to internal deal stages and explicit exit criteria.

Systems lens: the CRM and its integrations are treated as the data backbone for revenue reporting and decision-making.

Leadership communication: RevOps value is translated into revenue, cost, risk, and time metrics rather than operational activity.

Team design: centralized, decentralized, and hybrid structures are compared, with hiring focused on analytical, systems, and communication skills.

Definition: RevOps unifies sales, marketing, and customer success operations into one function responsible for process, technology, data, and enablement across the revenue lifecycle.

Scope: RevOps spans lead generation through renewal and expansion, rather than stopping at the closed-won handoff.

Three pillars: process, technology, and data; people and enablement cut across all three and determine whether the pillars produce results.

Primary goals: predictable revenue growth, operational efficiency, and a consistent customer experience across every revenue team.

Distinction from sales ops: sales ops optimizes the sales team's efficiency, while RevOps optimizes the end-to-end revenue system and shared goals across marketing, sales, and customer success.

Core KPIs: customer acquisition cost (CAC), lifetime value (LTV), win rate, sales cycle length, retention or net revenue retention, and CAC payback period.

Ratio formula: LTV:CAC compares lifetime customer value with acquisition cost; a higher ratio indicates more efficient revenue generation, subject to segment and payback constraints.

Maturity progression: RevOps typically moves from reactive ticket-taking, to defined processes and reporting, to proactive strategy and forecasting.

Misalignment symptoms: duplicate data entry, disputed lead definitions, unowned handoffs, and conflicting dashboards are evidence that revenue operations are fragmented.

Flywheel stages: attract, engage, and delight; each stage should generate momentum that carries a customer toward advocacy and repeat purchase.

Two forces: friction slows the flywheel, while momentum accelerates it; RevOps work is prioritized by which force it changes.

Friction examples: unclear handoffs, manual data entry, slow lead follow-up, inconsistent onboarding, and disconnected systems.

Momentum examples: fast response times, shared customer data, smooth handoffs, proactive customer success, and closed-loop feedback.

Handoff rule: the highest-value RevOps projects often sit at team boundaries, where ownership is ambiguous and customer experience degrades.

Closed-loop reporting: sales outcomes such as closed-won and closed-lost reasons are fed back to marketing so targeting, messaging, and lead definitions improve.

Stage metrics: attract uses traffic and marketing qualified leads; engage uses sales qualified leads, conversion, and win rate; delight uses retention, expansion, and referral or advocacy measures.

Single customer view: a shared CRM record across marketing, sales, and customer success reduces friction caused by conflicting or missing customer information.

Definition: a service-level agreement is a documented commitment between revenue teams that specifies lead standards, response times, follow-up cadence, and review responsibilities.

Common parties: marketing-to-sales SLAs define lead handoff; sales-to-customer-success SLAs define onboarding and account transfer expectations.

Required components: lead definitions, qualification criteria, response-time commitments, follow-up cadence, rejection and feedback rules, escalation path, and review cadence.

MQL definition: a marketing qualified lead meets agreed engagement or fit criteria; an SQL meets sales readiness criteria such as confirmed need, authority, or timing.

Response commitment: a typical SLA states that sales will attempt contact within a defined window, such as 24 hours, after receiving an accepted lead.

Feedback loop: sales must record why a lead is rejected so marketing can refine targeting and lead scoring instead of guessing.

Review cadence: SLA performance is reviewed monthly or quarterly using lead acceptance rate, response time, conversion rate, and rejection reasons.

Decision rule: a low lead acceptance rate triggers a review of lead definitions and targeting before any blame is assigned to either team.

Capacity check: SLA commitments must be matched to team capacity; unattainable response times create systematic SLA breaches.

Definition: a sales process map is a documented sequence of stages, activities, and exit criteria that describes how a deal moves from first contact to closed-won or closed-lost.

Typical stages: prospecting, qualification, discovery, proposal, negotiation, and closed-won or closed-lost; stage names should reflect the actual buying journey.

Exit criteria: each stage requires objective conditions before advancement, such as confirmed budget, identified decision-maker, or completed technical validation.

Buyer journey alignment: internal sales stages should correspond to buyer actions and decision points, not only to seller activities.

Data capture points: the map identifies which fields, notes, and activities must be recorded at each stage to support forecasting and reporting.

Bottleneck detection: stage-to-stage conversion rates and time-in-stage metrics reveal where deals stall and where coaching or process changes are needed.

Validation methods: map the process using rep interviews, call observations, CRM data, and buyer research so the documented process reflects reality rather than assumptions.

CRM configuration rule: deal stages in the CRM should mirror the mapped sales process, including required fields and exit criteria, so reporting matches the process.

Process metrics: sales cycle length, stage conversion rate, win rate, and slip rate measure whether the mapped process is being followed and producing results.

Source of truth: the CRM is the authoritative system for customer, contact, and deal data; revenue teams should record activity there rather than in disconnected spreadsheets.

Tech stack categories: CRM, marketing automation, sales engagement, customer success, analytics, CPQ or billing, and enrichment tools each serve a distinct revenue function.

Integration methods: native integrations are simpler but limited; middleware or APIs connect complex stacks but require monitoring, documentation, and ownership.

Data hygiene practices: deduplication, field validation, standardized picklists, enrichment, and scheduled audits keep records accurate and reportable.

Data governance: assign owners for critical objects and fields, define who can create or edit records, and document definitions for metrics such as active customer or qualified lead.

Permissions and security: role-based access protects sensitive customer and revenue data while still giving each team the fields and records it needs.

Change management: new systems require training, adoption tracking, and a feedback channel; low adoption is a process and enablement problem, not only a tool problem.

System audit metrics: active user rate, data completeness, duplicate rate, integration error rate, and report usage indicate whether the stack is healthy.

Decision rule: define and document the process before selecting or configuring a tool; automation applied to an undefined process simply scales the confusion.

Value categories: RevOps impact is expressed as revenue growth, cost savings, risk reduction, and time saved; each initiative should map to at least one category.

ROI formula: return on investment equals (benefit minus cost) divided by cost; benefits should include incremental revenue, avoided cost, and productivity gains.

Executive goals: frame proposals around the metrics leaders already track, such as growth rate, gross margin, CAC payback, retention, and forecast accuracy.

Baseline requirement: quantify the current state before a change so the after-state comparison is credible and attributable.

Metric examples: faster lead response, higher win rate, shorter sales cycle, lower duplicate data rates, improved forecast accuracy, and reduced manual reporting hours.

Stakeholder mapping: identify who sponsors, funds, implements, and is affected by each initiative, then tailor the message to each group's priorities.

Narrative structure: problem, quantified impact, proposed solution, required investment, expected outcome, and decision requested.

Reporting cadence: recurring business reviews with a small set of stable metrics build credibility better than one-off reports with shifting definitions.

Risk framing: data quality, compliance, forecast misses, and customer churn are risks that RevOps controls, and they resonate with executives when quantified.

Three models: centralized, decentralized, and hybrid; the right choice depends on company size, segment complexity, tech stack complexity, and RevOps maturity.

Centralized model: one team serves all revenue functions, producing consistent standards, shared data definitions, and efficient specialist use, but it can become a bottleneck.

Decentralized model: embedded operations staff sit within sales, marketing, or customer success, providing context and speed but risking duplicated tools and conflicting metrics.

Hybrid model: a central team owns standards, systems, and reporting while embedded specialists support each revenue team; this balances consistency with responsiveness.

Reporting line: RevOps often reports to a chief revenue officer, chief operating officer, or CEO, depending on which role owns cross-functional revenue accountability.

Common roles: RevOps leader, business analyst, systems administrator, process or program manager, and enablement specialist; small companies combine several of these.

Service model: a documented intake process or service catalog tells revenue teams how to request support, what SLA applies, and how work is prioritized.

Decision rule: centralize when data consistency and shared tooling are the main problems; embed when speed and team-specific context are the main problems.

Scaling trigger: add specialist roles when request volume, system complexity, or reporting demand exceeds what generalists can handle reliably.

Competency model: analytical ability, systems thinking, process design, stakeholder communication, project management, and hands-on CRM or data experience.

Technical versus strategic: junior roles often emphasize CRM administration and reporting; senior roles require roadmap prioritization, cross-functional influence, and business judgment.

Structured interviews: use the same competency questions and rating scales for every candidate so comparisons are consistent and bias is reduced.

Scorecard method: define required competencies and observable behaviors before interviewing, then rate each candidate against the same criteria.

Case exercise: ask candidates to diagnose a revenue operations problem, propose a data-informed solution, and explain tradeoffs to a non-technical stakeholder.

Work sample: a take-home analysis, dashboard, or process map reveals practical skill more reliably than stated tool familiarity.

Tool knowledge rule: hire for transferable analytical and process skills rather than specific vendor experience, because stacks change and fundamentals persist.

Onboarding: new RevOps hires should shadow sales, marketing, and customer success calls and review CRM data before owning projects.

Panel design: include stakeholders from sales, marketing, and customer success so the hire is evaluated on cross-functional fit as well as technical ability.

Measurement framework: track a small set of outcome metrics such as revenue growth, win rate, sales cycle length, CAC payback, retention, and forecast accuracy alongside operational metrics.

Maturity assessment: evaluate process, technology, data, and team capabilities against a maturity model to identify gaps and sequence the next set of improvements.

Quarterly business review: review revenue metrics, project outcomes, adoption, and stakeholder feedback to decide which initiatives to continue, adjust, or stop.

Process audit: compare documented processes with actual CRM activity and rep behavior to find drift, workarounds, and outdated steps.

Stakeholder feedback: structured input from sales, marketing, and customer success reveals friction that dashboards alone do not capture.

Pilot method: test a process or system change with a small group, compare results against a baseline, and scale only when the evidence supports it.

Roadmap reprioritization: reassess initiatives by impact, effort, dependencies, and adoption; low-adoption initiatives are candidates for redesign or cancellation.

Iteration loop: measure, diagnose, change one variable, measure again; this keeps RevOps improvements attributable and prevents random redesign.

Documentation: maintain a decision log and process documentation so iterations preserve institutional knowledge instead of repeating past experiments.

Application step: translate the certification domains into a current-state audit covering process, technology, data, team structure, and SLAs.

30-60-90 day plan: first 30 days learn the business and audit data, days 31-60 deliver quick wins and build relationships, days 61-90 launch a prioritized roadmap.

SLA starting point: document lead definitions, response-time commitments, rejection feedback rules, and a review cadence before enforcing accountability.

Process starting point: map the sales process with reps, define exit criteria, and align CRM deal stages to the mapped process.

Systems starting point: inventory the revenue tech stack, identify the CRM as the source of truth, and document integrations and data owners.

Stakeholder starting point: identify executive sponsors and build a value narrative using revenue, cost, risk, and time metrics.

Measurement starting point: select a baseline set of revenue and operational KPIs so future RevOps improvements can be compared against a known starting point.

Continuous learning: the certification is a foundation; ongoing practice, community participation, and hands-on projects build RevOps proficiency.