How much to charge for a CRM
How much to charge for a custom CRM comes down to one question: what does a lead that never got a follow-up, or a deal that went quiet, cost this business? A CRM is not a contact list to the client. It is the thing that stops sales falling through the cracks and stops the team asking each other "did anyone call them back?" Price the build on a share of that value, add lines for moving their data in, their workflow rules and each system it connects to, and quote a monthly plan for upkeep. Do not price it on screens or on hours.
CRMs are good work to sell with Claude Code because a working first version comes together fast, and you can show the client their own pipeline with their own stages early. The trap is that a CRM looks done the moment you can add a contact and drag a deal between columns. The hard part is everything around it: years of messy spreadsheet data, duplicate contacts, who is allowed to see what, and the follow-up rules that live in the owner's head. That is where the unpaid work hides if you priced the screens.
Should they buy a CRM instead?
Ask this before you quote. Plenty of businesses are well served by an off-the-shelf CRM, and if one fits, telling the client so builds more trust than any proposal. I would rather lose that build and keep the client for the next one.
A custom CRM earns its price when the business works in a way those tools fight. A sales process with steps that do not map to a standard pipeline. Records that need to tie leads to jobs, properties, vehicles or projects rather than just companies and people. Data that has to sit next to their existing app, database or customer portal. A team that tried a big CRM, found it too much, and went back to a spreadsheet. When you hear those, you are not pricing a contact list. You are pricing their way of working, and that is where the value sits.
The CCC CRM Quote
Five parts of a custom CRM quote
| Part | What it prices | Question to ask the client |
|---|---|---|
| Base build | The follow-ups, deals and admin time it saves | Where do leads come in today, who follows up, and how often does one slip through? |
| Data migration | Moving, cleaning and de-duplicating their existing records | Where does your customer data live now, and how clean is it? |
| Workflow rules | Stages, owners, reminders, permissions and required fields | Walk me through a lead from first contact to paid. Who touches it at each step? |
| Connections | Each email inbox, form, calendar or invoicing tool it syncs with | Where do leads come from, and where does the deal need to end up? |
| Keep plan | Monthly checks, fixes and small changes | What happens if leads stop landing in it on a Monday morning? |
Base build. Work out what the current mess costs: how many leads come in, how many get a late follow-up or none, what an average customer is worth to them, and how many hours the team spends digging for a customer's history. Price the build at a fraction of one year of that value, so they can see it pay for itself.
Data migration. This is the line builders forget and clients assume is free. Their customer data usually lives in a few spreadsheets, an email inbox and an old tool, with duplicates and missing fields everywhere. Look at a real export before you send the final number, and price the cleaning and matching on what you find. Get the client to sign off on how duplicates are handled, because they will notice if a customer's history disappears.
Workflow rules. Stages, who owns each lead, when reminders fire, which fields are required, and who can see or edit what. Every rule is a place where a lead can get stuck, so ask about them all. Permissions matter more than clients expect: a sales rep seeing every deal and the owner seeing only their own are very different builds.
Connections. Each outside system is its own line: the website form, the shared inbox, the calendar, the invoicing tool. Each one has its own access and its own way of changing. If the client mainly wants work to move automatically between tools rather than a place to manage customers, how much to charge for an AI automation is the better guide.
Ask these before you quote
- Show me where your customers live today. A real look at the spreadsheets and inbox tells you more about the migration line than any description.
- What does a good week of follow-up look like, and what does a bad one look like? The gap is the value you are pricing.
- Who uses it, and who is allowed to see what? Owners, sales reps and admins are different jobs with different permissions.
- What reports does the owner check? If they mostly want charts of the pipeline, part of this is a dashboard, and how much to charge for a dashboard covers that line.
- Who owns the accounts? Hosting, database and email should be in the client's name, and customer data is theirs. How to hand off a Claude Code project covers the checklist.
More questions that save a bad quote are in client discovery questions before you quote.
Always quote the Keep plan
A CRM holds the client's customer list, which is one of the most valuable things the business owns. When it breaks, leads stop landing in it and nobody notices until a prospect complains they never heard back. Form tools change, inbox connections expire, staff join and leave, and the owner adds a new stage or a new kind of deal.
Quote a monthly plan in the original proposal. Say what it covers: checking leads and syncs come through, fixing breaks when a connected tool changes, adding and removing users, backups, and small changes like a new field or stage. Say what it does not cover: new pipelines, new connections and new features, which are quoted separately. How to price a maintenance retainer covers the structure.
How to present the CRM quote
- Lead with the outcome in their words. One line on no more leads going cold, then the price.
- Itemize it. Base build, data migration, workflow rules, each connection, then the Keep plan. Itemized quotes get trimmed, not rejected.
- Gate payments on proof. A deposit to start, a payment when their real data is in and checked, and the final payment once the team is using it day to day. How to structure milestone payments for an AI project covers the schedule.
- Write the rules into the proposal. A short list of stages, owners, reminders and permissions, signed off by the client, ends the "it should have known that" argument before it starts.
And skip hourly. Claude Code makes the build fast, so hourly pricing turns that speed into a pay cut. I covered why in why I stopped charging hourly for AI builds. If the team needs a tool for doing operational work beyond managing customers, how much to charge for an internal tool is the better guide.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How much should I charge for a custom CRM?
Price it on what it fixes: missed follow-ups, deals that go quiet and time spent hunting for customer history. Charge a fraction of one year of that value for the build, add lines for data migration, workflow rules and each connection, and quote a monthly plan for upkeep.
Should I build a custom CRM or recommend an existing one?
If an off-the-shelf CRM fits the business, recommend it. A custom build is worth it when the business works in a way those tools fight, like records tied to jobs or properties, unusual sales steps, or data that has to live next to their existing app.
Should data migration be priced separately?
Yes. Moving, cleaning and de-duplicating existing customer data is real work and often the riskiest part. Look at a real export before you quote, and put migration on its own line.
Should I charge a monthly fee for a CRM?
Yes. Form tools, inbox connections and staff all change over time. A monthly plan covers checking leads come through, fixing breaks, managing users, backups and small changes like new fields or stages.
Should I charge hourly for a CRM build?
No. Claude Code makes the build fast, so hourly pricing punishes you for that speed. Price on the value of the leads and time it saves, with each part itemized.
Last reviewed by Duncan Rogoff on October 12, 2026
