Last updated: August 31, 2026

Ben Argeband, Founder & CEO of Heartbeat.ai — This is written for desk leaders who need faster submittals and cleaner gross margin without burning out recruiters.
What’s on this page:
Who this is for
This hub is for locums and permanent placement agencies that want to run their funnel like an operating system: measurable, coachable, and tied to gross margin, speed to submittal, and ROI.
- Agency owners who need predictable unit economics and fewer surprises.
- Recruiting managers who need throughput without treating \”more activity\” as the only lever.
- Ops leaders who need definitions, exports, and a weekly cadence that actually sticks.
Choose your path
- If you need to justify spend: use the contact data ROI measurement workflow.
- If recruiters are overloaded: use recruiter capacity planning for physician roles.
- If locums speed is the constraint: use the locum tenens sourcing playbook.
- If you want to test reachability quickly: start free search & preview data.
Quick Answer
- Core Answer
- Staffing agency economics in healthcare comes down to managing attempts-to-fill efficiency so speed to submittal improves while gross margin stays protected — tracked through measurable connects, conversations, submits, and fills.
- Key Insight
- Most \”margin problems\” are actually workflow problems: too many low-quality attempts happening before a qualified conversation, which slows submittals and inflates cost per fill.
- Best For
- Locums and permanent placement agencies.
Compliance & Safety
This method is for legitimate recruiting outreach only. Respect candidate privacy, opt-out requests, and local data laws. Heartbeat does not provide medical advice or legal counsel.
Framework: the Agency Math Loop — attempts → connects → convos → submits → fills
If you can’t see the conversion chain, you can’t manage it. This loop connects recruiter activity to outcomes and economics in the simplest terms available:
- Attempts: total outreach touches counted once per action (each dial, each email, each text), using one consistent counting rule across the desk.
- Connects: connected calls, not voicemails.
- Convos: qualified conversations. A conversation counts as qualified when you confirm specialty/role fit, confirm reachability for follow-up, and confirm interest or availability window.
- Submits: submitted or presented to the client.
- Fills: accepted offer, booked assignment, or confirmed start — pick one definition and standardize it desk-wide.
What actually drives agency economics
- Labor efficiency: attempts and recruiter time required to produce one fill.
- Speed to submittal: how quickly a qualified candidate gets in front of the client after intake.
- Conversion quality: connects → convos → submits → fills, broken out by desk and specialty.
- Data hygiene: fewer wrong numbers, fewer bounces, better suppression so you stop paying for dead ends.
- Client control: feedback speed, interview scheduling, and decision clarity — delays here eat recruiter time and lower fill probability.
Where to start
- Standardize definitions, especially speed-to-submittal and \”fill,\” before comparing recruiters or desks.
- Run one weekly export with timestamps and counts. Don’t build a dashboard you won’t maintain.
- Fix the biggest constraint in the loop — connectability, packaging, or client control — for one week at a time.
- Protect recruiter capacity by improving placement-per-attempt, not by demanding more attempts.
Step-by-step method
1) Standardize definitions so reports stop being arguments
These definitions keep dashboards consistent across locums and perm desks.
- ROI = (Incremental gross profit − Incremental cost) / Incremental cost. Use incremental values — what changed because of the tool or process — not total desk revenue.
- Speed-to-submittal = elapsed time from requisition intake (or job opened) to first qualified submittal. Report median and 75th percentile.
- Placement-per-attempt = fills / total attempts for a defined period. This is your efficiency metric and a proxy for recruiter capacity health.
For channel health, use consistent rate definitions with explicit denominators:
- Connect Rate = connected calls / total dials (per 100 dials)
- Answer Rate = human answers / connected calls (per 100 connected calls)
- Deliverability Rate = delivered emails / sent emails (per 100 sent emails)
- Bounce Rate = bounced emails / sent emails (per 100 sent emails)
- Reply Rate = replies / delivered emails (per 100 delivered emails)
- Fill Rate = fills / submits (per 100 submits) for the same period
2) Instrument the workflow with timestamps you already have
You don’t need a data warehouse. You need a weekly export with the same columns every time: requisition opened/intake timestamp, first outreach attempt timestamp, first connected call timestamp, first qualified conversation timestamp, first submittal timestamp, fill/start timestamp, and counts for dials, connected calls, emails sent/delivered/bounced, and replies.
3) Diagnose the constraint
Speed to submittal is usually slow for one of two reasons: a connectability problem, where you can’t reach the right clinicians fast enough, or a process problem, where you reach them but qualification, packaging, or client feedback slows the submit.
- Attempts high, connects low → fix phone/email quality, timing, and suppression.
- Connects fine, convos low → fix targeting and your opening lines.
- Convos fine, submits low → fix job clarity, rate/comp alignment, and submittal packaging.
- Submits fine, fills low → fix client control, interview scheduling, and close plan.
A quick way to think about the math
Use your own variables rather than industry benchmarks. If D is total dials and C is connected calls, Connect Rate = C/D. If Q is qualified conversations and S is submits, then S/Q is your qualified-convo-to-submit conversion. Improving either number reduces the number of dials needed per qualified conversation, which typically improves speed to submittal because you reach enough qualified yeses earlier in the week.
4) Protect recruiter capacity by improving placement-per-attempt
Recruiter capacity isn’t how many calls someone can make — it’s how many useful attempts they can make before quality drops. Pushing raw activity can inflate attempts while lowering connects and convos, which slows submittals and raises cost per fill.
- Suppression: stop re-hitting records that repeatedly fail — bad numbers, hard bounces, opt-outs.
- Prioritization: call the most reachable candidates first during your best windows.
- Packaging: reduce back-and-forth so a qualified yes becomes a same-day submittal.
- Segmentation: keep locums availability conversations separate from perm motivation conversations.
5) Run a weekly cadence that produces decisions, not dashboards
Run one weekly export by recruiter and by desk (locums vs. perm), calculate medians, and choose one constraint to fix over the next five business days.
- Export timestamps and counts for last week’s reqs.
- Calculate speed-to-submittal (median, 75th percentile) and placement-per-attempt by desk.
- Check channel health — Connect Rate, Deliverability Rate, Bounce Rate, Reply Rate — to see if the top of funnel is degrading.
- Pick one fix (suppression, prioritization, packaging, or client SLA) and run it for one week.
- Review what moved and keep only what improved outcomes.
Micro-Asset: ROI Calculator
Use case: decide whether a sourcing, data, or process change is worth it for a staffing agency desk without relying on industry averages.
Calculator card (copy into a spreadsheet)
| Input | What you enter | Notes |
|---|---|---|
| Incremental fills | # | Fills attributable to the change (be conservative) |
| Gross profit per fill | $ | Your actual gross profit, not revenue. Avoid benchmark assumptions. |
| Incremental gross profit | = Incremental fills × Gross profit per fill | Output |
| Incremental cost | $ | Tooling + data + labor time cost (loaded) |
| ROI | = (Incremental gross profit − Incremental cost) / Incremental cost | Output (ratio) |
Speed-to-Submittal Value worksheet
This leading-indicator worksheet avoids invented dollars. It helps you show you’re getting faster before fills show up in the numbers.
| Field | How to compute | Why it matters |
|---|---|---|
| Median speed-to-submittal | Median(time from req open/intake → first qualified submittal) | Direct competitiveness signal for clients |
| SLA hit rate | # reqs with first qualified submittal within your internal SLA / total reqs (per 100 reqs) | Shows consistency, not just best-case wins |
| Client response time | Median(time from first submittal → first client action) | Separates your speed from client-side delay |
Micro-Asset: Diagnostic Table
Use case: identify which lever to pull first — connectability, targeting, packaging, or client control — based on what you observe in a given week.
| Symptom you see | Likely cause | What to change this week | What to measure next week |
|---|---|---|---|
| High dials, low connected calls | Phone quality / wrong numbers / poor call windows | Refresh phone sources; suppress repeated failures; prioritize the most reachable numbers first | Connect Rate = connected calls / total dials (per 100 dials) |
| Connected calls, but few qualified convos | Targeting mismatch or weak opener | Tighten specialty + license + availability filters; rewrite opener to confirm fit in 20 seconds | Qualified convos per 100 connected calls; Answer Rate = human answers / connected calls |
| Qualified convos, slow first submittal | Packaging/credentialing friction | Standardize submittal packet; pre-collect must-have fields; enforce a same-day submit rule | Speed-to-submittal (median; 75th percentile) |
| Submittals, but low fills | Client control / close plan gaps | Set interview scheduling SLA; align on must-haves; run a close checklist | Fill Rate = fills / submits (per 100 submits) |
| Email volume up, replies flat | Deliverability or message-market mismatch | Clean bounces; reduce spam signals; segment by role type; tighten first line | Deliverability Rate = delivered / sent; Reply Rate = replies / delivered |
Micro-Asset: Weighted Checklist
Use case: choose what to fix first when ops time is limited. Score each item 0–2 (0 = not in place, 1 = partial, 2 = solid), multiply by weight, and treat the highest weighted total as your first project.
| Area | Item | Weight | Score (0–2) | Weighted |
|---|---|---|---|---|
| Measurement | Weekly export includes req open/intake → first submittal timestamps | 5 | ||
| Connectability | Phone outcomes tracked; repeated failures suppressed | 5 | ||
| Connectability | Email hygiene: bounces removed; deliverability monitored | 4 | ||
| Workflow | Same-day submittal rule after qualified yes | 5 | ||
| Workflow | Standard submittal packet (must-have fields) by specialty | 4 | ||
| Capacity | Protected calling blocks during prime windows (admin moved out) | 3 | ||
| Client control | Client feedback SLA and escalation path defined | 3 |
Interpretation: if Measurement and Connectability score low, fix those before debating sourcing channels. You can’t manage what you can’t see.
Common pitfalls
- Managing activity instead of throughput. Manage only dials and emails, and you can increase attempts while convos and submits stay flat.
- Inconsistent definitions across desks. One team calling \”fill\” an offer accepted while another means start date turns placement-per-attempt into noise.
- No suppression loop. Re-hitting bad numbers and bouncing emails inflates attempts and wastes recruiter capacity.
- Attribution inflation. Credit every fill to a single tool and ROI becomes a story instead of a decision metric.
- Ad hoc packaging. Slow submittals are often just a missing packet, missing fields, or unclear client must-haves.
How to improve results
Use a one-week improvement cycle. Change one thing at a time — change five and you won’t know what worked.
Weekly measurement instructions (minimum viable)
- Export last week’s reqs and candidate activity: dials, connected calls, emails sent/delivered/bounced, replies, first qualified convo date, first submittal date, fill/start date.
- Calculate by desk and recruiter: Connect Rate, Deliverability Rate, Bounce Rate, Reply Rate, speed-to-submittal (median and 75th percentile), and placement-per-attempt.
- Pick one constraint from the Agency Math Loop and run a one-week fix — suppression, prioritization, packaging, or client SLA.
- Keep only the change that improves outcomes; revert the rest.
High-leverage improvements that usually show up fast
- Prioritize reachability. Put your best call windows against the most reachable candidates first.
- Reduce dead ends. Fewer wrong numbers and fewer bounces improves placement-per-attempt and protects recruiter capacity.
- Standardize submittals. A consistent packet reduces back-and-forth and improves speed to submittal.
- Segment by intent. Locums availability and perm motivations differ; qualify and message accordingly.
Legal and ethical use
Use legitimate recruiting outreach only. Respect opt-outs, keep suppression lists current, and follow applicable privacy and communications laws where you operate. Keep access controls tight and avoid sensitive inferences about clinicians.
If you’re unsure about a specific outreach practice, get counsel. This page is operational guidance, not legal advice.
Evidence and trust notes
This hub avoids unsupported industry \”averages\” on purpose. Agencies win by measuring their own funnel and improving constraints. For how Heartbeat.ai approaches data quality, verification, and trust, see: Trust methodology and data quality approach.
Deep dives referenced in this hub:
- How to measure contact data ROI
- Recruiter capacity planning for physician roles
- Locum tenens sourcing playbook
FAQs
What is the simplest way to manage staffing agency economics in healthcare?
Run the Agency Math Loop weekly: attempts → connects → convos → submits → fills. Track speed to submittal and placement-per-attempt, then fix the biggest constraint first.
How do I define ROI for a recruiting workflow change?
ROI = (Incremental gross profit − Incremental cost) / Incremental cost. Use incremental fills and incremental costs attributable to the change, and keep attribution conservative.
What should I track to protect gross margin without relying on industry benchmarks?
Track your own placement-per-attempt and speed to submittal by desk and specialty. When placement-per-attempt improves, recruiter time per fill typically drops, which supports gross margin.
How do I measure speed to submittal in a way that’s fair across recruiters?
Define it as elapsed time from req intake/open to first qualified submittal, then report median and 75th percentile by desk. Use the same definition everywhere.
Where should a locums agency start if they need faster submittals?
Start with connectability and packaging: improve Connect Rate and enforce a same-day submittal packet once you have a qualified yes. Then refine targeting.
Next steps
- Implement the weekly export: follow the ROI measurement workflow and standardize your definitions.
- Fix capacity constraints: use capacity planning for physician roles to rebalance pods and protect calling blocks.
- Move faster on locums: use the locums sourcing playbook to tighten targeting and packaging.
- Test reachability now: start free search & preview data.
About the Author
Ben Argeband is the Founder and CEO of Swordfish.ai and Heartbeat.ai. With deep expertise in data and SaaS, he has built two successful platforms trusted by over 50,000 sales and recruitment professionals. Ben’s mission is to help teams find direct contact information for hard-to-reach professionals and decision-makers, providing the shortest route to their next win. Connect with Ben on LinkedIn.