How do I get my fractional CRO to present a 30-60-90 plan to my board in 2027?

Building the mandate before the calendar invite

The most common reason a fractional CRO never presents to a board is that nobody ever asked them to, in writing, with a date attached. Fractional revenue leaders operate on scoped engagements — typically 10 to 25 hours a week across three to nine months — and they optimize for whatever the statement of work names as a deliverable. If the SOW says "pipeline coverage improvement and sales process documentation," board communication is not on the list, and the CRO is behaving correctly by not preparing a deck.

Fix the input, not the person. Amend the scope of work, or add a one-page addendum, that names four specifics: the artifact (a 30-60-90 plan in the board's template), the audience (full board, not just you), the date (the next scheduled meeting, with the pre-read due five business days prior), and the standing cadence (a written progress update against that plan at every subsequent board meeting). Attach a small number of hours to it explicitly — a serious board plan plus a rehearsal is realistically 8 to 15 hours of work, and if you don't fund those hours you are asking someone to donate them out of the hours they were going to spend on pipeline.

Two adjacent scope items are worth adding while you have the document open. First, data access: the CRO cannot build a credible plan from a CRM they can only read through your screen share, so grant a licensed seat with reporting rights, plus read access to the billing or finance system for actual recognized revenue. Second, the right to talk to two or three customers and two or three reps directly. A plan built only from dashboards reads like a plan built only from dashboards, and boards can tell.

Set expectations with the CRO about the nature of the ask. Many fractional operators come from full-time CRO or VP Sales roles where board presentation was routine; others come from consulting backgrounds where the client, not the board, was always the audience. Ask directly in your next one-on-one: how many times have you presented to a board, and what format did they use? The answer determines whether you're removing a scheduling obstacle or coaching someone through their first board deck. Both are solvable. They require different amounts of your time.

Finally, be honest about the political read. A board that has not met your fractional CRO may interpret the introduction as a signal — either that you've brought in real help, or that you've outsourced a function the board expected you to own. Get ahead of that by framing the presentation in your own board pre-read: "I've asked our fractional CRO to own the revenue plan and present it directly, so you can question the source rather than my summary of the source." That single sentence converts a potential red flag into evidence of operating maturity.

The end-to-end process from mandate to standing agenda item

The sequence below is what a clean version looks like when the board meets quarterly and you have roughly six weeks of runway. Compress it if you have less, but do not skip the dry run — that is where nearly every fixable problem gets found.

Week one is scope and access. You amend the SOW, provision CRM and finance access, and send the CRO the last two board decks so they can copy the house format rather than invent one. Week two is diagnosis: the CRO pulls actual funnel data, interviews reps and a few customers, and builds a baseline. Week three is the draft plan. Weeks four and five are your review plus a dry run with you and ideally one friendly board member or advisor playing skeptic. Week six is the pre-read distribution and the meeting itself.

Two details in that flow matter more than they look. The pre-read deadline is a forcing function — a plan that must be finished five business days early is a plan that gets finished, and it gives directors time to arrive with real questions instead of clarifying ones. And the loop back from "numbers defensible" to diagnosis is not a failure state; it is the normal outcome of a first dry run, because the first draft of any 30-60-90 plan overstates what is knowable at day zero.

The standing-agenda step is the one founders forget. A one-time presentation is theater. A recurring five-minute slot where the CRO reports green, yellow, or red against the same 30-60-90 commitments converts the plan into an accountability instrument. It also protects the CRO: when the board sees the plan tracked over two or three meetings, a miss reads as a variance to be discussed rather than a surprise.

What actually belongs in each of the three windows

Boards do not want a to-do list. They want a hypothesis about why revenue is underperforming, a set of falsifiable bets, and a date by which each bet resolves. Structure the three windows around escalating commitment.

The first 30 days are diagnostic and should be almost entirely observation with a small number of no-regret fixes. Concretely: complete a funnel audit with stage-by-stage conversion rates, interview every rep and at least five recent won and lost accounts, validate the CRM's data hygiene, and document the current sales process as it actually runs rather than as the handbook describes it. The deliverables are a baseline scorecard and a ranked list of the three biggest leaks. The no-regret fixes are things nobody will argue about — a stalled-deal cleanup, a working definition of a qualified opportunity, a weekly forecast call that actually happens.

Days 31 to 60 are for the first structural changes. This is where the CRO installs a forecast methodology, rewrites qualification criteria, fixes routing or territory problems, and starts a targeted pipeline-generation motion against the leak identified in the first window. Anything that requires hiring, a new tool purchase, or a compensation change gets scoped here but not necessarily executed here, because those all have longer lead times than 30 days.

Days 61 to 90 are for proof and handoff design. The board should see early signal on the leading indicators — meetings booked, stage-two conversion, average cycle length — plus a hiring plan, a compensation recommendation, and an explicit statement of what happens after day 90. A good fractional CRO writes their own succession into the day-90 slide: either the engagement extends with a narrower scope, or the company hires a full-time leader and the fractional stays on for a defined transition, or the work is done and the engagement retires.

The single most valuable line in the whole deck is the one that says what the CRO will not do. Fractional operators fail when the scope quietly expands to include marketing, customer success, partnerships, and pricing. Naming the fence in front of the board makes it hard for anyone — including you — to move it casually later.

Where this creates revenue, and where it quietly leaks it

The value of a board-presented plan is not the presentation. It is the forced specificity. A plan written for you can stay at the level of "improve conversion." A plan written for directors who will ask "from what to what, by when, and how will we know" cannot.

The revenue creation shows up in three places. Forecast accuracy improves first, usually within a quarter, because the act of committing to a number in front of a board is a very effective filter on optimism — teams that adopt a documented qualification standard and a weekly inspection cadence typically tighten forecast variance materially inside two quarters. Second, resource decisions get faster: a board that has seen the plan approves the two-rep hire in the meeting rather than three weeks later over email. Third, the RevOps backlog gets prioritized against revenue impact instead of whoever complained loudest, because the plan names which systems work blocks which revenue motion.

The leaks are just as real. The largest one is attention displacement — if your fractional CRO spends 15 hours on a board deck out of a 40-hour month, that is nearly 40 percent of the engagement spent on communication rather than on revenue. Fund the hours separately or accept the trade explicitly. The second leak is plan theater: a beautiful 30-60-90 that nobody tracks after the meeting costs you the preparation time and buys nothing. The third is authority confusion. If the board starts directing the fractional CRO in the meeting, and you are not in the loop, you now have two bosses giving one part-time contractor conflicting priorities. Agree in advance that board input becomes input to you, and you re-prioritize.

There is an adjacent leak worth naming because it shows up constantly in fractional engagements: the plan commits to metrics the company cannot actually measure. If the CRO promises stage-two-to-stage-three conversion improvement and the CRM does not enforce stage entry criteria, the number will move because of hygiene changes rather than performance changes, and the day-90 review will be an argument about instrumentation. Have the CRO flag every metric in the plan as either "measurable today," "measurable after a RevOps fix," or "proxy only." Boards respect that distinction. They lose trust fast when they discover it was hidden.

Concrete numbers, benchmarks, and what to budget

Fractional CRO engagements in the mid-market generally run in the low-to-mid five figures per month, scaling with hours committed — a one-day-a-week arrangement sits far below an embedded three-day-a-week engagement. Whatever your rate, translate it to an hourly figure and use that to price the board work honestly. If you're paying for 40 hours a month and the board plan plus dry run plus deck revisions consumes 12, you have bought roughly a third of a month of communication. That may be a great trade in a fundraising quarter and a bad one in a make-the-number quarter.

Time-box the presentation itself. Fifteen to twenty minutes of prepared material and ten to fifteen minutes of questions is the shape that works in most quarterly board meetings; anything longer and you are eating the rest of the agenda. That constraint should drive the deck: roughly eight to twelve slides, one page of appendix per major claim, and a single-page summary that a director can read on their phone in the parking lot.

Set the pre-read at five business days. Three is too short for busy directors, seven invites the plan to be rewritten twice before it's presented. Include in the pre-read the baseline scorecard, the three-window plan, and the explicit asks — money, headcount, or decisions.

On the plan's own numbers, insist on ranges rather than points for anything past day 30. "Pipeline coverage moves from 2.4x to 3.0-3.5x by day 90" is a defensible commitment. "Pipeline coverage will be 3.4x" is a hostage. Boards read a false-precision number as either naivety or spin, and both cost credibility. The exception is anything fully within the CRO's control — process artifacts, cadence changes, documentation — which should be committed as binary done-or-not by a specific date.

Track a small number of leading indicators rather than a scoreboard. Four to six is the practical ceiling for a board slide: new qualified pipeline created per week, stage conversion at the one stage you're attacking, average sales cycle, forecast variance, and rep ramp status if you're hiring. Everything else lives in the appendix. A board that sees twenty metrics remembers none.

Budget for the second-order costs too. CRM seat and reporting access, possibly a data-hygiene contractor for two weeks, and your own time — realistically four to six hours across the six weeks for reviews and the dry run. Founders systematically underestimate that last one and then get frustrated when the draft they see two days before the meeting isn't what they wanted.

Pitfalls, and the checklist that prevents most of them

The failure modes are predictable enough to enumerate, and nearly all of them are preventable at scope-setting time rather than at deck-review time.

The plan is a strategy essay. Some fractional operators, especially those from consulting, produce a beautifully argued document with no owners and no dates. The fix is a hard template requirement: every line item has a name and a date, or it goes in the appendix as context.

The CRO presents your plan instead of theirs. If you rewrite the deck, the board will detect it in the Q&A, because the presenter won't defend the numbers with conviction. Review for accuracy and clarity, not for voice. If you disagree with a bet, argue it out before the meeting and let the CRO present whatever survives that argument as genuinely their own.

The first 30 days promise results. A plan that commits to revenue outcomes in month one is not credible and will be attacked. The first window earns credibility through diagnostic rigor, not through wins.

Nobody owns the follow-up. Without a standing agenda slot and a named owner for the progress update — usually the CRO, occasionally you — the plan dies after one meeting. Get it into the minutes.

Authority is never defined. Say out loud, in the meeting, what the fractional CRO can decide alone, what needs you, and what needs the board. Compensation changes and hiring almost always need at least you; process and cadence should not.

The engagement ends mid-plan. If your contract runs out at day 75 of a 90-day plan, either extend it before the presentation or reshape the plan to fit the term. Presenting a 90-day plan on a 60-day contract is an unforced error the board will catch.

Run that checklist twice: once at week two when the draft is forming, and once the day before the pre-read goes out. The week-two pass catches scope and access problems while there's still time to fix them; the pre-read pass catches the plan-quality problems.

Adjacent situations this same playbook covers

The mechanics generalize past the fractional CRO. A fractional CFO presenting a cash and unit-economics plan, a fractional CTO presenting a technical debt and roadmap plan, an interim VP Sales bridging to a permanent hire — all of them face the same three obstacles: no written mandate, no data access, no rehearsal. The remedy is identical.

The pattern also applies downstream, to the layer most companies neglect. Your RevOps lead — fractional or full-time — should be presenting the systems and data plan that makes the CRO's plan measurable. In practice these two documents should be built together, because a revenue plan whose metrics can't be instrumented is a wish. If you have both roles engaged, have them co-author the baseline scorecard section and let the CRO present it with the RevOps lead available for questions.

One more adjacent case: the board that wants to hear from the fractional CRO more often than quarterly. This usually surfaces after a bad quarter and it is a signal worth reading carefully. If a director asks for monthly access to your revenue leader, they are either genuinely trying to help or beginning to lose confidence in the reporting line. Either way, structure it — a short written monthly update to the board with an optional call, rather than ad-hoc director calls that consume the engagement's hours and route around you.

Finally, consider the conversion question early. A fractional CRO who presents well to a board is auditioning, whether or not anyone says so. Decide before the meeting how you'd answer if a director asks "why isn't this person full-time?" Having a real answer — the role doesn't need full-time yet, or we're evaluating conversion at day 90, or the CRO's model is deliberately portfolio-based — is far better than improvising one in the room.

Related questions

How long should a fractional CRO engagement run before a board presentation?

Enough time to have real data — typically 30 to 45 days in. Presenting in week two produces a plan built on assumptions. Presenting at day 60 wastes the diagnostic window's value as a board conversation.

Should the founder present alongside the fractional CRO?

Open with two minutes of framing, then hand over fully and stay quiet through Q&A unless a question is genuinely yours. Interrupting to rescue answers signals to the board that you don't trust the person you hired.

What if the board reacts badly to the plan?

Treat it as data, not a verdict. Ask the CRO to send a written response within a week addressing each objection — revised, defended, or acknowledged as unknown. A calm written follow-up recovers more credibility than a defensive live rebuttal.

Does the 30-60-90 plan replace the board's revenue forecast?

No. The forecast is a number the company commits to; the 30-60-90 is the operating plan meant to make that number achievable. Present them together so directors can see the mechanism behind the commitment.

Can a fractional CRO plan work without a dedicated RevOps function?

Yes, but with fewer measurable commitments. Without RevOps, more of the plan's metrics fall into the "proxy only" bucket. Label them honestly rather than promising precision the systems can't deliver.

FAQ

Can I require board presentations in a fractional CRO contract after it's already signed?

Yes — most fractional engagements are amended routinely, and adding a named deliverable with associated hours is a normal mid-engagement change. Put it in writing as an addendum rather than agreeing verbally in a one-on-one, and attach the hours so nobody is surprised when the invoice reflects the work.

What format should the 30-60-90 plan take?

Whatever format your board already uses. Send the CRO your last two board decks and ask them to match the house style. A plan that looks like every other board document gets read on its merits; one that arrives as a consulting deliverable in someone else's template invites a debate about the deck.

How much of the plan should be committed versus exploratory?

Everything inside the CRO's direct control — process, cadence, documentation, qualification standards — should be a firm commitment with a date. Everything dependent on hiring, market response, or systems changes should be a range with a stated assumption. Boards accept uncertainty they can see; they punish uncertainty they discover later.

Should the fractional CRO have access to the full board materials?

Give them the revenue-relevant sections, prior decks, and the meeting norms. Full access to compensation, cap table, or legal matters is rarely necessary and complicates the confidentiality picture. Ask your counsel about the NDA scope before expanding access beyond the revenue function.

What happens to the plan if the engagement ends at day 90?

The day-90 slide should include the handoff design: what's finished, what's in flight, who owns each in-flight item next, and what documentation exists. A fractional CRO who leaves without a written handoff has delivered a project, not a function. Make the handoff document a contractual deliverable from the start.

How do I tell whether the plan is actually good?

Three tests. Could a competent stranger execute it from the document alone? Does every claim have either a number or an explicit "we don't know yet" attached? And would you bet your own money on the day-90 targets? A plan that fails the third test is aspirational, and the board will find that out before you do.

Sources

• https://www.sec.gov/education/smallbusiness — SEC small business resources on governance and reporting obligations
• https://corpgov.law.harvard.edu/ — Harvard Law School Forum on Corporate Governance, board practice and director expectations
• https://www.nacdonline.org/ — National Association of Corporate Directors, board meeting and reporting norms
• https://hbr.org/topic/subject/boards — Harvard Business Review coverage of board effectiveness and CEO-board dynamics
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales — McKinsey research on commercial growth and sales operations
• https://www.gartner.com/en/sales — Gartner sales research on revenue operations and forecasting practice
• https://www.bain.com/insights/topics/sales-and-marketing/ — Bain insights on go-to-market and commercial effectiveness
• https://www.sba.gov/business-guide — U.S. Small Business Administration guidance on planning and operating documents

Related on PULSE

• [Should I Hire a Fractional CRO If I Need a 30-60-90 Plan Before a Board Meeting in 2027?](/knowledge/tl0581)
• [How do I turn a fractional CRO's 30-60-90 plan into a board-ready revenue forecast in 2027?](/knowledge/tl21810)
• [How do I prepare a fractional CRO onboarding plan during their first week in 2027?](/knowledge/tl21796)
• [What should I include in a fractional CRO's exit plan in 2027?](/knowledge/tl21795)
• [How do fractional CRO engagements get priced and structured in 2027?](/knowledge/tl10007)
• [Where do I get a fractional CRO in 2027?](/knowledge/tl21459)