Sales Org Chart for Multi-Location Services Businesses in 2027

The 26-location pest control rollup that stalled at $71M

Picture a private-equity-backed pest control platform: twenty-six branches across four states, $71M in system revenue, assembled from nine separate acquisitions over thirty-one months. On paper it is one company. In practice it is nine companies wearing a shared logo, and the org chart is the reason.

Six of the nine founders stayed on as "Branch Presidents," each reporting directly to the CEO. Three of the acquired companies kept their own marketing coordinator. Four different CRMs are in production. Two branches still quote off a laminated 2023 rate card. The CEO's direct-report count is nineteen. There is no Regional VP layer at all, because after every acquisition the integration plan said "we'll formalize the structure once things settle down," and things never settled down.

The symptoms show up in the numbers before they show up in the org chart. Same-branch revenue growth across the six oldest units is 2.1% — barely above inflation, well below the 6-12% a healthy multi-location services platform should post. Blended cost per acquired customer has drifted from roughly $180 at the first acquisition to something north of $290, because six branches are each buying local search ads against each other in overlapping metros and nobody is deduplicating the spend. The two best-run branches post 26% unit EBITDA. The two worst post 9%. Nobody at HQ can articulate why, because the branches report different line items in different formats on different cadences.

The instinct at this stage is almost always to hire people: a VP of Sales, a demand gen manager, maybe a Chief of Staff to absorb the span-of-control problem. That instinct treats a structural failure as a staffing shortfall. The actual problem is that nineteen people own revenue and zero people own the *system* of revenue. No layer exists between the CEO and the branch that can compare Phoenix to Tucson on identical terms, reallocate lead flow from a saturated branch to a starving one, or tell a founder-operator that their pricing is 14% below the platform floor.

The fix is not a new hire in isolation. It is a deliberate redraw: define who owns the unit, who owns the group of units, and who owns everything that should only be built once. That redraw is what the rest of this page specifies — and the same logic applies whether you run pest control, dental, HVAC, fitness studios, auto glass, physical therapy, or veterinary. The category changes the vocabulary. It does not change the shape.

One useful reframe before the mechanics: a multi-location services business is not a sales org that happens to have buildings. It is a manufacturing org whose product is a booked, completed, profitable job — and the sales function is one station on that line. Org charts that forget this end up optimizing bookings while completion rates, technician utilization, and rebook rates quietly rot.

How hub-and-locations actually splits the work

The mechanism that makes this structure work is a clean ownership split, enforced by comp and scorecards rather than by goodwill.

Locations own conversion, retention, and labor. The GM decides how many advisors to staff, how the schedule is built, how a lead gets worked once it lands, how a customer is recovered after a bad service call, and how local labor cost tracks against revenue. This is genuinely local knowledge. A GM in a dense urban market with a fifteen-minute drive radius runs a fundamentally different capacity model than one covering three rural counties, and no central team should be pretending otherwise.

The hub owns acquisition, infrastructure, pricing, and enablement. Demand generation, brand, the routing engine, the CRM, the comp model, the rate card architecture, onboarding curriculum, and system-level reporting are all built once and deployed everywhere. These are the functions with genuine returns to scale — a single strong demand gen team serving twenty-six branches will outperform twenty-six part-time local marketers on every dimension that matters, and it costs less in total.

Regional VPs own the translation layer. The RVP is not a super-GM and not a hub executive. Their job is to make five to eight units perform consistently, escalate systemic problems the hub needs to solve, and kill local experiments that conflict with platform standards. The failure mode where an RVP reverts to hands-on coaching at their favorite branch is common enough that it belongs in the scorecard design, not just the job description.

The routing engine deserves specific attention because it is where the two halves meet. A lead arrives from paid search, organic, a partner referral, or an inbound call. The engine assigns it to a location using service radius, current technician capacity, the location's trailing conversion rate on that lead type, and — critically — a fairness rule that prevents the strongest branch from vacuuming every high-intent lead and leaving the recovering branch with nothing to work with. Get that fairness rule wrong and you manufacture a two-tier system where weak branches stay weak because they never get enough volume to improve.

Note the dotted lines. Lead flow moves from RevOps to the location without passing through the RVP. That is deliberate. If the RVP becomes a gatekeeper for lead distribution, they will allocate politically — protecting their weakest branch from scrutiny or rewarding their favorite — and the routing logic loses its objectivity. The RVP should *see* the allocation and be able to escalate a dispute, but they should not be the one clicking the buttons.

Where RevOps reports is the other structural decision that quietly determines whether the whole thing holds. Under Marketing, the field stops trusting lead counts because the team scoring the leads also spends the budget that generates them. Under Sales, marketing disengages from attribution because they no longer own the measurement. Under the CFO, the team becomes a reporting shop that produces beautiful dashboards nobody uses to make a decision. RevOps reporting into the CRO, peer to Marketing and Enablement, is the only arrangement where the routing engine, the quota model, and the GM scorecard can all be governed by one accountable owner.

Real numbers: quota builds, spans, and hub cost

Concrete ranges matter more than principles here, because "GM owns the P&L" means nothing until you specify what number they carry.

GM quota construction for a $6M unit. A location doing roughly $6M in annual revenue typically carries a new-customer revenue target in the $1.8M–$2.4M range — thirty to forty percent of total — with the balance of $3.0M–$3.6M coming from rebooks, plan upgrades, expansion services, and recurring contracts. Layered on top are two constraint metrics rather than growth metrics: a unit EBITDA floor in the 18–24% band, and a labor-ratio ceiling expressed as payroll divided by revenue against the regional benchmark. The constraints exist so a GM cannot hit the revenue number by hiring their way there or by discounting to fill the schedule.

Quota-to-OTE ratios. GMs typically carry quota at roughly four to five times their on-target earnings — modestly below the ratio you would set for a pure-bookings seller, because the GM's variable compensation splits across revenue, margin, and retention rather than concentrating on new business alone. Frontline advisors run higher, often five to seven times OTE, since services deal cycles are measured in days and the lead is supplied rather than self-sourced.

Compensation architecture by layer. A GM in a mid-sized metro generally lands at $90K–$140K base with $180K–$260K OTE, typically a 50/50 to 60/40 base-to-variable split. The variable component is best structured as roughly half revenue attainment, thirty percent unit EBITDA, and twenty percent retention or customer satisfaction. Accelerators kick in past full attainment — commonly 1.5x above 100% and 2x above 115% — and PE-backed platforms usually layer in phantom equity in the 0.05%–0.25% range per location.

Regional VPs sit at $180K–$240K base against $320K–$480K OTE, with variable weighted toward regional EBITDA, same-unit growth, and a strategic-initiative component covering integrations, new-market openings, or system migrations. Equity for RVPs in rollup situations typically falls in the 0.25%–0.75% range of the platform entity.

Frontline advisors — the in-home consultants, treatment coordinators, membership advisors, service writers — run $45K–$70K base and $90K–$160K OTE at a 70/30 to 60/40 split. In a services org with a healthy central lead engine, advisor attainment should sit meaningfully above what you would expect in enterprise software, because cycles are short and lead quality is curated upstream. If your advisor attainment distribution looks like a long-cycle B2B org, the problem is almost always lead supply, not talent.

Span of control. Five to eight GMs per RVP is the working range. Below five, you cannot justify the layer economically. Above eight, the RVP degrades into a reporting conduit who visits each branch quarterly and knows none of them well. Once a platform passes roughly forty locations, an Area Director layer at three to five GMs each becomes defensible — but adding it earlier is one of the most reliable ways to slow decision-making without improving anything.

Hub cost. Fund the central hub as a percentage of system revenue, commonly in the 4–7% band for healthy multi-location services platforms, and hold it to KPIs with teeth: cost per qualified lead by location tier, lead-to-booked-revenue conversion audited monthly per location, system-level brand NPS, and a quarterly GM satisfaction survey on enablement quality. Critically, do *not* chargeback hub cost to individual locations. Chargebacks create a death spiral where GMs decline leads to reduce their allocated cost, hub volume drops, unit economics worsen, and the chargeback rate rises. Fund it from the top.

Central-to-location staffing ratio. Roughly one central FTE per six to nine locations is a reasonable planning heuristic for platforms above the $100M mark. Smaller platforms run leaner and lean harder on fractional or agency support for demand gen and creative, which is fine as long as routing, quota, and scorecard ownership stay in-house. Those three are the nervous system; outsourcing them is how you end up unable to answer basic questions about your own business.

Ramp expectations. A new GM at a greenfield location reaches full quota in roughly six to nine months. At an acquired location with an installed customer base, three to five months. Frontline advisors ramp in sixty to ninety days under a structured central onboarding — and centralized onboarding measurably beats letting each location train its own people, which is one of the clearest arguments for the hub that has nothing to do with marketing spend.

Trade-offs: what you give up by centralizing

Every structural choice here costs something. Pretending otherwise produces implementations that collapse the first time a strong GM pushes back with a legitimate objection.

Centralized demand gen costs you local nuance. A hub media buyer running twenty-six markets from one dashboard will miss that the Tucson branch gets its best leads from a specific regional home show every March, or that a particular referral relationship with a property management group drives a third of one branch's commercial volume. The mitigation is a local-discretion budget — a small percentage of the branch's marketing allocation the GM can direct without approval, reported into the hub for attribution but not gated by it. Five to ten percent is usually enough to preserve the good local instincts without reopening the door to twenty-six independent marketing programs.

Centralized pricing costs you margin in cost-mismatched metros. A flat national rate card destroys margin in high-cost markets and leaves money on the table in low-cost ones. The standard answer is tiered pricing — typically three tiers keyed to metro cost structure, refreshed on a regular cadence against published regional cost indices — with a bounded local adjustment band. Give the GM a corridor, not a blank check, and require documentation when they price at the edge of it.

Centralized CRM costs you migration pain and short-term productivity. Consolidating four CRMs into one is a genuinely disruptive project. Expect a productivity dip during cutover, budget for data cleanup that will take longer than quoted, and grandfather in-flight deals under the old comp treatment for a defined window so nobody's paycheck becomes collateral damage. The alternative — leaving four systems in place — makes cross-location benchmarking permanently impossible, which forfeits the entire reason for building a platform.

The RVP layer costs you salary and a decision hop. Three RVPs at fully-loaded cost is real money against a $71M platform. The return is measured in same-unit growth and EBITDA variance compression, not in anything directly attributable. If you cannot articulate what the RVP is doing that the CEO was previously doing badly, you are adding a layer for org-chart aesthetics.

There is also a genuine case for *not* doing this yet. A three-location business with $9M in combined revenue does not need three layers and a hub. The principles still hold — one person owns each unit's P&L, marketing and systems are built once — but the implementation collapses into a single operator overseeing three GMs directly, with a fractional marketing resource and a shared operations analyst. The structure described here starts earning its cost somewhere around eight to twelve locations, and becomes close to mandatory past twenty.

Adjacent structures worth knowing: franchise systems face the same acquisition-versus-conversion split but cannot mandate anything, so their "hub" operates through incentives and access to shared marketing funds rather than through direct authority. Managed-service and field-service software companies selling *into* these platforms should map their own account teams to this shape — sell the platform at the hub, but win adoption at the GM level, because the GM controls whether the tool actually gets used on Monday morning.

Where these org charts break

Five failure patterns recur often enough to plan around.

The mini-CEO GM who refuses central leads. A GM who insists on running their own marketing because "they know the local market" will drive materially higher acquisition cost within a year, and the duplicate spend usually shows up as branches bidding against each other in shared metros. The fix is compensation design, not persuasion: pay accelerators at full parity on centrally-sourced and locally-sourced revenue. The moment you pay more on local-sourced, you have funded the behavior you are trying to eliminate.

The RVP who reverts to super-GM. A strong GM gets promoted, keeps coaching deals at their old branch, and the other six locations go untouched for a quarter. Fix the scorecard: measure EBITDA *spread* across the region, not just regional total. An RVP whose best branch carries the group while three others stagnate should not clear their number.

Sandbagged, bottom-up quotas. If quota is set as "last year plus a bit," every GM has a rational incentive to underperform in Q4 to soften next year's target. Set quota top-down off market potential using third-party metro-level market sizing, apply a floor so a new number cannot fall below the prior year's actual by more than a defined margin, and publish attainment on a scoreboard every GM can see. Peer visibility is the cheapest motivational tool available and it costs nothing to deploy.

Promoting the top advisor into the GM seat. This is the single most common hiring error in multi-location services, and it fails at a high rate because the GM job is scheduling, coaching, vendor management, payroll discipline, and P&L literacy — none of which are adjacent to closing. The strongest predictor of GM success is prior multi-unit P&L experience in *any* services category. Operators coming from multi-unit retail or restaurant management frequently outperform internally-promoted top performers, and they arrive already knowing how to read a labor line.

No system-level quality signal. Without a consistent, centrally-administered customer satisfaction measure by location, you cannot distinguish a branch with a demand problem from a branch with a service problem — and those require opposite interventions. Run the survey centrally on the same instrument everywhere, and set a hard trigger: any location falling a defined margin below the system mean gets an RVP intervention within thirty days, with a documented plan. The rule matters more than the exact threshold, because it removes the discretion that lets a struggling branch drift for three quarters.

A sixth pattern worth flagging: integration debt after acquisitions. Every deal that closes without a firm date for CRM migration, comp plan conversion, and rate card alignment adds permanent complexity. Put those three dates in the deal model, not the post-close wish list. The pest control platform in the opening scenario did not decide to run four CRMs — it just deferred the decision nine times.

Implementation sequencing. Diagnostic and RVP hiring in the first thirty days: map every location's revenue, EBITDA, advisor headcount, and lead sources; appoint or hire RVPs at five-to-eight spans; stand up at minimum a VP RevOps, a marketing lead, and an enablement lead. Days thirty-one to sixty: roll out new comp plans with a ninety-day grandfather on in-flight deals, consolidate to a single CRM, and turn on central routing by radius and capacity. Days sixty-one to ninety: establish the weekly RVP-to-GM one-on-one, the monthly regional business review anchored on EBITDA and same-unit growth, and the quarterly system council; publish the scoreboard. Days ninety-one to one-eighty: layer in same-unit growth tracking and cohort retention reporting, then tune quotas against the observed attainment distribution — if nearly every GM clears 100%, the targets are soft; if very few do, they are punitive and you will lose people.

Related questions

How many locations before you need a Regional VP layer?

Roughly eight to twelve. Below that, a single operator can hold direct relationships with every GM. Past twelve, the direct-report count degrades attention per unit and you start seeing branches that go a full quarter without a substantive conversation about their numbers.

Should GMs be allowed to do any local marketing?

Yes, within a bounded discretion budget of roughly five to ten percent of their allocation, reported into the hub for attribution. This preserves genuinely local opportunities — trade shows, referral partnerships, community sponsorships — without reopening the door to twenty-six parallel marketing programs.

Does this structure work for franchise systems?

The ownership split does; the enforcement mechanism does not. Franchisors cannot mandate a CRM or a rate card, so the hub must earn adoption through shared marketing funds, superior lead economics, and demonstrably better tooling rather than through direct authority.

What is same-unit growth and why does it matter more than total revenue?

Same-unit growth compares each location's performance against itself year over year, excluding new openings and acquisitions. It is the only honest measure of whether the operating model is working, because total revenue growth can be entirely purchased through M&A.

Where should customer experience sit in this org?

In the hub, reporting to the CRO alongside RevOps and Marketing. CX owns the measurement instrument and the escalation path; the location owns the recovery action. Splitting measurement and remediation this way keeps the score honest.

FAQ

How many locations does a Regional VP typically oversee?

Five to eight, with the exact figure driven by geographic density and unit complexity. Tightly clustered urban branches with similar service mixes support the higher end; sprawling territories with mixed residential and commercial operations sit at the lower end. Above eight, the RVP stops being an operator and becomes a reporting relay.

What is the actual difference between a General Manager and a Regional VP?

The GM owns one unit's complete P&L — revenue, labor, margin, and local execution. The RVP owns EBITDA and same-unit growth across a group, plus the consistency of performance within it. A useful test: if the RVP's region hits its total number because one branch overperformed while three stagnated, the RVP has not done the job.

Does the central team set pricing for every location?

The hub designs and governs the rate card architecture to protect brand consistency and margin discipline, typically through metro-cost tiers rather than one flat national price. GMs get a bounded local adjustment corridor and are expected to document why they priced at the edge of it.

How does lead distribution work between the hub and the locations?

Central demand gen and RevOps own lead supply and qualification, then route to locations by service radius, current capacity, and trailing conversion performance, with a fairness rule preventing the strongest branch from absorbing all high-intent volume. GMs own conversion of what they receive, not generation of it.

What happens when a location underperforms under this structure?

The GM is accountable for the unit's revenue and margin targets, and the RVP intervenes with a documented plan inside a defined window. Persistent shortfalls can end in a GM change — but the hub is equally obligated to check whether lead supply, pricing tier, or comp design is the actual cause before anyone concludes it is a people problem.

Is this org chart overkill for a three-location business?

The full three-layer version is, but the principles are not. Run it as one operator overseeing three GMs directly, with a fractional or shared resource covering marketing and operations. Keep the two non-negotiables — one named owner per unit P&L, and marketing plus systems built once rather than three times — and add the RVP layer when direct reports pass roughly a dozen.

Sources

• https://www.bls.gov/cpi/regional-resources.htm
• https://www.sba.gov/business-guide/manage-your-business/hire-manage-employees
• https://hbr.org/2015/02/what-is-a-p-and-l-statement
• https://www.ibisworld.com/united-states/market-research-reports/
• https://www.census.gov/programs-surveys/susb.html
• https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights
• https://www.bain.com/insights/topics/private-equity-report/
• https://www.salesforce.com/resources/research-reports/state-of-sales/
• https://www.franchise.org/franchise-information
• https://www.irs.gov/businesses/small-businesses-self-employed

Related on PULSE

• [Sales Org Chart for B2B Professional Services Firms in 2027](/knowledge/ra0195)
• [How to architect revenue operations for a multi-location dental group (DSO) in 2027](/knowledge/ra0615)
• [How to architect revenue operations for a multi-location chiropractic clinic group in 2027](/knowledge/ra0640)
• [Revenue Architecture for Multi-Location Retail Chains Software in 2027](/knowledge/ra0153)
• [Top 10 revenue architecture frameworks for SaaS subscription businesses](/knowledge/ra0514)