Every hospice growth conversation eventually hits the tooling question, and there are really only three roads: a spreadsheet, a generic CRM like Salesforce or HubSpot, or a hospice-specific CRM. Each can work. Each fails in a predictable way. Here’s how to pick based on where your agency actually is.
Option 1: The spreadsheet
Why it works: free, instant, infinitely flexible, and everyone can use it. A disciplined leader with one liaison can absolutely run referral tracking in a spreadsheet.
How it fails: silently. Visit logging depends entirely on after-the-fact data entry, so the data drifts from reality within weeks. There’s no activity timeline per referral source, no alerting when a source goes quiet, and the whole system lives in one person’s head. When that person is out, so is your pipeline visibility.
The tell that you’ve outgrown it: you can’t answer “which referral sources went cold in the last 60 days?” in under a minute.
Option 2: Salesforce or HubSpot
Why it works: world-class platforms with automation, mobile apps, and reporting that can model anything — including hospice referral sales, if someone builds it.
How it fails: the build. Out of the box, these tools model deals and companies, not referral sources, liaisons, and admissions. Someone must design custom objects, conversion reporting, and field workflows — then maintain them through every staff change. Agencies routinely spend more on configuration than on licenses, and when the admin leaves, the system fossilizes. HIPAA handling also needs deliberate setup.
When it’s right: you’re part of a larger organization that already has Salesforce admins and wants one platform everywhere.
Option 3: A hospice-specific CRM
Why it works: the data model matches the job on day one — referral sources as accounts, visit logging built for the field, conversion and source-trend reporting prebuilt, market context included. Liaison adoption is the single best predictor of CRM success, and adoption tracks directly with how little translation the tool requires.
How it fails: if it’s treated as software-only. A CRM nobody implements is shelfware regardless of fit. That’s why we built CoPilot to ship with hands-on account management — setup, territory structure, and a weekly operating rhythm included. (For the broader landscape, see our hospice CRM comparison.)
Side-by-side
| Spreadsheet | Salesforce / HubSpot | Hospice CRM | |
|---|---|---|---|
| Upfront cost | $0 | Licenses + significant build | Subscription |
| Time to useful | Today | Months | Days–weeks |
| Field logging | Manual, after the fact | Good if built well | Built in |
| Referral-source reporting | DIY formulas | DIY objects + reports | Built in |
| Market intelligence | None | None | Often included |
| Maintenance burden | One hero | Admin required | Vendor |
| Fails when… | You grow | The admin leaves | You skip implementation |
A simple decision rule
- One liaison, founder-led sales: spreadsheet is fine — put a revisit trigger on hiring liaison #2.
- Existing enterprise CRM team in your org: use it; budget real admin hours for the hospice build.
- Everyone else: hospice-specific CRM, and weight the decision toward implementation support over feature count.
Whichever road you take, the system only matters if it changes Monday morning behavior: who calls which referral source, and what gets logged by Friday. If you’d like help standing that rhythm up — with or without our software — talk to us.
