21 published figures · 8 settled · 13 with something open

Where each number actually came from.

Every figure on this site is one of two things, and the difference is marked on each one. Settled means the basis and the check are both written down, and somebody with access could work the number out again. Open means part of it is not established yet — usually the rate behind a saving, or the period it covers.

13 of the 21 figures below have something open against them, and each says exactly what. We would rather publish the gap than round it away.

The rules behind the figures

Five rules, applied to all of them.

  1. 01

    A saving starts with the client's own account of the job, not our guess at it.

    Every "this much a year" figure begins with what the business told us they were doing before we built anything: how many people, how long it took, how often. We do not model it and we do not estimate upwards.

  2. 02

    A salary-equivalent figure means salary. It does not mean anyone lost a job.

    Where a figure is a year of someone's time, it is hours removed multiplied by an hourly rate. It is what the task was costing, not a claim that a person was let go, and in most of these the person is still there doing something better.

  3. 03

    The build cost is never quietly subtracted from the saving.

    A figure on this site is the saving. What we charged is on the price list, separately, and you are free to do the subtraction yourself.

  4. 04

    If we have not measured it, the row says "not measured" rather than something plausible.

    Several of these systems run every day and nobody has sat down and worked out what changed. That is an honest state to be in and it is written down as one.

  5. 05

    Anonymous means anonymous.

    Where a client has not agreed in writing to be named, their name, their industry and every figure belonging to their business stay off this site. What we describe is the method, which is ours to describe.

Figure by figure

Every number, and what stands behind it.

PlusRooms

2 settled · 3 open

Planning applications across London, collected overnight instead of checked by hand every morning.

≈ £27,000/yr — what the checking was costing

Open
Measured
A year of the working day that used to go on checking council portals.
How
Full-time hours multiplied by an hourly rate.
Checked
Arithmetic, on top of the row below.
Still open
Which rate and how many working weeks. £27,000 over 46 weeks at 37.5 hours is about £15.65 an hour; over 48 weeks it is about £15. Nobody has written down which was used.

A full working day, every day

Open
Measured
One person's daily trawl of London council planning portals, before any of this existed.
How
The client's own description of the job: one person, one full day, every working day.
Checked
The manual check stopped when the pipeline went live.
Still open
Hours per day and days per week, and whether that person moved onto something else or the task simply ended.

120,000+ applications collected

Settled
Measured
Rows in the database, cumulative since the pipeline started.
How
Counted in the database.
Checked
A count, re-runnable by anyone with access.

97% of London boroughs covered

Open
Measured
Boroughs whose portals the pipeline reads successfully, as a share of the 33.
How
The scraper's borough list, counted.
Checked
Read off the pipeline configuration.
Still open
Whether it is 32 of 33, as at what date, and which borough is missing and why. Coverage is of boroughs, not of every application in London — some publish far less than others.

Data under 24 hours old

Settled
Measured
The scrape schedule.
How
Scheduler configuration.
Checked
Timestamps on the dashboard.

Marmadbir

0 settled · 4 open

WhatsApp dispatch for a field-services platform. Every figure here belongs to the coordinator's job, not to the field workers'.

≈ £10,000/yr of coordination time

Open
Measured
A year of the coordinator hours that the build removed.
How
Hours multiplied by a rate.
Checked
Arithmetic.
Still open
Both halves of it — the hours and the rate. Neither is written down anywhere we can point at.

Time spent handing out jobs: zero

Open
Measured
Coordinator hours spent contacting workers one at a time to allocate a job.
How
The client's description of the job before the build.
Checked
Jobs are broadcast and claimed inside the system. There is no manual allocation path left in the code.
Still open
How many hours a day it had been, how many coordinators, and whether anyone still rings a worker for an odd case.

Messaging costs down 65%

Open
Measured
What coordination messaging cost before, against what it costs now.
How
A comparison of messaging spend across the change.
Checked
Supplier invoices.
Still open
Exactly what was set against what — previous call and SMS spend against templated WhatsApp cost — and over which months. It is the messaging line only; it does not mean the business spends 65% less overall.

Double-claimed payments: zero

Open
Measured
Whether two workers can be paid for the same job.
How
The claim is race-safe and confirmed inside the system.
Checked
The code path. There is no manual reconciliation step in it.
Still open
Whether a back-office spreadsheet exists outside the system that nobody mentioned.

Punthub

1 settled · 2 open

Our own product, built and owned by us. That makes it easy for us to verify and easy for you to discount, and both of those are true at once. It is evidence of what we can leave running unattended, not evidence that a client paid for it.

£13,000+/yr of running costs, gone

Open
Measured
Running costs that stopped once the pipeline replaced what came before it.
How
Not written down.
Checked
Not documented.
Still open
What the costs actually were — a part-time operator, a data supplier, a hosted service — and the sum behind the figure. This is the least substantiated number on the site and we would rather say so than dress it up.

Nobody touches it

Open
Measured
Human involvement in the nightly run.
How
The scheduler runs collection, the models, the cross-checks and the publish without anyone intervening.
Checked
Run logs.
Still open
Over what stretch of time zero interventions was actually observed.

6 data sources, 7 models, 21 nightly checks

Settled
Measured
What the pipeline is configured to do each night.
How
Counted from the configuration.
Checked
Counted again from the run logs.

A Story To Tell

3 settled · 1 open

A stalled platform picked up from a previous agency, gone through properly before anything new was built.

22 problems found

Settled
Measured
Findings raised going through the existing code, before building anything.
How
Counted from the written findings list.
Checked
Each one traced to the file and the line that caused it.

All 22 checked before invoicing

Settled
Measured
Findings re-verified against the code before they appeared on an invoice.
How
Every item on the list was reproduced before it was billed for.
Checked
The findings list against the commit history.

Scoped brief delivered within a week

Open
Measured
Elapsed time from the agreed scope to handover.
How
Dates on the engagement.
Checked
Commit history.
Still open
The exact start and end dates, which nobody has written down against the invoice.

Way past the login closed in week one

Settled
Measured
Time from finding the access problem to the fix being live.
How
Dates on the fix.
Checked
Commit history.

Anonymised — group of two trading entities

1 settled · 2 open

The client has not agreed to be named, so their name, their industry and every figure belonging to their business stay off this site. The numbers below are about the reconciliation itself, which is our method rather than their business.

55 of 97 cost centres checked and matching

Open
Measured
Cost centres where our figure agrees with the accounting system's own report.
How
Compared line by line against the accounting system's report.
Checked
Re-runnable against a fresh export.
Still open
Why the other 42 are not matched — most are cost centres with no activity in the period rather than disagreements — and that distinction is not yet written into the dashboard.

Agreement to within 1 penny

Settled
Measured
The tolerance at which a cost centre counts as matching.
How
A threshold set in the reconciliation.
Checked
Read from the code.

1,090 invoices accounted for, both sides

Open
Measured
Invoices present and matched across both sets of books.
How
Counted during reconciliation.
Checked
Counted again from a later export.
Still open
The date of the export this count came from.

Anonymised — law firm

1 settled · 1 open

In testing, not live, and offered as nothing more than that. A qualified solicitor still reads everything before it goes anywhere.

Made-up references: zero

Open
Measured
Invented case citations in the drafts produced during testing.
How
Every citation is checked back against the documents the solicitor uploaded; anything unverifiable is flagged on the page rather than written as fact.
Checked
Tested against two purpose-built case files with known defects planted in them.
Still open
Zero across the testing done so far, which is two case files and three model tiers. It is not a guarantee about every future document, and we will not describe it as one.

Time saved: not yet measured

Settled
Measured
Nothing. This is the honest state of it.
How
No measurement has been taken.
Checked
Not applicable.
Two things not on this site

Work that is in testing is labelled in testing. The drafting assistant for a law firm is running on real matters and is not offered as proof of anything, because nobody has measured what it saves.

Work that is still being built says so. The matching engine has a database and a scoring step and no matching yet. We will publish how well it works when there is something to publish.

There is no star rating anywhere on this site and no review markup in its code. We do not mark up claims about ourselves that nobody independent can check. The work pages carry the same figures with a link to each business instead.