Guides
A UK energy broker CRM typically costs between £150,000 and £450,000, depending on how many supplier panels it connects to, how much of the meter-point hierarchy (MPAN and MPRN) needs modelling, and how much commission reconciliation and conduct-rule reporting the business needs. A single-office build sits at the low end; a franchised network with settlement-level data sits at the high end.
£150k–£450k
The variables that matter most are supplier panel count, whether the CRM needs to handle LOA issue and expiry, and how much commission reconciliation and clawback tracking the agent structure requires. Elexon settlement data integration and multi-office rollout push a build towards the top of the range.
What moves the number
| Cost driver | Low end | High end | Indicative impact |
|---|---|---|---|
| Integration count | One supplier price feed and one telephony/call recording platform. | Multiple supplier panels, Elexon settlement data, a dialler, and an accounting system for commission remittance. | Each supplier feed or panel integration typically adds £10,000–£30,000, depending on feed format consistency. |
| User count | A single brokerage team under 30 agents. | Multiple offices or a franchised agent network of 200+ users with tiered commission structures. | Adds permissioning and reporting-rollup complexity; £15,000–£45,000 at the high end. |
| Compliance scope | Standard GDPR and PECR consent tracking. | Full Ofgem/TPI conduct-rule audit trail, retrievable call recording linkage, and a formal complaints-handling record. | Adds £15,000–£40,000 for the audit trail, consent model and retrieval-on-demand reporting this needs. |
| Data migration volume | A single clean export from an existing CRM or spreadsheet register, under 10,000 sites. | Multiple legacy CRMs or spreadsheets per office with duplicate MPAN/MPRN records to de-duplicate and reconcile. | £8,000 for a clean single-source load; £35,000–£70,000 for multi-source meter-point reconciliation. |
| Design complexity | Standard pipeline and account views following established CRM patterns. | Portfolio roll-ups across sites with blended pricing, contract-end-date-driven pipeline views, and a partner-facing quoting tool. | Adds £15,000–£45,000, largely for the portfolio and Contract End Date-driven views this business model needs. |
| Ongoing support | Business-hours support, reviewed monthly. | Renewal-season priority support with rapid turnaround given the time-sensitivity of Contract End Date-driven work. | Not part of build cost; typically 15–20% of build cost per year. |
Three budget levels
£150,000–£200,000
A single-office broker CRM with a site/MPAN/MPRN hierarchy, Contract End Date-driven renewal pipeline, one supplier price feed integration, PECR-compliant contact tracking and standard commission calculation for a flat agent structure.
Timeline
14–16 weeks
Team shape
1 tech lead, 2 full-stack engineers, 1 designer, 1 QA engineer
£260,000–£340,000
A multi-office broker CRM covering several supplier panels, LOA issue and expiry tracking, tiered agent commission with clawback on early termination, call-recording linkage for Ofgem/TPI audit purposes, and migration from two legacy CRMs.
Timeline
20–24 weeks
Team shape
1 tech lead, 3 full-stack engineers, 1 integration engineer, 1 designer, 1 QA engineer, 0.3 project manager
£400,000–£450,000+
A franchised-network platform integrating multiple supplier panels and Elexon settlement data for larger commercial sites, portfolio-level blended pricing views, a partner-facing quoting and LOA portal, full conduct-rule audit trail, and de-duplication of meter-point records across several legacy sources.
Timeline
28–34 weeks for the first release, phased rollout to franchise offices thereafter
Team shape
1 principal engineer, 1 tech lead, 4–5 full-stack engineers, 1–2 integration engineers, 1 data engineer, 1 designer, 2 QA engineers, 0.5 project manager
Day rates assume £550–£750 for a tech lead or principal engineer, £450–£600 for a full-stack or integration engineer, and £400–£550 for a designer or QA engineer, blended across our UK, Germany and Pakistan delivery teams.
Not included
Where the money goes
Discovery for a broker CRM spends a disproportionate amount of time on the meter- point data model: confirming how MPAN core, top line and MPRN values are currently captured across existing spreadsheets or CRMs, and where they conflict between sources. Getting this model right before build starts is what allows the Contract-End-Date-driven pipeline and portfolio views to work correctly on day one, rather than needing a data-model rework six months in.
Supplier price feed integration cost varies more than most cost drivers because feed quality and format consistency vary by supplier — some publish clean, versioned feeds; others require a scraping or manual-upload fallback that has to be built and maintained. We scope each panel relationship individually during discovery rather than quoting a flat per-integration figure across the board.
Because renewal activity clusters around contract end dates, the system needs to perform reliably under load during renewal-heavy periods rather than on an average day. This affects the ongoing support band more than the build cost, but it is worth budgeting for a support arrangement with faster response times during known renewal peaks rather than a flat SLA year-round.
How we produce an estimate
These ranges are indicative, not quotes. A real estimate comes from a discovery and scoping sprint, scoped against your actual supplier panel, agent structure and legacy data. See broker CRM development, LOA and contract workflow and quote and tender engine for how we structure this work, and our custom CRM cost guide for the general CRM cost picture this guide builds on.
Questions
Because a meter point, not an account, is the true unit of the energy supply relationship. The CRM needs a data model where every MPAN core and top line, or MPRN, is a child record of a site with its own contract, tariff and consumption history, rather than a single free-text field on an account. Retrofitting this into a generic CRM object model is more expensive than building it in from the start.
Yes, where a supplier or panel provider offers a feed. Coverage and reliability vary by supplier, so we scope this per panel during discovery rather than assuming universal live pricing from day one. Confirm current panel and feed coverage with your supplier relationships.
A letter of authority workflow needs a record of which supplier or third party holds authority to act on a site, the date range it covers, the document itself, and an audit trail of when it was issued, used and expired. This underpins renewal and switching activity and is a compliance requirement, not an optional extra.
Commission and uplift rules are configured per agent, supplier and contract term, calculated when a contract is confirmed, and reconciled against supplier remittance data as it arrives, with clawback tracked against the original calculation on early termination.
Only if your business model requires settlement-level visibility, such as validating consumption against supplier billing for larger commercial or half-hourly metered sites. It is a distinct integration, priced separately, not a default part of every broker CRM build.
Call recording retrieval against the account, PECR consent and suppression tracking, and an auditable record of the advice given at the point of sale are the requirements that most often need dedicated data model and reporting work, rather than being satisfied by a CRM's default activity log.
Tell us how many supplier panels and offices are in scope and we will tell you which band you are in.
Talk to us