How Many Sales Reps Do I Need to Hire for My Restaurant POS Company in 2026?

What headcount math actually means for a POS company

Sales headcount is not a staffing question — it is a capacity question. Every rep is a unit of production with a known output, a known warm-up period, and a known probability of leaving. The number you hire is the arithmetic that closes the distance between the revenue you already have and the revenue you have promised, with enough slack built in that the plan survives contact with reality.

Restaurant POS makes this harder than generic B2B software for four structural reasons, and each one changes a variable in the equation.

Your revenue has two engines. A restaurant POS deal is software subscription plus payment processing residuals, and often hardware. The software line is predictable — a terminal count times a monthly rate. The payments line moves with the restaurant's volume, which means it grows on its own after the sale and craters when a location closes. When you compute "revenue per rep," decide up front whether you are counting booked software ARR, blended software-plus-payments recurring revenue, or first-year total contract value including hardware. Mixing these across quarters is the single most common reason a headcount model produces a number that turns out to be wrong by 40%.

Your base grows without new logos. If a restaurant that signed last year adds a second terminal, turns on online ordering, and processes more volume than it did at signup, your revenue from that account rises with zero sales effort. That is net revenue retention, and in POS it is frequently above 100% because payments attach scales with the customer's own growth. High NRR shrinks the net-new number your reps must carry, which shrinks headcount. A team obsessing over hiring while ignoring expansion is solving the expensive half of the problem.

Your average deal is small and your sales cycle is short. An independent restaurant deal is usually in the low thousands of dollars of first-year value, closed in days or weeks, not quarters. That means rep capacity is bounded by activity volume — demos run, sites visited, calls made — far more than by deal complexity. In enterprise software you model capacity from pipeline coverage. In SMB restaurant POS you model it from throughput: how many qualified demos a rep can physically run in a month, times close rate, times deal size.

Your churn is baked into the market. Restaurants fail at a meaningfully higher rate than most business categories. A share of your logo churn each year has nothing to do with your product — the location simply closed. That churn drag raises the net-new number reps must produce just to stand still, and it belongs in the model before you compute a single hire.

The practical consequence: two POS companies with identical revenue and identical goals can need wildly different headcount. One selling five-terminal small chains at $900/month with 118% NRR needs a fraction of the reps of one selling single-terminal independents at $180/month with 96% NRR. Benchmarks are a sanity check, never the answer. Your own trailing six months of data is the answer.

The step-by-step process for sizing the team

Run these six steps in order. Skipping any one of them is how a plan misses by six figures.

Step one: fix the revenue gap precisely. Take current recurring revenue, apply your realistic NRR to get what the base produces on its own, and subtract that from the goal. At $7M current, 112% NRR, and a $10M goal, the base carries to about $7.84M and the gap the sales team owns is roughly $2.16M. If your NRR is below 100% — common when restaurant closures outpace expansion — the base *shrinks*, and the gap is larger than the naive goal-minus-current difference. Compute NRR from your own cohort data over the trailing twelve months, not from a category benchmark.

Step two: compute true productive capacity per ramped rep. Do not use the quota on the comp plan. Use what your median ramped rep actually produced in the last four quarters. Take total net-new revenue closed by reps who were past ramp for the full period, divide by that headcount. If your team of six ramped reps closed $1.5M net-new last year, your capacity figure is $250K, regardless of what the plan said. If you have no history — a first sales hire — build it from throughput: demos per month × close rate × average first-year value × 12. Twenty-five demos at an 18% close rate on a $3,200 average is about $14,400 monthly, or roughly $173K annually.

Step three: convert the gap to rep-years. Gap divided by capacity. $2.16M ÷ $250K = 8.6 rep-years of *productive* capacity required. This number is not your hire count. It is the amount of fully ramped output you must have on the field for the full period.

Step four: apply the ramp discount. A rep hired in month one does not deliver a full rep-year in year one. If a new hire produces roughly zero in months one and two, 30–50% of capacity in months three and four, and 80–100% from month five onward, their first twelve months yield something like 0.55–0.65 of a rep-year. Divide your rep-years by that factor: 8.6 ÷ 0.6 ≈ 14.3 hires if every hire starts on day one of the plan year. This is the step teams skip, and it is why they miss.

Step five: add attrition backfill. Apply your observed annual attrition rate to your existing team to find how many hires simply hold the line. A team of ten with 25% attrition needs two-to-three hires that add nothing to capacity. Then add expected attrition among the new cohort itself — new-hire washout in field POS sales frequently runs higher than tenured attrition.

Step six: build the start-date schedule backward. Capacity is needed on specific dates, so work backward from when the revenue must land: subtract the ramp period, then subtract time-to-hire (sourcing through accepted offer routinely takes 30–60 days for field sales). A rep who must be producing in July needs to start in February or March, which means the requisition opens in December.

The loop at the end matters. Capacity per rep is not a constant — it rises as your enablement improves and falls when you push reps into thinner territories. Re-derive it quarterly from actuals and let the hire count move with it.

Costs, timelines, and typical ranges to plan against

Ramp length. Restaurant POS ramp is longer than generic SMB SaaS because a rep must learn payment processing economics, hardware configurations, menu and modifier setup, kitchen display and online ordering integrations, and how you position against the well-known incumbents in the category. Plan three to four months to a consistent first close and five to six months to full productivity. A rep hired from a payments or merchant-services background may compress this by a month; a rep hired from restaurant operations may know the buyer cold but need longer on the commercial side.

Attrition. Field and inside sales roles in payments and POS carry high turnover relative to enterprise software. Planning on 20–40% annual attrition is realistic, weighted toward the first year. A meaningful share of new hires will not clear quota in year one. Two structural drivers make this worse when unmanaged: territories that cannot support the quota assigned to them, and comp plans where the payments-residual component takes months to become material, so early earnings look thin even when the rep is performing.

Time to hire. For field sales roles, 30–60 days from requisition to accepted offer is normal, longer in dense metros where you are competing with every other payments company for the same profile. Stack that on top of ramp: from "we decided to hire" to "this person is at full quota" is commonly seven to nine months. That single number should govern your planning cadence more than any other.

Capacity ranges by segment. These vary enormously by motion, so treat them as bands to test against your own data rather than targets. Reps selling single-location independents on short cycles land toward the lower end of net-new production because deal sizes are small, even though volume is high. Reps selling small multi-unit chains produce more per deal but close fewer, with longer cycles and more stakeholders — a franchise group evaluating a switch involves an owner, an operations lead, and often an accountant. Enterprise and large-chain motions are a different job entirely and should not share a quota model with SMB.

Territory density drives everything. Restaurant count within reasonable travel distance is the hard constraint on a field rep's throughput. A rep in a dense urban core can physically visit several restaurants a day; a rep covering a wide rural territory spends most of the week driving. Tier your territories by restaurant density and set differentiated quotas accordingly. Giving a rural rep the same number as an urban rep is not fairness — it guarantees the rural rep misses, disengages, and quits, and you pay the hiring cost twice.

Cost per hire. Budget beyond base salary: recruiting cost or agency fee, onboarding and training time from senior reps and sales engineers, hardware and demo equipment, CRM and tooling seats, travel, and the opportunity cost of accounts assigned to a rep during ramp who could have gone to a producer. The all-in cost of a field POS rep in their first year is substantially more than their base, and a rep who washes out at month seven has consumed nearly all of that cost while returning a fraction of it. This is precisely why attrition belongs in the model as a first-class variable rather than a footnote.

A worked example. A restaurant POS company at $4M recurring revenue targets $6M. NRR is 108%, so the base carries to about $4.32M, leaving a $1.68M gap. Trailing data shows ramped reps producing $220K net-new annually. That is 7.6 rep-years. With a first-year ramp factor of 0.6, that is roughly 12.7 hires for reps starting at the top of the year — and materially more if hires are staggered through the year, because a rep starting in month seven contributes almost nothing to that year's number. The existing team of eight, at 25% attrition, needs two backfills. Total: something like fourteen to fifteen requisitions, opened on a schedule that puts most starts in the first quarter. If that number is unaffordable, the honest conclusion is that the $6M goal is not funded — either the target moves, the timeline extends, or per-rep capacity has to rise through better territories, better enablement, or a higher-value segment.

Where teams get this wrong

Dividing the gap by quota and calling it done. This is the default error and it under-hires by roughly 40%. Quota is an aspiration; capacity is an observation. And a hire made today is not a rep-year — it is roughly 0.6 of one in the first twelve months. Skipping the ramp discount produces a plan that looks affordable in the board deck and misses in Q3.

Ignoring attrition until it happens. Turnover in field POS sales is not an anomaly to be surprised by, it is a planning input. If you know a quarter of the team turns over annually, budget the backfills at the start of the year. Teams that treat every departure as an unplanned emergency spend the year in reactive recruiting, which produces worse hires, which raises attrition further.

Hiring the whole cohort in one wave. A large simultaneous class overwhelms onboarding capacity. Senior reps who should be selling are training instead, the sales engineer is booked solid, and every new hire gets a thinner version of the enablement that the previous cohort got. The result is a cohort that ramps slower and washes out faster than a staggered one. Hiring in waves of two to four, spaced six to eight weeks, lets you fix onboarding problems between cohorts and keeps mentorship capacity available.

Uniform quotas across non-uniform territories. Covered above, and worth repeating because it is the quietest destroyer of headcount plans. The rep who cannot hit an unachievable number leaves, you backfill, the replacement inherits the same territory and the same impossible number, and you have institutionalized a vacancy. Fix the territory, not the rep.

Confusing revenue definitions between the plan and the comp plan. If the headcount model counts blended software-plus-payments recurring revenue but reps are compensated on software MRR alone, reps will optimize for software and your model's payments assumptions will not materialize. Whatever definition the capacity model uses, the comp plan must reward the same thing.

Hiring reps to fix a conversion problem. If demo-to-close has fallen from 20% to 13%, adding reps buys you the old conversion rate at a much higher cost. Diagnose whether the constraint is capacity or conversion before signing requisitions. A five-point close-rate improvement across an existing team of eight often delivers more net-new revenue than three new hires, at a fraction of the cost and none of the ramp lag.

Forgetting the support functions. Reps do not sell alone. Sales engineers for complex menu and integration questions, implementation staff to install and configure, and support to keep new merchants live all scale with rep count. A plan that adds ten reps and no implementation capacity produces a backlog of sold-but-not-live accounts, delayed revenue recognition, and early churn that shows up in next year's NRR — which then makes next year's headcount number worse.

Never revisiting the model. The plan built in December is stale by March. Capacity per rep, close rates, average deal size, NRR, and attrition all move. Re-run the calculation quarterly against trailing actuals and adjust the remaining hiring schedule.

Decision framework: when to hire, when to fix something else

Before opening a requisition, determine whether headcount is genuinely the binding constraint. Work through it in this order.

Are your current reps at capacity? If ramped reps are running fewer demos than their throughput ceiling, the constraint is pipeline, not headcount. Adding reps splits the same lead volume across more people, lowers per-rep attainment, and raises attrition. Fix lead generation first — reps who cannot fill a calendar quit.

Is close rate stable or declining? A declining close rate points at product fit, pricing, competitive pressure, or qualification discipline. New hires ramping into a broken motion convert worse than tenured reps, so hiring into a conversion problem amplifies it.

Is there unworked territory? If reps are at capacity, close rates are healthy, and identifiable restaurant density sits uncovered, that is the clean case for hiring. It is also the case with the highest expected return, because the new rep inherits genuine unworked demand rather than a slice of someone else's.

Can expansion close the gap more cheaply? In POS, moving NRR up a few points through payments attach, additional terminals, or module adoption can cover a large share of the gap without a single hire. A customer-success or account-management hire focused on expansion is often cheaper per dollar of recurring revenue than a new-logo rep, and it compounds — every point of NRR shrinks next year's gap too.

Can you afford the full number? If the model says fourteen and the budget supports eight, say so explicitly rather than hiring eight and hoping. The options are a lower target, a longer timeline, or a deliberate investment in per-rep productivity. Presenting the shortfall as an arithmetic fact is far better than discovering it in Q4.

The framework's purpose is to keep you from spending the most expensive resource you have on a problem it cannot solve. Headcount is the right lever only when demand exists, conversion works, and the reps you already have are full.

Related questions

How do I size the team if I have no sales history yet?

Build capacity from throughput instead of trailing actuals: demos a rep can realistically run per month, times an estimated close rate, times average first-year value. Hire one or two reps first, measure their real numbers for two quarters, then scale the model on observed data rather than assumptions.

Should my first POS sales hire be a rep or a sales leader?

For most companies under a few million in recurring revenue, hire two individual contributors first. They generate the actual capacity and close-rate data a leader would need anyway. Bring in a leader once you have four or more reps and onboarding has become a full-time job.

How does payment processing revenue change the headcount math?

Payments revenue grows with merchant volume after the sale, which lifts NRR and shrinks the net-new gap reps must carry. It also lags — a rep's payments contribution builds over months. Model booked software separately from processing residuals so ramp assumptions stay honest.

Does inside versus field sales change the number of reps I need?

Substantially. Inside reps run more demos per week because they do not travel, so per-rep capacity on small independents is often higher. Field reps win denser multi-unit and chain deals where in-person presence matters. Segment first, then size each motion with its own capacity figure.

How often should I recalculate the headcount plan?

Quarterly, using trailing actuals for capacity, close rate, average deal size, NRR, and attrition. Any single variable moving ten percent materially changes the hire count, and adjusting the remaining schedule mid-year costs far less than discovering the miss in the fourth quarter.

FAQ

What is the most common mistake when sizing a POS sales team?

Dividing the revenue gap by quota and hiring that number. It ignores two facts that dominate the outcome: a new hire delivers roughly 60% of a rep-year in their first twelve months because of ramp, and a meaningful share of the team turns over annually. Both must be in the model before the number means anything.

What is a realistic productive capacity for one ramped rep?

It depends entirely on segment, deal size, and motion, which is why you should derive it from your own trailing four quarters rather than a benchmark. Take net-new revenue closed by reps who were past ramp for the whole period and divide by that headcount. That observed figure, not the comp plan's quota, is your capacity input.

How much attrition should I plan for?

Field and inside sales in payments and POS commonly runs 20–40% annually, weighted heavily toward the first year. Apply your own observed rate to your existing team to size backfills, and expect washout among new hires on top of that. Attrition is a planning input, not a surprise.

Should I hire all the reps at once or stagger them?

Stagger them. Waves of two to four every six to eight weeks protect your onboarding capacity, keep senior reps available for mentorship, and let you correct enablement problems between cohorts. Large simultaneous classes ramp slower and wash out faster, which raises the effective cost per productive rep.

What if I cannot afford the number the model produces?

Then the target is not funded, and the honest move is to say so before the year starts. Your options are to lower the goal, extend the timeline, or raise per-rep capacity through better territory design, stronger enablement, or a shift toward higher-value multi-unit accounts. Under-hiring quietly against an unchanged goal is the worst of the three.

How far ahead of the revenue do I need to hire?

Add time-to-hire to ramp: 30–60 days to fill a field sales role, plus five to six months to full productivity. That is roughly seven to nine months from opening a requisition to a rep carrying a full number. Revenue needed in the second half of the year requires requisitions opened before the year begins.

Sources

• https://restaurant.org/research-and-media/research/ — National Restaurant Association research on restaurant industry operations and technology adoption
• https://www.bls.gov/ooh/sales/sales-representatives-wholesale-and-manufacturing.htm — Bureau of Labor Statistics occupational data for sales representatives
• https://www.bls.gov/bdm/entrepreneurship/bdm_chart3.htm — BLS Business Employment Dynamics data on business survival rates by industry
• https://hbr.org/topic/subject/sales — Harvard Business Review research on sales force effectiveness and scaling
• https://www.gartner.com/en/sales — Gartner research on sales productivity, quota setting, and go-to-market planning
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights — McKinsey insights on sales capacity and go-to-market strategy
• https://www.sec.gov/edgar/searchedgar/companysearch — SEC EDGAR filings for public POS and payments companies, useful for benchmarking retention and sales efficiency
• https://openviewpartners.com/expansion-saas-benchmarks/ — OpenView SaaS benchmarks on net revenue retention and sales efficiency

Related on PULSE

• How Many Employees Should I Schedule Each Shift at My Mediterranean Restaurant?
• How Many Employees Should I Schedule Each Shift at My Thai Restaurant?
• How Many Employees Should I Schedule Each Shift at My Vegan Restaurant?
• How Many Employees Should I Schedule Each Shift at My Indian Restaurant?
• How Many Employees Should I Schedule Each Shift at My Korean BBQ Restaurant?
• How Many Employees Should I Schedule Each Shift at My Hot Pot Restaurant?