The pricing engine your software can license.
You've built the workflow — the CRM, the diary, the crews. You just need the price to be right. We price; you keep everything else.
A price you can defend, in one call.
A penny-exact price, versioned, with the full contribution breakdown — every line traceable to a fact of the job. Deterministic: the same request returns the same price, this year or next. Replayable and auditable, forever.
When the engine is unsure, it says so — flags surface for your users to read, and the quote still prices. It never blocks, and it never silently guesses.
{
"contractVersion": "v1",
"status": "priced",
"engineVersion": "v5.97.0",
"price": {
"total": 1048.64,
"currency": "GBP",
"band": { "low": 996.21, "high": 1101.07 }
},
"crew": 3,
"hourlyRate": 100,
"breakdown": [
{ "component": "labour",
"label": "3-person crew, about 10.1 hrs at £100.00/hr",
"amount": 1010.00 },
{ "component": "mileage",
"label": "12.4 miles @ £1.10/mile",
"amount": 13.64 },
{ "component": "adjustment",
"label": "Stairs (no lift) × 1",
"amount": 25.00 }
],
"flags": [
"crew headcount is borderline near a tier
threshold - confirm before dispatch"
]
}A real response from engine v5.97.0 — reference-rate config, 3-bed Bristol → Bath, trimmed for length. No firm's actual rates appear.
However your product meets the job.
The API
Your workflow calls, we price. One request in, a governed, versioned price out.
The embed widget
The price on your clients' own websites — same engine, their branding.
Hosted quote pages
A quote the customer opens, with a deposit paid on acceptance.
A second country is a config, not a fork.
Region is a parameter of the engine rather than a branch of it. Ireland already prices in kilometres and euros, with Irish holidays, Irish VAT and the drivers'-hours regime that actually applies there — through the same code path a British firm uses, with no change to the product they already have.
We are open in the United Kingdom, Ireland and France today. Other regions are built and declared rather than trading, and each one opening is its own decision — we would rather tell you that plainly than imply a map we do not serve. What the architecture guarantees is the part that matters to an integrator: adding one costs you nothing that already works.
We price. We never become your CRM.
That's a promise written into how the product is governed, not just a positioning line. Cerrax prices the job and helps run the job it priced; it does no customer management — no contact history, no pipelines, no marketing. The relationship with your customer stays yours.
Each firm's data serves that firm first. The engine improves from governed, aggregated outcomes across the network — that's why every partner's pricing gets sharper over time. Customer records never leave your system — the job's facts, nothing else.
Talk to us about the API.
Tell us what you're building or which CRM you run. We'll show you the engine against a real job and walk through the guarantees.
Talk to us about the API