What a Fractional CRO Does in the First 90 Days: Week-by-Week Playbook

A fractional chief revenue officer engagement lives or dies on the first 90 days. The reason is structural. A fractional CRO operates 2–3 days per week inside a company that has built a sales motion largely around the founder's personal selling ability. The CRO has to build their own operating credibility fast, identify the highest-leverage problems without a six-month listening tour, and generate visible change before the board's patience runs out.

The arc: diagnostic audit (Days 1–7), pipeline rebuild (Weeks 2–4), process install (Weeks 5–8), and handoff prep (Weeks 9–12). Each phase has clear deliverables. If you can't point to those deliverables at the end of each phase, something is wrong — with the engagement or with what the company is willing to change.

If you're still deciding whether fractional is the right model, what a fractional CRO is and when to hire one covers the definition and role boundaries. The fractional leadership service page explains the commercial structure.

The first week is not an orientation. It is a structured diagnostic sprint.

Pipeline coverage. Pull 90 days of closed deals. Calculate coverage by stage: how many opportunities were in each stage 60 days ago, and what percentage closed? In most first-week audits, Stage 4 is inflated with stale opportunities that haven't moved in 45 days, and the founder's "strategic" deals represent 40% of total pipeline value.

Win/loss patterns. Review the last 20 closed-won and 20 closed-lost deals. Look past the stated reason — reps always say "price." Deals lost consistently at Stage 3 indicate a discovery problem. Deals lost at Stage 4+ indicate a closing or commercial problem.

Qualification language. Ask two reps to independently score the same three live deals. If scores diverge by more than one tier on any criterion, you don't have a shared qualification language — you have a field with a label attached. This is one of the most common sources of forecast inaccuracy and one of the most fixable problems in the first 30 days.

Rep skill assessment. Listen to three discovery calls per rep — recorded, not live — scoring against a rubric covering problem identification, stakeholder mapping, multi-threading, and commercial framing. The gap between reps is usually larger than the founder expects.

Deal-room hygiene. Open the top 10 deals by value. Check: last update date, economic buyer identified by name, next committed action with a date, mutual action plan for deals above $25K ACV. In most audits, more than half have no documented next action and no identified economic buyer.

By Day 7, the fractional CRO should have a written one-page diagnostic: the three problems with the highest revenue impact, the evidence for each, and the order of attack.

The pipeline rebuild phase is operational. The goal is to move the current pipeline from unreliable to trustworthy — not by adding deals, but by cleaning what exists and installing the discipline to keep it clean.

Fix the qualification language. Run a 2-hour workshop where the team builds the scoring rubric together, applies it to three live deals, and calibrates disagreements out loud. The output is a single-page qualification card. This is the highest-leverage intervention in the first 30 days: it fixes forecast accuracy, shortens sales cycles, and reduces late-stage deal deaths.

Multithread the top 5 deals. For each Stage 3+ deal, map known stakeholders against the actual buying committee. In most B2B SaaS deals at $30K–$100K ACV, the deal is stalled because only one stakeholder has been engaged and that person doesn't have budget authority. Coach each rep on a specific multithreading play — not general advice about executive access.

Install the forecast cadence. Weekly pipeline review, fixed agenda: Stage 3+ deals, ordered by close date, scored against the qualification card. The rep states the next committed action; the CRO challenges the close date against the score. The first two meetings will be uncomfortable. By Week 4 it should run in 45 minutes with consistent scoring.

Start removing the founder from mid-funnel. For deals below $50K ACV, the fractional CRO takes over the calls in Week 3. Above $50K ACV, the rep leads and the CRO shadow-coaches from a private Slack thread. The founder attends only when there is a specific relationship or strategic reason.

By Week 5, the pipeline should be cleaner, the forecast call running consistently, and reps sharing a qualification language. The process install phase builds the infrastructure that makes these behaviours self-sustaining when the fractional CRO is not in the room.

Manager review cadence. Install a 1:1 cadence mirroring the pipeline review structure: deals, qualification scores, next actions, coaching needs. The goal is for the manager to run the pipeline review independently by Week 8. This is the moment you find out whether the existing management layer has the instincts to run the process or has been hiding behind the absence of one.

Stage exit criteria. Write stage exit criteria into the CRM as binary checkbox conditions. A deal should not advance from Stage 2 to Stage 3 unless: economic buyer identified by name and title, a defined problem documented, a next step agreed in writing with a date. Reps will game the checkboxes initially — the gaming reveals where criteria need tightening.

Qualification gates. Apply the rubric as a formal gate at Stage 3 entry. Any deal scoring below the threshold requires manager review before it advances. The first time a manager declines to advance a deal the rep was confident about is the moment the process becomes real.

Coaching library. Record 2–3 coaching call segments per rep — one strong, one average, one with an identifiable flaw. Build a private library in Notion or Loom. This becomes onboarding material for the next hire and the reference point for performance conversations.

The handoff phase is the one most fractional CROs underinvest in — and it determines whether the 90-day investment produces durable change.

Playbook. Document the qualification framework, stage criteria, pipeline review agenda, coaching rubric, and ICP definition in a single working document. Not a deck — a document with examples from real deals and the reasoning behind each design decision. The test: can a new AE hired in Week 14 score a deal and run a pipeline review without talking to anyone from the first 90 days? If not, it's a summary, not a system.

Training handoff. In Weeks 9–10, run two pipeline reviews where the manager leads and the fractional CRO observes, offering calibration notes at the end. In Weeks 11–12, two more with the fractional CRO absent. The first meeting without the CRO reveals whether the manager has internalised the method or has been mirroring questions without understanding why.

Monitoring dashboards. Three dashboards: pipeline coverage by stage (weekly), win rate by stage-exit criteria pass/fail (monthly), and forecast accuracy rolling 4-week average (weekly). Without these, the company reverts to managing by anecdote within 60 days.

Succession plan. By Week 12, the fractional CRO should present a clear answer to: who runs this function when I exit? Options: an existing team lead elevated with a coaching plan, a VP of Sales hire with a role brief, or a reduced fractional arrangement explicitly scoped. The founder re-absorbing the function is not an acceptable answer at Week 12.

For the diagnostic that sets this engagement up, the pre-CRO sales audit describes the 14-day assessment that identifies which problems the 90-day playbook needs to solve.

Boards who have endorsed a fractional CRO arrangement will probe at three points.

Day 30. A written diagnostic: where pipeline was lost, what the qualification language gaps were, what the founder's deal involvement looked like quantitatively. Not opinions — numbers. Pipeline coverage by stage, win rate by close-reason category, deals with no documented economic buyer. The board should agree on the problems, even if they disagree on the remedies.

Day 60. Evidence of mechanical change. The qualification rubric is in daily use with consistent scores across reps. The forecast call is running on schedule with decreasing variance. At least three of the top five deals have been multithreaded. Founder deal involvement has dropped measurably.

Day 90. A handoff package: the operating playbook, the succession plan, the monitoring dashboards, and a forward forecast built by the sales team without the fractional CRO constructing it. If the honest answer at Day 90 is "the function will regress without the CRO," the engagement has not achieved its primary objective.

Most fractional CRO engagements that underdeliver fail for one of three reasons.

Failure mode 1: The founder pulls the fractional CRO into one big deal. A large deal — $200K ACV, a marquee logo — arrives at a critical juncture in Week 3. The founder asks the fractional CRO to join the calls. The CRO agrees. Over the next four weeks, 60–70% of the CRO's time goes into this one deal. Qualification work stalls, pipeline reviews become irregular, and the process install never happens. The big deal may not close. The rest of the pipeline is worse than Day 1.

The rule: a fractional CRO should touch a deal only to coach the rep running it. If the CRO is personally on the call, the engagement has lost roughly 80% of its structural value.

Failure mode 2: No operating authority is delegated before Day 1. A fractional CRO who cannot change CRM stage criteria, close out a stale deal, or have a performance conversation with an underperforming rep is an expensive observer. Before Day 1, the founder should write down the specific decisions the CRO can make without approval. If that list is vague, the CRO will default to generating recommendations the founder defers — and by Day 60 has stopped making them.

For a comparison of how the fractional CRO model differs from a full-time CRO on authority and ownership, particularly at the $5M–$15M ARR range, that article covers the boundaries both models require before the hire.

Failure mode 3: The engagement is scoped as infrastructure, not transformation. Some fractional arrangements are sold as a playbook-building project: document the process, hand off templates, exit. A playbook that has never been operated — never tested in live pipeline reviews, never resisted by reps, never revised based on what broke — is not a playbook. It is a document. Documents don't fix sales processes. The fractional CRO has to run the Monday pipeline review, coach the stalling deals, and have the uncomfortable conversation with the rep who hasn't absorbed the qualification framework four weeks in. That discomfort is what makes the infrastructure stick.

If you're evaluating which structure fits your revenue leadership gap, fractional sales leader vs. CRO and founder-led sales to fractional CRO address the decision from different angles. For what a specific engagement looks like in practice, working with Iryna Avrutova as your fractional CRO covers the operating model from first call to exit.