Bespoke CRM vs off-the-shelf: UK costs and ownership

This guide is for partners and practice managers at UK regulated firms (accountants, financial advisers and immigration advisers) who are choosing between a bespoke CRM, also called a custom CRM, and a subscription product. The choice matters because a subscription is charged for every user in every month, while a build has a fixed price but its ownership depends on the contract. We built Filyst, our case management product for immigration firms, as a bespoke system, and one section says what that taught us. The other sections cover the definition, when each option fits, published UK prices, five-year totals, copyright, what a regulated firm needs, and a checklist for moving off spreadsheets.

What is a bespoke CRM?

A bespoke CRM is customer relationship management (CRM) software written for one firm’s clients, workflow and records. An off-the-shelf CRM is one product licensed to many firms, sold as a subscription per user per month. “Custom CRM” means the same as “bespoke CRM”; this guide uses bespoke.

An integration sits between the two. An integration is code that passes data between products the firm already uses, so staff enter each record once. A firm that buys a product and commissions one integration owns a small piece of bespoke software.

When is an off-the-shelf CRM the right choice?

An off-the-shelf CRM is the right choice when the product already matches how the firm works. Four conditions point to buying:

• The workflow matches how the product expects you to work.
• The product has the records your regulator expects, such as an audit trail, permissions and retention dates.
• The firm has no person to own a bespoke system after it is built.
• The per-user fee, multiplied by your users over five years, stays below the cost of a build and its upkeep.

When does a bespoke CRM pay off?

A bespoke CRM pays off when the gap between the firm’s process and the product costs more than the build. Four conditions point to building:

• Staff re-type the same data between products every day.
• The firm’s process differs from the product’s, and changing the process would lose something clients value.
• The firm needs a control the product lacks, such as sign-off by a second person that the system enforces.
• The per-user fees over five years exceed the build price plus five years of upkeep.

Is there a middle option between buying and building?

Yes: keep the core product, connect it to the firm’s other systems, and build only the workflow it does not cover. For a regulated firm we would start here. The firm keeps the records already held in the product, and staff keep the screens they know.

The price gap is large. Our integration sprint is £900–2,000 per integration, and our bespoke CRM build is £8,000–25,000. Both figures exclude VAT and appear in the table below.

What does a bespoke CRM cost in the UK?

A bespoke CRM from VexraLabs costs £8,000–25,000 excluding VAT, paid in phases over 6–12 weeks. That is our own published price, not a market average. Every supplier sets its own price, so the table labels each figure with the page it comes from, as published on 8 October 2026.

VexraLabs prices are in pounds and exclude VAT; the full list is on our services and pricespage. Microsoft’s page states that its prices do not include VAT. Salesforce’s page shows its prices in pounds without a VAT statement, so confirm the VAT treatment with Salesforce. Vendors change prices; open Salesforce’s pricing page and Microsoft’s pricing page before you budget. We name the two vendors as price examples, not as recommendations.

How do you compare the cost over five years?

Compare five-year totals, not first-year prices. For a subscription, multiply the per-user price by the number of users and by 60 months. For a bespoke CRM, add the build price to 60 months of upkeep and hosting.

These are worked examples from the published prices above, not quotes. All five totals exclude VAT treatment differences, setup work, add-ons and price changes. The two build totals also exclude hosting, which the care retainer’s listed deliverables do not include, and £350 a month is the retainer’s starting price. Run the sums again with your own user count and the plan you would really buy.

Who owns the code of a bespoke CRM?

The supplier owns the copyright in a bespoke CRM unless the supplier assigns it to the firm in writing. The rules come from the Copyright, Designs and Patents Act 1988 (CDPA), which treats a computer program as a literary work (section 3(1)(b)).

• Section 9(1) defines the author as “the person who creates” the work.
• Section 11(1) says: “The author of a work is the first owner of any copyright in it, subject to the following provisions.”
• Section 11(2) says that where a literary work “is made by an employee in the course of his employment, his employer is the first owner of any copyright in the work subject to any agreement to the contrary.”
• Section 90(1) says copyright “is transmissible by assignment, by testamentary disposition or by operation of law, as personal or moveable property.”
• Section 90(3) says: “An assignment of copyright is not effective unless it is in writing signed by or on behalf of the assignor.”

Section 11(2) covers employees. A supplier’s developers are not the buying firm’s employees, so section 11(2) does not make the buyer the first owner. Payment is not one of the routes section 90(1) lists. From a supplier, the route is assignment, and section 90(3) sets its form: in writing and signed by or for the supplier.

Section 90(2) allows an assignment to be partial: limited to some of the owner’s exclusive rights, or to part of the copyright period. Read the clause for both limits. A sales page that says “you own the code”, ours included, is not an assignment. Ask every supplier, VexraLabs included, for the signed clause before work starts.

An off-the-shelf CRM works differently. The vendor keeps the copyright and the firm holds a licence to use the product on the vendor’s terms for as long as it pays.

What does a regulated firm need from either kind of CRM?

A regulated firm needs the same records and contract terms from a bespoke CRM as from a subscription product. The rules below apply to the firm, not to the software, so the firm checks them whichever option it picks.

A processor is a supplier that handles personal data on the firm’s behalf; the firm is the controller. SYSC is the Senior Management Arrangements, Systems and Controls sourcebook of the Financial Conduct Authority (FCA), which regulates financial advisers. SYSC 8.1 sets the outsourcing rule that FCA outsourcing rules (SYSC 8): checking a supplier explains provision by provision.

Beyond those rules, we would ask any CRM, bought or built, for four things:

• An audit trail of who did and approved each step.
• Permissions by role, so staff see only the records their work needs.
• A retention date on every record.
• A full export of the firm’s data in a format another system reads.

Where the CRM uses AI, the AI drafts and a person signs off. AI in regulated industries: UK rules and human review sets out the rules that the sign-off step answers.

What did building Filyst teach us about bespoke software?

Building Filyst taught us that a bespoke system earns its cost through controls the system enforces. Filyst rejects self-approval on the server, so a second person signs off each case stage. It keeps an audit log, and it sets a retention date when a case closes: six years by default for UK firms.

Upkeep is the other lesson. Filyst has 3,449 automated tests, and those tests are what let us change one rule without breaking another. Filyst has no client firms yet, so this is what we learnt building it, not a result from firms using it.

How do you move from spreadsheets to a CRM?

Move from spreadsheets to a CRM in five steps: map, clean, dry run, check, switch. The steps are the same for a bought or a bespoke CRM. Use the list as a planning checklist and set your own dates; the time each step takes depends on how many sheets and records the firm holds.

1. Map. List every spreadsheet, its owner and what it holds. Match each column to a field in the CRM. A partner approves the mapping.
2. Clean. Remove duplicates and fix errors in a copy, never in the original. Leave out personal data that has passed its retention period.
3. Dry run. Import the cleaned copy into a test copy of the CRM.
4. Check. Compare record counts per client, money totals per client and year, and a sample of records field by field. Record the results.
5. Switch. Move to the CRM on a set date after a partner signs off the checks. Keep the old files read-only until then.

Two UK GDPR principles shape the clean step. Article 5(1)(d) requires personal data to be “accurate and, where necessary, kept up to date”. Article 5(1)(e), storage limitation, is the reason to leave expired records behind.

What should a bespoke CRM proposal include?

A bespoke CRM proposal should fix price, ownership, data handling and exit in writing before work starts. Ask for six items:

• A fixed scope and price for each phase, with written acceptance criteria.
• A written assignment of the copyright in the code, signed by or on behalf of the supplier (CDPA section 90(3)), covering all rights for the full copyright period.
• A processor contract under UK GDPR Article 28(3) where the supplier handles client personal data.
• A statement of where the code, data and accounts live, with the accounts in the firm’s name.
• A statement of support hours, response times and the monthly cost of care after launch.
• A description of how the firm exports its data and moves to another supplier.

What are the risks of a bespoke CRM?

A bespoke CRM carries four risks, and each has a control the firm sets in the contract.

Where should a firm start?

Start by mapping the workflow, because the map shows whether the firm needs a product, an integration or a build. A workflow audit produces that map: Workflow audit: meaning, what it covers and cost describes the steps and the deliverables.

This guide is the pillar of our custom software topic. The prices in it come from our services and prices, where each option lists its deliverables and timeline.

Frequently asked questions

Sources

1. Copyright, Designs and Patents Act 1988, section 3 (literary works include computer programs)
2. Copyright, Designs and Patents Act 1988, section 9 (authorship)
3. Copyright, Designs and Patents Act 1988, section 11 (first ownership)
4. Copyright, Designs and Patents Act 1988, section 90 (assignment and licences)
5. UK GDPR Article 5 (principles), legislation.gov.uk
6. UK GDPR Article 28 (processor), legislation.gov.uk
7. FCA Handbook, SYSC 8.1 (outsourcing)
8. Salesforce UK, Sales pricing (subscription prices in GBP)
9. Microsoft UK, Dynamics 365 Sales pricing (subscription prices in GBP)