Alternatives to hiring an SDR, priced over a full year
Compare twelve months of modeled costs and held, accepted meetings. Salary, employer costs, infrastructure, ramp and each provider’s assumed productivity affect the result. Inputs are scenarios, not a historical meeting forecast or a prediction that either option will deliver them.
Run your own twelve months
Set separate meeting assumptions and ramps for the in-house SDR and agency. Email volume independently selects the in-house infrastructure tier; meetings do not determine sends. Enter a complete agency monthly fee including its infrastructure and required extras. This is a one-SDR, fixed-fee comparison; use the pricing-model calculator to model per-unit or revenue-share fees.
In-house versus outsourced, across the first year
Illustrative defaults: five held, accepted meetings per fully productive month on each path; $80,000 OTE, 25% employer costs, a three-month in-house ramp, a $5,000 complete monthly agency fee and one-month agency ramp. Monthly emails are independently set to 25,000. Other monthly in-house costs and one-time setup/recruiting costs default to zero and must be replaced when applicable.
No lower in-house unit cost within year one
At these assumptions, the in-house path does not achieve a strictly lower cumulative cost per held, accepted meeting in the modeled year. This is a cost scenario, not a quality or hiring recommendation.
Lower in-house unit cost appears in months 7–12
The model finds a strictly lower cumulative unit cost in the second half. Actual ramp, retention, scope and productivity can change the result.
Lower in-house unit cost appears in months 1–6
The model finds a strictly lower cumulative unit cost in the first half of year one. Confirm costs, productivity, retention and scope before using this scenario in a hiring decision.
Cost per meeting is not comparable
At least one path has zero modeled meetings. Its cost per meeting is uncalculable. This does not establish that the other path is better.
Equal modeled unit costs
Both paths have the same modeled cumulative unit cost throughout the year at these inputs. Cost alone does not distinguish them.
The scenario descriptions are all readable without JavaScript. With JavaScript enabled, the matching result is shown. A first lower-cost month does not establish that the option remains cheaper or delivers better outcomes.
The arithmetic. Monthly emails are your independent 25,000 input; the published infrastructure tier is $2,023. In-house monthly cost = OTE × (1 + employer percentage) / 12 + infrastructure + other monthly costs = $10,356.33. Each path pays its entered recurring costs for twelve months plus its one-time cost in month one. Expected output in month m = that path’s full-productivity meetings × min(1, m / (ramp + 1)). Cumulative unit cost divides costs to date by expected meetings to date. Zero meetings makes the unit cost uncalculable. Fractional meetings are scenario values, not observed counts.
Model limits. Ramp is a chosen linear scenario, not measured productivity: month m uses min(1, m / (ramp + 1)). Attrition, vacancies, holidays, management capacity, prospect availability and changing quotes are not forecast. Fractional meetings are expected scenario values. A zero meeting assumption makes that path’s cost per meeting uncalculable; it does not make the work free.
How much volume does one person have to support?
Sending workload and sales outcomes are separate planning questions. Choose infrastructure from your operating requirements, then model meetings independently. The table lists published infrastructure tiers only; it does not convert meetings into sends or promise inbox placement.
| Email volume per month | Published monthly infrastructure | Outcome assumption |
|---|---|---|
| 25,000 | $2,023 | Enter held, accepted meetings independently |
| 50,000 | $2,841 | Enter held, accepted meetings independently |
| 75,000 | $4,315 | Enter held, accepted meetings independently |
| 100,000 | $5,531 | Enter held, accepted meetings independently |
| 250,000 | $12,036 | Enter held, accepted meetings independently |
| 500,000 | $22,493 | Enter held, accepted meetings independently |
| 1,000,000 | $44,090 | Enter held, accepted meetings independently |
A higher infrastructure tier changes modeled costs. It does not establish that one employee can manage that volume or that more sends will produce more accepted meetings. Compare staffing and handoff requirements before sizing the program.
If you already have suitable infrastructure, use your actual costs when comparing a hire and an agency. The published tiers are a reference scenario, not a requirement to purchase a specific stack.
What operating that volume actually involves
Operating responsibilities include domain and mailbox configuration, authentication, contact data, copy review, reply handling, qualification and reporting. Identify the owner and workload of each task. Sending volume alone does not establish staffing capacity.
List maintenance and reply handling continue after launch. Treat automatic replies, referrals, buying interest, bookings and held meetings as separate categories. The reply research describes campaign responses; it does not establish how many meetings a new employee or provider will produce.
The four alternatives at a glance
These options buy different scopes: an employee’s capacity, managed execution, a contract-defined appointment or an infrastructure-and-revenue-share arrangement. Confirm the handoff and records you receive rather than assuming they deliver the same outcome.
| Option | What you commit to | Who carries the ramp | What you keep | Right when |
|---|---|---|---|---|
| Hire one SDR | Compensation, employer costs, tools, management and hiring costs | Model the actual ramp and vacancy risk | Confirm company-owned systems, data rights and continuity | You can hire, manage and support the function. |
| Agency on retainer | Complete recurring fee, setup and minimum term | Confirm launch readiness and required fees during ramp | Confirm records, data rights and access on exit | Managed scope and capacity fit your requirements. |
| Pay per appointment | Per-unit fees plus floors, setup and other charges | Qualification and billable-unit definitions determine exposure | Confirm records and ownership in writing | You can define and verify the purchased unit. |
| Infrastructure plus revenue share | Published infrastructure plus share of attributable revenue | Infrastructure remains; variable pay depends on revenue terms | Confirm access, data and attribution obligations | Margins, sales timing and revenue reporting support the agreement. |
When hiring in-house is the right call
ReplyLead sells an outsourced service and publishes this comparison. In-house ownership, product knowledge, integration and coverage may matter beyond modeled unit cost. The calculator does not score those benefits or independently validate provider performance.
- The workload fits the role. Assess research, writing, response handling, qualification and reporting separately. A meeting target does not establish email volume or prove that one person has enough capacity.
- You have management capacity. Agree who will coach, review work and cover absences. The calculator does not validate these responsibilities or predict their effect on ramp.
- Outbound is a permanent function, not a test. If you are still proving the channel works, you are paying to learn on your own payroll - and the person carries the blame for a market that may simply be too small.
- You want the data and the relationships in-house. A legitimate reason to pay more per meeting. Just make that trade deliberately rather than discovering it in month nine.
And when it is not
Use cost alongside strategic fit, management capacity and the quality of the underlying assumptions. A modeled crossover does not establish that the target market can supply the meetings or that the employee will stay. If an outcome assumption lacks support, collect evidence before committing to either path.
Model inputs and limitations
Independent cost and outcome inputs
No historical SQL count, sends-to-meetings constant or reply-to-meeting ratio is used. Each side’s meeting assumption is entered separately. Both must use the same held, accepted-meeting definition and comparison period.
What the separate reply research measures
The separate first-party reply study covers 115 campaigns in seven programs, including internal work. Its 81-campaign subset with at least 500 contacted leads has a median reply rate of 2.12% and quartiles of 1.38% and 2.97%. Automatic replies are included. Those reply rates do not imply meetings or a staffing forecast. See the research and method.
Limitations, stated plainly
Each ramp, meeting target and cost is a scenario input. Linear ramp and constant post-ramp output simplify reality; they are not measured outcomes. Zero or missing outcome evidence does not justify a confident cost-per-meeting conclusion. Actual qualification, attrition, revenue and sales-cycle timing require separate records.
What is not first-party
The $80,000 OTE and 25% employer-cost defaults are illustrative hiring assumptions, not a verified salary-survey finding. Agency fees, other costs, setup and meetings are buyer inputs. Published infrastructure tiers are identified as ReplyLead’s offer; no market-average agency fee is claimed.
Our standards are on methodology and editorial standards.
Related
If the crossover never arrived on your numbers, that is worth a conversation before you open a role. We will tell you if we think the hire is the better call.
Apply to work with us