The story
Built inside an insurance repair firm. Not a software company.
Most software for contractors is written by people who have never chased an excess, never priced a reinstatement at a kitchen table, and never taken the nine o’clock call from an insurer about a policyholder nobody had rung. We did all three, for twenty-five years, and wrote the answer to each one into the system our firm ran on. This page is where the rules came from.
In four lines
- We spent twenty-five years in insurance repair and grew our firm from two staff to seventy.
- Nothing off the shelf understood a claim, so we built our own system and ran the firm on it every working day.
- Every rule in it was paid for: a missed contact, an underpriced job, a number changed with no trail.
- We sold the firm as a multi-million-pound business. The rules are now Claim Job Control, rebuilt for the web.
Two people and a van
The firm started with two members of staff doing storm damage and escape of water for insurers and loss adjusters: on the tools first, then running the office, then running the business. It handled property damage claims for households and businesses: storm, escape of water, fire, impact, the full book of domestic and commercial repair work that insurers instruct out to contractors every day of the week.
By the end, seventy people worked there, and the business was worth enough that the proceeds of its sale were enough to retire on. That did not happen because the firm was good on the tools. Plenty of firms are good on the tools. It happened because the office answered, every single day, the two questions an insurance repair firm lives or dies on: does the insurer trust us with the next instruction, and did we make money on the last one?
What insurance work is really like
From the outside, insurance repair looks like building work with a different customer. It is not. The policyholder did not choose the contractor and did not want the damage. The insurer is paying but is not on site. The loss adjuster wants it priced right and done quickly. And everyone involved has a complaints procedure with the contractor’s name at the top of it.
A claim is a chain of promises with clocks on them. Ring the policyholder before they ring the insurer. Survey before the damage spreads. Price it right first time. Start when you said you would. Invoice what was agreed. Chase what you are owed. Miss one link and the claim goes quiet, and a quiet claim is a complaint, a lost panel place, or a loss on the books that nobody notices until year end.
The firm missed every one of those links at some point. The insurer rang at nine about a policyholder nobody had contacted. A surveyor drove forty miles to a house where nobody was in, because the appointment had been booked before anyone spoke to her. A team found rotten joists, carried on and did the right thing, and the insurer refused to pay for it because there was no written instruction. The excess went uncollected on jobs we could still name. A rate changed in an estimate and nobody could say who changed it.
The lessons that became rules
Each of those cost money. Each time, a rule went into the system, and the rule was made something the office could not work around.
When a policyholder went uncontacted and the claim collapsed into a complaint, the rule went in: no appointment can be booked until contact is logged. Not a warning box. The button is not there. No exceptions, not even for emergencies, because emergencies are exactly when people cut corners. When a job left the yard underpriced, the margin floor went in: checked when the surveyor prices it, again before acceptance, and watched while the works run. When a number changed with no trail, the audit went in: every quantity, rate and price change written down with who and when, and accepted estimates locked, so the people running a job cannot quietly adjust the figures they are judged on.
“Every rule in this system exists because it made or saved money in our own business. Not one of them is a guess.”
The timescales in the platform, first contact within fifteen minutes, survey within forty-eight hours, estimate within twenty-four hours of the visit, works started within seven days of acceptance, were not invented as aspirations. They are the service standard the firm actually worked to: the standard that won insurer work and kept it coming while other firms were being dropped from panels.
Why we built our own
We looked at what was on the market. Job-management software for tradesmen understood a diary and an invoice. It did not understand a policyholder, an excess, a loss adjuster, a variation that needs written instruction, or a margin floor that differs by insurer. Nothing we could buy knew what a claim was.
So we built our own system, and then did the thing that matters more than building it: we ran the business on it, every working day, for years. Administrators, surveyors, works managers and the bookkeeper each had their own worklist telling them what needed doing today, with badges that had to be cleared. Control that slows the office down is worse than no control at all, so the discipline had to live in the software, not in anybody’s head.
Seventy staff, then the sale
The firm grew on those rules to seventy people handling thousands of claims a year, from a burst pipe in a flat to a fire in a factory, and was sold as a multi-million-pound business. The rules did not retire with the firm’s sale. They are in the software: the contact discipline, the clocks, the margin control, the audit trail, the worklists. Claim Job Control is that system rebuilt as a modern web application. It is not a technology company’s guess at how a repair business works. It is how one actually worked, when it worked well.
Who it is built for
Firms already running insurance work that know jobs are quietly leaking money, or that are fighting a system never built for how claims move. Claim Job Control was built for exactly that problem, inside a firm exactly like theirs.
Firms looking to get into insurance work, who want to be ahead from the first instruction: the timescales adjusters and insurers expect, enforced from day one, and a margin gate that turns the estimate red whenever a job is priced below that insurer’s floor, while they learn the market. We learned those lessons the expensive way. You do not have to.
Bring one of your own jobs to a demo and we will run it through the system on the call.
The business it ran
- 25 yearsin the insurance repair trade
- 2 → 70 stafffrom two people and a van to a seventy-strong firm
- Soldas a multi-million-pound business; the proceeds were enough to retire on
- Domestic & commercialstorm, escape of water, fire, impact: the full repair book
What survived into the software
- The 15-minute first-contact clock, with an optional automatic chase email and a prompt when the letter requesting contact is due
- Contact-before-appointment, enforced, no exceptions
- The 48-hour survey and 24-hour estimate clocks
- Per-insurer margin floors, checked three times per job
- The estimate audit trail, written by the database
- One worklist per desk, warning badges that must be cleared
See it running
Judge it the way an insurer would.
A demo walks one claim through the whole platform, end to end, exactly as the firm ran it. Half an hour, no slides.