How Many Sales Reps Do I Need to Hire for My Payment Processing ISV?

What this method replaces, and why the alternatives keep failing

Most payment processing ISVs arrive at a rep count through one of four shortcuts, and each fails in a predictable direction. Knowing which shortcut you are currently using tells you which way your number is already wrong.

The quota-divided-by-gap shortcut. You take the revenue gap, divide by the quota printed on the comp plan, and hire that many people. This under-hires almost every time, because paper quota is not productive capacity. If your quota is 4M in annualized processing volume and your team attains at 72 percent of it, real capacity is closer to 2.9M. A 27M gap divided by 4M says seven reps. Divided by 2.9M it says ten — and that is before ramp or attrition. The error compounds because it is invisible until Q3, when the plan is unfixable.

The mirror-last-year shortcut. "We added six reps last year and grew, so add six again." This ignores that your existing merchant portfolio behaves differently every year. An ISV with a portfolio churning at 12 percent needs materially more net-new signings than one churning at 6 percent, even at identical growth targets. Retention and hiring are the same equation viewed from two ends, and a plan built on last year's retention will be wrong by exactly the amount your retention moved.

The budget-first shortcut. Finance says the plan allows nine heads, so you hire nine and assign each a stretch quota. What actually happens: nine reps carrying 133 percent of realistic capacity means attainment collapses, the strongest reps leave first because they can read a spreadsheet, and you end the year with seven reps and a worse pipeline than you started with. Over-quota'ing a team is a form of under-hiring with a delay fuse on it.

The recruiter-throughput shortcut. You hire whoever the pipeline produces and stop when it dries up. This produces a headcount number driven by your recruiting funnel rather than your revenue plan — usually too few reps started too late.

The capacity model beats all four because it makes every assumption explicit and falsifiable. Gap, organic growth, real attainment, ramp curve, attrition — each is a number someone owns and can be held to. When the plan misses, you can point at which input was wrong instead of arguing about effort. That auditability is the actual product of doing this properly; the headcount figure is almost a byproduct.

There is a fifth alternative worth naming honestly: not hiring reps at all. Plenty of payment processing ISVs grow faster by deepening a handful of referral partnerships, ISO relationships, or vertical software integrations than by adding direct sellers. If one integration partner can route 8M in annual volume and costs you a partner manager plus revenue share, that is one head producing what three direct reps would. Run the capacity model against a partner-led motion before you assume the answer is direct headcount — the same arithmetic applies, only the capacity-per-head input changes.

How to choose between direct reps, partner managers, and no hire at all

The choice is not philosophical. It resolves to four questions with numeric answers, worked in order.

Question one: what is your true net-new gap? Start with current annualized processing volume — say 40M across your platform. Set the target — 70M. Now subtract what your existing book produces without any new logo. If embedded merchants expand volume roughly 8 percent through their own growth, and you lose 5 percent to merchant attrition, your base drifts to about 41.2M. Net-new required: 28.8M. That number, not the 30M headline gap, is what your sales reps must actually sign.

Question two: what does one ramped rep really produce? Pull twelve months of closed-won annualized volume per rep who has been in seat more than a year, then subtract the merchant volume that churned out of their book within the same period. Net production, not gross signings. Most payment processing ISVs are surprised here — a rep who "signed 3.4M" often netted 2.7M once first-year merchant attrition is applied. Use the net number.

Question three: how long is your ramp? In payments, ramp is longer than in most software categories because the rep has to learn interchange, residual math, underwriting risk, and integration realities before they can hold a credible conversation with a merchant's controller. Six to nine months to full productivity is common; treat a rep hired in month one as delivering roughly half a year of capacity in year one, and a rep hired in month seven as delivering close to nothing.

Question four: what is your attrition? Take last year's voluntary plus involuntary departures over average headcount. If you run twenty reps and lost four, that is 20 percent. Applied to your existing team, that is four backfills before a single incremental head.

Run those four and the arithmetic falls out. 28.8M net-new divided by 2.7M net capacity is 10.7 rep-years. Ramp discount means a hire lands closer to 0.55 rep-years of first-year output, so you need roughly 19 rep-starts to produce 10.7 rep-years — except your existing ramped team already covers part of it. Net the existing team's contribution, add the four backfills, and the honest answer lands in the 12 to 14 range with staggered start dates.

The fork in that diagram matters more than it looks. Many payment processing ISVs run both motions and split the net-new gap between them — 60 percent direct, 40 percent partner-sourced — then size each side independently. Splitting first and sizing second prevents the common failure of hiring direct reps to cover volume that a single integration partner was always going to deliver anyway.

What it costs, how long it takes, and what you actually get back

Headcount planning is cheap. Headcount is not. Get honest about both before you sign an offer letter.

Tooling cost. The model itself runs in a free browser calculator or a spreadsheet you build in an afternoon. Purpose-built planning platforms — the Pigment, Anaplan, Cube, Mosaic tier — are quote-based and generally start in the four-to-five-figures-per-year range, with enterprise sales planning tools landing well above that. Buying one before your headcount plan is a continuous, multi-segment exercise is premature. A payment processing ISV with under thirty sellers gets the same answer from a spreadsheet, faster.

Fully loaded cost per rep. Base plus variable is only part of it. Add employer taxes, benefits, laptop and software seats, CRM and sales engagement licenses, data and enrichment tools, travel to merchant sites or trade shows, and the manager time consumed by a new hire. The fully loaded number is commonly 1.3 to 1.5 times cash compensation. If your on-target earnings for a payments partnership rep is 150K, budget closer to 200K all-in per head, per year.

Ramp cost specifically. This is the line item RevOps leaders most often omit. A rep who takes seven months to reach full productivity has consumed roughly seven months of fully loaded cost against a fraction of expected production. Across twelve hires, that is a real cash trough in the first three quarters. Model it explicitly: month-by-month cost against a month-by-month production curve, not annual against annual. Boards forgive a planned trough; they do not forgive a surprise one.

Recruiting timeline. Sourcing, interviewing, offer, and notice period for an experienced payments seller commonly runs 60 to 90 days from opening the requisition to a start date. Stack that on a six-to-nine-month ramp and you are ten to twelve months from requisition to full production. If you need capacity live by Q3 of next year, the requisition opens now — not next quarter. This is the single most actionable output of the whole model, and it is why the plan produces start dates rather than a bare count.

What you get back. The return is not the rep's first-year production; it is the annuity. A merchant signed onto your platform produces residual processing revenue every month it stays. A rep who nets 2.7M in annualized volume in year one is compounding — assuming reasonable merchant retention, that book keeps paying while the rep signs another cohort. This is why payments capacity models should be built on multi-year net revenue retention rather than single-year bookings. A direct seller who looks marginal on a twelve-month payback frequently looks obvious on a twenty-four-month one.

Where the model breaks. Two failure modes. First, if your underwriting or onboarding function cannot process the volume the reps sign, you have bought a queue, not revenue — check that boarding capacity scales with sales capacity before you hire. Second, if your merchant attrition is above roughly 15 percent, hiring is the wrong lever entirely; you are filling a bucket with a hole in it, and a retention investment returns more per dollar than a rep does. Run the retention math first and be prepared to spend the headcount budget somewhere other than headcount.

Segmenting the plan so the number survives contact with reality

A single aggregate rep count is a planning artifact, not an operating plan. Break it apart along the dimensions that actually change capacity.

By segment. A rep selling to single-location merchants through your software has a completely different capacity profile from one chasing multi-location enterprise accounts or ISV-to-ISV integration deals. Small-merchant motion: high volume, short cycle, low volume per account. Enterprise: 9-to-18-month cycles, few deals, large annualized volume each. Averaging them produces a capacity number that describes nobody. Model each segment separately and sum.

By channel. Direct outbound, inbound from your software product's install base, partner-referred, and reseller-sourced deals close at different rates and different sizes. Install-base motion is usually your cheapest volume — the merchant is already using your software and adding payments is an upsell, not a displacement. Size that motion first, because the reps who work it have inflated capacity relative to pure outbound sellers, and a plan that treats them identically will over-hire on the easy side and under-hire on the hard one.

By tenure cohort. Split existing reps into ramping, ramped, and at-risk. Ramping reps contribute partial capacity; at-risk reps (low attainment, disengaged, or in a territory you are about to restructure) should be modeled at reduced capacity or as pending backfills. A plan that credits full capacity to a rep you know is leaving is not a plan.

By geography and vertical. If your ISV serves specific verticals — restaurants, healthcare practices, field services, retail — territory carrying capacity differs sharply by density. A rep covering a metro with thousands of qualified merchants operates differently from one covering a sparse region. Territory design and headcount are the same decision; deciding headcount without redrawing territories usually produces reps with nothing left to sell in month eight.

Adjacent to all of this: the same segmentation logic applies to the support functions around the reps. Sales engineers who handle integration questions, underwriting analysts who clear applications, and implementation staff who board merchants all scale with signed volume. A common ratio structure is one sales engineer per four to six quota-carriers in an integration-heavy motion, and boarding capacity sized to peak monthly application volume rather than average. Hiring twelve reps without adding a single boarding analyst produces a beautiful pipeline and a furious merchant base.

Building the plan, staffing it, and handing it to the people who execute

The model is worthless as a slide. It has to become requisitions, start dates, territories, and a review cadence.

Step one: lock the inputs with owners. Every input needs a named owner who signs off. RevOps owns net capacity per rep and attrition, derived from CRM and HRIS data. Finance owns the target and the fully loaded cost assumption. The sales leader owns ramp duration and segment mix. Written down, dated, and versioned — because when the plan is questioned in month eight, you need to know which assumption moved.

Step two: convert rep-years into start dates. Rep-years of capacity are not hires. Work backward from when production must land. If a rep needs seven months to ramp and 75 days to recruit, a head producing in September of next year opens its requisition roughly now. Stagger the starts into cohorts of three or four rather than hiring twelve at once — a single onboarding class that size will overwhelm enablement and produce a synchronized ramp failure.

Step three: hand recruiting a real brief. Not "hire twelve sales reps." Hand over segment, channel, required background (payments experience versus adjacent SaaS versus vertical expertise), compensation band, target start date per cohort, and the interview loop. A recruiter working from a headcount number rather than a profile will fill seats with people who cannot hold an interchange conversation.

Step four: pre-build territories and quotas. Territory assignment should exist before the rep starts, not be improvised in week three. Same for the ramped quota schedule — month one through month six carry reduced numbers stepping to full. Ambiguity here is the leading cause of early attrition, which feeds straight back into your backfill line.

Step five: instrument the leading indicators. Do not wait for closed volume to know whether the plan is tracking. Watch application submissions, approved merchants, time-to-first-deal per cohort, and pipeline coverage against ramped quota. If cohort two's time-to-first-deal is running 40 percent longer than cohort one's, your enablement broke or your hiring profile drifted — and you have five months to fix it rather than discovering it at year end.

Step six: re-run the model quarterly. Attrition moves. Merchant retention moves. Capacity per rep moves as the product and the pricing move. A capacity model reviewed once a year is a historical document. Quarterly, with the same owners in the room, keeps it a decision tool.

That loop back to the inputs is the part teams skip. A capacity plan that never gets corrected teaches you nothing; one that gets corrected quarterly becomes the most accurate forecasting instrument a payment processing ISV owns, because it ties headcount, retention, boarding capacity, and revenue into a single set of numbers everyone has already agreed to.

Related questions

How does merchant attrition change my rep count?

Directly and severely. Every point of merchant churn increases the net-new volume your sales reps must sign to hit the same target. At a 40M base, moving churn from 5 percent to 10 percent adds 2M to the net-new gap — nearly a full rep-year of capacity before ramp or backfills.

Should I hire reps or partner managers first?

Compare volume per head. If one integration or referral partnership can route several million in annual processing volume against one partner manager's cost, it usually beats direct headcount on efficiency. Most payment processing ISVs run both, splitting the net-new gap by channel and sizing each side separately.

How do I size sales engineers and underwriting alongside reps?

Scale support functions to signed volume, not rep count alone. Integration-heavy motions commonly run one sales engineer per four to six quota-carriers. Board underwriting and implementation staff against peak monthly application volume — average-based sizing creates queues exactly when the new cohort starts producing.

What if I cannot measure productive capacity yet?

Use the logic with estimates and mark them as estimates. Take gross closed volume per tenured rep, haircut it for attainment and first-year merchant churn, and proceed. The model's value is making assumptions visible; refine the inputs as CRM data accumulates rather than waiting for perfect numbers.

When should I buy a planning platform instead of a spreadsheet?

When headcount planning becomes continuous and multi-segment — typically past roughly thirty sellers, several territories, and scenario requests arriving monthly. Below that, a well-built spreadsheet or a free calculator gives the same answer with less overhead and fewer implementation weeks.

FAQ

How do I calculate the exact number of sales reps I need?

Start with current annualized processing volume and your target. Subtract organic growth from your existing merchant base and add back merchant attrition to get true net-new volume required. Divide by net productive capacity per ramped rep — actual closed volume minus churned volume, not paper quota. Add backfills for expected team attrition, then inflate the count to compensate for ramp, since a first-year hire delivers only a partial year of capacity.

What is a realistic productive capacity per rep at a payment processing ISV?

It varies far more by segment and channel than most planning decks admit. Reps working an existing software install base carry higher effective capacity than pure outbound sellers, and enterprise reps sign fewer, larger merchants on much longer cycles. Rather than borrowing a benchmark, derive yours: twelve months of closed annualized volume per tenured rep, minus volume churned from those same accounts.

How much does ramp time change the answer?

Substantially. With a six-to-nine-month ramp, a rep hired at the start of the year delivers roughly half a year of capacity, and one hired mid-year delivers close to nothing. That gap is why the model outputs start dates alongside a count. Stack a 60-to-90-day recruiting cycle on top and you are typically ten to twelve months from opening a requisition to full production.

What attrition rate should I plan for?

Use your own trailing twelve months rather than an industry figure — voluntary plus involuntary departures divided by average headcount. Whatever it is, apply it to your existing team and add those backfills before counting a single incremental head. Twenty reps at 20 percent attrition means four hires that add zero net capacity, and a plan that omits them will miss by exactly that much.

Should RevOps or Finance own this model?

Split it by input. RevOps owns capacity per rep, attrition, and ramp duration because those come from CRM and HRIS data it already stewards. Finance owns the revenue target and the fully loaded cost assumption. The sales leader owns segment mix and territory design. Named owners per input are what make the plan auditable when it misses.

When is hiring the wrong answer entirely?

When merchant retention is the binding constraint. If your portfolio is churning above roughly 15 percent, incremental reps are refilling a leaking bucket, and a dollar spent on retention, onboarding quality, or product stability returns more than a dollar spent on headcount. Also check boarding and underwriting throughput first — reps who sign volume your operations cannot process create backlog, not revenue.

Sources

• Harvard Business Review — sales force sizing and structure research: https://hbr.org/2006/07/match-your-sales-force-structure-to-your-business-life-cycle
• SHRM — human capital benchmarking, turnover and cost-per-hire: https://www.shrm.org/topics-tools/research
• Bureau of Labor Statistics — Job Openings and Labor Turnover Survey (JOLTS): https://www.bls.gov/jlt/
• Bureau of Labor Statistics — Occupational Outlook Handbook, sales occupations: https://www.bls.gov/ooh/sales/
• McKinsey & Company — growth, sales, and marketing insights: https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• Federal Reserve — Payments Study, card and electronic payment volume data: https://www.federalreserve.gov/paymentsystems/fr-payments-study.htm
• Nilson Report — payments industry data and merchant processing statistics: https://nilsonreport.com/
• Electronic Transactions Association — payments industry association and education: https://www.electran.org/
• Bain & Company — customer retention and revenue economics research: https://www.bain.com/insights/

Related on PULSE

• [How Many Sales Reps Do I Need to Hire for My Logistics Company?](/knowledge/tl0058)
• [How Many Salespeople Do I Need to Hire for My Car Dealership?](/knowledge/tl0052)
• [How Many Producers Do I Need to Hire for My Insurance Agency to Grow My Book?](/knowledge/tl0015)
• [How Many Attendants Should I Schedule Each Day at My Car Wash?](/knowledge/tl0067)
• [How Do I Figure Out How Many People to Schedule Each Day and at What Times for My Single Store?](/knowledge/tl0002)