The ROI of fax triage software for a mid-to-large gastroenterology practice comes from three lines: staff hours recovered on classifying and filing documents, procedure revenue recovered from referrals that would have leaked during slow intake, and avoided cost from misfiled or delayed results. The first line is the one a CFO will check, and it's usually enough on its own. The second is where GI economics diverge from other specialties, because a converted referral is a procedure rather than an office visit. Payback for most groups lands inside twelve months, and often inside six.
The labor formula, and the three inputs you already have
The baseline is one line of arithmetic: documents per day × minutes per document × loaded hourly cost, annualized, netted against subscription plus implementation.
Documents per day. Documents, not pages. A 30-page hospital packet containing a discharge summary, a pathology report, and a records release is three units of decision-making, not thirty. Pull thirty days from your fax server and count per site.
Minutes per document. Time it for a week rather than borrowing a vendor's average. Simple items — a single-page lab result, a records-request acknowledgment — run three to five minutes end to end. A colonoscopy referral packet with a demographics sheet, insurance card, and prior procedure report runs ten to fifteen.
Loaded hourly cost. Not the wage. The Bureau of Labor Statistics put the median annual wage for secretaries and administrative assistants at $47,460 as of May 2024. Add 25% to 40% for payroll taxes, benefits, PTO coverage, and the recruiting and training cost of turnover, and a $22-an-hour intake coordinator actually costs somewhere in the $28 to $31 range.
That last input keeps moving against you. MGMA's 2025 Management and Staff Compensation Data Report documented support-staff pay rising faster than in most of the past decade, and nearly two-thirds of medical groups budgeted another 1% to 3% base increase for 2026, with 23% budgeting 4% to 6%. The manual baseline is a line item that grows every year you defer the decision.
A worked example, in ranges rather than false precision
Here's the shape for a GI group with six locations and roughly 20 gastroenterologists and advanced practice providers. Every figure is a range on purpose — precision you didn't measure is precision you can't defend in front of a board.
- Inbound fax documents: 200 to 300 per day across all sites
- Blended handling time: 5 to 8 minutes per document
- Daily staff hours consumed: roughly 17 to 40
- Loaded hourly cost: $27 to $34
- Daily labor cost: roughly $450 to $1,360
- Annualized over 250 business days: roughly $110,000 to $340,000
Now the part vendor ROI calculators skip. Automation does not recover all of that. A realistic touch reduction on a mature deployment is 50% to 70%, which puts gross annual labor recovery at roughly $55,000 to $240,000. Wide band, and it's the honest one. You narrow it by measuring your own three inputs.
GI sits at the favorable end of this range for a structural reason: a large share of the document stream is recurring and standardized — pathology from your regular lab, referrals from the same handful of primary care offices, payer correspondence with stable layouts. Recurring and standardized is exactly what classification handles well. A practice whose mix is mostly one-off handwritten correspondence performs worse.
The referral-conversion line, and why it's bigger in GI
This is the line operators consistently leave out, and in gastroenterology it can rival the labor savings.
Roughly half of the 100 million-plus specialty referrals made in the US each year are never completed. A faxed referral that sits three days before anyone reads it is a referral that may get scheduled somewhere else — and the window is narrower than most practices assume. Speed to first contact is the variable that moves conversion most.
What makes GI different is the value of the converted referral. In most specialties, a recovered referral is an office visit. In gastroenterology it's frequently a screening or diagnostic colonoscopy — a procedure with facility and anesthesia components attached. Recovering even two to four additional scheduled procedures per site per week compounds quickly against your own contribution margin.
That matters more now than it did a decade ago. Reimbursement for colonoscopy with biopsy has fallen roughly 40% over fifteen years, so volume conversion carries more of the practice's economics than it used to. Meanwhile the screening-eligible population grew by roughly 19 million people when guidelines moved the starting age to 45. More referrals arriving, thinner margin per procedure, same intake staff.
Run this line with your own numbers rather than an industry average: incremental scheduled procedures per week × contribution margin per procedure × 50 weeks. Present it as a sensitivity range, not a point estimate, and a CFO will engage with it rather than discount it.
What does implementation actually cost?
Three parts, and only one appears on the quote.
Subscription. Priced per-document, per-page, per-site, or per-seat. Per-page looks cheapest until a month of long hospital packets lands. Ask for a modeled annual cost at your measured volume, and confirm in writing whether exception documents — the ones the system routes to a human — bill at the same rate as fully automated ones. Some contracts charge full price for the work you're still doing.
Implementation and integration. A one-time fee plus the EHR connection. This is where timelines slip. A group on one EHR instance across six sites is a different project than a group that acquired two practices still running separate systems. Ask specifically whether the platform writes into the chart through an interface or through screen automation, because the second breaks on upgrades.
Your own team's time. The line that gets missed. Budget four to twelve weeks of parallel running where staff review automated output alongside the old workflow. That's real payroll spend, and skipping it is how practices discover misfiled documents six months later.
Time to value follows a consistent pattern: shadow mode for the first few weeks, accuracy tuning through weeks four to eight, steady state somewhere between weeks eight and sixteen. Add integration time before automation time if you're among the nearly one in four practices that still don't have digital fax fully integrated with the EHR.
How to read a vendor's ROI claim
Vendors will bring you a number. Three questions turn it into something you can use.
What touch-reduction rate is it assuming, and on what document mix? A 90% automation claim built on a mix of clean, single-page lab results tells you nothing about a queue that's 30% multi-page referral packets. Ask for the assumption, not just the output.
Does it count exception handling? A model that assumes staff time goes to zero is describing a product that doesn't exist. Plan on 10% to 25% of documents still needing human eyes.
Does it assume you act on the savings? Recovered labor is notional until something changes — staff redeployed to authorization or scheduling, attrition not backfilled, an acquisition's volume absorbed without new hires. Groups that automate and change nothing about staffing end up with soft benefits and a hard invoice.
Honey Health belongs in that evaluation on the same terms as anyone else you're considering. Ask for the touch-reduction assumption, the exception-handling model, and a cost projection against your measured volume — then hand every candidate 100 documents from last month's real queue, including your worst scans and longest packets, and score classification and patient matching separately.
What the ROI model shouldn't claim
Name these before a skeptical partner does.
- Bad source documents. A third-generation photocopy with handwritten details still needs a person. Extraction confidence tracks source quality, and no model fixes that.
- Downstream capacity. If your next available colonoscopy slot is eight weeks out, faster intake moves the bottleneck rather than removing it. The referral-conversion line assumes you can actually schedule the patient.
- Referring-office behavior. Incomplete referral packets keep arriving incomplete. Automation surfaces the gap sooner; someone still has to call.
- Compliance and audit risk. Fewer lost documents reduces exposure, but it's a risk-reduction note in the model, not a dollar line — until a recoupment letter makes it one.
Frequently Asked Questions
How fast is payback on fax triage software for a GI practice?
Most mid-to-large specialty groups model payback between four and fourteen months, driven mainly by document volume and how much of the recovered labor they actually redeploy. Higher-volume groups on a single EHR instance land at the fast end. Groups running multiple systems after an acquisition should assume the longer end, because integration work dominates the first quarter.
Should the ROI model include referral revenue or just labor savings?
Include both, but present them separately and defend them differently. Labor savings are calculable from your own volume and wage data and will survive CFO scrutiny. Referral-conversion revenue is real and larger in GI than most specialties, but it's a sensitivity range rather than a point estimate — model it with your own contribution margin per procedure.
Does the ROI depend on cutting staff?
No, but it depends on redeploying them. The benefit shows up as either reduced payroll or absorbed growth without new hires. Many GI groups choose the second, moving intake coordinators to prior authorization and scheduling work where the backlog is larger and the revenue impact is more direct.
How do we baseline if we've never tracked fax volume?
Pull thirty days of inbound documents from your fax server or EHR document queue by site, then have two or three intake staff log handling time on every document for one week. That gives you volume and minutes; finance supplies loaded hourly cost. Total effort is about a week of light tracking, and it's the input that makes every downstream number defensible.
Which pricing model is best for a GI document mix?
Per-page pricing tends to be the worst fit, because GI receives long multi-page hospital and procedure packets. Per-seat is predictable and decouples cost from growing volume. Per-document aligns cost with value most cleanly, provided the contract doesn't bill exception documents at the automated rate.
Can one deployment cover sites running different EHR instances?
Technically yes, but cost and timeline scale with the number of distinct integrations rather than the number of sites. Six locations on one instance is a single integration project; the same six across three systems is three. Price and schedule the business case on integration count, not site count.
