\nCompliance & Safety<\/strong><\/p>\nThis method is for legitimate recruiting outreach only. Always respect candidate privacy, opt-out requests, and local data laws. Heartbeat does not provide medical advice or legal counsel.<\/p>\n<\/blockquote>\n
<\/span>Framework: The \u201cAgency Math\u201d Loop: attempts \u2192 connects \u2192 convos \u2192 submits \u2192 fills<\/span><\/h2>\nIf you can\u2019t see the conversion chain, you can\u2019t manage it. This loop is the simplest way to connect recruiter activity to outcomes and economics:<\/p>\n
\n- Attempts<\/strong>: total outreach touches counted once per action (e.g., each dial, each email sent, each text sent), using one consistent counting rule across the desk.<\/li>\n
- Connects<\/strong>: connected calls (not voicemails).<\/li>\n
- Convos<\/strong>: qualified conversations. A conversation counts as qualified when: (1) you confirm specialty\/role fit, (2) you confirm reachability for follow-up, and (3) you confirm interest or availability window.<\/li>\n
- Submits<\/strong>: submitted\/presented to the client.<\/li>\n
- Fills<\/strong>: accepted offer \/ booked assignment \/ start confirmed (pick one and standardize it).<\/li>\n<\/ul>\n
<\/span>What actually drives agency economics (in plain terms)<\/span><\/h3>\n\n- Labor efficiency<\/strong>: how many attempts and how much recruiter time it takes to produce one fill.<\/li>\n
- Speed to submittal<\/strong>: how quickly you can get a qualified candidate in front of the client after intake.<\/li>\n
- Conversion quality<\/strong>: connects \u2192 convos \u2192 submits \u2192 fills, by desk and specialty.<\/li>\n
- Data hygiene<\/strong>: fewer wrong numbers, fewer bounces, and better suppression so you stop paying for dead ends.<\/li>\n
- Client control<\/strong>: feedback speed, interview scheduling, and decision clarity (because delays consume recruiter time and reduce fill probability).<\/li>\n<\/ul>\n
<\/span>Key takeaways (what to do first)<\/span><\/h3>\n\n- Standardize definitions (especially speed-to-submittal and \u201cfill\u201d) before you compare recruiters or desks.<\/li>\n
- Run one weekly export with timestamps and counts; don\u2019t build a dashboard you can\u2019t maintain.<\/li>\n
- Fix the biggest constraint in the loop (connectability vs packaging vs client control) for one week at a time.<\/li>\n
- Protect recruiter capacity by improving placement-per-attempt, not by demanding more attempts.<\/li>\n<\/ul>\n
<\/span>Step-by-step method<\/span><\/h2>\n<\/span>1) Standardize definitions (so your reports aren\u2019t arguments)<\/span><\/h3>\nThese definitions keep your dashboards consistent across locums and perm.<\/p>\n
\n- ROI definition<\/strong>: ROI = (Incremental gross profit \u2212 Incremental cost) \/ Incremental cost<\/strong>. Use incremental values (what changed because of the tool\/process), not total desk revenue.<\/li>\n
- Speed-to-submittal definition<\/strong>: elapsed time from requisition intake (or job opened) to first qualified submittal<\/strong>. Report median and 75th percentile.<\/li>\n
- Placement-per-attempt definition<\/strong>: fills \/ total attempts<\/strong> for a defined period (week\/month). This is your efficiency metric and a proxy for recruiter capacity health.<\/li>\n<\/ul>\n
If you track channel health, use canonical rate definitions with explicit denominators:<\/p>\n
\n- Connect Rate<\/strong> = connected calls \/ total dials (per 100 dials).<\/li>\n
- Answer Rate<\/strong> = human answers \/ connected calls (per 100 connected calls).<\/li>\n
- Deliverability Rate<\/strong> = delivered emails \/ sent emails (per 100 sent emails).<\/li>\n
- Bounce Rate<\/strong> = bounced emails \/ sent emails (per 100 sent emails).<\/li>\n
- Reply Rate<\/strong> = replies \/ delivered emails (per 100 delivered emails).<\/li>\n
- Fill Rate<\/strong> = fills \/ submits (per 100 submits) for the same period.<\/li>\n<\/ul>\n
<\/span>2) Instrument the workflow with timestamps you already have<\/span><\/h3>\nYou don\u2019t need a data warehouse. You need a weekly export with the same columns every time:<\/p>\n
\n- Requisition opened (or intake) timestamp<\/li>\n
- First outreach attempt timestamp<\/li>\n
- First connected call timestamp<\/li>\n
- First qualified conversation timestamp<\/li>\n
- First submittal timestamp<\/li>\n
- Fill\/start timestamp (based on your standardized definition)<\/li>\n
- Counts: dials, connected calls, emails sent\/delivered\/bounced, replies<\/li>\n<\/ul>\n
<\/span>3) Diagnose the constraint (connectability vs process)<\/span><\/h3>\nSpeed to submittal is slow for two reasons:<\/p>\n
\n- Connectability problem<\/strong>: you can\u2019t reach the right clinicians fast enough.<\/li>\n
- Process problem<\/strong>: you reach them, but qualification, packaging, or client feedback slows the submit.<\/li>\n<\/ul>\n
Use the loop to pinpoint the leak:<\/p>\n
\n- Attempts high, connects low<\/strong> \u2192 fix phone\/email quality, timing, and suppression.<\/li>\n
- Connects fine, convos low<\/strong> \u2192 fix targeting and your first 30 seconds.<\/li>\n
- Convos fine, submits low<\/strong> \u2192 fix job clarity, rate\/comp alignment, and submittal packaging.<\/li>\n
- Submits fine, fills low<\/strong> \u2192 fix client control, interview scheduling, and close plan.<\/li>\n<\/ul>\n
<\/span>Time math example (no benchmarks, just your funnel)<\/span><\/h3>\nUse variables so you can plug in your own numbers. If D<\/em> is total dials and C<\/em> is connected calls, then Connect Rate = C<\/em>\/D<\/em>. If Q<\/em> is qualified conversations and S<\/em> is submits, then qualified-convo-to-submit conversion is S<\/em>\/Q<\/em>. Improving Connect Rate or improving qualified conversations per connected call reduces dials per qualified conversation, which usually improves speed to submittal because you reach \u201cenough qualified yeses\u201d earlier in the week.<\/p>\n<\/span>4) Protect recruiter capacity by improving placement-per-attempt<\/span><\/h3>\nRecruiter capacity is not \u201chow many calls someone can make.\u201d It\u2019s how many useful<\/em> attempts they can make before quality drops. The trade-off is\u2026 pushing raw activity can inflate attempts while lowering connects and convos, which slows submittals and increases cost per fill.<\/p>\nOperational levers that usually improve placement-per-attempt:<\/p>\n
\n- Suppression<\/strong>: stop re-hitting records that repeatedly fail (bad numbers, hard bounces, explicit opt-outs).<\/li>\n
- Prioritization<\/strong>: call the most reachable candidates first during your best call windows.<\/li>\n
- Packaging<\/strong>: reduce back-and-forth so a qualified yes becomes a same-day submittal.<\/li>\n
- Segmentation<\/strong>: separate locums availability conversations from perm motivation conversations.<\/li>\n<\/ul>\n
<\/span>5) Run a weekly cadence that produces decisions (not dashboards)<\/span><\/h3>\nRun one weekly export by recruiter and by desk (locums vs perm), calculate medians, and choose one constraint to fix for the next 5 business days.<\/p>\n
Measure this by\u2026 running the same weekly export every Friday and comparing medians week-over-week by desk (locums vs perm) and by recruiter.<\/p>\n
\n
![\"54210\"](\"http:\/\/hc.heartbeat.ai\/wp-content\/webp-express\/webp-images\/uploads\/2026\/02\/agency-economics-43d886de.png.webp\")
<\/p>\n