Latent Works /
Understand the process before building anything.
The first job is to find out how the process really runs, including the steps nobody wrote down.
- 01 / Understand
The process as it runs.
We map the spreadsheets, handoffs and checks, including the knowledge that sits with one person.
- Start with
- The people doing the work, the source records and the steps that cause friction.
- Make visible
- Where information comes from, how it changes and who checks it.
- 02 / Agree
Limits agreed together.
Compliance, legal and the business owner agree what is allowed, who approves it and what evidence each output needs.
- Before data moves
- Agree the permitted data and tools, access boundaries and approval responsibilities.
- Before building
- Set out the scope, what the output must demonstrate and how it will be checked.
- 03 / Deliver
Checked work. A named owner.
Modular, cloud-hosted software with readable code, checked outputs and a named owner for everything that goes live.
- Check the result
- Compare the output with the agreed acceptance checks. Where a spreadsheet is being replaced, run the new and existing versions alongside each other.
- Agree the handover
- Make ownership, documentation and any ongoing support arrangements explicit in the engagement scope.
Show the evidence.
Name the owner.
We treat work as finished once the output has been checked, not when the code first runs.
If something is late or wrong, we tell you straight away, with the evidence and the fastest fix.