Why this post exists
Most fractional RevOps firms describe their process in abstract terms: "We audit your systems, align your teams, and optimize your revenue engine." That sounds good in a pitch deck but tells you nothing about what actually happens on Monday morning.
This post is the version I wish existed when I was on the buying side. A transparent, week-by-week breakdown of what a fractional RevOps engagement looks like from kickoff to handoff.
Before we start: who this is for
Fractional RevOps makes sense for B2B SaaS companies in a specific window:
- $2-20M ARR — enough revenue motion to optimize, not yet enough to justify a $200K+ full-time senior hire
- 10-50 person sales org — complexity is real but manageable
- Existing CRM (usually Salesforce or HubSpot) — there's something to work with, it's just not working well
- A known pain point — pipeline visibility, lead routing, data quality, forecasting, outbound efficiency
If you're pre-product-market-fit or still figuring out your ICP, you don't need RevOps yet. You need more conversations with customers.
Weeks 1-2: The audit
The first two weeks are entirely diagnostic. No building, no changing, no "quick wins" that break something else downstream.
What happens
Day 1-2: Access and orientation
- CRM admin access granted
- Connected tools inventoried (enrichment, outreach, analytics, billing)
- Existing documentation reviewed (if it exists — it usually doesn't)
- Key stakeholders identified for interviews
Day 3-5: Stakeholder interviews
- 30-minute conversations with CRO/VP Sales, sales managers, top-performing reps, marketing leader, and anyone who touches the CRM
- Questions focus on: What's working? What's broken? Where do you waste time? What don't you trust?
- These conversations surface the real problems, which are rarely what was described in the initial sales call
Week 2: System deep dive
- CRM architecture mapped: objects, fields, automation, integrations
- Pipeline stages analyzed: conversion rates between stages, average time in stage, drop-off points
- Data quality assessed: field completion rates, duplicate density, stale record percentage
- Lead flow traced: from source through routing to outcome
- Reporting audited: what exists, what's trusted, what's missing
What you receive
A written audit document (typically 8-15 pages) covering:
- Current state architecture diagram
- Top 5 pipeline leaks ranked by revenue impact
- Data quality scorecard
- Process gaps and automation opportunities
- Recommended build priorities (what to fix first and why)
- Quick wins vs. structural fixes
This document becomes the roadmap for everything that follows. Nothing gets built without it.
Weeks 3-6: The build
This is where the actual engineering happens. The audit determines what gets built first, but the most common projects fall into a few categories:
Common build #1: Pipeline visibility
The problem: The CRM has data in it, but nobody trusts the reports. Pipeline reviews are based on spreadsheets pulled from Salesforce, manually adjusted, and emailed around.
The fix:
- Stage definitions rewritten with exit criteria
- Validation rules that enforce required fields at each stage
- Automated decay rules for stale opportunities
- Real-time dashboards that replace the spreadsheet (in Salesforce or a connected BI tool)
- Weekly automated pipeline snapshot for historical trending
Timeline: 2-3 weeks
Common build #2: Lead routing and speed-to-lead
The problem: Inbound leads sit in a queue for hours or days. Routing logic is tribal knowledge. Some leads fall through the cracks entirely.
The fix:
- Lead-to-account matching (so inbound leads attach to existing accounts)
- Round-robin or territory-based routing with rules codified in automation
- SLA tracking: time from form fill to first rep touch
- Alerting when leads breach SLA
- Fallback routing so nothing sits unassigned
Timeline: 1-2 weeks
Common build #3: Outbound infrastructure
The problem: SDRs are doing manual research, building lists in spreadsheets, and sending sequences with no signal-based targeting.
The fix:
- Signal pipeline: champion job changes, funding rounds, hiring surges feeding into a qualified account queue
- Enrichment automation: firmographic and contact data appended without manual lookup
- Sequence triggers: the right outreach fires when a signal is detected
- Reporting: signal-to-meeting conversion tracking
Timeline: 3-4 weeks
Common build #4: Forecasting and deal inspection
The problem: Forecast is a guess. The CRO asks each manager to "commit a number" and rolls it up. No systematic inspection of deal health.
The fix:
- Forecast categories (commit, best case, upside) with clear definitions
- Deal health scoring based on engagement signals (multi-threading, stakeholder access, activity recency)
- Automated weekly forecast snapshot
- Exception alerts: deals in commit with no recent activity, deals with slipping close dates
Timeline: 2-3 weeks
Weeks 7-10: Tuning and iteration
Nothing works perfectly on first deployment. The tuning phase is where the system goes from "technically working" to "actually useful."
What happens
- Feedback loops: Reps and managers report what's working and what's friction. Routing rules get adjusted. Alert thresholds get tuned. Dashboards get refined.
- Edge cases: The automation that worked for 90% of scenarios gets patches for the weird 10%. The lead that comes in from a partner channel. The deal that skips two stages. The rep who covers two territories.
- Adoption tracking: Are reps actually using the new workflows? Where are they reverting to the old way? The system needs to be easier than the workaround, or people won't use it.
- Performance measurement: The first real data starts coming in. Signal-to-meeting rates. SLA compliance. Forecast accuracy vs. prior quarters.
Weeks 11-12: Documentation and handoff
The engagement ends with everything documented and transferred.
Deliverables
- System documentation: Architecture diagrams, automation logic, field definitions, integration maps. Written for the person who will maintain this after the engagement ends.
- Runbook: Step-by-step instructions for common maintenance tasks. How to add a new rep to routing. How to adjust lead scoring weights. How to create a new signal trigger.
- Training sessions: Recorded walkthroughs for admins and end users.
- Maintenance calendar: What needs to be reviewed weekly, monthly, quarterly (data quality audits, scoring model recalibration, routing rebalancing).
The decision point
At week 12, you have a working system and the documentation to maintain it. Two paths:
- Handoff: Your team takes over. You have the runbook, the documentation, and the training. The system runs. You maintain it.
- Retain: You keep the fractional engagement at reduced hours (5-10/week) for ongoing monitoring, tuning, and iteration. New builds as the business evolves.
Most companies at $5-15M ARR choose option 2 for 3-6 months, then hire a full-time RevOps person and transition to option 1.
What this doesn't include
Transparency means being clear about scope:
- Strategy consulting. This engagement builds systems, not sales strategies. If your ICP is wrong or your pricing is broken, those are separate conversations.
- Rep coaching. RevOps builds the infrastructure. Sales enablement trains the team. Different disciplines.
- Tool selection. If you need to evaluate and purchase new software (choosing a CRM, outreach platform, etc.), that's a separate workstream that happens before the build.
How to evaluate if it's working
By week 12, you should be able to answer yes to these questions:
- Do you trust your pipeline number?
- Can you forecast within 10-15% accuracy?
- Do inbound leads get a response within your SLA?
- Are reps spending less time on admin and more time selling?
- Can you identify where pipeline leaks and take action?
If the answer to those is yes, the engagement worked. If some are still no, the scope was either too ambitious or there's more to build — both of which should be clear and unsurprising by that point.