Operating blueprint

Revenue operations: the first 90 days.

Forecasting does not improve because people try harder. It improves when a stage means the same thing to everyone, a review asks the same questions every week, and a new rep is certified against a written standard. This is the charter for the person who owns that.

30 / 60 / 90

Three windows, in order.

Days 1–30 — Make the pipeline legible

  • Publish exit-criteria stage definitions; audit every open deal against them and re-stage in one pass.
  • Separate stages from forecast categories (Pipeline / Upside / Most likely / Commit) so a stage change is not a forecast change.
  • Lock required fields at stage change: close date, next step, economic buyer, competition, amount.
  • Baseline the true funnel: opportunity creation, stage conversion, win rate by source, cycle length, slip rate.
  • Stand up one forecast of record with a weekly snapshot, so accuracy can be measured retroactively.

Days 31–60 — Make the review rhythmic

  • Install the weekly cadence below with a fixed agenda and a written deal review rubric.
  • Ship the coverage model: opportunities required per rep per quarter, split by inbound and outbound.
  • Define territory and account segmentation so new cohorts land on named accounts, not leftovers.
  • Build the onboarding curriculum and certification gates; assign an owner who is not the founder.
  • Publish quota, ramp schedule and comp mechanics for the next four cohorts before the first offer goes out.

Days 61–90 — Make it predictable

  • Move from a judgment forecast to a weighted forecast plus a committed roll-up, and report both variances.
  • Instrument ramp: time to first meeting, first opportunity, first win, and time to quota by cohort.
  • Close the loop to marketing on source quality by stage-2 conversion, not by lead volume.
  • Set the hiring trigger rules: no new cohort until coverage and manager span tests both pass.
  • Hand leadership one page: pipeline created, coverage, forecast accuracy, ramp status, capacity versus plan.

Stage architecture

A deal advances when the buyer does something.

Stages describe verified buyer progress. Forecast categories describe confidence. Keeping them separate is what stops a stage change from quietly becoming a forecast change.

StageOwnerExit criteria (evidence required)Forecast category
0 — TargetBDR / MarketingAccount fits ICP; a named contact in the buying centre has agreed to a first meeting.Not in pipeline
1 — DiscoveryRepDocumented current-state problem, its business cost, and who feels it. Meeting held with at least one person who owns the problem.Pipeline
2 — Validated needRep + SolutionsSuccess criteria written and confirmed by the buyer in their words. Technical evaluation scoped with named participants and dates.Pipeline
3 — EvaluationSolutions leadEvaluation complete against the written criteria; buyer confirms the criteria were met. Competitive alternatives known.Upside
4 — Economic buyer alignedRepMeeting held with the person who can sign. Budget source, amount and approval path confirmed. Mutual action plan dated back from the desired go-live.Most likely
5 — ContractingRep + LegalPaper with the buyer, security and procurement reviews under way, signature date agreed in writing.Commit

Ageing rule. Any deal older than 1.5× the average cycle in a single stage is auto-flagged for inspection and cannot sit in Commit. Pushed close dates count as a slip and are reported by rep and by stage.

Inspection

Eight questions, same order, every week.

Deal review rubric

Any unanswered line caps the deal at Upside.

  1. 01Problem

    Can you state the buyer's problem and its cost in their words?

    Evidence: Discovery notes quote the buyer verbatim.

  2. 02Impact

    What measurable outcome does this change, and who is accountable for it?

    Evidence: A number the buyer agreed to.

  3. 03Champion

    Who is selling this internally when you are not in the room?

    Evidence: Champion has shared something internal with you.

  4. 04Economic buyer

    Have you met the signer? What are their priorities?

    Evidence: Meeting held, not just named.

  5. 05Criteria

    What written standard must be met to choose you?

    Evidence: Criteria document exists and is confirmed.

  6. 06Competition

    What is the alternative, including doing nothing?

    Evidence: Named, with your differentiation per criterion.

  7. 07Process

    What are the steps and dates to signature?

    Evidence: Mutual action plan the buyer has edited.

  8. 08Risk

    What is most likely to kill or slip this deal?

    Evidence: Named risk with an owner and a next action.

Weekly operating cadence

Fixed agendas. Decisions, not status.

  • Monday — Forecast call (45 min)

    Sales leader, reps, RevOps

    Commit and Most-likely deals only. Every deal states its close date, next step and what changed since last week. RevOps records the number; no re-litigating stages.

  • Tuesday — Deal inspection (60 min, rotating)

    Rep, manager, solutions lead

    Two deals per rep taken through the rubric. Output is actions with owners, not status. Deals failing a stage's exit criteria move backwards that day.

  • Wednesday — Pipeline generation review (30 min)

    Marketing, BDR lead, RevOps

    Opportunity creation against the coverage requirement for the quarter two quarters out. Shortfalls trigger campaign or territory changes, not quota changes.

  • Monthly — Inspection of the inspection (60 min)

    Leadership

    Forecast accuracy versus actual, stage conversion, slip rate, ageing by stage, ramp progress by cohort. Fix the model, then the message.

Forecast accuracy targets

Measured, published and owned by RevOps.

  • Quarter-start commit vs. actual±10% by quarter 3
  • Week-4 forecast vs. actual±5%
  • Deals slipping a quarterunder 20%
  • Pipeline coverage entering a quarter3× quota

Onboarding

Productive at month four, against gates.

Certification gates, not a reading list. A rep who misses a gate repeats it before taking new accounts — which is also what makes ramp measurable enough to model.

WindowFocusCertification gate
Week 1Company, market and category narrative. Shadow four live calls.Pass the five-minute positioning pitch.
Week 2Product mechanics and the technical evaluation motion.Deliver a full demo to the enablement owner.
Week 3Discovery framework, objection handling, competitive comparisons.Role-play discovery scored against the rubric.
Week 4–6Own outbound sequences on named accounts; co-run live meetings.First self-sourced opportunity accepted at stage 1.
Week 7–10Full territory ownership with manager in-deal support.Three deals passing stage-2 exit criteria.
Week 11–16Independent selling; weekly rubric review only.Pipeline at 3× quarterly quota — productive at month four.

Hiring triggers

Both tests pass, or the cohort waits.

Coverage test: existing reps enter the quarter at 3× quota coverage. Adding reps to a thin funnel lowers win rate for everyone.

Span test: no frontline manager carries more than six reps, and no manager onboards more than four new reps at once.

Enablement test: the curriculum, certification gates and owner exist before the offer is signed — otherwise ramp stretches past four months.

Support test: solutions engineering and customer success ratios hold at the new rep count, or technical evaluations become the bottleneck.

Put the charter to work

Test the hiring triggers against a real plan.

The planner prices out what this cadence assumes: ramp you can measure, coverage two quarters out, and hiring dates that still pay back inside the year.