An account checker for B2B billing and recoveries.
A Deliver better product, built during the LSE AI Leadership programme: it runs the pre-recoveries checks any B2B biller needs — still trading, still at that address, bill accurate and enforceable — and leaves the decision with a person.
- The role
- Built it end to end — the idea, the design and the build — as part of my studies during the LSE AI Leadership course
- Status
- A Deliver better product, available to demo on request;
- Capabilities
- AI · Projects
The problem it solves
Before any B2B organisation acts on an overdue account — chases a debt, sends a letter before action, starts recoveries — someone has to be sure of the basics: the company still exists and is still trading, it’s still at the address you hold, and the latest bill is accurate and enforceable.
In most organisations those checks are manual, scattered across teams and done inconsistently, which is where wrong-party chases, complaints and wasted legal cost come from. Off-the-shelf tools tend to assume you already know the customer, or deal only with the court process — not the checks in the middle that tell you whether you should be acting at all.
What it does
For a given account, the tool gathers the evidence and answers each check, showing where every answer came from. It starts with public sources: a Companies House lookup (still trading? registered office?), business and map listings to confirm the address, and a credit check.
With the right access, it can also read an organisation’s own systems to confirm an accurate, current bill has been produced and sent, check deliverability, and sense-check the latest bill against expected consumption — flagging where fresh information is needed before a reliable bill can be relied on.
Where it can’t confirm something, it says so and hands it to a person. It helps someone decide; it doesn’t decide for them.
How it was built
A Deliver better product, built during the LSE AI Leadership programme using Claude and Claude Code with a set of public and system APIs.
It was built on public data first, which proved the approach without needing anything sensitive, and designed so any organisation can connect its own customer and billing data to run the same checks against real accounts before collections or recoveries.
What it means
You catch problems before the letter before action, not after: confirm the company still trades and is where you think it is, and that the bill is accurate and enforceable, so you’re not chasing the wrong party or the wrong amount. Because the checks belong across the whole customer life, running them earlier keeps data clean the whole way through.
The software is the quick bit. If a tool like this can't do the job on your data, that's a data problem, not an automation opportunity — worth knowing before you buy anything.
Related services and insights.

Deliver better AI
See the service →
Deliver better Projects
See the service →
Your AI problem is probably an access problem
Read the insight →
Your human in the loop may have stopped looking
Read the insight →
The slow yes: why AI resistance rarely looks like resistance
Read the insight →Got a checking process that eats people's time?
Tell us how it works today. We’ll work out whether an AI-assisted workflow would help, and show you the one already built.