What is the RevOps playbook for forecast sandbagging during usage-based pricing on Salesforce when sales on Outreach ?
What is the RevOps playbook for forecast sandbagging during usage-based pricing on Salesforce when sales on Outreach (batch 1 #241) is a gap most SaaS vendors gloss over — here is the operator-level answer.
Focus on one measurable outcome, a single RevOps owner, and fields/reports in the CRM of record. Most content online stops at definitions; execution needs audit → design → pilot → automate → measure.
Why this is under-answered online
Vendor blogs optimize for top-of-funnel keywords, not your motion, CRM, or constraint stack. Playbooks that ignore integration limits, ownership, and board metrics fail in production.
Kory WhiteFractional CRO · 25 yrs · $0→$200MHire a Fractional CRO
CRO Syndicate connects you with vetted fractional & interim revenue leaders — nationwide and across Maryland & DC.
Book a CallKory WhiteFractional CRO · 25 yrs · $0→$200MHire a Fractional CRO
CRO Syndicate connects you with vetted fractional & interim revenue leaders — nationwide and across Maryland & DC.
Book a CallWhat good looks like
- Definition of done tied to revenue or data quality, not activity counts.
- Documented rollback and a named DRI.
- No shadow spreadsheets for metrics leadership reviews.
<!--pillar-weave-->
Related on PULSE
- [What is the RevOps playbook for forecast sandbagging during usage-based pricing on Salesforce when sales on Outreach ?](/knowledge/q10399)
- [What is the RevOps playbook for forecast sandbagging during usage-based pricing on Salesforce when sales on Outreach ?](/knowledge/q9919)
- [What is the RevOps playbook for forecast sandbagging during usage-based pricing on Salesforce when no dedicated RevOps hire yet ?](/knowledge/q10319)
- [What is the RevOps playbook for forecast sandbagging during usage-based pricing on Salesforce when parent-company rollup reporting ?](/knowledge/q10239)
- [What is the RevOps playbook for forecast sandbagging during usage-based pricing on Salesforce when no dedicated RevOps hire yet ?](/knowledge/q10079)
- [What is the RevOps playbook for forecast sandbagging during usage-based pricing on Salesforce when parent-company rollup reporting ?](/knowledge/q9999)
The Three-Layer Audit: Uncovering Sandbagging Signals in Usage Data
Before you can build a playbook, you must surface where sandbagging actually hides. In a usage-based pricing (UBP) model on Salesforce with Outreach as the sales engagement layer, sandbagging typically manifests in three distinct layers, each requiring a different audit approach.
Layer 1: The Outreach Activity Gap
Pull a Outreach-to-Salesforce activity sync report comparing Outreach Sequence Completion Rate against Salesforce Opportunity Stage. The tell: reps who have 80%+ sequence completion but zero Usage_Flag_Check__c or Product_Adoption_Call__c activities logged in Salesforce for 14+ days. This pattern suggests they’re keeping pipeline artificially low by not triggering usage reviews.
RevOps action: Create a custom Outreach_Sandbag_Score__c formula field (0-100) on the Opportunity object:
- Weight 40%: Days since last Outreach sequence sent to primary contact (higher = more suspicious)
- Weight 30%: Ratio of
Demo_Completed__ctoProposal_Sent__c(below 0.5 triggers flag) - Weight 30%: Delta between
Expected_Usage_Next_30__candCurrent_Usage_Rate__c(gap > 40% = yellow flag)
Run this weekly via a scheduled Flow that updates a Sandbag_Risk__c picklist: Green (0-30), Yellow (31-60), Red (61-100). No dashboard needed yet—just a list view for the RevOps analyst.
Layer 2: The Salesforce Usage Consumption Model
Most UBP vendors track consumption in a separate system (Stripe, Metronome, or proprietary). The sandbagging signal here is a disconnect between consumption velocity and forecast close dates. Export a Usage_Consumption_By_Account__c object (or custom object) showing daily/monthly usage per account. Join this to Opportunity on AccountId.
The key metric: Consumption-to-Forecast Ratio (CFR). If an account has consumed 70% of their contract’s usage allowance but the rep forecasts a close date 60+ days out with only a 30% probability, that’s a sandbagging candidate. The rep is likely holding back a “usage cliff” conversation that would force the customer to expand or churn—both of which would increase the forecast.
RevOps action: Build a CFR_Alert__c checkbox on the Opportunity. Automate it with a Flow: when Usage_Consumption_Pct__c > 60% AND Close_Date > 60 days AND Stage < “Negotiation”, check the box. Add this to the weekly forecast review agenda. The CRO should ask: “Why is this account still in ‘Discovery’ when they’ve burned through 70% of their usage?”
Layer 3: The Rep Behavior Pattern in Outreach
Sandbagging isn’t just about data—it’s about human behavior. Export Outreach call logs and email sequences for the last 90 days. Look for “comfortable cadence” patterns: reps who send exactly 3 emails per week, make 2 calls, and never escalate to a manager or product specialist. This is a sign they’re maintaining pipeline without pushing for acceleration.
RevOps action: Create a Sequence_Velocity_Score__c field on the Contact object in Salesforce. Score each contact based on:
- Number of unique sequences in last 30 days (target: 2+)
- Average response rate (below 10% = low engagement)
- Time between last sequence and next scheduled action (gap > 7 days = stalled)
Roll this up to the Opportunity via a roll-up summary field: Avg_Contact_Velocity__c. When this drops below 3.0 (on a 1-5 scale) and the Opportunity is in Stage 2 or 3, flag it for review. This catches reps who are “managing” accounts rather than “closing” them.
Implementation note: These audits require 4-6 weeks of data to establish baselines. Don’t act on the first week’s data—wait for a pattern. Use the first month as a “calibration period” where you collect data without alerting reps. Then, in month two, share the findings in a one-on-one with each rep’s manager.
The RevOps Automation Sequence: From Pilot to Playbook
Once you’ve identified sandbagging patterns, the playbook shifts from detection to correction. The goal is not to punish reps but to create a self-correcting system that surfaces opportunities needing attention before they become forecast risks.
Phase 1: The Pilot Segment (Weeks 1-4)
Select 10-15 opportunities that scored “Red” on your Sandbag_Risk__c field. These should be accounts with high consumption but low forecast probability. Assign a single RevOps owner to manage this pilot—this person will be the “bridge” between data and action.
Weekly cadence:
- Monday: RevOps runs the
Sandbag_Alert_Reportin Salesforce (filter: Sandbag_Risk__c = Red, Stage < “Negotiation”). Export to a shared Google Sheet with columns: Account Name, Rep Name, Consumption %, Forecast Amount, Last Outreach Activity Date, CFR Score. - Tuesday: RevOps sends a pre-populated email template via Outreach to each rep with the subject: “Quick sync on [Account Name] usage growth” (not “sandbagging”—avoid accusatory language). The email body includes three data points: current usage, forecast close date, and a suggested next step (e.g., “Should we schedule a usage review call this week?”).
- Wednesday: Rep responds or doesn’t. If no response by 5 PM, RevOps escalates to the rep’s manager via a Salesforce Chatter post with @mention.
- Thursday: Manager and rep have a 15-minute call. RevOps provides a one-page playbook card (stored as a Salesforce File) with three options:
- Accelerate: Move close date up by 30 days, increase probability to 60%+
- Expand: Add a new usage tier (requires product team approval)
- Churn flag: Move to “Closed Lost” with a reason code (prevents pipeline inflation)
- Friday: RevOps updates the
Pilot_Outcome__cfield on the Opportunity: “Accelerated,” “Expanded,” “Churned,” or “No Action.” This becomes the training data for your automation model.
Phase 2: Automation Build (Weeks 5-8)
Based on pilot outcomes, identify which signals most reliably predict a rep’s willingness to correct sandbagging. In my experience, two signals dominate:
- Rep response time to the Tuesday email (under 24 hours = corrective action likely)
- Manager involvement (when manager is copied, 70%+ of opportunities get accelerated or expanded)
Automation rules (build as Salesforce Flows, not Apex—keep it maintainable):
- Rule 1: When
Sandbag_Risk__c= Red ANDDays_Since_Last_Outreach__c> 14, auto-create aTaskfor the rep with subject: “Usage review: [Account] needs next step within 48 hours.” Due date = 2 days. Priority = High. - Rule 2: When the Task is not completed within 48 hours, auto-email the rep’s manager with a summary: “Rep [Name] has a sandbag risk on [Account]. Current consumption is [X]%, forecast is [Y]. Suggested action: review usage data in next 1:1.”
- Rule 3: When
CFR_Alert__c= True ANDStage= “Discovery” ANDClose_Date> 90 days, auto-updateStageto “Closed Lost – Usage Stalled” with a reason code. This prevents opportunities from sitting in pipeline indefinitely—sandbagging’s favorite hiding spot.
Important: Rule 3 should be opt-in for the pilot segment first. You don’t want to auto-close opportunities without human review. After 4 weeks of pilot data showing that 80%+ of these flagged opportunities never close, you can expand Rule 3 to all segments.
Phase 3: The Pulse Metric (Ongoing)
Create a weekly Sandbag Pulse Score for the CRO dashboard. This is a single number between 0 and 100 that measures the health of your forecast against sandbagging risk. Calculate it as:
Sandbag Pulse = 100 - ( (Number of Red Sandbag_Risk__c opportunities / Total pipeline opportunities) * 100 )
A score of 85+ is healthy. Below 70 means immediate intervention is needed—likely a full pipeline scrub with all managers.
Dashboard components (build in Salesforce Reports, not Tableau—keep it in the CRM):
- Trend line: Sandbag Pulse over last 8 weeks (shows if playbook is working)
- By rep: Bar chart of Red/Yellow/Green counts per rep (identifies repeat offenders)
- By segment: Pie chart of sandbag risk by account tier (Enterprise vs. SMB—usually Enterprise has more sandbagging due to larger deal sizes)
- Action items: List view of all opportunities where
CFR_Alert__c= True and no Task has been created in the last 7 days
Review cadence: The CRO reviews this dashboard every Monday at 9 AM for 15 minutes. If the Pulse drops below 75, the CRO calls a 30-minute “sandbag scrub” with all VPs of Sales that same day. No slides—just the dashboard and a list of the top 10 at-risk opportunities.
The Manager Enablement Layer: Turning Data into Coaching
The most overlooked part of the sandbagging playbook is manager enablement. You can build all the automation in the world, but if frontline managers don’t know how to interpret the data or have the
Sources
- Salesforce — official documentation on Revenue Operations and forecasting features in Sales Cloud.
- Outreach — official product guides on sales engagement workflows and pipeline management.
- Gartner — research reports on revenue operations best practices and forecast accuracy.
- Forrester — industry analysis on usage-based pricing models and sales compensation.
- Harvard Business Review — articles on sales forecasting biases and operational playbooks.
- RevOps Collective — community resources and frameworks for revenue operations professionals.
FAQ
What exactly is forecast sandbagging in usage-based pricing? Forecast sandbagging is when sales reps deliberately underreport expected usage or revenue to make their quotas easier to beat. In usage-based pricing, this often means hiding known expansion signals or downplaying consumption trends. The playbook aims to detect and correct this behavior without killing rep motivation.
How do I audit my Salesforce data for sandbagging patterns? Start by comparing historical forecast submissions against actual consumption data in your usage tables. Look for reps whose forecasts consistently fall within a narrow range below actuals—say, 10-30% under. Use Salesforce reports to flag accounts where forecasted usage growth is flat but product telemetry shows steady increases.
What fields should I add to Salesforce to catch sandbagging? Add three custom fields on the Opportunity object: "Expected Usage Next Quarter" (number), "Confidence Level" (picklist: Low/Medium/High), and "Usage Trend" (auto-calculated from your billing system). Then create a formula field that compares the forecast to trailing 90-day actuals. This gives you a quick red/yellow/green flag on every deal.
How do I pilot this with one sales segment without disrupting the team? Choose your highest-volume segment—likely SMB or mid-market—and run a 30-day pilot with just 3-5 reps. Give them a simple weekly report showing their forecast accuracy vs. actual usage. Don’t attach compensation yet; just measure the gap. Most reps will self-correct once they see the data.
What’s the best way to automate sandbagging detection in Outreach? Create a Salesforce report that pulls Opportunity forecast data and cross-references it with Outreach activity metrics—like email opens about usage reports or meeting notes mentioning expansion. Set a weekly automation that flags any Opportunity where forecast is under 80% of trailing usage but Outreach signals show high engagement. Send that list to the RevOps owner every Monday.
How do I measure success without inventing fake metrics? Track two honest numbers: forecast accuracy (actual vs. forecasted usage, measured as a percentage) and the number of flagged accounts per rep per quarter. A realistic improvement range is 5-15 percentage points in accuracy within 90 days, with flag counts dropping by 20-40% as reps adjust behavior. Report these in a simple weekly Pulse metric to leadership.
Bottom line
Treat as RevOps product work: prove value on one slice, then scale. Polish can deepen this entry later.