Fixed quote after a free call

Medical CRM automation for your clinic's new-patient pipeline

Clinics win patients through web forms, phone calls, online directories, insurer listings and referring physicians, and most track them in an inbox or a spreadsheet. We connect every source to one healthcare CRM pipeline, from first enquiry to first visit, with automatic acknowledgements, coordinator tasks and a weekly report showing which channels and referrers bring patients who book. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why clinics lose new-patient enquiries

A clinic rarely loses a new patient on purpose. The enquiry arrives on a busy afternoon as a voicemail, a web form, a directory message or a fax from a referring practice, and by the time someone looks, the patient has booked elsewhere.

Nobody can then answer basic questions: how many enquiries came in for physical therapy last month, how many were called back the same day, which referring physicians send patients who actually attend, or whether the new paid campaign brought anyone at all.

What we build

What our medical CRM automation includes

One pipeline for every source

Web forms, website chat, missed calls, directory and insurer listing enquiries, and referrals flow into one CRM pipeline.

Stages that match your clinic

New enquiry, contacted, eligibility checked, first visit booked, attended, plan of care started, set up per service line.

Fast first reply

An approved acknowledgement and booking option within minutes, with stop rules once the patient books or replies.

Coordinator tasks

Call-back tasks with due dates and owners, so no enquiry depends on someone remembering.

Referrer tracking

Referring practices recorded as sources, so you can thank the ones who send patients and spot the ones who have gone quiet.

Weekly source report

Enquiries, first visits booked and attended by channel, referrer and service line, emailed every Monday.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Enquiry arrives

    A form, call, chat, directory message or referral creates or updates a CRM contact.

  2. 02 Automated

    Acknowledged

    The patient gets an approved reply and booking option within minutes.

  3. 03 Automated

    Stages update

    Bookings and attendance from the EHR move the record forward where the integration allows.

  4. 04 Coordinator review

    Coordinator follows up

    The patient coordinator calls, answers practical questions and records the outcome.

  5. 05 Clinician or medical director decides

    Clinical suitability

    Whether a service is right for the patient is decided by a clinician, never by the CRM.

How it behaves

How the healthcare CRM pipeline behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the patient sees

  • A quick acknowledgement and a booking option after they enquire
  • A call from a coordinator if they asked for one
  • A couple of follow-ups at most, stopping once they book

What staff see

  • One pipeline board per service line
  • Call-back tasks with owners and due dates
  • A weekly report by channel and referrer

What the automation does

  • Captures and de-duplicates enquiries from every source
  • Moves stages from EHR booking and attendance data
  • Sends follow-ups with stop and opt-out rules

Edge cases and fallbacks

Same person enquires twice
Matched by phone or email and merged into one contact.
Existing patient uses the new-patient form
Flagged to the coordinator rather than opening a new deal.
Enquiry includes symptoms
Kept out of the CRM notes and routed to staff under the clinic's urgent process.
CRM or EHR API outage
Enquiries queue and retry, and the practice manager gets an alert.

Architecture

A healthcare CRM pipeline for a clinic at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Web and chat Forms, live chat Phone calls Missed and answered Referrals Physicians, payers n8n Capture, dedupe Healthcare CRM HubSpot, Salesforce Follow-ups Text and email Coordinator Tasks and calls Weekly report Source, referrer
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Enquiries arrive from the website, phone system, directories and referring practices.
  2. 2 n8n captures each one, removes duplicates and creates or updates the contact and deal in the CRM.
  3. 3 Approved follow-ups go to the patient and call-back tasks go to the patient coordinator.
  4. 4 A weekly report shows enquiries, bookings and attendance by channel, referrer and service line.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Healthcare CRM & new-patient pipeline project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Enquiry and referral sources, current tracking, service lines and what the clinic wants to measure.

  2. 02

    Design

    2 to 3 days

    Pipeline stages, field mapping, duplicate rules, consent rules and what stays out of the CRM.

  3. 03

    Build

    1 to 2 weeks

    Source connections, pipeline, follow-ups, coordinator tasks and the weekly report.

  4. 04

    Shadow run

    About 1 week

    Enquiries flow into the CRM while staff keep their old tracking, and we compare the two.

  5. 05

    Launch

    1 to 2 days

    Switch over and train coordinators and the front desk.

  6. 06

    Support

    Ongoing

    New sources, service lines and report changes.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n HubSpot CRM API or Salesforce Health Cloud Website forms and chat Your phone system (call events) EHR via FHIR API or vendor API (read-only to start) Twilio SMS and your email provider

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Workflow mapping with the clinic team, wording, data flows and a written specification.

    $200 – $400

  • Build

    The n8n workflow, rules, AI step where useful, logging and error handling.

    $500 – $1,300

  • Integrations

    EHR or practice management access, messaging and staff alert channels.

    $150 – $400

  • Testing and shadow run

    Acceptance tests and a side-by-side run while staff keep the old process.

    $100 – $250

  • Launch and training

    Go-live, front-desk walkthrough and a short run book.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. CRM licences, messaging and n8n are billed to you directly. A two-way EHR link or many sources may need a second workflow.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • CRM licence: Your CRM vendor's own plan (HubSpot, Salesforce or the CRM you already use).
  • n8n: Free self-hosted Community edition on your own server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing). A BAA needs Twilio's Security or Enterprise Edition if patient information is in the messages.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: HIPAA and CRM vendors

A CRM holding patient information for a covered clinic is a business associate and needs a written agreement; if the vendor will not sign one, clinical details stay out of it. General information, not legal advice.

Source: www.law.cornell.edu

US: promotional texts need written consent

Follow-ups that promote services are marketing and need prior express written consent; the healthcare exemption covers only narrow purposes such as appointment reminders.

Source: www.law.cornell.edu

UK: marketing by text and email

PECR requires consent, or the soft opt-in conditions, for marketing by electronic mail, with a simple way to refuse in every message.

Source: www.legislation.gov.uk

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Healthcare CRM & new-patient pipeline questions, answered.

A medical CRM tracks prospective patients and referral sources from first contact to first visit. It sits beside the EHR, which still holds charts and appointments, and answers the question of where patients come from and who is following them up.

Mostly HubSpot and Salesforce Health Cloud, both with documented APIs, and we can work with a CRM you already pay for. We pick based on your sources, EHR, budget and whether the vendor will sign a BAA for the data you plan to store.

Usually, by reading appointments from the EHR through its FHIR API or vendor API. We start read-only so the CRM can mark a booking as attended without ever writing into the chart.

Yes. Each referral is linked to the referring practice, so the report shows which referrers send patients who book and attend, and which have gone quiet.

Partly. Fast acknowledgements and coordinator tasks are service, and source reports help marketing decisions. Promotional messages go only to people who agreed to receive them.

Enquiries by source, time to first reply, share contacted the same day, first visits booked and attended, and referrals by referring practice. We set these up from day one.

Free 20-minute call

Want this for your healthcare clinic?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call