Setting Comp and Quota for Your First Provider-Facing Sales Reps

Setting Comp and Quota for Your First Provider-Facing Sales Reps
Most health-tech comp plans I review were not designed. They were inherited, usually from whatever SaaS company the founder or the first sales leader came from, and then adjusted by feel. A 50/50 base-variable split, a quota set at 4 to 5x on-target earnings, quarterly targets from month one. Those defaults come from horizontal SaaS, where sales cycles run 30 to 90 days and a rep controls most of the variables between first call and signature.
Provider-facing selling breaks most of those assumptions, and comp plans built on them tend to fail in a specific and expensive way: the plan punishes reps for the structure of the market rather than for their own performance, your best rep leaves at month ten, and you conclude that sales talent was the problem.
I should be clear about my evidence base before offering numbers. I am drawing on roughly a dozen provider-facing placements I have been involved with over the past two years, plus the comp plans that candidates share during searches, which is a biased sample in ways worth remembering: I mostly see plans at companies that are hiring, and companies are often hiring because a previous plan did not work. Treat what follows as informed hypotheses to test against your own market, not as settled benchmarks.
Why the SaaS template misfires
Three structural differences matter for comp design.
First, cycle length. Selling into health systems and provider groups runs 6 to 18 months when an EHR integration, a security review, or a committee decision sits in the path. A rep on a quarterly quota with a nine-month cycle spends three quarters being told they are failing before the pipeline they built can possibly close. The plan is measuring the market's clock, not the rep's work.
Second, attribution. Provider deals close because of a champion physician, a pilot result, a CMIO's risk tolerance, and sometimes a rep's eleven months of stakeholder management. Deciding how much of that was the rep is genuinely hard, and comp plans that pretend otherwise create resentment in both directions.
Third, the pilot problem. A large share of first deals are pilots at modest contract values, with expansion economics arriving in year two. If variable comp keys entirely on first-year contract value, you are asking the rep to be indifferent to the outcome that matters most to the company.
What the placements actually show
With the sample-size caveat repeated, here is what I have seen work, or at least fail less often.
Base salaries for experienced provider-facing reps in my placements ran $115K to $155K, with OTE between $185K and $240K. That is a higher base-to-OTE ratio than horizontal SaaS, roughly 60/40 rather than 50/50, and I think the logic holds: when cycle length and committee dynamics sit outside the rep's control, more of their income has to sit outside those dynamics too, or you are simply transferring market risk onto the employee and paying for it in turnover.
For contract reps engaged through a 1099 structure, hourly rates in my searches ran $90 to $130 for provider-facing software work, sometimes with a modest completion bonus tied to defined activity milestones rather than contract signatures. The 1099 versus W2 tradeoffs deserve their own analysis, but on comp specifically, hourly structures sidestep the attribution problem entirely, which is one reason early-stage companies find them easier to reason about. If you want to pressure-test a specific rate, the salary calculator gives you a benchmark by role and region.
| Element | Common SaaS default | What I see working in provider-facing |
|---|---|---|
| Base / variable split | 50 / 50 | 60 / 40 |
| OTE range (experienced rep) | Varies widely | $185K to $240K |
| Quota basis, year one | ARR closed | Pipeline milestones + closed revenue mix |
| Quota period | Quarterly | Semi-annual, first year |
| Pilot deals | Often uncredited | Credited at defined milestone values |
| Contract rep hourly | Rare | $90 to $130 |
Quota when there is no history
The honest answer for a first sales hire is that a year-one revenue quota is a guess wearing a spreadsheet. You have no baseline conversion data, and your one or two founder-led deals were closed with advantages a rep will not have. I want to be careful about overpromising any alternative, but two approaches distribute the guesswork more fairly.
The first is a milestone quota for the first two or three quarters: qualified opportunities created, pilots signed, committee presentations reached. These are observable, largely within the rep's control, and they generate the conversion data you need to set a defensible revenue quota in quarter four. The objection, that activity quotas reward motion instead of results, is fair. The mitigation is defining milestones as verified pipeline stages rather than raw activity counts. A committee presentation either happened or it did not.
The second is a wide-band revenue quota with a low threshold and an uncapped upside, semi-annual rather than quarterly. You are acknowledging variance instead of pretending precision. Companies that pick this route should expect to reset the bands after two quarters, in either direction, and should say so up front.
What I would avoid is the borrowed 5x-OTE quota. In my sample, the reps who hit those numbers in year one at an early-stage health-tech company were the exception, three or four out of the dozen, and each had unusual conditions: an existing book of relationships in the exact buyer persona, or a pilot pipeline the founders had already built. Setting a quota most competent reps will miss is a plan for paying below OTE while advertising above it, and experienced candidates read it that way in the first interview.
Sequencing the decision
Comp design interacts with the staffing model, and it may be worth settling the model first. If the honest state of the company is that you are still discovering the sales motion, a contract rep at an hourly rate converts your comp problem into a scoping problem, which is easier. Once the motion is repeatable, the W2 plan above has something to key on. I laid out that sequencing argument in how to staff a provider-facing sales role, and the team-scale version in building a healthcare software sales team. For companies right at the first-hire moment, the first commercial hire piece covers the ground before this one.
Designing the role before you design the plan?
We help health-tech companies scope provider-facing sales roles and place experienced reps, contract or full-time. Share where the company is and we'll suggest a structure, including comp ranges from comparable placements.
Scope the role with usFrequently Asked Questions
Should the first rep's variable comp include expansion revenue?
I lean yes, with a time bound. Crediting expansions that close within 12 to 18 months of the initial deal keeps the rep invested in pilot quality rather than pilot count. The tradeoff is a longer comp tail to administer, and finance teams reasonably dislike that. Cap the tail rather than dropping the credit.
What should a pilot count for against quota?
A defined milestone value, agreed in advance, rather than zero or face value. In my placements the range was 25 to 50% of a standard deal credit, depending on how reliably that company's pilots converted. If you have no conversion history yet, pick a number and commit to revisiting it with data at the six-month mark.
Are these benchmarks different for selling to private practices versus health systems?
Meaningfully, and my sample skews toward health systems, so discount accordingly. Practice-level sales cycles are shorter, deal values lower, and the SaaS-style quarterly structure works better there. The 60/40 split and milestone quotas earn their keep specifically where committees and integrations set the pace.
When should we hire a sales leader instead of another rep?
In my sample, companies regretted hiring the VP before two reps had validated the motion more often than they regretted waiting. A leader hired to run an unproven motion tends to redesign it toward whatever worked at their last company, which is the same inherited-template problem this article started with.