Running a probate property services firm without the spreadsheet sprawl

Somewhere in your office there is a spreadsheet holding the firm together. It has a name like cases_2026_FINAL_v7.xlsx, three people edit it, and one person actually understands it. The keysafe codes live in a different file, or in someone's head. Photos from this morning's inspection are in a WhatsApp thread. The invoice run happens at month end, from memory, against the spreadsheet.

None of this is carelessness. Probate property work grew out of relationships with solicitors, and the tools grew out of whatever was to hand. But every firm we speak to hits the same wall: the work scales and the spreadsheets do not. This piece sets out why the usual software answers fit this sector so badly, and what a system shaped around the actual work looks like. We build such systems, so we have a view; we have also tried to be honest about when you do not need one.

What the work actually involves

Probate property services is not desk work with occasional site visits. It is a field operation, a professional services practice and a small logistics business running as one firm. A single instruction can involve most of this:

• An instruction arriving from a solicitor or executor, usually by email, with partial information
• Property access: keys, keysafes, and the codes that go with them
• Inspection visits with photographs, meter readings and condition notes, often in properties with no power or connectivity
• A valuation the estate can rely on
• Clearance, storage of items, and the billing that follows storage month after month
• Introductions to estate agents, and tracking offers through to completion
• Invoicing the estate correctly, and reporting to solicitors in the format they expect

Each of those steps produces records another step depends on. The inspection feeds the valuation. The valuation feeds the agent introduction. Storage feeds billing, month after month, until someone remembers to stop it. When those records live in separate files, the connections live in people's heads, and the firm depends on those people never being on holiday.

Why generic software keeps failing this sector

Firms that go looking for probate case management software in the UK find two shelves. The first holds legal practice software: strong on matters, documents and time recording, built for people who sit at desks. The second holds job management tools for trades: strong on scheduling vans, blind to everything legal. A probate property firm is both at once, so each shelf covers half the operation and the spreadsheet returns to glue the halves together.

The deeper problem is that packages make you bend your process to the software. If the package has no concept of a keysafe code, or of storage that bills monthly until released, or of a valuation that must stand behind an estate account, then those things go back into Excel. Eighteen months after buying a package, many firms are paying per seat and still double keying.

To be fair to the shelves: if your process is genuinely standard, a package is the right answer, and cheaper. The question that decides it is simple. Is the way you run cases part of why solicitors instruct you? If your process is your edge, software that flattens it costs more than it saves.

What a system built around the work looks like

We built exactly this for a UK probate property services firm: an operations platform that runs their daily work in production. Not a demo, a working system; you can walk through it here. The shape of it follows the work:

One case record. Everything hangs off the case: jobs, visits, photographs, quotes, invoices, storage, agent introductions, correspondence. Anyone in the office can open a case and see its whole state without asking the person who knows.

A field app that expects bad signal. Inspections are captured on site on a phone, photos and readings included, working offline and syncing when coverage returns. The report is largely written before the van leaves the street, not typed up from paper that evening.

Valuations built on data. Alongside the platform we built Appraised, a valuation engine that can value residential property across England and Wales from public data, with the two-sided agent platform around it. The estate gets a figure with evidence behind it.

Paperwork that writes itself. Quotes, invoices, storage billing runs and the reports solicitors receive are generated from the case record. The month-end assembly ritual disappears because the figures were never apart.

An audit trail by default. Estates deserve scrutiny and sometimes get it. When every action is recorded against the case as it happens, answering questions stops being archaeology.

Under all of it sits the same six elements we build every system from: Data, Interface, Intelligence, Automation, Output and Governance. The elements never change; the configuration does.

Where AI genuinely earns its place

This sector attracts AI theatre, so it is worth being specific. The useful work is unglamorous: an assistant that answers questions from the live system, reads documents that arrive with instructions, and drafts the repetitive reports for a human to approve. Practical, logged, and governed, with a person signing off anything that leaves the building. That is what AI-native means in an operations system: intelligence wired into the workflow, not a chatbot bolted onto the side.

If you are weighing this up

Whatever you buy or build, hold it to this list. One record per case that everything else references. Field capture that works in a house with no power. Documents generated, not assembled. History you can show a scrutineer. And your data exportable on the day you ask, because a system you cannot leave is a system you do not own.

If a package demo can walk your actual workflow end to end, buy the package. If the demo keeps saying "you would handle that outside the system", that phrase is the spreadsheet sprawl being reinvented, and it is the moment to consider a system built around your work instead. We wrote a fuller guide to that decision and a plainer one on the sprawl itself.

Common questions