How do I structure a fractional CRO's first 90-day plan when the sales team has never had a formal onboarding process in 2027?

The job this fractional role is actually hired to do

A full-time CRO gets twelve to eighteen months before anyone asks hard questions. A fractional one gets a quarter. That asymmetry should shape everything about how you write the 90-day plan, because the buyer is not paying for presence — they are paying for a finished thing that outlives the contract.

When a sales team has never had a formal onboarding process, the mandate narrows to something unusually concrete. The fractional CRO is hired to build the machine that turns a new hire into a quota-carrying rep on a predictable timeline. That is the deliverable. Everything else — pipeline reviews, forecasting cadence, territory design, comp restructuring — is either upstream of it or downstream of it, and the plan should say so out loud rather than pretending all of it is equally urgent.

Why does this specific gap attract fractional leadership rather than a full-time hire? Three reasons show up repeatedly. First, the company is usually too small to justify a $300K+ full-time executive but too big to keep winging ramp. Somewhere between the fifth and the twentieth sales hire, tribal onboarding breaks: the founder who used to sit with every new rep now has a board, a product roadmap, and two other departments. Second, the work has a natural end. Onboarding is a build-and-hand-off project — once the curriculum, certification, and manager cadence exist, an enablement lead or a sales manager can run it. Third, the diagnosis is genuinely hard to do from inside. Internal leaders are too close to the existing habits to see which of them are load-bearing and which are just folklore.

The scope document matters more here than in almost any other fractional engagement, because "build onboarding" is elastic enough to swallow a year. A well-written mandate names what ships: a competency map by ramp stage, a certification gate before a rep carries full quota, a manager-led coaching cadence with a fixed agenda, and a scorecard that shows time-to-first-deal and time-to-full-quota by cohort. Four artifacts, ninety days. If the engagement delivers those, the company has something it can run without the fractional CRO in the room.

There is a second job hiding inside the first, and it is worth naming in the plan because buyers underweight it. The fractional CRO is also installing a *standard*. Right now every new rep learns the job from whoever happens to be free that week, which means the company has as many onboarding processes as it has managers. The fractional hire's real leverage is converting that private knowledge into a shared, inspectable process — one that survives turnover in the sales manager seat, one that a VP of Sales hired in month seven can inherit rather than reinvent.

Finally, be honest about what the fractional CRO cannot do in 90 days. They cannot fix a broken product-market fit, they cannot rebuild a compensation plan from scratch without destabilizing the quarter, and they cannot personally coach twenty reps to quota. A good 90-day plan states these exclusions. Buyers trust a scope document that says no.

How onboarding work fits the RevOps stack

Onboarding is not a sales-only artifact. It sits at the intersection of four functions, and the reason it so often rots is that no single owner spans all four. RevOps is the natural home, which is why a fractional CRO building onboarding should be explicitly plugged into the RevOps function rather than operating beside it.

Upstream, onboarding depends on product marketing for positioning and messaging, on enablement for curriculum design, and on sales operations for CRM hygiene and reporting. Downstream, it feeds forecasting (a rep who ramps late distorts the pipeline model), territory planning (you cannot assign accounts to someone who cannot yet work them), and compensation (ramp quotas and guarantees only make sense if you know how long ramp takes). A fractional CRO who treats onboarding as an isolated training event will produce a curriculum that nobody maintains and that the CRM cannot measure.

The practical integration point is a single source of truth for ramp. Define the stages — say, pre-start, week one, weeks two through four, months two and three, and post-ramp — and attach to each stage an owner, an artifact, and a measurable exit criterion. RevOps owns the measurement layer. Sales managers own the coaching layer. Enablement owns the content layer. The fractional CRO owns the design and the first two cohorts, then hands the keys over.

This is also where the fractional engagement earns its fee beyond the artifacts. A RevOps function that has never measured ramp does not know whether its problem is hiring, curriculum, coaching, or territory. The fractional CRO's first thirty days are largely a diagnostic exercise: pull the last four to six cohorts, chart days-to-first-opportunity and days-to-first-closed-won, and interview every rep hired in the past year. Almost always the data reveals that the bottleneck is not where leadership assumed. Founders typically blame the curriculum. The data more often points at manager bandwidth or at a first-month workload that buries new reps in product training before they ever speak to a prospect.

There is an adjacent workflow worth wiring in early: the hiring handoff. Onboarding actually begins before day one, in how the role is described, what the recruiter promises, and what the offer letter says about ramp expectations. Companies that skip this step onboard reps into a job that does not match the job they accepted, and the resulting attrition looks like a training failure when it is a recruiting failure. A thorough 90-day plan includes a short upstream fix here — a one-page role reality document that recruiting uses in every interview loop.

Engagement models, pricing, and what a 90-day build actually costs

Fractional CRO engagements come in a handful of recognizable shapes, and the shape you pick determines what a 90-day onboarding build can realistically produce.

The most common is a retainer at a fixed monthly rate for a defined number of days per month. Typical market ranges run from roughly $5,000 to $20,000 per month depending on company stage, geography, and whether the fractional executive is carrying a team or advising one. A lighter engagement at two to four days per month suits a company that mainly needs design review and a plan. A heavier engagement at six to ten days per month suits a company that needs the fractional CRO in the room for hiring, ride-alongs, and live coaching during the pilot cohort.

A second model is project-based, with a fixed fee for a defined deliverable. For an onboarding build, this is often quoted as a flat fee covering the audit, the curriculum, the certification gate, and two pilot cohorts. It is attractive because the buyer knows the number up front and the scope is bounded. The trade-off is that change management — arguably the hardest part — gets squeezed, because the fee is tied to artifacts rather than to adoption.

A third model, less common but real, is fractional-to-full-time conversion, where the engagement carries an explicit option to convert at a defined milestone. This can work well for onboarding specifically, because the natural conversion point is the moment the process is running and the company needs a permanent owner. If you take this route, put the conversion terms in the original agreement; retrofitting them later is awkward for both sides.

A fourth shape worth mentioning: fractional CRO paired with a fractional enablement or RevOps contractor. Onboarding is unusually amenable to this because the design work and the build work are separable. A fractional CRO designs the competency map and the certification standard; a fractional enablement lead builds the actual content, the LMS structure, and the assessment items. Companies that try to get both from one person usually find that the content build consumes the entire engagement and the strategic design never gets finished.

What drives the number up or down? Team size matters less than you would think. What matters more: how many hiring managers are involved, whether the CRM is clean enough to measure ramp, whether there is any existing documentation at all, and whether the sales leader is a partner or a skeptic. A skeptical sales leader can add four to six weeks to any onboarding build, because every artifact gets relitigated. Ask about that dynamic in the buying process — it will tell you more about the likely outcome than the rate card will.

One pricing caution specific to this work: avoid engagements priced purely on hours. Onboarding builds involve a lot of asynchronous review and iteration, and hour-based billing creates a perverse incentive to attend meetings rather than to ship. Fixed-fee-per-phase or retainer-with-defined-deliverables align better.

How to evaluate and shortlist fractional CRO candidates

The market for fractional revenue leadership has grown fast enough that the titles have outrun the substance. Plenty of capable people use the label; so do plenty of people who have never carried a number. Shortlisting well means testing for the specific thing you need — someone who has built onboarding from nothing, not someone who has inherited a mature program at a large company.

Start with the artifact test. Ask each candidate to walk you through an onboarding process they personally built, and ask to see it. Not a slide about it — the actual document, the actual competency map, the actual certification rubric. Candidates who have done this work have the artifacts and can explain the reasoning behind specific choices: why the certification gate sits at week six rather than week four, why the first-month quota is zero, why they cut the product training from three weeks to eight days. Candidates who have only managed an existing program will describe principles but not decisions.

Second, test the diagnostic instinct. Give them a stripped-down version of your own situation — headcount, average deal size, current ramp time, attrition in the first year — and ask what they would investigate in the first two weeks. Strong candidates ask about cohort data, manager span of control, and whether the CRM records first-touch activity. Weak candidates start proposing curriculum.

Third, probe the handoff plan. A fractional CRO who cannot describe how the process survives their departure is a retainer trap. Ask directly: who owns this on day 91, and what does that person need to have learned from you by then? The best answers name a specific role (often a sales manager or an enablement hire) and a specific transfer mechanism — shadowing the second cohort, co-facilitating the certification review, owning the scorecard from week eight onward.

Fourth, check the RevOps fluency. Onboarding that cannot be measured will quietly die within two quarters. Ask how they would instrument the process: what fields in the CRM, what dashboard, what review cadence. If they cannot describe the measurement layer in concrete terms, the build will be a training event rather than a system.

Fifth, get references from companies of similar size and stage, and ask the reference a specific question: what did the fractional CRO ship that you are still using two years later? Vague praise is a soft signal. Named artifacts still in use are a strong one.

Finally, be wary of the generalist pitch. Fractional CROs are often marketed as covering everything from pricing to partnerships to board reporting. Breadth is fine, but for this engagement you are buying depth in one narrow area. A candidate who says "onboarding is where I would start, and here is why it is the highest-leverage thing in your business right now" is showing you the prioritization instinct you are paying for.

Buyer decision framework

The decision framework for this purchase is not "who is the most senior person we can afford." It is a fit question across four axes, and getting it wrong in either direction wastes the engagement.

The first axis is whether onboarding is genuinely the constraint. If first-year attrition is low and reps are hitting quota by month four, the problem is elsewhere and a fractional CRO should be scoped to that problem instead. Running an onboarding build against a hiring problem produces a beautiful curriculum and no improvement in outcomes. Spend the first two weeks of any engagement validating the diagnosis before committing to the build.

The second axis is engagement shape, covered above. The rule of thumb: if you need design and a plan, buy days. If you need the process built and proven with a live cohort, buy a project with a defined end state.

The third axis is the internal partner. Every successful onboarding build has a named internal owner from day one — usually the sales leader or a senior sales manager. That person is not a spectator; they co-design, they run part of the pilot, and they inherit the process. Companies that hire a fractional CRO and then route everything through a project manager get a document instead of a system.

The fourth axis is measurement readiness. Before you start, confirm that the CRM can answer: when did this rep start, when was their first qualified opportunity created, when was their first closed-won deal, and when did they reach full quota attainment? If it cannot, the first deliverable of the engagement is fixing that, because without it you will never know whether the new process worked.

One more decision worth making explicitly: what happens at day 90 if the build is only 70% done? The best contracts build in a short extension option at a pre-agreed rate, triggered by a defined milestone rather than by open-ended need. That protects the buyer from a cliff and protects the fractional CRO from being forced to declare victory prematurely.

Related questions

How long should a fractional CRO engagement run for an onboarding build?

Ninety days is enough to audit, design, pilot, and launch if the scope is tight. Most engagements run three to six months, because the second cohort — the one that proves the process is repeatable — usually starts in month four. Budget for a short extension.

What should the fractional CRO deliver in the first thirty days?

A written ramp audit: cohort data on time-to-first-deal and time-to-full-quota, interview findings from every rep hired in the past year, and a one-page diagnosis naming the actual bottleneck. No curriculum yet. Diagnosis first, build second.

Should the fractional CRO report to the CEO or to the sales leader?

To whoever owns the commercial number, which is usually the CEO in companies small enough to need a fractional CRO. If there is a sitting sales leader, the fractional CRO should be scoped as a peer building a system, not as an evaluator of that leader's performance.

Can we run this build without dedicated enablement headcount?

Yes, but the content build will consume most of the engagement. Many companies pair a fractional CRO for design with a contractor or internal instructional designer for content production. Separating those two workstreams is usually the difference between finishing in 90 days and running long.

What is the single biggest reason these builds fail?

No named internal owner. The fractional CRO ships the process, the engagement ends, and nobody is accountable for running cohort three. Every successful build has a specific person who owns the process before the fractional engagement closes.

FAQ

How much should we expect to pay for a fractional CRO to build onboarding?

Retainers commonly run from roughly $5,000 to $20,000 per month depending on days per month and company stage, with fixed-fee project pricing available for a defined build. The variance is driven less by team size than by how many stakeholders must be aligned and whether the CRM can already measure ramp.

Do we need a fractional CRO at all, or could a sales manager build this?

A strong sales manager can run an onboarding process but rarely has the bandwidth to design one from scratch while carrying a team. The fractional CRO's value is the design work plus the political cover to change habits. If you have a sales manager with genuine spare capacity and process instincts, that person may be the better and cheaper answer.

What does a formal onboarding process actually include?

At minimum: a competency map defining what a rep must be able to do at each ramp stage, a curriculum with owners for each module, a certification gate before full quota, a manager coaching cadence with a fixed agenda, and a scorecard tracking time-to-first-deal and time-to-full-quota by cohort. Anything less is orientation, not onboarding.

How do we measure whether the new process worked?

Compare cohorts. Track days-to-first-qualified-opportunity, days-to-first-closed-won, percentage of reps reaching full quota by month six, and first-year attrition. A process that improves ramp time but not retention has fixed the wrong problem. Give it two full cohorts before drawing conclusions.

What happens to the process when the fractional CRO leaves?

It should be owned by a named internal person — typically the sales leader or a sales manager — who co-designed it and ran part of the pilot. The fractional CRO should be shadowed out, not handed off to. If the process only works when the consultant is in the room, the build failed.

Can this work for a team of five reps, or is it overkill?

For five reps, a full curriculum build is usually overkill. What a small team needs is a documented first-30-days checklist and a manager cadence. A fractional CRO can deliver that in a light engagement of two to four days per month, or you may find a strong sales manager can do it without outside help.

How does RevOps fit into the build?

RevOps owns the measurement layer: the CRM fields, the dashboard, and the review cadence that shows whether ramp is improving. Without that layer, onboarding becomes an unmeasured training event that quietly dies. The fractional CRO should design the process and RevOps should instrument it, working in parallel rather than sequentially.

Sources

• Harvard Business Review — research and articles on sales management and onboarding: https://hbr.org/topic/sales
• McKinsey & Company — growth, marketing, and sales insights: https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• Gartner — sales research and revenue operations guidance: https://www.gartner.com/en/sales
• HubSpot Sales Blog — sales onboarding and ramp benchmarks: https://blog.hubspot.com/sales
• Salesforce — sales analytics and CRM reporting resources: https://www.salesforce.com/products/analytics/overview/
• Society for Human Resource Management — onboarding research and practice guidance: https://www.shrm.org/topics-tools/topics/onboarding
• Sales Enablement Society — practitioner resources on ramp and enablement: https://www.salesenablementsociety.org/
• LinkedIn Sales Solutions Blog — sales team development and ramp content: https://business.linkedin.com/sales-solutions/blog

Related on PULSE

• [How do you build a sales onboarding curriculum from scratch?](/knowledge/tl0141)
• [What ramp metrics should RevOps track for new sales hires?](/knowledge/tl0187)
• [How do you structure a fractional RevOps engagement?](/knowledge/tl0203)
• [How do you hand off a process build from a consultant to an internal owner?](/knowledge/tl0226)
• [How do you measure time-to-first-deal by cohort?](/knowledge/tl0233)