How do I hire a fractional head of revenue in Mountain View in 2027?

The job a fractional head of revenue is actually hired to do

A fractional head of revenue is not a part-time VP of Sales, and confusing the two is the single most common reason these engagements fail in the first sixty days. A VP of Sales is hired to run a team: recruit reps, manage quota attainment, hold weekly one-on-ones, build a comp plan, and own a number that rolls up from individual contributors. A fractional head of revenue is hired to install the system that a VP of Sales will later run. The output of the engagement is not a quarter of bookings — it is a working revenue motion that survives the person's departure.

That distinction matters enormously in Mountain View, where the default failure pattern for a seed-stage or Series A company is founder-led sales that plateaus. The founder closes the first fifteen or twenty deals on charisma, domain credibility, and the willingness to discount. Then the founder's calendar fills with fundraising, product, and hiring, pipeline generation stops, and the company discovers that nothing about how those deals closed was written down. There is no ICP definition anyone else can apply, no qualification framework, no discovery script, no pricing logic beyond "what the last customer paid," and no CRM data worth forecasting from. The fractional head of revenue's job is to reverse-engineer the founder's implicit process into an explicit one, then prove it works by having someone other than the founder close a deal with it.

Concretely, the work in a typical engagement breaks into five buckets. First, diagnosis: pipeline audit, win/loss review across the last twenty closed opportunities, CRM hygiene assessment, and customer interviews. Second, ICP and segmentation: who actually buys, at what company size, with what trigger event, and — critically — who has been sold to unsuccessfully and should be disqualified faster. Third, process design: stages with exit criteria, a qualification framework the team can actually apply, a discovery call structure, and forecast definitions that mean the same thing to the founder and the board. Fourth, pricing and packaging: whether the current model captures value, whether discounting is structural or ad hoc, and whether the contract shape supports expansion. Fifth, the hiring plan: what the first two or three revenue hires should be, in what order, with what compensation, and what "good" looks like at day ninety for each.

There is a second job that goes unwritten in most scopes but drives a lot of the value: translating the revenue function for the board. Bay Area boards ask specific questions — net revenue retention, magic number, CAC payback, pipeline coverage against next quarter's plan — and a founder without a revenue background often cannot answer them in the vocabulary the board expects. A fractional leader who has sat on the other side of that table can build the board reporting pack once, teach the founder to run it, and materially change how the next funding conversation goes. That deliverable alone frequently justifies the retainer for pre-Series-B companies.

What the role is not built to do: build culture, mentor junior sellers over multiple quarters, or absorb the emotional load of managing a team through a bad quarter. Those require presence and tenure. If your actual problem is that you have eight reps and nobody is managing them, you need a full-time leader, and hiring fractionally will simply delay a decision you have already made. The honest test is whether your problem is a missing *system* or a missing *manager*. Fractional solves the first and papers over the second.

How the role fits into the RevOps stack around it

A fractional head of revenue arrives into an existing — usually messy — operational stack, and the engagement's velocity depends almost entirely on how quickly they get authority over it. In a Mountain View startup at the 500K to 5M ARR range, that stack typically means a CRM (Salesforce or HubSpot), a sales engagement tool, a conversation intelligence layer, some form of enrichment and data provider, a billing system, and a warehouse or BI layer that may or may not be connected to any of it. The RevOps question is not which tools are in the stack — it is which one is the system of record and whether anyone enforces it.

The most common finding in the first two weeks is that the CRM is a reporting afterthought rather than the operating surface. Deals get updated the night before the board meeting. Stages are named after internal activities ("demo done") rather than buyer commitments ("buyer confirmed budget and named the approver"). Close dates cluster at quarter end because nobody re-dates a stalled deal. A fractional leader who does not fix this cannot forecast, and cannot prove the process they installed is working. So the sequencing is almost always: fix the data contract first, then the process, then the pipeline.

This is also where the boundary with an existing RevOps function gets negotiated. If you already employ a RevOps analyst or ops manager, they should own implementation and the fractional leader should own the specification — the definitions, the stage exit criteria, the forecast categories, the required fields. If you have no RevOps function, the fractional leader will do both, which consumes a meaningful share of the retainer on work a contractor could do more cheaply. Many companies get better value by pairing a two-day-per-week fractional head of revenue with a part-time RevOps contractor handling the build, rather than paying executive rates for field configuration.

Downstream effects are worth naming because founders routinely underestimate them. Changing stage definitions invalidates historical conversion rates, so you lose your baseline for a quarter. Tightening qualification shrinks pipeline on paper, which looks alarming in a board deck unless it is pre-framed. Introducing forecast categories the founder has never used means the first two forecasts will be wrong, and the value only appears in the third. A good fractional leader tells you this in week one. A weak one lets you discover it in month three.

Two adjacent motions often get pulled into scope and should be priced explicitly rather than absorbed. The first is partnerships or channel — if a meaningful share of your pipeline could come through a cloud marketplace or a systems integrator, that is a separate build with its own timeline, not a bullet under "sales." The second is customer success and expansion. Plenty of Mountain View SaaS companies at this stage have a retention problem masquerading as an acquisition problem: gross retention below the low nineties will eat any new-logo motion you install. Ask a candidate to look at retention before they look at pipeline, and pay attention to whether they volunteer that themselves.

Pricing, engagement models, and what the ranges actually depend on

Fractional revenue leadership is priced on a monthly retainer tied to a committed number of days per week, and the honest answer to "what does it cost" is that the spread is wide and driven by four variables rather than by geography. Rather than quote numbers that vary by year, market, and individual, it is more useful to understand the multipliers so you can evaluate any quote you receive.

Days committed. The base unit is a day per week. Two days is the most common shape for a company under roughly 2M ARR — enough for a weekly pipeline review, deal coaching, and one build workstream. Three to four days is appropriate when the leader is also running a small team or executing a heavy build, such as a full CRM re-architecture plus a pricing change. Five days is functionally an interim executive rather than a fractional one, and should be priced and contracted differently, usually as a defined-term interim role with a stated end date and a successor plan.

Stage and complexity. Pre-seed and seed companies pay toward the lower end of any given practitioner's range because the surface area is small: one product, one segment, short cycles. Series A and B pay more because the leader is coordinating multiple motions — self-serve plus sales-led, or SMB plus mid-market — and because the reporting burden is heavier. Enterprise sales cycles with security review, procurement, and multi-threaded buying committees are materially more work than transactional cycles, and pricing reflects that.

Equity in place of cash. Offering equity is standard and typically lands in the range of half a percent to two percent for a meaningful engagement, vesting monthly over twelve to twenty-four months, often with a cliff of one to three months rather than the usual twelve. The practical effect is a cash reduction of roughly ten to twenty percent, not a fifty percent one — fractional leaders run portfolios and need cash flow. Structure matters: options versus restricted stock, single-trigger versus double-trigger acceleration on a change of control, and what happens to unvested equity if either party exercises the termination clause. Get this in the agreement rather than in an email, and have counsel confirm the instrument is appropriate for a contractor rather than an employee.

Scope shape. A pure advisory engagement — weekly call, review the deck, answer questions — costs a fraction of an operating engagement where the leader is on prospect calls, rewriting sequences, and owning a pipeline number. Be explicit about which you are buying. A large share of disappointment in these arrangements traces to a founder who bought advisory pricing and expected operating output.

On the Mountain View premium specifically: there is no local discount, and there may be a modest premium for practitioners who understand venture-backed board dynamics and Bay Area enterprise sales cycles. But paying for a physical presence in Mountain View is generally poor value in 2027. The talent pool for fractional revenue leadership is national and largely remote, and the constraint that actually matters is timezone overlap plus willingness to be on site for quarterly planning, a sales kickoff, or a critical customer meeting. Structure that as a stated travel expectation with expenses reimbursed rather than as a location requirement in your search, and your candidate pool multiplies.

Two contract mechanics are worth insisting on. First, a three-month minimum with a 30-day termination clause for either party — shorter than three months and nobody can produce durable change; longer than six without a review gate and you lose leverage. Second, a scope document listing specific deliverables with dates, not a vague "own revenue" mandate. "Deliver a written 30-day diagnostic covering pipeline health, process gaps, pricing, and a prioritized plan" is a testable commitment. "Improve revenue" is not.

How to evaluate and shortlist candidates without getting sold

Fractional revenue leaders are professional sellers, which means your interview process is being run against a person who is better at interviews than you are. Assume the pitch is polished and design a process that rewards specificity over polish.

Start with sourcing. The reliable channels are operator communities where revenue leaders congregate, warm referrals from other founders at your stage who have actually run one of these engagements, your investors' talent partners, and boutique fractional-executive firms that vet and place. Cold LinkedIn search produces volume but poor signal — the title "fractional CRO" has no barrier to entry, and a meaningful share of people using it are between full-time roles rather than running a deliberate portfolio practice. That is not automatically disqualifying, but it changes the risk: someone job-hunting will leave when a full-time offer lands, and you should ask directly.

The single highest-signal question is stage fit. Ask what ARR range they have worked with most, then ask them to describe the revenue motion at that stage in operational detail. Someone whose experience is at 20M-plus will reflexively propose structures — sales ops, enablement, SDR pods, territory carving — that will crush a company doing 900K. The reverse also fails: a leader who has only worked pre-product-market-fit will not have a plan for procurement, security review, or multi-year contracts. Neither is a bad operator; both are wrong for the other company.

Then push on outcomes with numbers. Ask them to walk through one engagement end to end: ARR at start, cycle length, win rate, the three specific things they changed, and what those metrics looked like six months later. Follow up on the mechanism — *why* did the win rate move? A strong candidate names a specific change ("we added a mandatory economic-buyer confirmation before stage three and disqualified twenty percent of pipeline, which raised win rate and shortened the cycle"). A weak one narrates outcomes without mechanism. Ask what did not work in that engagement. Everyone has a failed one; refusing to name it is itself the answer.

Test working style with artifacts rather than assertions. Ask for a sample weekly schedule from a prior engagement. If it contains only board meetings and dashboard reviews, you are buying advisory. It should show blocks for pipeline review, live deal coaching, CRM inspection, and time on actual customer calls. Ask for a redacted 30-day diagnostic from a past client. Practitioners who do this seriously have one and will share it under NDA; those who cannot produce any written artifact have probably never delivered one.

Run a paid working session before you sign. Two to four hours, compensated at their rate, in which they review your pipeline and last ten closed-lost deals and come back with observations. This is the closest thing to a trial you can get, it is cheap relative to a bad three-month engagement, and it separates people who diagnose from people who present. Watch for whether they ask for data you did not offer — good operators immediately want the loss reasons and the retention numbers.

References are non-negotiable and should be founders or CEOs, not peers. Ask three questions: what specifically did they build that outlasted the engagement, what would you have done differently in the scope, and would you hire them again for the same stage. Vague or hedged references are a decline. Finally, ask how many concurrent clients they carry. Beyond three or four meaningful engagements, attention is thin no matter how good the person is, and you should know where you sit in that portfolio before you sign, not after.

A decision framework for whether fractional is even the right answer

Before running any of this, pressure-test whether a fractional head of revenue is the correct instrument. There are four adjacent options, and choosing wrong is more expensive than choosing slowly.

If you are pre-revenue or below roughly 500K ARR with an unvalidated motion, the founder should still be selling. No fractional executive can find product-market fit on your behalf, and hiring one at that stage usually produces a well-designed process for a market that does not want the product yet. A sales coach working with the founder a few hours a month is cheaper and better matched.

If you are between roughly 500K and 5M with founder-led sales that works but does not scale, and your problem is missing systems, fractional is the intended fit. This is the sweet spot: enough revenue to have real data, not enough team to need a full-time manager.

If you are above 5M with multiple reps, quota carriers, and a team that needs daily management, hire full-time. Use a fractional leader only as a bridge while you run the search, with an explicit mandate to help you hire your own successor and a defined end date.

If your problem is specifically operational — reporting, CRM architecture, forecasting hygiene, territory and comp mechanics — the right hire may be a fractional RevOps leader rather than a revenue leader. Different skill set, generally lower cost, and often the actual bottleneck. Plenty of companies hire a revenue leader who then spends the first two months doing RevOps work at executive rates.

One more scenario deserves naming because it is common in Mountain View specifically: the company that has just raised and feels pressure to look built out. Hiring a fractional executive to have an impressive name on the team page is a real motivation and a bad one. The engagement will be under-scoped, the leader will disengage, and you will have spent three months of retainer on a logo. If you cannot write the one-page mandate, you are not ready to hire.

Onboarding and the first ninety days, where most of the value is won or lost

The engagement is decided in the first thirty days. A fractional leader operating two days a week has roughly eight working days in that window — there is no room for a slow ramp, and it is your job to remove friction before day one, not after.

Have access provisioned before they start: CRM with admin or near-admin rights, conversation intelligence, the sales engagement tool, billing or subscription data, Slack, and the shared drive with existing decks, pricing sheets, and contracts. Every day spent chasing a password is a day of retainer spent on nothing. Also pre-schedule the meetings: a standing weekly with the founder, a weekly pipeline review with whoever touches deals, and three to five customer conversations in week one. Customers will take the call if the founder asks; they will ignore a cold request from a name they do not know.

Give them the raw material rather than a curated summary. The top ten customers with deal histories, every closed-lost opportunity from the last two quarters with stated reasons, the current pricing sheet plus every deal that deviated from it, churn and downgrade history, and the last two board decks. Founders often withhold the ugly parts out of embarrassment. The ugly parts are the job.

Set the week-four deliverable explicitly in the contract: a written diagnostic covering pipeline health and coverage against plan, sales process gaps with named fix priority, pricing and packaging observations, data quality assessment, and a prioritized ninety-day plan with owners. Written, not a verbal readout. If a candidate resists producing a written artifact, that is a signal about how the rest of the engagement will go.

From there the cadence is roughly: weeks five through eight execute the top two priorities from the diagnostic — usually stage redefinition plus one pipeline generation motion — while the leader sits on live calls and coaches in the moment. Weeks nine through twelve prove the motion with someone other than the founder, and produce the hiring specification for your first full-time revenue hire. At the ninety-day mark, hold a real review: what changed in pipeline coverage, cycle length, and win rate; what got built that will outlast the engagement; and whether to extend, narrow scope, or exit.

Know your kill criteria in advance. If at day sixty there is no written diagnostic, no change in how deals are inspected, and no visible improvement in data quality, exercise the 30-day clause. That is the entire reason it exists. A capable fractional leader will not be surprised by a clean exit — they run portfolios, they have seen mismatches, and they will help with the transition. Dragging a bad fit to month six because the conversation is awkward is the most expensive mistake available to you in this whole process.

Related questions

What is the difference between a fractional CRO and an interim CRO?

Fractional means ongoing part-time capacity across a portfolio of clients, typically two to three days weekly for three to six months. Interim means near-full-time coverage of a vacant seat for a defined period, usually while you run a search. Interim costs more and ends when the permanent hire starts.

Should the fractional leader help hire their full-time replacement?

Yes, and write it into the scope. They know the specification better than anyone, can screen candidates on operational depth, and have a network. Add a clause covering what happens to their equity and notice period once the permanent leader starts, so the transition is not a negotiation.

Can one person cover sales, marketing, and customer success fractionally?

At small scale, sometimes. Below roughly 2M ARR the three functions are close enough that one strong operator can set direction across all of them. Above that, breadth becomes shallowness. Narrow the mandate to the function that is actually broken rather than buying a title.

How do I keep momentum after the engagement ends?

Insist that every deliverable is documented rather than resident in one person's head: written stage definitions, a qualification framework, discovery scripts, pricing rules, and a board reporting pack. Assign an internal owner for each before the final month. Undocumented process decays within a quarter of departure.

Does a fractional revenue leader replace a RevOps hire?

No. They specify what the systems should do; RevOps builds and maintains it. Pairing a fractional leader with a part-time RevOps contractor is usually cheaper and faster than having an executive do field configuration at executive rates.

FAQ

How long does the hiring process realistically take?

Two to four weeks if you have a written mandate before you start sourcing, and six to eight if you do not. The mandate is the bottleneck: candidates cannot self-select without knowing scope, days per week, and stage, so an unclear brief produces a wide unqualified funnel. Budget one week to source, one to two weeks for screens and a paid working session, and a few days for references and contracting.

Do I need someone physically located in Mountain View?

Rarely. The relevant constraints are Pacific-timezone overlap, willingness to travel for quarterly planning and key customer meetings, and fluency with venture-backed board expectations. Requiring a Mountain View address shrinks your pool substantially without improving outcomes. Write travel expectations into the agreement — a defined number of on-site days per quarter with expenses covered — instead of filtering on location.

What should the engagement produce that outlasts it?

Written stage definitions with exit criteria, a qualification framework, an ICP definition with disqualification rules, a discovery structure, documented pricing and discount policy, a clean forecast process, a board reporting pack, and a hiring specification for the first full-time revenue leader. If nothing on that list exists at the end, you rented advice rather than building capability.

How much equity is appropriate, and how should it vest?

Half a percent to two percent is the common band for a substantive multi-month engagement, vesting monthly, usually over twelve to twenty-four months with a short cliff rather than the standard one-year employee cliff. Define the instrument, acceleration terms on a change of control, and treatment of unvested shares on early termination in the agreement itself, and have counsel confirm the structure fits a contractor relationship.

What are the clearest warning signs during evaluation?

An inability to name a failed engagement; outcomes described without mechanism; no written artifacts from prior clients; unwillingness to disclose how many concurrent clients they carry; a proposed plan produced before they have seen your pipeline data; and references who will not discuss specific numbers. Any one is a conversation. Two or more is a decline.

Can a fractional leader work if we have no CRM discipline at all?

Yes, but expect the first several weeks to go into data hygiene rather than pipeline generation, and price that reality into your expectations. Consider pairing the engagement with a RevOps contractor to handle the build so executive time goes to process design and deal coaching. Either way, nobody can forecast from a CRM that nobody updates.

Sources

• Harvard Business Review
• First Round Review
• SaaStr
• Bessemer Venture Partners — Cloud insights
• a16z Enterprise
• Pavilion
• RevOps Co-op
• U.S. Department of Labor — Fair Labor Standards Act
• SEC — Rule 701 employee and consultant equity

Related on PULSE

• Fractional RevOps leadership versus a full-time operations hire
• How to write a one-page revenue mandate before you hire
• Sales stage definitions and exit criteria that survive an audit
• What a 30-day revenue diagnostic should contain
• When to replace founder-led sales with a repeatable motion
• Equity structures for contractors and advisors at seed stage