RevOps at 100 People: The Three Hires That Compound
RevOps in early stage is one person doing Salesforce admin. At 100 employees, three hires compound — but only in one order. Sales operations lead, marketing operations lead, data analyst, in that sequence. Hiring out-of-order kills the function.
The short answer
RevOps at scaleup scale needs three specific hires in a specific order: sales operations lead first (forecasting, comp, territory), marketing operations lead second (attribution, MAP, lead routing), data analyst third (cohort and pipeline analytics). The order is not arbitrary — each hire creates the data foundation that makes the next one productive. Hiring out of order produces three expensive specialists doing low-leverage work, and the RevOps function never compounds.
Key Takeaway: The hire-order is the structural decision. Sales ops first because the forecast is the operating-model spine; marketing ops second because attribution depends on a clean pipeline; data analyst third because analytics depends on both clean pipeline data and clean attribution. Hiring data analyst first or marketing ops first produces specialists working with broken inputs.
Why most founders get this wrong
The most common mis-hire is data analyst first. The board asks for better pipeline analytics; a data analyst is hired; the analyst arrives, opens the CRM, and finds that the pipeline data is unreliable, the comp plan is undocumented, and the attribution model is non-existent. The analyst spends six months building reports that get dismissed because the underlying data is questioned. The investment looks like RevOps; the output is dashboards nobody trusts.
The second common mis-hire is marketing ops first. The marketing team asks for proper attribution; a marketing operations lead is hired; the lead arrives and finds the lead-routing rules are inconsistent, the lifecycle stages are not standardised, and the sales team's pipeline conventions do not match the marketing team's lead conventions. The marketing ops lead has to spend the first six months reconciling with sales, which is sales operations work, not marketing operations work. The leverage is dissipated.
The third error is treating "head of RevOps" as a single hire who covers all three functions. At under 50 employees, this works because the volume is low and one person can hold the entire model. At 100 employees, the volume across forecasting, attribution, and analytics is too large for one person, and the head of RevOps becomes a generalist firefighter rather than a builder of the operational backbone.
Why the order matters structurally
Sales ops produces the forecast. The forecast is the spine of the operating model — it is what the board asks about, what investor decks rely on, and what the comp plans pay against. A reliable forecast requires clean pipeline data, clear stage definitions, comp-aligned activity capture, and a documented forecasting methodology. None of this exists by default; sales ops builds it.
Marketing ops produces the attribution model. Attribution requires reliable pipeline data — the input to attribution is "where did this opportunity come from" and the answer requires the pipeline data the sales ops lead just cleaned up. Without sales ops first, marketing ops attempts attribution against unreliable data and produces unreliable conclusions.
Data analyst produces the analytics. Analytics requires both reliable pipeline (sales ops) and reliable attribution (marketing ops) — cohort analysis, channel ROI, payback by segment all depend on both. Without the first two hires, the data analyst either produces analytics on broken inputs (which get dismissed) or rebuilds the inputs themselves (which is the wrong job for the role).
What "good" looks like
The three hires, in order, with the deliverables for each hire:
The three RevOps hires — scope, deliverables, lead time
| Hire (in order) | Primary deliverables | Lead time to compounding leverage |
|---|---|---|
| 1. Sales operations lead | Forecast methodology, pipeline hygiene rules, comp-plan administration, territory design | 3-6 months |
| 2. Marketing operations lead | Attribution model, lead-routing rules, MAP administration, lifecycle-stage discipline | 3-6 months after #1 |
| 3. Data analyst | Cohort analytics, channel ROI, segment-level unit economics, pipeline-conversion analysis | 3-6 months after #2 |
The pattern is roughly nine months of staggered hires producing a fully functional RevOps team at month 12 to 15. Compressing the timeline by hiring all three at once produces three new hires waiting on each other; spacing them too widely produces gaps where the function is half-built and the rest of the company works around the gaps.
The structural test for readiness
The right time to start hire one is when the existing single-person RevOps owner is spending more than 50 percent of time on forecasting and comp administration. The right time to start hire two is when the marketing team is making decisions on inconsistent attribution data. The right time to start hire three is when the executive team is asking analytic questions that the existing CRM reports cannot answer cleanly.
The Bottom Line
RevOps at scaleup scale is a function that compounds non-linearly when built in the right order. Sales ops first because the forecast is the spine; marketing ops second because attribution depends on the pipeline; data analyst third because analytics depends on both. Out-of-order hiring produces specialists working with broken inputs and a function that costs twice as much for half the leverage.
How to apply it to your round
Series B partners diligence RevOps quality through the forecast-accuracy and pipeline-hygiene metrics. The IC memo asks: what is your forecast accuracy over the past four quarters; how is pipeline hygiene maintained; what is your channel-attribution methodology. A founder who can answer with the documented sales-ops, marketing-ops, and data-analyst deliverables presents a mature operating model. A founder who can describe RevOps only as "we have someone in Salesforce" presents a structural risk that affects every other operating-model claim.
The implementation sequence for companies approaching the 100-employee threshold:
Hire one — sales ops lead — before 100 employees. The function is most valuable in the lead-up to scale; arriving after the team has scaled means rebuilding processes that are already in production. Hire the sales ops lead at 60 to 80 employees and let the function mature ahead of headcount.
Hire two — marketing ops lead — within 6 months of hire one. The marketing ops lead's productivity depends on the sales ops lead's foundational work being in place. Six months is the right interval; longer than 12 months and the marketing team builds workarounds that are harder to dismantle than to design correctly.
Hire three — data analyst — within 6 months of hire two. The data analyst is the productivity multiplier. With the foundation in place from the first two hires, the analyst produces analytics that the executive team trusts and the board cites. Without the foundation, the analyst produces dashboards that get dismissed.
Cross-link reading: outbound at scaleup scale for the SDR-pod design that depends on RevOps infrastructure; GTM efficiency in 2025 for the metrics that RevOps produces and the partners price.
The reporting structure that supports the function
RevOps reporting structure matters as much as the hire-order. The most common structures are: RevOps reporting to the CFO (treats it as a finance function — over-emphasises forecast accuracy, under-emphasises sales-team enablement); RevOps reporting to the CRO (treats it as a sales function — over-emphasises sales support, under-emphasises marketing attribution); and RevOps reporting to a dedicated head of RevOps who reports to the CEO (treats it as a cross-functional operating-model function — typically the structure that produces the highest leverage at scale). The third structure is rarer because it requires a senior RevOps leader to hire, but it is the structure that produces the strategic decision-quality that partners diligence positively.
The choice of reporting structure should be made before the second hire (marketing operations lead) is brought on. If marketing ops reports to the CMO and sales ops reports to the CRO, the two functions cannot align attribution and pipeline definitions without escalation, and the data-analyst hire (the third) inherits the misalignment. The unified reporting structure should be in place by the time the second hire arrives.
The tooling investment that compounds with the team
RevOps tooling is not the function — but the function depends on it. The minimum viable tooling stack is: a CRM with disciplined administration (Salesforce or HubSpot, configured with documented field standards and data hygiene), a marketing automation platform with attribution capability (Marketo, HubSpot, or equivalent), a data warehouse for cohort and pipeline analytics (BigQuery, Snowflake, or equivalent), and a BI tool layered on top (Looker, Tableau, or Mode). The stack should be in place before the third hire arrives; the data analyst's productivity depends on it.
The common tooling mistake is to over-invest in CRM customisation early and under-invest in the data-warehouse layer late. CRM customisation is reversible and can be re-thought; data warehouse architecture is structural and harder to change once the analytics function depends on it. Founders who get the tooling sequence wrong spend the data analyst's first six months rebuilding the data layer instead of producing the analytics that justified the hire.
Related reading
For the outbound design that depends on RevOps infrastructure, see outbound at scaleup scale: the two-pod model. For the GTM efficiency metrics that RevOps produces, see GTM efficiency in 2025. For the talent framework that interlocks with RevOps hiring, see scaling talent: the L4/L5/L6 framework. For the framework view, see The Opagio 12™.
Build the spine before the team scales
Eight minutes. Twelve drivers. The starting frame for a RevOps function that compounds across pipeline, attribution, and analytics in the only order that works.