Attio for healthcare: how clinics and health-tech model patients, examinations, and retention without a specialized CRM

A healthcare CRM has to model two things most CRMs cannot. A patient is not a contact. A visit is not a deal. The default Salesforce pipeline collapses both into the same shape, and the data either gets lost or gets stuffed into free-text fields nobody reads.

The market response has been a wave of specialized healthcare CRMs. NexHealth, Pabau, Salesforce Health Cloud, Creatio. They handle EHR integration and HIPAA out of the box. They also start at $300 per user per month and ask for $50,000 to $200,000 in implementation. For a small clinic or a health-tech startup, that math does not work.

There is a middle path. A flexible CRM with real custom objects, the kind that lets you model People, Patients, and Examinations as separate things with separate workflows. Attio is the cleanest example. I have built this for a preventive-care provider running both individual care and corporate partnerships, and the model works.

Here is what an Attio setup looks like for a healthcare business and where it stops working.

What a healthcare CRM has to handle that a generic CRM cannot

A person is not a patient

Identity, marketing email history, and form submissions belong on the Person record. Active care belongs on a separate Patient record. Treating both as the same record means a lead who never converts shows up in retention reports, and a patient who finished care still gets newsletter campaigns about being a lead. The journey loses its shape.

Each visit is its own atomic record

A visit has a date, a type, a price, products purchased, and notes. Stuffing those into fields on a contact loses history every time the patient comes back. The third visit overwrites the second. Total revenue per patient becomes a guess.

Recurring follow-ups depend on date triggers, not memory

Preventive care lives or dies on follow-up cadence. A patient due for a check next quarter does not surface unless the system schedules it. CRMs that rely on someone remembering to set a reminder lose 20 percent of retention every cycle.

B2C and B2B run on different rhythms inside the same business

Individual leads convert in days. Corporate partnerships (insurers, banks, employers, Rotary clubs) move over months with proposals and committee approvals. Forcing both through one pipeline means either the B2C team waits for B2B-shaped stages or the B2B team gets dropped in a B2C kanban that does not fit. Most teams pick the wrong tradeoff and live with it.

Why a flexible CRM with real custom objects clears the bar

Three structural features matter for healthcare, and most CRMs only have one or two.

Custom objects as first-class citizens. Patient and Examination should be their own objects with their own workflows, not awkward extensions of Contact and Deal. If the CRM treats custom objects as a paid add-on or a database afterthought, the modeling breaks within three months.

Many-to-many relationships. A patient buys multiple products. A product is bought by multiple patients. A B2B company has multiple key contacts. A doctor sees patients across multiple insurance partners. Forcing these into one-to-many through workarounds creates phantom records and broken reports.

Scheduled workflows, not just trigger-based ones. Retention requires "every Monday, look at patients due in 30 days and move them to the right list." That is a different primitive than "when someone fills a form, send an email." A CRM that only does the second cannot do recurring care.

Attio has all three. So does Notion CRM (sort of, but the workflow engine is weaker). HubSpot's custom objects sit behind the Enterprise tier at roughly the same price as Salesforce Health Cloud, which defeats the cost argument.

The data model that holds up in production

Five objects. The shape stayed consistent across consult calls with five different healthcare operators last quarter. The fields shift by specialty.

People. Source of identity and the journey from lead to retention. Status field with four stages: Lead, Warm Lead, Ongoing Patient, Retention. Source field tagged by acquisition channel (web form, referral, partner, event). Type field for B2C versus B2B contact. Email and phone history anchored on the record, deduplicated on email.

Patients. A custom object created automatically when a Person flips to Ongoing Patient. Holds care-specific fields only: linked Person, next examination date, total lifetime cost (rolled up from Examinations), number of past examinations, current treatment notes. Separated from People because the workflows are different. People care about acquisition. Patients care about cadence.

Examinations. One atomic record per visit. Fields: date, type (full health check, specific test, follow-up), value (this visit only), products purchased, summary notes. The Patient record never overwrites; the history is the list of Examinations linked to it.

Companies. B2B partners running their own pipeline: insurers, banks, employers, Rotary clubs, corporate health programs. Fields for company type, key contact person, qualifying stage (Need, Choose, Worry, Commit), deal value, package, channel, and reseller. This object lives parallel to People; a corporate contact gets a Person record linked to the Company.

Products. Services purchased by patients. Many-to-many with People for accurate revenue tracking. Each Product has a price. Aggregated values roll up to the Patient lifetime cost.

That is the full model. It runs without any healthcare-specific software.

Running B2C and B2B side by side

The trap most clinics fall into: they pick one CRM for individual patients and a second CRM for corporate sales. Two tools, two sets of contacts, no shared revenue picture, two subscriptions.

In Attio, the same People object handles both. A B2C lead has Status moving through the patient journey. A B2B contact has a Type field that flags them as a corporate contact, with a relationship pointing to the Company. The kanban view filters by Type so the B2C team sees only individuals; the partnerships team sees only corporate.

Companies have their own pipeline with qualifying stages that match a longer sales cycle: Need (problem identified), Choose (evaluating solutions), Worry (objection handling), Commit (contract negotiation). A B2B dashboard tracks deal value by stage, channel, and reseller. None of this leaks into the patient journey reports.

Both pipelines feed the same revenue dashboard at the end of the month.

Automations that make recurring care actually recur

Six automations carry the load.

1. Form submission to Person, no duplicates. Typeform and Google Sheets rows flow into Attio via a workflow tool. If the Person exists, the source field updates. If not, a new Person is created. A Slack approval gate on outbound email prevents anything going out unreviewed.
2. Person becomes Patient automatically. When status flips to Ongoing Patient, a linked Patient record is created with default fields inherited from the Person. No manual duplication.
3. Lifetime value rolls up from Examinations. Each new Examination triggers a workflow that sums examination cost and updates Total Value on the linked Patient. Revenue per patient stays accurate without manual entry.
4. Examination type routes the patient. When an Examination is logged, the linked Patient is pushed to the right list (Full Health Check or Specific Test) based on type. No manual list management.
5. Date-triggered retention staging. Four scheduled workflows scan the retention list daily. Patients due in one month or one week move into the right stage automatically. Follow-ups never depend on memory.
6. Post-visit Typeform fills patient fields. When a patient submits the post-visit Typeform, the workflow finds the matching Patient and populates the answered fields. No re-keying.

The retention automation is the one that pays for the entire setup. A clinic that captures 70 percent of follow-up visits versus 50 percent recovers the implementation cost in the first quarter on a base of 200 active patients.

The two dashboards the team actually opens

Patient Operations dashboard. Number of patients, examinations, revenue, and ARPU per month and quarter. Trend across the active care base. A visual of patients overdue for follow-up. This is the dashboard the clinic manager opens on Monday.

B2B Pipeline dashboard. Deal value by qualifying stage, channel, and reseller. Proposal-sent rates. Meetings booked from Rotary, partnership outreach, and inbound. This is the dashboard the partnerships lead reviews with the founder.

Both rebuild from raw data every time. No manual reporting.

The HIPAA question, honestly

Attio offers HIPAA compliance on the Enterprise tier with a signed BAA. That is real, but it is also priced for funded teams, not solo clinics.

The practical answer for most healthcare businesses I work with: keep PHI out of Attio, and use Attio for the journey and the relationship layer. Names, emails, phone numbers, lead source, examination dates, examination type, and revenue are not PHI on their own. Diagnostic data, treatment plans, and clinical notes are. Those stay in the EHR.

This split works for preventive care, wellness clinics, health-tech with a B2C funnel, and concierge medical practices. It does not work for hospital systems handling clinical workflows in the CRM. For those, Salesforce Health Cloud or a specialized healthcare CRM is the right call regardless of price.

If the line between PHI and journey data feels blurry for your specific operation, the safest move is a 15-minute conversation with your compliance officer before the implementation, not after.

When Attio is not the right fit

A few cases where I tell people to look elsewhere.

Hospital systems with clinical workflows in the CRM. Salesforce Health Cloud or Epic are the standards for a reason. The cost of integration with billing, claims, and clinical data is the actual product.

Practices that need built-in EHR. Pabau, NexHealth, and Practice Better bundle scheduling, charting, and patient portal. Attio is a pure CRM. If the team will not run two systems, the bundle wins.

Operations that bill insurance directly through the CRM. Attio has no claims module. A third-party tool covers it, but the integration adds work.

Single-doctor practices with under 100 patients. A Google Sheet works fine until you cross that threshold. Setting up a CRM before the volume justifies it is cost without return.

How long the setup takes

A core healthcare build (five objects, lead intake automation, retention staging, B2B pipeline, dashboards) takes about nine working days. Faster for narrower scope. Longer when historical imports from Sheets, Brevo, Calendly, and Gmail are part of the project.

The blocker is rarely Attio. It is the team agreeing on what each pipeline stage means and what triggers a status change. Once that is settled, the build is mechanical.

Getting this set up for your clinic

If this maps to how your clinic or health-tech business runs, book a call. Thirty minutes, no pitch. We walk through your patient journey, your B2B partners if you have them, and your follow-up cadence. By the end of the call you have a written sketch of the data model that fits your operation.

For a fuller picture of the implementation, see the Attio for healthcare overview and the Elfcare case study on a preventive-care provider that consolidated five tools into one Attio workspace.

If you want to try Attio first, sign up through my link for 10% off.

Free audit of your Attio workspace

If your clinic already runs Attio and you want a second pair of eyes, I run a free 48-hour audit. You add me to your workspace as an Attio expert, no extra seat and no billing. I send back a one-page written teardown ranked by impact, the three highest-leverage fixes with the exact setting change, and a 5-minute Loom walking through the top fix. No call, no pitch. 5 slots a week.

Get your free Attio audit