# Custom CRM development UK: bespoke CRM and ERP systems built for your firm.

Canonical: https://appagentix.co.uk/services/custom-crm-erp-development/

We do custom CRM development: a CRM, a light ERP or both, built around how your firm works, with your data moved from spreadsheets and old tools. Below: our prices, a cost estimator, a licence sum and a filled scope.

- Custom CRM first version in 8 to 14 weeks, at one fixed price after discovery
- A one-page scope signed in week 2: roles, stages, fields and links
- Every record counted in, loaded or rejected on a sheet you sign
- Running costs listed line by line, billed to accounts in your name

## How much does a custom CRM system cost?

A first version of a custom CRM costs £15,000 to £40,000 and takes 8 to 14 weeks. A CRM joined to ERP modules such as quotes, stock and invoicing takes 4 to 8 months. Discovery takes 2 weeks and its fee comes off the build price. All prices exclude VAT. For example, a first version for a 40-staff firm moving from an old CRM and two spreadsheets is a fixed £27,000. Price your own version with the calculator on this page.

- CRM first version: 8 to 14 weeks
- Full CRM or CRM plus ERP modules: 4 to 8 months
- Discovery: 2 weeks, fee taken off the build price
- Support: monthly, 3-month minimum, then 30 days notice

## What is custom CRM development?

A CRM holds your customers and sales steps; a light ERP runs the quotes, orders, stock and jobs behind them. In 2023, 61% of UK firms had adopted specialised software (ONS Management and Expectations Survey, 2023).

### Pipeline stages written from your own sales steps

Your own stages, fields and approval rules, with a forecast from your deals.

Stages and fields go on the scope you sign in week 2.

### One record per customer

Emails, call notes, quotes and support cases sit on one timeline. The clinic platform we built for a healthcare business keeps clinical notes, appointments and billing in one system with the patient records.

Every record shows who changed it and when.

### Quotes, orders and invoices

A quote from your price list becomes an order, then reaches your accounts package by an automatic link.

Each link to another system is a named, priced line on the quote.

### Bespoke ERP: stock, jobs and suppliers

Stock, purchase orders, job sheets and suppliers for a back office still run on spreadsheets.

We build only the modules listed on the quote.

## One record, every team

A custom system joins the steps your tools keep apart.

1. Enquiry
2. Customer record
3. Quote
4. Invoice
5. Reports

## Which do you need: a CRM, an ERP module, or a ready-made tool?

Start from the problem, not the label.

What is going wrong today?

- If Your sales steps or pricing rules need workarounds in every standard tool, choose **A custom CRM**. Pipeline, records, roles and reports follow your rules, and a first version takes 8 to 14 weeks.
- If Staff retype each accepted quote into an order, then into an invoice, choose **A CRM with quotes and invoices**. One record carries the quote to the order and on to your accounts package.
- If Stock levels, purchase orders or job sheets still live in spreadsheets, choose **A CRM with ERP modules**. Each module is a priced line on the quote; full builds take 4 to 8 months.
- If You have under about ten users, or a standard pipeline already fits, choose **A ready-made CRM**. It is cheaper, and our discovery report says so in writing.

## When does a build cost less than licences? Run the sum

Users times the monthly fee times 12 gives the yearly bill. Divide the build price by the monthly bill to find when it pays for itself.

**Licence bill against the example first version, at one round fee per user a month**

| Users | Months of fees that equal the build |
| --- | --- |
| 10 | 54 |
| 20 | 27 |
| 40 | 13.5 |
| 60 | 9 |
| Your firm |  |

The fee per user is a round figure, not any vendor’s price: use your own bill. For a fairer answer, take the running-cost estimate on your quote off the monthly bill first.

## The one-page scope you sign in week 2

Filled in for an imaginary firm before the build starts: 40 staff, about 4,800 customer accounts, an old CRM and two spreadsheets.

**One-page scope, first CRM version**

| Item | What is agreed | Status |
| --- | --- | --- |
| Roles | Sales, account manager, finance and admin; sales cannot change prices | Agreed |
| Pipeline stages | Enquiry, qualified, quote sent, negotiation, won, and lost with a reason | Agreed |
| Fields on a deal | Value, expected close date, source, product line, discount and approver | Agreed |
| Fields on a contact | Consent date and source, business type and a do-not-contact flag | Agreed |
| Link 1 | Accounts package: invoices out, payment status back | Agreed |
| Link 2 | Website enquiry form: each enquiry becomes a deal | Agreed |
| Link 3 | Phone system call log on the customer timeline | Open: your phone provider confirms API access in week 3, then it is priced as a change or moves to phase 2 |
| Data to move | Old CRM export, customer spreadsheet and supplier list | Agreed |
| Out of scope | Stock, purchase orders, payroll and a customer portal | Not in this price |

Signed by your project owner and our lead; anything not on it is a change, priced in writing first. An example for an imaginary firm, not a client document.

## Bespoke CRM development, week by week

A first version (MVP) typically takes us 9 to 10 weeks. This plan, with a data move from an old CRM, runs about 12; each ERP module repeats the build step.

### Discovery (Weeks 1 to 2)

We sit with the people who use the current tools and follow three real deals from enquiry to payment.

You receive: The signed scope, a prototype and one fixed quote.

### Data audit (Weeks 2 to 3)

We open every spreadsheet and export, count the records and list duplicates and blanks.

You receive: A count per source and the questions for your data owner.

### Design (Weeks 3 to 4)

Screens for each role, tried by five of your own staff.

You receive: Final screens and where staff got stuck.

### Build in two-week sprints (Weeks 4 to 9)

Each sprint ends with a working system on a test site you log in to.

You receive: Three releases, each with a note on what shipped.

### Data move and trial (Weeks 9 to 10)

We load cleaned data into a copy, your staff work in it for a week, and totals are compared with the old tools.

You receive: The data-move check sheet, row by row.

### Test and fix (Week 11)

Role checks, a load test with your expected users and a restore from backup.

You receive: A test report you can read, misses included.

### Launch and handover (Week 12)

The old tools go read-only on an agreed date, once the check sheet is signed.

You receive: The live system and a handover pack.

## The data-move check sheet: records in, loaded, rejected

On every row, found minus loaded must equal rejected, or the load runs again, and each rejected row gets a reason and a named person to fix it.

**Data-move check sheet, trial load 2**

| Source | Records found | Loaded | Rejected | Result | Why, and what happens next |
| --- | --- | --- | --- | --- | --- |
| Customer spreadsheet | 4,812 | 4,790 | 22 | Pass after fix | 22 duplicates merged after your sales lead chose which to keep; counts matched on the second load. |
| Old CRM export, contacts | 9,640 | 9,640 | 0 | Pass | Counts match, with consent date and source carried across on every contact. |
| Supplier list | 310 | 295 | 15 | Open | 15 suppliers lack a VAT number; your accounts team sends them by Friday, then we reload those rows. |
| All sources | 14,762 | 14,725 | 37 | 22 settled, 15 open | The old tools stay live until every row reads Pass. |

Signed by your data owner before the old tools go read-only. An example for the same imaginary firm, not a client result.

## Custom ERP development: how a quote becomes a paid invoice

The links we are asked for most often are your accounts package, email, phone system and website forms. On the clinic platform we built, laboratory data arrives through an HL7/FHIR link.

1. **Quote.** From your price list, with discount and approval rules.
2. **Order.** The accepted quote becomes an order, no retyping.
3. **Invoice.** Raised in your accounts package, such as Xero or Sage, through the link.
4. **Payment status.** Paid, part-paid or overdue is read back from the accounts package.
5. **Customer record.** Staff see the status on the customer timeline.

## Bespoke CRM and ERP, line by line

After discovery you get one fixed figure for a written scope, not a range or an hourly rate.

| Option | Price | Time | Includes |
| --- | --- | --- | --- |
| First call | Free | 30 minutes | A written view on scope, timeline and price range in two working days. |
| Discovery | 2 weeks |  | Scope, prototype, data audit, a build-or-buy recommendation and one fixed quote. The fee comes off the build price. |
| Custom CRM system, first version | 8 to 14 weeks |  | Pipeline, customer records, roles, reports, up to three links and one data move with its check sheet. |
| Full CRM, or CRM with custom ERP modules | 4 to 8 months |  | Quotes, orders, invoicing links, stock or jobs, a customer portal, an audit trail and screens designed to WCAG 2.2 AA. |
| Support after launch | Monthly | 3-month minimum, then 30 days notice | Security updates, bug fixes, small changes and a monthly report. Faults against the agreed scope are fixed free for the first 3 months. |

Finance, manufacturing and multi-site stock in one system are quoted after discovery.

## Estimate your custom CRM in a minute

Pick your starting data and what the system should do.

Discovery, pipeline, customer records, roles, testing and launch: £11,000 to £16,000, 8 to 9 weeks.

### Starting data

- Fresh start: included
- One spreadsheet or export: £2,000 to £3,500
- Several sources or an old CRM: £4,000 to £7,000

### What it does

- Reports, dashboards, up to 3 views: £8,000 to £12,000
- Accounts package link (Xero, Sage): £2,500 to £4,000
- Quotes and orders: £4,000 to £7,000
- Invoicing link and payment status: £2,500 to £3,500
- Stock and purchase orders: £5,000 to £8,000
- Customer portal: £5,000 to £7,500
- Workflow and approvals: £3,000 to £4,500
- AI feature on one workflow: £15,000 to £20,000

An estimate, not a quote, excluding VAT. The fixed price follows discovery.

## What it costs to run after launch: the lines on your quote

You pay no fee per user, because each line below is billed by its provider to your company’s account.

**Running-cost lines, first CRM version**

| Line | Account holder | On the quote |
| --- | --- | --- |
| Hosting | Your company | Quoted per month, estimate on the quote |
| Database | Your company | Quoted per month, estimate on the quote |
| Email sending | Your company | Quoted per month, estimate on the quote |
| SMS sending | Your company | Quoted per month, estimate on the quote |
| Backups and file storage | Your company | Quoted per month, estimate on the quote |
| AI use, if any | Your company | Quoted per month, estimate on the quote |
| Support, if you choose it | Contract with us | Monthly fee, 3-month minimum, then 30 days notice |

Each estimate states its assumption, here 40 staff and 4,800 customer accounts, so you can redo the sum.

## Code, database and hosting accounts: whose name they sit in

Everything is in your business’s name, and the repository sits in your GitHub or GitLab organisation from the first commit, with us as collaborators. Database, hosting, domain and sending accounts are opened in your company’s name, never ours. If we part, we remove our access within one working day, and you can export all your data in a standard format.

## What is included and what is not

Both lists go into the quote.

- Included: one data move with a signed check sheet
- Included: 3 months of fixes after launch
- Included: the repository, a handover pack and a restore test
- Not included: VAT
- **Not included: hosting and third-party bills.** Billed by each provider.
- **Not included: choosing between conflicting records.** We find duplicates and blanks; your team decides which record is right.
- **Not included: features added after the scope is signed.** Each is priced in writing first.

## How we test it, including any AI parts

Only 22% of UK businesses considered cyber security to a large extent when buying software (DSIT Cyber Security Breaches Survey 2025/2026), so ask any supplier to show its tests.

### Automated tests on every change

Pricing, tax and permission rules are tested each time the code changes.

Results are visible in your repository.

### Totals checked against your old tools

Order values, balances and stock counts are compared on move day.

The check sheet shows every difference and its fix.

### Load and restore tests

We load-test with your expected users, then restore a backup to a clean site.

The restore time is measured and written in the handover pack.

### AI answers checked on your cases

Any feature that drafts replies or reads documents runs on your examples, each answer marked right or wrong. Among UK businesses with 10 or more staff, 21% used text generation with large language models in September 2026 (ONS Business Insights and Conditions Survey).

You read the full result, wrong answers included, before launch.

## Why do so many CRM programs fail?

Three risks sit outside the code; each has a control.

Scope drift is the first: new requests keep moving the launch date, and the control is the signed scope, with each change priced first.

Unowned data is the second: nobody knows which of two records is right, so you name one data owner, who signs the check sheet.

A launch with no trial is the third: staff meet the system on day one and drift back to spreadsheets, so they spend a week in a trial copy first.

## When a custom CRM system is the wrong choice

Under about ten users with a standard pipeline, buy the ready-made tool. If nobody can yet describe how a deal moves from first call to payment, write that down first.

### What we would say no to, and why

- Copying an unwritten process: we would be guessing your rules
- Rebuilding payroll or statutory accounts: a standard package does it, so we link to one
- A fixed price before discovery: the figure would hide a guess
- Switching off the old tools before the check sheet is signed
- A promised sales result: we commit to what we build and test

## UK rules turned into build decisions

Each rule becomes a field, a button or a link in the scope. Among smaller businesses brought into Making Tax Digital from April 2022, 54% used fully functional software (HMRC Making Tax Digital for VAT final evaluation, 2025). We sign a data processing agreement, and you stay the data controller. Rules as of November 2026; not legal advice.

| UK rule | What it changes in the build |
| --- | --- |
| UK GDPR right of access | A one-person export button on every customer record. The ICO says people can ask for a copy of their data. |
| UK GDPR rights to correction and erasure | An edit history on each record and a logged delete. Both are individual rights in the ICO guide. |
| PECR consent for marketing emails and texts | A consent date and source on every contact, plus a do-not-contact flag. The ICO says individuals need specific consent, with a limited exception for your own previous customers. |
| PECR treatment of sole traders | A business-type field, so a sole trader is never handled as a company. The ICO treats sole traders and some partnerships as individuals. |
| Making Tax Digital for VAT | An automatic link to your accounts package, so no VAT figure is copied by hand. HMRC says all VAT-registered businesses need to keep digital records and submit VAT returns using compatible software. |

## Systems we have built

We have been building apps since 2019, and our longest client relationship is seven years and counting. A few examples from the many business systems we have built, where staff track people, bookings and payments in one place.

### Clinic records platform

Healthcare

We built a clinic EMR platform for a healthcare business, covering patient management, electronic medical records and history, clinical notes, appointment scheduling, a doctor dashboard, a patient portal and billing. Laboratory integration uses HL7/FHIR data exchange, and it runs on React, Java, SQL and AWS.

[Read the Clinic records system case study](https://appagentix.co.uk/our-work/clinic-records-system/)

### Coding school platform: admissions and portals

Education

We built the admissions side of this coding school platform so each applicant is tracked automatically and staff no longer chase people by hand. Prospects book an information call online, and admissions, alumni and employer portals give each group its own view of the same records. Access is set by role, sign-in uses two factors, and it runs on Node.js, PostgreSQL and AWS.

[Read the E-learning and admissions platform for a coding school case study](https://appagentix.co.uk/our-work/coding-school-platform/)

## Custom CRM and ERP questions

### How much does it cost to build a custom CRM?

With us, a first version takes 8 to 14 weeks. A two-week discovery ends with one fixed figure for a signed scope, excluding VAT. Price your own version with the calculator on this page.

[UK app prices, line by line](/app-development-cost/)

### How do I create my own ERP system?

Start with one process, not the whole back office. Map how an order moves from quote to payment, build the module with the most retyping first, and link a standard package for payroll and statutory accounts.

### Can I develop my own CRM?

Yes, if a developer stays to maintain it. A pipeline and contact list are quick; the data move, permissions, backups and UK data rules are slow and need an in-house owner.

### What are the key differences between off-the-shelf software and custom software, and when should I choose which one?

Off-the-shelf software is rented per user and works the vendor’s way; custom costs more up front and follows your process. Choose custom when workarounds cost hours a week or the licence sum says so.

### Why do so many CRM programs fail?

Mostly outside the code: a growing scope, unowned data and staff who never tried the system. Our controls: a signed scope, one named data owner and a week in a trial copy.

### Do you really need a CRM in 2026?

Not always. A few people with a short customer list can use a shared spreadsheet, but once follow-ups get missed, start with a ready-made CRM.

### Why do most ERP projects fail?

An ERP touches every team at once, so each risk is larger: too many modules going live together, and unchecked old data. We build one module at a time, with a signed check sheet before each launch.

### How much do ERP systems cost?

A rented ERP is a licence bill, often priced per user each month, and Microsoft sends buyers to a partner for consulting services. With us, a CRM joined to custom ERP modules such as quotes, stock or jobs is priced module by module in the calculator on this page.

## Related services

- [Web app development company](https://appagentix.co.uk/services/web-app-development-company/)
- [Software modernisation](https://appagentix.co.uk/services/software-modernisation/)
- [Product engineering](https://appagentix.co.uk/services/product-engineering/)
- [Agentic AI development](https://appagentix.co.uk/services/agentic-ai-development/)
- [App maintenance and support](https://appagentix.co.uk/services/maintenance-support/)
- [App development cost in the UK](https://appagentix.co.uk/app-development-cost/)
- [Clinic records system (EMR): case study](https://appagentix.co.uk/our-work/clinic-records-system/)
- [Construction software development](https://appagentix.co.uk/industries/construction-software-development/)
- [Aviation software development](https://appagentix.co.uk/industries/aviation-software-development/)
- [Healthcare software development](https://appagentix.co.uk/industries/healthcare-software-development/)
- [Insurance software development](https://appagentix.co.uk/industries/insurance-software-development/)

By [Megha Sharma](https://www.linkedin.com/in/meghanify/), Chief Marketing Officer, AppAgentix. Reviewed November 2026.

[Book a call](https://appagentix.co.uk/requestaquote/)
