When a business owner asks me what a CRM costs, I always have to pause before answering. The honest answer is: it depends on which costs you are counting. The subscription price is visible and easy to compare. Everything else tends to show up later, in ways that are easy to dismiss as one-time problems until they keep happening every year.

I have helped enough companies move off of platforms they thought were affordable to have a pretty clear picture of where the money actually goes. Most of it never shows up in the sales demo.

Per-Seat Creep

Per-seat pricing sounds reasonable when you are a team of five. It stops sounding reasonable when you add a few field techs, an office coordinator, a part-time estimator, and a subcontractor you want to give limited access to. Suddenly you are at twelve seats, some of which are rarely used but still billed monthly.

The platforms that charge per seat know this. The math works strongly in their favor as teams grow. I have watched companies go from a $200/month CRM bill to $900/month inside two years without meaningfully expanding what they were doing in the system. They just hired people.

With a custom build, you are typically paying for the software itself, not per user. Seat count stops being a lever someone else controls. That alone changes the long-run cost shape significantly for growing teams.

Add-Ons That Should Have Been in the Base Product

This one irritates me more than it probably should. A lot of CRM platforms sell you a base package and then charge separately for things that feel like they should be standard: email sequences, SMS, reporting dashboards, two-way calendar sync, document storage, proposal builders. Each add-on is a modest monthly fee. Together they double the bill.

When you are evaluating platforms, it is worth mapping out exactly which features your team will actually use on day one and which ones you will want within six months. Then price the full bundle, not the base tier. The comparison against alternatives looks different once you do that exercise.

Integration Fees

Your CRM will need to talk to something. QuickBooks, your estimating tool, your scheduling software, your website contact forms. Native integrations sometimes exist but often have gaps. When the native integration does not do what you need, you are looking at a middleware service like Zapier or Make, which adds another monthly cost and another system to maintain.

For more complex workflows, you may need a developer to build a custom integration anyway. At that point you are paying a developer to work around the limitations of a platform you are already paying for. That is a real cost that rarely gets factored into the initial buy decision.

I wrote more about this in the context of CRM integrations — the short version is that integration complexity is one of the main reasons businesses end up building custom rather than staying on a platform.

Data Cleanup and Migration

At some point, most businesses switch CRMs. When that happens, data quality becomes the first painful problem. Years of inconsistent entry, duplicate contacts, missing fields, and notes stuffed into the wrong places mean that migration is never just an export and import. It is an audit, a cleanup project, and a rebuild of however your old system organized things into however your new system wants them organized.

I have seen this take a week of internal staff time for a small team and months of consultant time for a mid-size company. Neither of those hours usually gets counted when people say what their CRM cost them.

If you ever think you might switch platforms, it is worth setting up good data hygiene habits early and making sure your data is exportable in a clean format. That is one area where open data models, like what you get with a custom CRM built on a database you own, make a real difference. You are not negotiating with a vendor to get your own records back.

Training Time

Every CRM has a learning curve. For a simple team using basic pipeline tracking, the curve is shallow. For a team that needs the system to match real workflows — job stages, estimate approvals, dispatch, follow-up sequences — the curve gets steeper, especially when the software was not designed for your specific type of business.

Training time has a real cost in staff hours, and it also has a softer cost in adoption drag. When people find the system confusing or poorly matched to how they actually work, they use it less. They keep notes elsewhere. The CRM becomes a partial record instead of the system of truth, which undermines the whole reason you bought it.

This is one of the arguments I make for investing time in getting your team to actually use the CRM — but the foundation of that is building or configuring the system to match real workflows rather than asking staff to adapt their habits to the software.

Ongoing Platform Risk

Software companies get acquired. Pricing tiers get restructured. Features get moved to higher plans. Support quality shifts. These are real risks you accept when you depend on a third-party platform. I am not saying they are reasons to avoid all SaaS — they are just costs in a different form: the cost of uncertainty and the occasional forced migration when something upstream changes on you.

A custom build has its own risk profile, which I covered in the build vs. buy piece. Neither option is risk-free. The point is to go in clear-eyed about what you are actually agreeing to.

How Custom Changes the Cost Shape

A custom CRM has higher upfront costs. That is real and I will not minimize it. What changes is the ongoing cost structure. You are not paying per seat. You are not paying for add-ons. You own the data and the codebase. You are not dependent on a vendor deciding to raise prices or discontinue a feature.

For some businesses that math never works out in favor of custom. For others — particularly those with ten or more users, complex workflows, or strong integration requirements — it often does, especially over a three-to-five year horizon.

The best way to run that comparison for your specific situation is to map the total cost of ownership for the platform option, including seats, add-ons, integration tools, training, and a realistic estimate for future migrations. Then compare it against a real quote for a custom build. The gap is usually smaller than it looks at first glance.

If you want to talk through whether custom makes sense for your situation, the CRM ROI piece has a framework for thinking through that calculation, and the custom CRM page covers how I approach these builds.