A custom CRM rarely fails because of the code. It fails because nobody owns the data model, old records arrive dirty, roles get bolted on late, and the first release tries to replace every spreadsheet at once. Each of these problems is cheaper to fix on paper than in a live system. Below are eight pitfalls from the business systems we’ve built, and what to do about each one before you sign a contract.
This guide assumes you’ve already decided to build. If you haven’t, start with what a custom CRM costs and when a ready-made one is cheaper.
| Pitfall | Early warning sign | What to do instead |
|---|---|---|
| Rebuilding what any CRM does | The spec starts with contacts, deals and email templates | Build only the workflow no ready-made CRM handles |
| Launching everything at once | The first release has more than one main job | Start with one job and add the rest in iterations |
| Treating migration as a weekend task | Nobody has opened the old data yet | Clean and test-load real records before the build |
| Adding roles late | “Admin” and “user” are the only roles in the spec | List who sees, edits and approves what, for each role |
| Underestimating integrations | “It has an API” is the whole integration plan | Check access, cost and limits of each system first |
| Reports that change behavior by accident | Metrics get picked after launch | Decide what each number will be used for |
| Ignoring personal data rules | No plan for deletion or export requests | Put deletion, export and access logs in version one |
| Fixing the price before the scope is known | A fixed price signed on a two-page brief | Fix the price for a first release, then switch models as it grows |
Contacts, deals, pipelines, tasks and email templates exist in every ready-made CRM. Paying to rebuild them is the fastest way to spend a custom CRM budget. Custom code pays off for the part of your work that no CRM settings menu covers.
SmartBuilding shows what that part looks like. Construction supervisors needed to scan a QR code on a worker’s helmet and see who let that worker onto the site, which areas they may enter, which safety briefings they’ve attended and which violations are on record. Cameras scan the same codes to catch people walking into areas they shouldn’t. No CRM sells that. We built the platform from scratch in 2 months, and it cost 15 times less than a similar product SmartBuilding’s competitors had developed (SmartBuilding case study).
If your work is a standard sales pipeline, set up a ready-made CRM and build only the missing pieces. We do both: Rocketech is a Bitrix24 Silver Partner.
A big first release means a long wait before anyone uses it, and every wrong guess gets built into many screens at once.
Hays, the recruitment company, started small. Its 200+ recruiters spent up to 2 hours formatting each CV. We built a prototype to test the idea, then added the LinkedIn and job-site integrations, data uploads, storage, segmentation and personal data protection in separate iterations. The tool cut formatting to 2 minutes per CV and grew into a mini-ERP tied to recruiters’ KPIs and bonuses. It grew that way because each step was small enough to check.
Before SmartBuilding, the client tracked dozens of construction sites in paper journals and copied them into Google Docs by hand. Old data in a large company often looks no better. It sits in spreadsheets, inboxes and an old system, with duplicates, empty fields and three spellings of the same client.
Open the old data before the build starts. Pick one person on your side who decides what gets cleaned, merged or dropped. Then load a real sample into a test copy of the new system, and do a full dry run before go-live.
In SmartBuilding, users get rights to view, manage or edit worker profiles, and the screens each person sees depend on their role. Deleted construction objects disappear from the dashboard but stay in the database, so a mistake can be undone. Decisions like these shape the data model. Added after launch, they mean rework across many screens.
Write down every role before the build: who sees which records, who edits them, who approves and who can delete. Include people outside your company, like contractors and partners.
Every outside system adds work, and some charge for access. Hays’ tool had to pull candidate data from LinkedIn and the region’s largest job site, and convert Word files. The job site’s licence was costly enough that Hays hesitated to buy it, so the integration had to work around it.
WTF, a fund with $100M in assets, shows the other side. The plan included links to outside systems, but because of time and cost, the finished system takes PDF reports uploaded straight to the server (WTF case study). It was a deliberate trade. Make yours early too: decide which integrations must work on day one and which can start as a file upload.
For each system, ask three questions before you sign. Is there a documented API? What does access cost? What limits apply?
Limits change with the plan. HubSpot’s private apps get 100 API requests per 10 seconds on the Free and Starter plans and 190 on Professional and Enterprise, with 250,000 to 1,000,000 requests a day per account (HubSpot usage guidelines). Microsoft gives each paid Dynamics 365 user 40,000 requests a day, and background integrations share a pool that starts at 500,000 (Power Platform request limits). A nightly sync that updates 300,000 records one call at a time already goes over HubSpot’s smallest daily cap, so count the calls before you design the sync.
Hays’ tool shows statistics for each recruiter. Those numbers became the basis of a new reward system, and recruiters’ bonuses were linked to the number of CVs they produced. Once a CRM number feeds pay or rankings, people work toward that number.
So decide what each report is for before you build it. If a number might one day feed a bonus, define it carefully now and check how someone could push it up without doing better work.
A CRM is a store of personal data. Under Article 17 of the UK GDPR, people have the right to have their personal data erased, and the ICO says you must respond without undue delay and at the latest within one month. If deleting one person’s data means a developer running a script by hand, every request turns into a small project. Since June 2026, UK organisations must also give people a clear way to make a data protection complaint and acknowledge each one within 30 days (ICO).
Build these into the first release: finding everything stored about one person, exporting it, deleting it, a log of who opened which record, and a dated record of each complaint. At Hays, personal data storage and protection was a step of its own in the plan. This isn’t legal advice, so ask your lawyer which rules apply in your countries.
A fixed price works for a first release with a clear scope. It works badly for a system that keeps growing, because every change reopens the price. Hays started on a fixed price and moved to a dedicated team as the tool grew.
Two more contract points matter as much as the price. The code, the cloud accounts and the domain should be in your company’s name. And design decisions need one owner: on WTF, custom design elements went through several rounds of rework, which stretched the timeline.
A first release that covers one workflow typically costs $5,000 to $15,000 and takes 2 to 4 weeks. Larger systems are priced at $39 to $55 an hour, or built by a dedicated team at $6,000 to $9,000 per developer a month. The team starts in 3 to 5 days, or within 2 weeks if we hire someone new. Internal tools like Hays’ and SmartBuilding’s are part of our web app development work.
Already have a CRM that another team built, and it’s stuck? A code and architecture audit costs a fixed $3,500 and takes 5 working days. It tells you what to keep, fix or rebuild.
You can see what your CRM costs to build before your first call with any vendor.
Usually not because of the code. The common causes are rebuilding features a ready-made CRM already has, launching too much at once, dirty data from old systems, roles added late and integrations nobody checked. Each one is cheaper to fix before the build.
Set up a ready-made CRM if your process is a standard sales pipeline or order flow, and build only the parts it can’t handle. Build a custom one when the workflow is specific to your business, like SmartBuilding’s QR access control on construction sites.
A first release that covers one workflow typically takes 2 to 4 weeks with us. SmartBuilding’s platform took 2 months. A system like Hays’ keeps growing over many iterations after that.
Pick one owner for the data, export a sample early, clean it and merge duplicates, load it into a test copy, and do a full dry run before go-live. Paper records, like SmartBuilding’s journals, have to be typed or scanned in first.
Your company. Put the code repository, cloud accounts and domain in your company’s name from the start, so you can change vendors without losing the system.
Before building a CRM, decide which data and workflows must be custom and which a standard CRM already covers. The Hays tool started with one task, CV formatting, and grew into a mini-ERP linked to recruiter KPIs. Explore software development services and the Hays case study.
Scope a custom CRM around your real workflows
Start with an AI-assisted project brief covering scope, budget, market assumptions and risks. Review its hypotheses before making a commitment.
Carefully curated content for resourceful Devs, CTOs, and PMs. No spam.