How Many Sales Reps Do I Need to Hire for My Field Service Software Company in 2026?

The outcome you should expect

The output of this exercise is not a single number. It is a hiring schedule — a count paired with start dates and a cost curve you can defend in a board meeting. That distinction matters more in field service software than in horizontal SaaS, because your buyer is a contractor who runs a business on trucks, not a VP who evaluates software for a living, and the learning curve for your reps is correspondingly steeper.

Here is what a finished plan looks like. You start with two revenue numbers: where you are and where you want to be. Say you run a company at $6M ARR selling scheduling, dispatch, and invoicing software to HVAC, plumbing, and electrical contractors, and the board wants $9M by the end of next year. That is a $3M gap on paper. It is not a $3M sales problem. If your net revenue retention runs 112% — plausible for field service software where payments processing, extra technician seats, and add-on modules like inventory or memberships expand accounts naturally — your existing base grows to roughly $6.72M without a single new logo. Your reps have to carry about $2.28M of net-new.

Now divide by what a ramped rep actually produces. Not quota. Production. If your team's history says a fully ramped rep selling to small trades contractors lands somewhere near $480K in new ARR per year at typical attainment, $2.28M requires about 4.75 rep-years of productive capacity. That is the honest denominator, and it is where most plans quietly break — leaders divide by the quota they wrote rather than the number their reps have historically hit.

Then two adjustments turn 4.75 rep-years into a real hire count. First, ramp: a rep who starts in March does not produce a full year of capacity in that calendar year. If ramp runs five months and the rep contributes maybe 30% of full productivity during it, a March start yields roughly seven or eight months of real output. Second, attrition: at 20% annual turnover on a twelve-rep team, you lose two or three people, and those hires replace capacity rather than adding it.

Net it out and the answer lands around eight to ten hires, front-loaded early enough in the year that ramp completes before you need the production. That is the expected outcome — a specific count, a specific sequence of start dates, and a fully loaded cost you can compare against the incremental ARR it buys. Everything downstream from recruiting pipeline to onboarding curriculum to territory design flows from that schedule, which is why RevOps should own the model rather than inheriting a number from finance.

One more expectation worth setting: the plan will be wrong. Attainment will drift, one hire will wash out in month two, a competitor will change pricing. The value is not precision — it is having an explicit model whose assumptions you can revisit quarterly instead of arguing about vibes.

What drives that outcome

Five inputs move the answer, and they do not move it equally. Ranked by leverage:

Net revenue retention. This is the single biggest lever and the one most founders underweight. At 112% NRR on a $6M base, your reps owe $2.28M. Drop to 100% and they owe $3M — a 32% increase in the sales job, which pushes the hire count from eight to something closer to eleven or twelve. In field service software you push NRR up through payments attach rates, technician seat growth as contractors add trucks, and module expansion. A dollar of retention improvement is meaningfully cheaper than a dollar of new-logo capacity, so before you approve a hiring plan, ask whether the customer success and product teams have a credible path to two or three points of NRR. That conversation frequently removes a headcount from the plan.

Real productive capacity per rep. Use trailing twelve-month actuals segmented by tenure. If reps past their first year averaged $460K and you plan at $600K because that's the new quota, you will under-hire by roughly 25% and then wonder why the year missed. Segment further if your motion splits — one-truck operators close in three weeks at $6K ACV; a fifteen-truck multi-location contractor takes four months at $40K ACV. Those are different capacity numbers and arguably different roles.

Ramp time. In field service software, ramp is longer than generic SMB SaaS because the product knowledge is operational. A rep has to explain to a plumbing owner how dispatch boards handle emergency calls, how the mobile app behaves when a tech loses signal in a crawlspace, how invoicing syncs to QuickBooks, and how you compare to ServiceTitan, Jobber, and Housecall Pro. That is trade fluency, not feature memorization. Plan three to six months for the SMB motion, six to nine for anything upmarket.

Attrition. Fifteen to twenty-five percent annually is the common band for SaaS sales teams, concentrated in the first year. Model it explicitly rather than assuming a stable team.

Lead supply. The quietest constraint. Capacity math assumes reps have something to work. If marketing generates 200 qualified opportunities a quarter and your existing team already consumes them, ten new reps will not produce ten reps' worth of revenue — they will split the same pipeline and everyone's attainment falls. Always run the demand-side check before signing the hiring plan.

The order of operations in that flow is not decorative. Applying NRR before dividing by capacity is what keeps you from hiring for revenue your customer success team already produces. Checking lead supply last is what keeps you from hiring capacity your marketing engine cannot feed.

Benchmarks and realistic ranges

Treat every number here as a starting hypothesis to replace with your own data as soon as you have twelve months of it.

Capacity per ramped rep. For SMB trades — one to ten trucks, ACV typically in the low thousands to low five figures — a ramped rep in field service software commonly produces somewhere in the $350K to $600K range in new ARR annually. Mid-market and multi-location contractors, where ACV climbs into the tens of thousands and the cycle stretches past a quarter, can support $600K to $1M quotas, but attainment distributions widen considerably. A reasonable planning midpoint for an SMB-focused company is around $480K, and you should sanity-check it against a rule of thumb: fully loaded rep cost including commission and benefits should generally sit somewhere near a fifth to a third of the ARR they produce, or the model does not pay for itself.

Ramp. Three to six months to full productivity for SMB field service software. Six to nine for upmarket. During ramp, expect 20% to 40% of full quota. Model ramp as a curve, not a switch — month one near zero, month three maybe a third, month five approaching full.

Attrition. 15% to 25% annually, weighted toward the first twelve months. Vertical SaaS sometimes runs slightly lower than horizontal because the domain knowledge creates stickiness — a rep who has learned how trades businesses run has less transferable optionality than someone selling generic CRM. Do not count on that.

NRR. Field service software has structurally good expansion mechanics. Contractors grow by adding trucks and technicians, which grows seats. Payments processing attaches as a revenue share and compounds with the customer's own volume. Modules — inventory, marketing automation, membership plans, financing — stack over time. Healthy vertical SaaS in this space often clears 105% to 115%; the best push higher on payments attach alone.

Sales cycle. One-truck operators can close in days to a few weeks; they are owner-operators making a fast decision. Ten-to-thirty-truck companies typically take one to three months and involve an office manager plus the owner. Multi-location or private-equity-backed roll-ups take a quarter or more and add procurement. Cycle length feeds directly into how quickly a ramped rep's pipeline converts, which affects when their capacity actually shows up as recognized revenue.

Ratios around the rep. Capacity planning fails when it treats the rep as a standalone unit. Common supporting ratios: one sales engineer or solutions consultant per three to six reps once deals involve integration questions, one SDR per one to two AEs if you run an outbound motion into trade contractors, one manager per six to eight reps, and one onboarding or implementation specialist per some volume of closed accounts. Ten new AEs without a corresponding manager hire means a span of control that guarantees weak coaching during exactly the ramp window when coaching matters most.

Segment split. If half your net-new target comes from mid-market accounts at $40K ACV and half from SMB at $8K, run the capacity math twice with different assumptions and sum the results. Blending them into one average produces a number that is wrong for both motions.

Risks, edge cases, and failure modes

Hiring ahead of pipeline. The most expensive mistake. Reps ramp, arrive productive, and find no accounts to work. Attainment collapses across the whole team, the good reps leave first, and you have burned a year of payroll to end up smaller. Before approving headcount, model opportunity supply per rep at the target team size. If the math says each rep gets thirty qualified opportunities a quarter and your historical win rate needs forty to hit quota, you have a demand problem wearing a headcount costume.

Dividing by paper quota. Covered above, but it deserves restating because it is so common. Quota is an incentive instrument. Capacity is an observed average. Using the first where you need the second under-hires you by whatever the attainment gap is — often 20% to 30%.

Ignoring the ramp calendar. Counting a rep who starts in September as a full unit of next-year capacity is technically correct and practically misleading, because their contribution is back-loaded. If the board expects linear quarterly progress, a hiring plan that back-loads production will look like a miss for three straight quarters even when the annual number lands.

Backfills counted as growth. If you plan ten hires and lose three, you added seven. Track gross hires and net adds as separate lines. Boards routinely conflate them.

Manager span blowout. Ten new reps under two existing managers means twelve to fifteen direct reports each. Coaching stops, ramp lengthens, attrition rises, and the model's ramp and attrition assumptions both degrade simultaneously — a compounding failure, not an additive one.

Recruiting throughput as the real bottleneck. Nobody hires ten qualified field service software reps in a month. If your historical hiring rate is one or two per month and your plan needs ten starts by Q2, the plan is arithmetic fiction. Either extend the timeline, invest in recruiting capacity ahead of the reqs, or lower the target.

Onboarding capacity. Related and equally overlooked. If your enablement function can genuinely ramp three reps at once, a cohort of eight means five of them get a degraded experience. Ramp lengthens, capacity per rep drops, and the model breaks from the inside.

Territory and account conflict. In a vertical company, your total addressable market is finite — there are only so many HVAC contractors of a given size in a given metro. Doubling the sales team can mean cutting territories in half, which caps individual capacity below your planning assumption regardless of talent. This is the edge case that makes vertical SaaS capacity planning genuinely different from horizontal: you can run out of market before you run out of reps.

Channel and partner overlap. Many field service software companies sell partly through distributors, trade associations, or manufacturer partnerships. If a meaningful share of net-new arrives through channel, subtract it from what direct reps must carry before dividing. Otherwise you hire capacity for revenue that would have arrived anyway.

Product-led signup cannibalizing the model. If contractors can self-serve onto a starter tier, some net-new arrives without rep involvement. Same correction: separate rep-sourced from self-serve before sizing headcount.

Cash constraint. All of this assumes you can fund it. A fully loaded rep at, say, $150K to $200K all-in who contributes little for five months represents real burn before return. If runway is tight, phase in cohorts of two or three per quarter, accept slower growth, and say so explicitly rather than approving a plan you cannot fund and then freezing hiring mid-year — the worst of both outcomes.

A practical rollout plan

Run this as a sequence with owners and dates, not a spreadsheet exercise.

Week one: assemble the actuals. Pull trailing twelve-month new ARR per rep, segmented by tenure band and by segment. Pull real NRR from your billing system, decomposed into churn, contraction, seat expansion, and payments or module expansion. Pull attrition by tenure. Pull average ramp measured as months-to-first-quota-attainment, not months-to-first-deal. If you cannot produce these cleanly, that is the first project — the rest of the model is guesswork without them.

Week two: build the base model. Current ARR, goal ARR, NRR, capacity, ramp, attrition, current headcount in; hire count and start dates out. A calculator or a clean spreadsheet both work. What matters is that every assumption is visible and editable. PULSE publishes a free [Recruiting Calculator](/tools/recruiting-calculator) that runs exactly this model in the browser if you would rather not build one.

Week three: run three scenarios. Conservative (NRR flat, attainment at trailing average, ramp at the long end), base (your honest expectation), and aggressive (NRR improves two points, ramp shortens with better enablement). Present the range to leadership. The spread between conservative and aggressive is usually three to four hires, and seeing that spread is what turns the conversation from "how many" to "which levers are we actually pulling."

Week four: constraint-check. Test the base scenario against recruiting throughput, onboarding capacity, manager span, lead supply, and territory availability. Whichever constraint binds first sets your real ceiling. Adjust the plan to that ceiling and document why.

Weeks five through eight: sequence and staff. Convert the count into dated cohorts working backward from when you need production. If you need full productivity in Q3 and ramp is five months, those reps start no later than early Q2, which means reqs open now. Hire in cohorts of two to four so onboarding scales and the cohort supports each other. Pair each cohort with a manager who has capacity.

Ongoing: instrument and revisit quarterly. Track four numbers monthly — actual ramp versus modeled, actual attainment by tenure band, actual attrition, actual NRR. When any drifts more than about 10% from plan, rerun the model. A capacity plan reviewed once a year is a document; reviewed quarterly it is an operating system. This is a RevOps function: own the model, own the inputs, own the recalculation cadence.

Related questions

Should I hire AEs or SDRs first?

Depends on where deals stall. If your AEs have more qualified pipeline than they can work, hire AEs. If they are prospecting into contractors themselves and closing less as a result, an SDR or two frees capacity faster and cheaper than another AE.

How do I split the plan across segments?

Run the capacity math separately for SMB and mid-market, since ACV, cycle length, and ramp all differ, then sum. Blending them into one average produces a plan that under-serves the upmarket motion and over-hires for SMB.

What if my board wants a number tomorrow?

Give the range, not a point. Conservative and aggressive scenarios with the assumption that separates them is a more defensible answer than a single number you cannot support, and it moves the conversation to which levers you're pulling.

Does this model work for hiring implementation staff too?

Yes, with different inputs. Replace ARR gap with onboarding volume and per-rep capacity with accounts-implemented-per-specialist-per-month. Same structure: demand divided by capacity, adjusted for ramp and attrition.

How often should I rerun the model?

Quarterly at minimum, and immediately whenever attainment, ramp, attrition, or NRR drifts more than roughly 10% from what you assumed. An annual plan goes stale by month four in a growing company.

FAQ

How long does a new field service software rep take to become fully productive?

Typically three to six months for a rep selling to small trades contractors, and six to nine months for anyone selling to larger multi-location or roll-up accounts. During ramp, expect roughly 20% to 40% of full quota. The extra time in this vertical comes from operational fluency — a rep has to genuinely understand how dispatch, scheduling, technician mobile workflows, and invoicing work in a contractor's day before they can sell against established competitors credibly.

What is a realistic quota for a rep selling to HVAC, plumbing, and electrical contractors?

For SMB contractors running roughly one to ten trucks, a ramped rep commonly produces in the $350K to $600K range of new ARR per year, with something near $480K a reasonable planning midpoint. Upmarket and multi-location accounts can support higher numbers, often $600K to $1M, but with longer cycles and wider variance in attainment. Always validate against your own trailing twelve-month actuals rather than adopting a benchmark.

What if I can't afford to hire eight to ten reps at once?

Phase it. Hire cohorts of two or three per quarter, confirm the first cohort is tracking to ramp before committing to the next, and accept that growth arrives later. This is a legitimate trade — it lowers cash risk substantially at the cost of a slower revenue curve. Say so explicitly in the plan so leadership is choosing the trade rather than discovering it.

How do I account for attrition in the hire number?

Apply your actual turnover rate to your current team, not the industry average. At 20% on twelve reps you lose two or three people annually, and those hires replace capacity rather than add it. Report gross hires and net adds as separate lines so nobody confuses backfills with growth, and weight expected attrition toward the first twelve months of tenure where it concentrates.

What happens to the model if my NRR is lower than assumed?

Every point of NRR you lose transfers directly to your reps as additional net-new they must sell. At 105% NRR instead of 112% on a $6M base, the net-new requirement rises from roughly $2.28M to $2.7M, which adds two or more hires. This is why improving retention is often cheaper than adding sales capacity — run that comparison before approving the reqs.

Do I need a software tool for this, or is a spreadsheet fine?

A spreadsheet is fine and fully transparent, which is its main advantage — every assumption is visible. The risk is a broken formula nobody catches and a model that only one person understands. A purpose-built calculator removes that risk for the core math; planning platforms make sense once headcount planning is continuous rather than annual. Start free, upgrade when the model matters enough that fragility becomes a real liability for your company.

Sources

• https://www.saastr.com/
• https://openviewpartners.com/blog/
• https://www.bain.com/insights/topics/technology-report/
• https://hbr.org/topic/subject/sales
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• https://www.salesforce.com/resources/
• https://www.hubspot.com/sales-statistics
• https://www.gartner.com/en/sales
• https://www.bls.gov/ooh/sales/sales-managers.htm

Related on PULSE

• [How Do I Get My Field Reps to Sell Service Agreements?](/knowledge/q15863)
• [How Do I Score My Field Techs on Sales and Service?](/knowledge/q16037)
• [When should a 2027 sales org split inside sales and field sales teams?](/knowledge/q12472)
• [What's the OTE breakdown for inside vs field sales at $30k ACV?](/knowledge/q14)
• [How do you coach a field rep to use their time in-territory well?](/knowledge/q14049)
• [How do you calculate field marketing event ROI in 2027?](/knowledge/q12684)