Doing the same coverage by hand takes about 123 hours, which is why nobody had ever done it completely. This did not make the job faster. It made an undoable job happen every week.
Over twenty developer sources arrive as price lists and floor plans, in whatever shape each developer likes. The platform collects them unattended, extracts them, matches them against about 250 projects on the company's live public property portal, and writes back through a human approval gate with an audit log behind it. Twenty page routes and 152 API routes, and the people who use it are not engineers: they drag schedules on a calendar, approve or reject in a queue, and edit project details that write back to the portal.
- The hard part is dirty input, not architecture. Every developer's spreadsheet is laid out differently, and the same unit is written one way on the price list and another way on the floor plan. Matching runs on normalisation and fuzzy linkage with confidence bands, and anything under the automatic threshold goes to a person.
- A write window that is only ever open for one project. Each production write is fenced to the single project being processed and closes immediately after. If a file cannot be read it is held rather than guessed at, a file with an anomalous page count is refused, and if the vision quota runs out the system will not fall back to the weaker reader. Output identical to the input while claiming to have marked up N units is a hard error.
- Multi source reconciliation found problems nobody had reported. Comparing the price list, the marketing floorplates, the archived files and the live portal surfaced seven units carrying another building's price, and sold stock still publicly listed. The drift came from handoffs between systems rather than careless typing, so the fix was a scheduled reconciliation rather than a one off cleanup.
- I found a concurrency fault by reading a broken artefact. A scheduled job and a hand run job reached the markup stage through different entry points, shared no lock, and produced a zero byte deliverable. All paths now take one operating system level file lock.
- 35,000+
- automated writes to the live portal and Dropbox: listings created, repriced, withdrawn and relisted, plus price lists and floor plans filed
- 24
- developer sources collected unattended, reconciled against about 250 projects on the live portal
- 2,359
- price labels printed onto 505 floor plates, held back rather than published when a check fails
- 2,687
- test functions across 210 test files, a test to code line ratio of 0.71
- 803
- commits, all mine, 12 May to 26 August 2026
What it is not, because the scale invites the wrong guess: a single tenant internal platform on one machine with one SQLite database and an in process scheduler. Not multi tenant, not distributed, not microservices. It holds developer credentials and full pricing, so it is deliberately not opened up to the sales floor. Running it on a server with CI is the next thing it needs.