How do I structure a fractional CRO's first 90-day plan when the company has no existing sales data in 2027?

The job this tool/role is hired to do

A fractional CRO brought into a company with no existing sales data is not hired to optimize a funnel — there is no funnel yet to optimize. The job is to build the instrumentation, the process, and the first real dataset simultaneously, while still producing enough early revenue signal that the board or founder believes the investment is working. That is a fundamentally different mandate than a fractional CRO walking into a company with two years of CRM history: there, the job is diagnosis. Here, the job is construction.

Three things have to happen at once, and a fractional CRO's calendar in month one should visibly reflect all three. First, define who the company actually sells to — not the aspirational ICP in the pitch deck, but a working hypothesis built from the founder's anecdotal wins, the product's actual usage patterns, and a handful of exploratory calls with the best current customers (even five or six paying accounts, if they exist, are more useful than zero). Second, stand up the mechanical layer: a CRM with defined pipeline stages, mandatory fields, and activity logging, because without this every week that passes generates zero usable data. Third, start selling — the fractional CRO or a founder-led motion needs live deals in the pipeline within the first two to three weeks, because the entire 90-day plan depends on having enough deal volume by day 60 to say something statistically meaningful, even if that "meaningful" is directional rather than definitive.

The company's existing muscle matters here. If the company has never sold in a structured way, the fractional CRO is also building the sales team's habits — call notes, next-step discipline, stage-exit criteria — at the same time as building the pipeline itself. That dual mandate is why generic 90-day sales leadership templates fail in this specific situation: they assume a CRM full of historical win/loss data to mine, a set of reps with tenure, and quota history to benchmark against. None of that exists. The plan has to be rebuilt from the ground up to treat the absence of data as the central constraint, not a footnote.

How it fits the RevOps stack

A fractional CRO's 90-day plan is not a standalone sales initiative — it has to slot into the broader RevOps stack the company will eventually run on, even if that stack is being assembled in parallel. The CRM becomes the system of record from day one, marketing (if it exists) needs to feed leads into the same pipeline stages the CRO defines, and finance needs early visibility into bookings definitions so revenue recognition doesn't get relitigated in month four. The plan below shows how discovery, instrumentation, and the live pilot connect into the stack the company keeps after the engagement ends.

Every box in that flow produces an artifact the company keeps: the ICP scoring model becomes marketing's targeting brief, the CRM instrumentation becomes the permanent system of record, and the pilot cohort's conversion numbers become the company's first real baseline for quota-setting and forecasting. This is the structural difference between a fractional CRO who leaves behind a document and one who leaves behind a working system — the RevOps stack has to survive the engagement, not just describe it.

Pricing, engagement models, and typical ranges

Fractional CRO engagements are almost always structured as a part-time, recurring commitment rather than a project fee, because the work — pipeline reviews, forecast calls, rep coaching — has to repeat weekly to matter. The most common structure is a monthly retainer tied to a fixed number of days or hours per week, commonly somewhere between one and three days weekly for an early-stage company, scaling up if the company is also expecting the CRO to run point on hiring the first full-time sales leader. Some engagements add a variable component — a bonus tied to pipeline generated or a small equity grant — particularly at companies too early-stage to pay a full market rate, though a fractional CRO worth hiring will usually insist the fixed retainer covers baseline compensation regardless of outcome, since in a zero-data environment the CRO cannot fairly be held to revenue targets they had no baseline to set.

Contract length matters more than the headline rate. A 90-day engagement that is explicitly scoped as "build the data and the process" should have a defined off-ramp at day 90: either the company extends the retainer into an ongoing fractional arrangement, converts the role to a full-time hire the CRO helps recruit, or the engagement ends with a documented playbook the company runs internally. Companies that skip this decision point tend to let fractional engagements drift indefinitely without ever re-evaluating whether fractional leadership is still the right structure once real pipeline data exists to hire against.

Pricing conversations should also separate "strategy and coaching" time from "hands-on selling" time. A fractional CRO who is expected to personally close the first pilot deals — common when the company has no other seller — is doing a different job than one who is purely advising a founder-led sales motion, and the engagement terms should reflect that split explicitly rather than leaving it ambiguous until month two, when disagreements about scope tend to surface.

How to evaluate and shortlist

Because there's no historical data to check a candidate's plan against, evaluating a fractional CRO for this specific situation comes down to how they reason about uncertainty, not how polished their deck is. Ask for a walkthrough of how they'd spend the first two weeks specifically — not the whole 90 days — because a candidate who can't name concrete day-one and day-five actions (which customers they'd call, what fields they'd add to the CRM, what they'd ask the founder) is still operating at a strategy-deck level of abstraction that won't survive contact with a company that has nothing built yet.

Check their instrumentation instincts directly: ask what the minimum viable CRM setup looks like for a company with zero pipeline history, and listen for whether they name specific stages, exit criteria, and required fields, or whether they gesture vaguely at "implementing a CRM." The candidates worth shortlisting will also push back on unrealistic 90-day revenue expectations — a fractional CRO who promises a fully mature forecast by day 90 in a company with no prior data is either inexperienced with cold-start environments or telling the company what it wants to hear.

References matter more here than in a typical hire, specifically references from other cold-start engagements, not just RevOps leadership roles at established companies. A CRO who has only ever optimized existing pipelines may have excellent instincts for tuning conversion rates but no practiced method for generating the first dataset from nothing. Ask reference-checkers directly: "Did this company have sales data before they started, or did they have to build it?" — the answer changes what skill set actually got tested.

Finally, evaluate the shape of their proposed 30/60/90 milestones. Day-30 milestones should be almost entirely about infrastructure and hypothesis (ICP defined, CRM live, first pilot deals sourced) rather than revenue. Day-60 milestones should show early conversion data, even if the sample size is small. Day-90 milestones should include a baseline model the company can use to set next quarter's targets. A candidate whose milestones front-load revenue commitments before the infrastructure exists is setting the company up for a plan that collapses the moment reality diverges from the deck.

Buyer decision framework

Once a shortlist exists, the company still has to decide whether a fractional arrangement is the right structure at all for this stage, versus hiring a full-time VP of Sales or continuing founder-led selling a while longer. The framework below captures the gate most companies should run before signing an engagement.

The key decision point most companies underweight is the day-90 gate. Extending a fractional engagement without re-scoping it is a common failure mode — the original 90-day plan was built around getting from zero data to a first baseline, and once that baseline exists, the next 90 days need a different plan entirely, built around the actual numbers the company now has instead of hypotheses.

Related questions

How is a fractional CRO's 90-day plan different from a full-time CRO's?

A full-time CRO's early plan usually starts from diagnosis of existing pipeline and team performance. A fractional CRO in a zero-data company starts from construction — building the CRM, ICP, and first pilot cohort before any diagnosis is possible.

What should be true by day 30 with no existing sales data?

The CRM should be instrumented with defined stages and required fields, a working ICP hypothesis should exist, and the first pilot deals should already be sourced or in early conversation, even before real conversion data appears.

Can a fractional CRO set accurate revenue targets with no historical data?

Not with precision by day 90. Targets set that early should be framed as a first baseline drawn from the pilot cohort's real conversion numbers, explicitly revisited once a full quarter of data exists.

Should the company hire full-time sales reps during the fractional CRO's first 90 days?

Usually only after the ICP and pipeline stages are defined — hiring reps before that risks having them sell against an unvalidated target market and generating data that has to be discarded later.

How does the fractional CRO's plan connect to marketing if marketing also has no data?

The ICP-fit scoring model the CRO builds in weeks one through three should become the same targeting criteria marketing uses, so both functions are generating and reading from one shared, structured definition of the buyer rather than two.

FAQ

What's the very first thing a fractional CRO should do with no existing sales data? Talk directly to the handful of customers or prospects the company already has, even informally, before touching the CRM. Those conversations produce the first real signal about who buys, why, and what objections come up — raw material the rest of the 90-day plan depends on.

How many pilot deals are enough to call the data "real"? There's no fixed number that applies to every company, since deal cycle length and market size vary widely. The practical marker is whether the pipeline has moved enough deals through enough stages that conversion patterns start repeating rather than looking like isolated anecdotes.

Does the fractional CRO need to personally sell during this period? Often yes, especially if no other seller exists yet. Personally running some pilot deals gives the CRO firsthand objection-handling and messaging data that secondhand rep reports can't replicate in a company this early.

What happens if the 90 days end and the pipeline still isn't repeatable? The engagement should be extended with a re-scoped plan rather than treated as a failure — some markets and sales cycles genuinely take longer than 90 days to produce a stable pattern, and forcing a premature baseline does more damage than extending the discovery period.

How does this differ across company stages — very early startup versus a company relaunching a stalled sales motion? A pre-revenue startup is building an ICP from nothing. A company relaunching a stalled motion may have anecdotal history but untrustworthy data (bad CRM hygiene, inconsistent stage definitions), which means the fractional CRO's first move is often to discard the old data rather than build on it.

Should the 90-day plan be shared with the whole company or kept between the CRO and the founder? It should be visible at least to the leadership team and anyone in sales or marketing whose work feeds the pipeline, since the plan sets shared definitions — stage criteria, ICP, required CRM fields — that only work if everyone touching the pipeline uses them consistently.

Sources

• https://hbr.org/topic/subject/sales
• https://www.gartner.com/en/sales
• https://www.saastr.com
• https://blog.hubspot.com/sales
• https://www.bridgegroupinc.com
• https://www.winningbydesign.com
• https://www.forrester.com/blogs/category/sales/
• https://www.salesforce.com/resources/articles/sales-operations/

Related on PULSE

• Who places fractional Chief Revenue Officers?
• What service finds fractional CROs for you?
• Can I find a fractional CRO on LinkedIn?
• Is there a directory of fractional CROs?
• Who do I contact to find a fractional Chief Revenue Officer?