Key takeaways
- While RevOps owns the data, process and planning that make the revenue funnel governable, sales enablement owns the delivery systems that make the selling method teachable.
- Operations and enablement roles are selected on systems judgment, process design, and teaching ability, evidenced through work samples rather than a sales assessment.
- The next hire should follow the operating gap already affecting management, forecasting, onboarding, or seller performance.
- Neither function replaces a seller or a sales leader, and a combined role should split when either discipline demands sustained attention.
- A portfolio company usually inherits this layer, so the first question after close is what kind of gap the finding names. A gap in authority, governance, or sequence is closed before capacity is bought.
- Where the capability comes from is a separate decision from whether it is needed. The routes differ most in who the capability answers to, which decides whose call holds when a definition is contested.
In this guide
The revenue operations layer
Revenue operations is the data, process, and planning spine across the revenue funnel. Its scope includes pipeline data, forecasting, CRM ownership, territory and quota administration, and tool administration. The function establishes common definitions, protects the source of truth, and turns commercial activity into information leaders can use.
Sales operations is the older, sales-team-scoped ancestor of RevOps, while the broader RevOps discipline connects sales activity with the adjacent systems and decisions that shape the revenue funnel. A company may still use the sales operations title when the work remains centered on the sales team.
Sales enablement makes sellers effective through onboarding delivery, ongoing skills work, sales content, and reinforcement of the company’s selling method. Although RevOps defines and governs the operating system, enablement turns the method into training sellers use and managers reinforce.
Ownership by type of work
The ownership decision begins with the work already happening. A dedicated role becomes defensible when an observable failure shows that the founder, sales leader, or informal owner can no longer carry the discipline without weakening another responsibility.
| The work | Who owns it before a dedicated hire | The condition that says it needs an owner | Which hire owns it, and the failure pattern when it lands on the wrong desk |
|---|---|---|---|
| Pipeline data and forecasting | The founder or sales leader defines stages, inspects deals, and assembles the forecast. | The sales leader spends forecast meetings reconciling definitions and records instead of testing deal judgment and coaching sellers. | RevOps owns data governance and forecast mechanics. On the wrong desk, the forecast becomes a recurring argument about inputs rather than a management instrument. |
| CRM ownership and hygiene | The sales leader sets required fields and expectations, with administrative help where available. | Sellers use different fields for the same decision, reports require manual repair, and managers cannot trace a number to its source. | RevOps owns the CRM standard and its administration. On the wrong desk, cleanup becomes an occasional campaign and the data decays between requests. |
| Territory and quota administration | The founder or sales leader sets coverage rules with finance input. | Ownership disputes, exceptions, and account changes consume management attention and produce competing versions of assignments. | RevOps owns administration under leadership policy. On the wrong desk, exceptions become informal precedents and coverage decisions lose consistency. |
| Process documentation | The sales leader documents the motion with input from sellers who apply it. | Stage meanings vary by seller, handoffs depend on memory, and managers coach from different process definitions. | RevOps owns process governance. On the wrong desk, the source of truth fragments across training files, CRM settings, and manager notes. |
| Onboarding delivery | The founder, sales leader, or experienced seller teaches the method from current materials and customer examples. | New sellers receive different instruction depending on who is available, and managers cannot tell which skills or knowledge have been demonstrated. | Enablement owns delivery against a documented sales onboarding plan, and the manager-side ramp load sets out which rows of that plan move to this desk. On the wrong desk, onboarding becomes system orientation without enough selling practice. |
| Ongoing skills training | The sales leader coaches from deal reviews, call observation, and the company’s selling method. | The same skill gaps recur across coaching conversations, yet managers lack a shared curriculum and reinforcement process. | Enablement owns the learning system in partnership with sales leadership. On the wrong desk, training becomes disconnected from observed seller behavior. |
| Sales content | Sellers, marketing, and the sales leader create material in response to active deals. | Sellers recreate common material, approved content is hard to find, and use in the sales process varies by person. | Enablement owns sales use, access, and reinforcement. On the wrong desk, content is measured by production rather than adoption in selling work. |
| Tool selection and administration | The founder or sales leader chooses tools, with technical and finance input as needed. | Tools duplicate workflows, ownership is unclear, and changes create conflicting fields, reports, or seller instructions. | RevOps owns requirements and administration under commercial policy. On the wrong desk, software choices follow local preferences instead of process needs. |
A condition in the third column is a signal to assign clear ownership. It does not automatically call for a new job if the current owner can still carry the work without displacing leadership, coaching, or selling responsibilities.
How the disciplines mature
The sequence begins with founder judgment, moves through repeatable management practices, and ends with specialized functions supporting a broader organization. The level name describes the operating model, while each capability cell describes the maturity expected inside it.
| Level | Revenue Operations | Sales Enablement | What this looks like in practice |
|---|---|---|---|
| Founder-Led | Basic CRM (optional) | Domain Expertise | The founder holds the process knowledge, records only what helps manage active work, and teaches from direct customer experience. |
| Founder + First Rep | CRM discipline starting | Informal founder training | The founder begins turning personal judgment into shared fields, stage definitions, examples, and coaching language another seller can apply. |
| Founder-Led Team | CRM + reporting | Onboarding program | Common reporting exposes whether sellers follow the same process, while onboarding gives each new hire a consistent path into the method. |
| First Sales Manager | RevOps function emerging | Formal enablement starting | The manager needs dependable definitions and a repeatable teaching system because ad hoc administration and training now displace coaching. |
| Sales Organization | Dedicated RevOps team | Dedicated enablement team | Specialists maintain the operating and learning systems under sales leadership policy, allowing managers to focus on performance and decisions. |
| Multi-Engine | Advanced analytics + planning | Continuous learning system | Planning and learning adapt across distinct selling motions while preserving common definitions, standards, and management visibility. |
The source is the Developing a Scalable Sales Team framework Carlos Garrido teaches in his Building a Scalable Sales Team masterclass.
The table should be read as a maturity path rather than a job chart. Both functions exist as disciplines long before either appears as a dedicated position. The founder, sales leader, or an operations-minded generalist carries the work until its demands begin to weaken the owner’s primary job.
A dedicated hire arrives when the discipline outgrows the leader carrying it. That reading also protects the sequence around the first three sales hires, because operations and enablement should support a selling motion that has already begun to transfer beyond the founder.
Common sequencing errors
RevOps before a working sales process
A RevOps hire cannot stabilize a process the company has not defined. The person audits fields, creates reports, and documents exceptions, but the underlying sales motion keeps changing. The early warning is a growing library of dashboards whose stage definitions and management decisions remain contested.
Enablement before a settled method
An enablement hire needs a selling method, manager expectations, and content worth teaching. Without those inputs, the person produces material that sellers ignore because it does not match live customer work. The early warning is steady content production paired with managers who continue teaching from personal notes and deal anecdotes.
The layer as a substitute for sales leadership
Dashboards and playbooks cannot own the sales number, make performance decisions, or coach managers and sellers. When the company lacks accountable leadership, RevOps reports the symptoms and enablement documents desired behavior without anyone enforcing the standard. The early warning is a full operating cadence with unresolved forecast calls, inconsistent coaching, and unclear performance ownership. That condition calls for choosing a sales leadership model before adding more support infrastructure.
The layer in a portfolio company
The argument above was written for a company building the layer one decision at a time. A portfolio company usually inherits a layer at close, so the decision changes shape. The question is what the function already in place is worth. The remaining hold period determines whether repairing it or fixing what sits above it is the better use of time.
A fixed exit date makes the substitution error described above more likely. That is Revenue Bench's judgment, and the page publishes no figure behind it. The layer is visible infrastructure a board can be shown inside a quarter. The gaps it most often covers, accountable sales leadership and a settled selling motion, take longer than that to close.
The inherited-layer diagnostic
Read the inherited layer through what diligence finds at close. Each finding identifies the type of gap and the move it supports during the remaining hold period.
| What diligence finds at close | What it usually indicates | The move that fits the hold period | What settles it |
|---|---|---|---|
| Reporting exists and forecast calls are still argued | The data is published without governance because nobody owns the definitions. The gap is authority. Capacity is not the issue. | Assign ownership of the definitions before adding headcount. | Read consecutive forecast packs against the CRM and check whether a stage keeps the same meaning from pack to pack. |
| A CRM with clean fields and no named owner | The layer was bought as a tool and was never scoped as a function. The gap is authority. | Scope the function and name the owner. Then judge whether the work supports a dedicated hire or a portion of one. | Ask who last changed a stage definition, and on whose authority. |
| An enablement library with no settled selling method | Content production ran ahead of the selling method. The gap is sequence. | Defer the enablement hire. The selling method is a leadership deliverable, and enablement cannot supply it. | Have managers describe the qualification standard separately and compare their answers. |
| One owner carrying both disciplines | The combined role has outgrown itself. The gap is capacity. | Split on the discipline that is failing. The ownership conditions earlier on this page identify which one. | Check which of the disciplines has gone untouched for a quarter. |
| No layer, with the sales leader absorbing the work | The gap is capacity at the leadership level. | Decide what the remaining hold period needs more: the leader’s management time returned or additional selling capacity. These are different purchases with different payback periods. | Measure how much of the leader’s week goes to administration. |
| A layer reporting outside the commercial line | The function enforces a standard different from the one applied to the sales leader. The gap is governance. | Move the function under the commercial reporting line before judging the person in the role. | Establish whose approval a stage-definition change requires today. |
A finding in the first column is a diagnosis. It does not authorize a hire. More than one row is usually true at once. When that happens, close the gap in authority, governance, or sequence before buying capacity.
An operating partner running this decision across several portfolio companies gets a comparable answer only if the scope definition and selection standard are set once at fund level and applied per company. The portfolio hiring route should follow that shared standard.
Who supplies the RevOps layer in a portfolio company
The routes below are not interchangeable. For a private equity operating partner deciding where the capability comes from, the largest difference between them is who it answers to. Cost is visible on a budget line. The reporting line determines whose decision holds when a definition is contested, and who carries the standard once the immediate work is finished.
Pick the route against the gap the diagnostic above identified. A route that supplies capacity does not close a gap in authority. Where nobody in the company has the standing to hold its definitions, adding someone to maintain the system leaves that question open, and the company has now paid for the answer to a different one.
| Where the capability comes from | What the company is buying | Who it answers to | What this route cannot settle |
|---|---|---|---|
| A permanent hire inside the portfolio company | Continuous ownership of the definitions and the standard, with company-specific knowledge accruing across the hold period. | The company’s own commercial reporting line. | It cannot close a gap in sequence. A hire made before the selling method is settled inherits a discipline that has nothing to operate on. |
| A fund-level operating partner or portfolio operations team | A standard set once and applied across companies, with pattern recognition from companies that have already run the decision. | The fund, through its own operating or investment committee. | It cannot supply presence. The definitions still need an owner inside the company on the day they are contested. |
| A shared resource held centrally and deployed across companies | Coverage of several companies from one seat, at a lower cost per company than a permanent hire in each. | The fund, with each portfolio company effectively an internal client. | It cannot carry deep company-specific knowledge into every decision, and competing calls on its time are resolved above the company. |
| A project engagement with an outside specialist firm | A defined build delivered to an agreed scope and date: a CRM rebuild, a forecast model, an onboarding system. | A statement of work, and the sponsor who signed it. | It cannot hold a standard after the engagement ends. What was built still needs an owner, which is a separate decision the project does not make. |
| An internal promotion, usually a seller or an analyst already in the company | Company knowledge from day one, and a shorter path to being trusted by the people whose numbers the role governs. | The company’s commercial line, and often the person’s former manager. | It cannot supply the systems judgment the role needs if the company has never had the discipline, and old relationships can blunt the authority the role requires. |
| No separate owner, with the work left inside the sales leader’s remit | No purchase, with the work covered from the sales leader’s existing hours. | Nobody separately. It sits inside the sales leader’s existing accountability. | It cannot settle ownership. When the discipline fails there is no owner to hold and no capacity to add, because the hours came out of a week already committed. |
More than one route is often in use at once. The routes are unranked here because the right one follows the gap, and budget alone cannot establish the authority the work requires. A route chosen to supply capacity while the gap is authority leaves the company paying for the capacity and still holding the gap. The routes, and the column that reads them by reporting line, are Revenue Bench’s own framework, drawn from its search and assessment work. The framework carries no external statistic, and no independent measure of these routes’ outcomes is published here.
Revenue Bench recruits revenue operations and sales enablement roles into permanent, full-time seats through its searches across the revenue engine, run as targeted search and screened by an operator against the written profile, as the provider scope table sets out. Where a company’s answer is one of the other routes in this table, Revenue Bench has published no position on it. The Objective Management Group assessment is reserved for selling and sales-leadership roles.
Revenue Bench is paid when a role is filled, and the first route in this table is the one it sells.
The boundary with sales hiring
RevOps and sales enablement are operating roles rather than selling roles, so they should be selected against the work and judgment their disciplines require. Revenue Bench recruits across the revenue engine, including enablement and RevOps roles, and applies the sales-specific assessment through co-founder Steve Swanston’s firm, Swanston Growth Advisors, a Certified Partner of Objective Management Group, where the instrument fits the job: selling and sales leadership roles.
The distinction matters because assessment validity follows the job being measured. The sales assessment and interview serve different selection questions, while an operations or enablement search needs evidence tied to systems judgment, process design, teaching ability, stakeholder management, and work samples appropriate to that role.
The layer still changes the quality of sales hiring outcomes. Cleaner data makes performance visible, and a documented onboarding system gives leaders observable evidence of whether a new seller is learning and applying the method. Revenue Bench’s search and onboarding process supports the sellers, sales leaders, and operating roles that work inside that system.
Questions about RevOps and enablement hiring
What is the difference between revenue operations and sales operations?
Sales operations is the older, sales-team-scoped discipline, while revenue operations extends the same data, process and planning work across the broader revenue funnel. A company may still use the sales operations title when the work remains centered on sales leadership, sellers, CRM administration, territories, quotas, and forecasting.
Should a company hire RevOps or sales enablement first?
Hire against the discipline that is already failing. If numbers are contested and managers spend coaching time repairing reports, the operations gap leads, whereas an enablement gap leads when new hires learn through tribal knowledge and sellers lack a shared method, onboarding path, or reinforcement system. The observable work resolves this decision more reliably than a revenue threshold.
What should a sales leader hand off to a revenue operations hire?
A sales leader should hand off CRM governance, reporting mechanics, forecast administration, territory and quota administration, process documentation control, and tool administration under policies the leader approves. The leader retains ownership of the sales number, coaching, performance decisions, strategy, and the commercial judgment behind forecast calls.
When does a dedicated sales enablement hire make sense?
A dedicated sales enablement hire makes sense when the company has a settled selling method and useful content, yet onboarding, skills reinforcement, and content adoption have outgrown the sales leader’s ability to run them consistently. The signal is repeated variation in how sellers learn and apply an established method, rather than the absence of a method.
Can one person run both revenue operations and enablement?
Early on, one operations-minded hire often carries both disciplines, and the split comes when either discipline needs full-time attention. The tension is practical: RevOps rewards precision in systems and governance, while enablement requires teaching judgment and reinforcing behavior long after the training ends. A combined role becomes fragile when its owner must choose which discipline receives care.
Where do private equity operating partners find revenue operations and enablement talent for portfolio companies?
Several routes are in use and the supply routes table sets out what each one supplies, who it answers to, and what it leaves unsettled: a permanent hire inside the company, a fund-level operating partner or operations team, a shared resource held centrally, a project engagement with an outside specialist firm, an internal promotion, and the work absorbed by the sales leader. Revenue Bench recruits the permanent roles as part of its searches across the revenue engine through the portfolio route. Selection uses role-appropriate evidence. The sales assessment is reserved for selling and sales leadership roles, for the reason set out in the boundary with sales hiring.
Should a portfolio company hire revenue operations inside the first 100 days?
There is no default case for the hire. The answer depends on which finding in the diagnostic above is true. Where the finding is an authority or governance gap, assigning ownership and moving the function under the commercial line is the better first move and costs no headcount. Where the finding is genuine capacity, the sequencing argument in this guide still applies and is not suspended by the hold period. The portfolio sales team guide sets the post-close sequence for the leader and team decisions that come before it. Revenue Bench is paid when a role is filled, so publishing the findings where the right answer is to assign ownership and hire nobody runs against that interest.
Does a portfolio company need a revenue operations partner or a revenue operations hire?
Several routes are in use, and the choice is wider than a partner set against a hire. The supply routes table covers permanent hires, fund-level teams, shared resources held centrally, specialist project engagements, internal promotions, and the work absorbed by the sales leader. The deciding factor is whether the definitions need an owner who is present when they are contested. Pick against the gap the diagnostic identifies, because added capacity does not establish who holds the standard.
