The RevOps Build Playbook
The methodology for turning a CRM into an operating system. Diagnostic, foundation, scoring, routing, forecast, reporting, and the operating cadence that holds it all together.
- A written diagnostic of the eight RevOps areas with severity and recommended sequence
- Lifecycle stage definitions enforced by workflow with required properties as the gate
- A lead scoring model calibrated against actual sales-accepted leads from the trailing 90 days
- A weighted forecast model that lands within plus or minus 10 percent on a rolling 90 day window
- Three role-based dashboards: rep, manager, CRO. Plus exec and board views from the same source of truth.
- A weekly pipeline review, monthly forecast review, and quarterly RevOps reset with written agendas
Why this playbook exists
RevOps is the discipline that turns a CRM into an operating system. Most teams have HubSpot or Salesforce running, but the lifecycle stages are not defined, the lead scoring is not calibrated, the forecast is a spreadsheet, and marketing and sales argue every Monday about whose number is right. RevOps is what makes that argument disappear.
Phase 1: Diagnose
RevOps engagements never start with building. They start with diagnosing what is actually broken. INSIDEA's diagnostic covers eight areas. The output is a written assessment with severity and recommended sequence.
- Data model: are the right objects, properties, and associations in place to power the reporting the team needs
- Lifecycle stages: are they defined, automated, and trusted across sales, marketing, and customer success
- Lead scoring: does the score produce a signal sales actually acts on, or is it ignored
- Lead routing: are leads going to the right rep within minutes, not hours
- Forecast model: does the prediction land within plus or minus 10 percent of actual on a rolling 90 day window
- Reporting: is there one source of truth or are there two arguments running in parallel
- Automation: are workflows doing the routing or are reps doing it in slack messages
- Team capacity: who can actually own RevOps after INSIDEA leaves
The diagnostic is shared with leadership in a single working session. The eight areas get ranked by impact and effort, the sequence gets agreed, and the engagement plan is written.
Phase 2: Foundation
The foundation is non-negotiable. Lifecycle stages and the property model. Without them, every later piece is built on sand.
Lifecycle stage definitions
Every stage from Subscriber through Evangelist gets a written definition with entry criteria, exit criteria, and an owner. The definitions live in HubSpot as required properties on the contact record, gated by workflow. Until those properties are populated and confirmed, the lifecycle stage cannot change. This is what kills the 'I never agreed to that lead' argument.
Property model
ICP segment, industry, revenue band, employee count, tech stack flags on the company. Lead source, lead score, deal source, deal owner on the contact. Stage exit criteria on the deal. Every property has a type, a use case, and an owner. New properties go through change control. Quarterly audit archives anything without an active workflow or report dependency.
Phase 3: Scoring and routing
Lead scoring lives or dies by calibration. INSIDEA builds the model with explicit fit signals (job title, seniority, ICP segment, company size, industry) and implicit intent (pricing page visits, demo requests, content downloads, email engagement). Each weight is set against actual sales-accepted lead data from the past 90 days, not against a marketing dashboard intuition.
Routing happens in a single workflow with no slack-message arguments. Round-robin by territory or segment. SLA re-route if the assigned rep does not act within the agreed window. The CRM enforces the rules. No manual triage.
Phase 4: Forecast and reporting
The forecast model is the headline output of RevOps. INSIDEA builds a weighted forecast on top of pipeline stage probability, deal size, and historical close rate by segment and rep. The forecast is reviewed weekly by the sales leadership and monthly by the executive team. The target is plus or minus 10 percent accuracy on a rolling 90 day window.
Reporting consolidates into three dashboards. The CRO sees pipeline coverage, forecast trend, win rate, sales velocity, and average deal size. The board sees revenue, ARR, NRR, churn, and CAC. Reps see their own pipeline, their open tasks, and their conversion rates. One source of truth, three views.
Phase 5: Operating cadence
Cadence is what turns a CRM build into a RevOps function. INSIDEA installs three meetings.
- Weekly pipeline review: AEs walk every open opportunity above a deal-size threshold against stage exit criteria. The output is a deal status update on every record and a flagged at-risk list.
- Monthly forecast review: weighted forecast vs commit vs best case for the quarter. Variance against last month's forecast gets explained. The CRO walks the number into the executive meeting.
- Quarterly RevOps reset: revisit lead scoring weights, lifecycle definitions, pipeline stages, and property model. Archive what is not earning its keep. Adjust what is drifting.
Asked while scoping this engagement.
Does INSIDEA do RevOps on Salesforce, not just HubSpot?
Yes. INSIDEA holds both Elite HubSpot Partner status and Official Salesforce Partner status. The RevOps methodology is platform-agnostic; the implementation is platform-specific. We give the honest read on which CRM fits during Discovery.
Can INSIDEA stay on as our fractional RevOps team?
Yes. After the build, customers commonly transition to an INSIDEA RevOps retainer. The retainer runs the cadence, ongoing optimization, and net new builds while the customer focuses on selling.
How accurate should the forecast be?
Within plus or minus 10 percent on a rolling 90 day window after the model is calibrated and the pipeline data is clean. If the variance is wider, either the weights need tuning or the input data is dirty. Both are fixable.
What does INSIDEA NOT do in a RevOps build?
We do not write sales scripts, design comp plans, or run trainings on selling skills. RevOps is the system, not the selling. We collaborate with whoever owns those (sales enablement, leadership, an external sales trainer) but they sit outside the engagement scope.
How do you handle multiple regions or business units?
Multiple pipelines, region-aware routing rules, segmented forecast models, and dashboards that filter by region or unit. The architecture brief covers segmentation rules up front so they are not bolted on later.
Want this playbook delivered? Book a strategy call.
30 minutes with a senior INSIDEA consultant. We scope the engagement against this playbook and you walk away with a clear timeline and price.
How INSIDEA works
