CRM and sales decision

Unlock Patients

A competent technical user can build a useful replacement for the dashboard, call-tracking, and verification pipeline, but the full paid offering (agency-managed ad optimization, proprietary models/operations, and HIPAA-compliant service guarantees) is harder to match and represents durable value the vendor claims.

Visit website
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off126 h to build

$500/mo6 h/mo upkeep

No published price to break even against.

The code exists. It is not what you are paying for.

These 2 projects are real, published, and do the core job — and this page still says keep paying. What the subscription buys is proprietary models and compliance and regulation, and none of that ships in a repository. Fork one anyway if you want to. Go in knowing what it does not carry. What stays hard ↓ · All Unlock Patients alternatives, with the arithmetic →

What a replacement has to do

  • Create targeted ads, track incoming calls, transcribe/analyze calls to verify bookings, store metrics and show ad-to-booking dashboard, optionally push verified bookings into an EMR.

What it still won’t have

  • Established agency expertise and ongoing paid-ads optimization
  • Proprietary historical ad creative and campaign tuning
  • Hands-on managed service that runs and scales campaigns for you
  • Service-level guarantees and vendor support/operations
  • Any proprietary analytics or labeled training data used to improve booking verification

What remains hard

  • Proprietary modelsproprietary dashboard and AI call analysis
  • Compliance and regulationHipAa compliant
Read the build prompt

First-year cost

No published price

Unlock Patients does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a self-hosted patient-acquisition dashboard in Node.js (Express) + Postgres, React frontend, deploy to a single small cloud VM (DigitalOcean/AWS t3.small). Core features in scope: (1) connectors to create/manage Google Ads and Meta campaigns (OAuth + simple campaign templates), (2) phone provisioning and call routing using Twilio with encrypted S3 call storage, (3) speech-to-text pipeline (open-source Whisper or cloud STT) and an LLM-based verifier (OpenAI or local LLM) that labels calls as booking/no-booking, (4) attribution logic that links clicks → calls → verified bookings, (5) authenticated dashboard showing ad spend, clicks, calls, verified bookings, and per-campaign ROI, (6) webhook/CSV export to push verified bookings into an EMR. Out of scope: advanced automated bid optimization, multi-account agency UI, and training proprietary ML models from scratch. Include error handling, input validation, unit tests for backend routes, and CI deploy scripts.
How we checked5 sources · 2/3 runs agreed · evidence score 22

How the score was reached

  • Pay verdict base20
  • An open-source build was found+5
  • 5 cited sources+3
  • Hard moats found in the evidence-6
  • Evidence score22

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 5

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 2 moats quoted from the page