Pipeline stages were copied from a HubSpot template instead of built around the actual buyer journey.
Revenue operations
Stop reporting activity. Start producing decisions.
Most early-stage RevOps work optimises the dashboard. The work that matters is upstream: clean stages, decision rules, and a weekly cadence the team uses to scale, stop, or fix things.
What this problem looks like
If you recognise three of these, this page is for you.
- Pipeline stages mean different things to sales, marketing, and the founder.
- Weekly reporting is a lot of charts but produces almost no decisions.
- Forecast accuracy is poor — every quarter ends with a surprise.
- Conversion rates between stages aren't tracked, or aren't trusted.
- Marketing and sales argue about lead quality every two weeks.
Why it usually happens
The root cause is rarely what the team thinks it is.
The team built dashboards before agreeing what decisions the dashboards exist to support.
Nobody owns the operating cadence — RevOps is treated as data hygiene rather than commercial signal.
How I diagnose it
A focused diagnostic, not a six-week consultancy review.
- 01Audit pipeline stages with sales, marketing, and the founder — find the points where definitions diverge.
- 02Look at the last quarter's deals: where did they sit longest, where did they actually move, where did they die.
- 03Read the existing weekly reports and ask the team: what decision did this report help you make. The honest answer is usually "none".
- 04Score the constraint across pipeline definition, conversion measurement, forecast accuracy, and operating cadence.
- 05Decide which one or two of those layers actually move the needle in the next 90 days.
How I fix it
Build the system, then transfer it.
- 01Rewrite pipeline stages around buyer commitment signals (not internal task completion). Get sales + marketing + founder to agree on the new definitions.
- 02Set conversion targets between every stage — even rough ones — and track them weekly.
- 03Build one growth dashboard the team uses to make decisions, not five they ignore.
- 04Set a weekly RevOps rhythm: read signal Monday, decide Friday, no debates outside those windows.
- 05Forecast monthly using a simple weighted-pipeline + cohort method — not a black-box CRM number.
Example deliverables
What you actually leave with.
Pipeline stage definitions doc (signed off by sales, marketing, founder)
Stage-to-stage conversion tracking — live, weekly
Single growth dashboard tied to decision rules
Weekly RevOps meeting format and decision log
Forecast model (weighted pipeline + cohort)
Marketing-to-sales handoff SLA
Mini example · B2B SaaS · pre-Series B
- Problem
- Forecast missed by 30%+ for two consecutive quarters. Marketing and sales argued about lead quality every standup. Pipeline meeting was a chart parade with no decisions.
- Action
- Rewrote pipeline stages around buyer commitment. Built stage conversion tracking. Set a weekly rhythm with explicit scale / stop / fix calls. Set a marketing-sales SLA on lead quality.
- Result
- Forecast accuracy moved from ~70% to ~92% inside one quarter. Sales-marketing tension dropped because the data finally agreed.
Who this is for
Best fit if any of these apply.
- Post-PMF teams (£1m–£10m ARR) where forecasting, pipeline, or sales-marketing alignment is breaking.
- Founders preparing for a Series A or B raise who need a clean RevOps narrative.
- Teams that just hired a sales leader and need the operating system to back them up.
Common mistakes
What teams get wrong before they call.
- Buying a bigger BI stack before the pipeline definitions are agreed — you end up with the same confusion in a more expensive tool.
- Treating MQLs as the success metric instead of stage-to-stage conversion.
- Adopting MEDDIC or BANT or another methodology without first deciding what your stages even mean.
- Reporting weekly with no decision rules, so reporting becomes a ritual, not a tool.
FAQ
Common questions before booking.
Do I need a RevOps hire?
Eventually, if you're scaling past 5-10 sellers. Before that, the work is mostly definitional and process — a fractional senior operator builds the system, then a RevOps hire runs it.
What CRM do you work in?
HubSpot, Salesforce, Attio, Pipedrive — tool-agnostic. The work is upstream of the tool.
How long until forecasting improves?
Most teams see meaningful accuracy improvement in one quarter once stages and conversion tracking are clean. Compounding effect over 2-3 quarters.
Is this just sales ops?
No. RevOps spans marketing, sales, and CS — the operating cadence has to be one connected system, not three siloed ones.
Next step
Diagnose this in 20 minutes.
Bring the current state of your revenue operations. We'll diagnose the constraint and decide if working together makes sense — or where else to go if it doesn't.
Prefer email? daniel@wescalestartups.com
Last updated: 11 May 2026