How a California Health Insurer Moved Off Per-Seat CRM Fees: A Custom CRM Case Study

A California health insurer replaced monthly third-party CRM fees with a one-time build: a custom, HIPAA-compliant CRM on its own private server, delivered January to June 2023 by 5 specialists. The case covers what was built and how PHI is protected, with a way to estimate the same move for your team.

In short

  • A California health insurer needed a CRM its account managers would use, without buying accounts and functionality from bloated off-the-shelf platforms.
  • We built a custom HIPAA-compliant CRM on the client's private server, with development from January 2023 to rollout in June 2023 and a team of 5 specialists.
  • The client made a one-time payment instead of monthly third-party CRM fees and now pays only for hosting and maintenance, and this page shows how to estimate the same move for your own seat count.

A California health insurance company stopped paying monthly per-seat fees for a third-party CRM by replacing it with a custom one. We built a HIPAA-compliant CRM on the client's private server, mapped to how its agents move a lead to a customer. Development started in January 2023 and the system rolled out in June 2023, with a team of 5 specialists. The client made a one-time payment for a lean system it will use for years, and now pays only for hosting and maintenance.

This write-up sticks to what the case record states. It has no savings percentage, because none was measured for publication. If you want a dollar comparison for your own team, the last sections show how to build one.

What problem was the insurer trying to solve?

The insurer's account managers needed a digital workflow for managing leads, opportunities and customers. Off-the-shelf CRMs such as Salesforce had bloated feature sets for what the team needed. Buying accounts and functionality from those platforms was cumbersome and impractical financially.

Two more constraints shaped the project. The CRM would collect and store protected health information (PHI), so it had to be HIPAA-compliant. And the agents work with insurance-specific data, so the system had to reflect the company's actual business process rather than a generic sales pipeline.

Why does per-seat pricing hurt a team like this?

Per-seat platforms charge the full edition price for every user, whether that person uses one screen or the whole product. For context, Salesforce Health Cloud lists at $350 to $725 per user per month, billed annually, depending on edition. A team whose agents mostly need leads, tasks, notes and a few reports pays for the whole edition on every seat.

A custom CRM flips the cost shape. You pay for the build once, then for hosting and maintenance. Adding an agent does not add a license fee. That trade is worth it when the workflow is specific and stable enough to build once and maintain, which was the case here.

What did the CRM need to hold?

Agents work with data that generic CRMs do not have fields for out of the box:

  • Medicare Beneficiary Identifier (MBI)
  • Healthcare proxy
  • Health plan
  • Primary care physician
  • Pharmacy

Managers also track results for the Medicare enrollment windows. The Open Enrollment Period, often called AEP, runs October 15 to December 7. The Medicare Advantage Open Enrollment Period (OEP) runs January 1 to March 31 and applies to people already in a Medicare Advantage plan. Each window has its own pace and its own success measures, so the reporting had to separate them.

What did we build?

  • A data model around the insurer's actual workflow: Lead, then Opportunity, then Contact (a customer who bought a health plan), with contact, convert and lost status indicators.
  • Lead capture from two sources: a public web form with explicit consent capture, and manual entry by agents.
  • Searchable account views with filters by date, status, assignee and source, plus a full interaction timeline and document history for each account.
  • Insurance-specific reporting: AEP and OEP success rates, monthly lead and opportunity counts, and lead-to-closed and opportunity-to-closed ratios.
  • A user interface iterated several times at the client's request to make it as usable as possible.

The tech stack was CakePHP, PostgreSQL and Angular, with design in Figma. The system is deployed on the client's private server, which is what removed the recurring monthly SaaS fees.

How is PHI protected in the CRM?

The case record lists four controls:

  • The principle of least privilege for system users, so each person reaches only what their role needs.
  • Password rotation.
  • Automatic logout after 15 minutes of inactivity.
  • Hosting on the client's private infrastructure.

These map to the HIPAA Security Rule. Under 45 CFR 164.312, access control means allowing access only to people or software that have been granted access rights. Automatic logoff, which ends a session after a set period of inactivity, is an addressable implementation specification under the same section. Password rules and least privilege support the same goal: only the right person, in the right role, sees a member's record.

If you plan a similar build, start from the full rule, because this list covers only part of it. The Security Rule also covers unique user identification, emergency access, audit controls, integrity and transmission security, and 45 CFR 164.308 requires an accurate and thorough risk analysis. On any project we sign a BAA before we touch PHI and run penetration tests before launch.

What changed for the insurer?

The case record states these results:

  • Instead of incurring hefty monthly fees for third-party CRM services, the client made a one-time payment for a lean solution they will use for years, paying only for hosting and maintenance.
  • The implementation and user onboarding were both easy.
  • The system reduces the need for manual data entry and thus errors.
  • The CRM speeds up lead processing and helps distribute the workload better.
  • The software has increased the insurance agents' productivity.

The record does not publish dollar amounts, seat counts or before-and-after time measurements, so we do not state any here. If a vendor shows you a case study with a precise savings figure, ask how it was measured and over what period.

Is a custom CRM right for your plan?

These questions separate a good candidate from a poor one:

  • Do most of your users need a narrow set of features, such as leads, tasks, notes, documents and a handful of reports?
  • Does your process depend on insurance-specific fields and enrollment windows that a generic CRM handles only with heavy customization?
  • Is your license bill growing with every agent you hire?
  • Do you have, or can you contract, someone to maintain the system every year?
  • Do you want PHI on infrastructure you control?
  • Can you live without the long tail of features a large platform offers?

If most answers are yes, a custom build deserves a proper estimate. If you rely on many products from one CRM vendor working together, or on staff who already know that platform deeply, staying and trimming may be the better first step.

How do you estimate the same move for your team?

Compare the two cost shapes over the same period. Use your own quotes:

saas_per_year   = users x price_per_user_month x 12 + add-ons + admin
custom_one_time = build quote (team size x months x rate) + data migration
custom_per_year = hosting + maintenance + admin
break_even_year = custom_one_time / (saas_per_year - custom_per_year)

If the break-even year is well inside the time you expect to keep the system, the build is worth a closer look. If it is past that, or if saas_per_year minus custom_per_year is close to zero, stay on the platform and right-size it instead. Run it at your current headcount and at the headcount you plan for in three years, because the per-seat line grows and the custom line mostly does not.

Count the one-time costs honestly: migrating records and history, rebuilding reports, connecting the systems you already use, and training staff. A project like this one, with a team of 5 specialists over six months, is a useful scale reference for a focused CRM. Your scope decides your own timeline.

Want to talk it through?

Talk to an engineer at Onix Health about your seat count and workflow. Onix Systems has built software since 2000 and has 370+ engineers. Our 5-day free technical audit ends with a written report, so you can decide on a custom CRM, a trimmed platform, or neither, with real numbers.