Skip to content

HomeProof

Built, running, measured

Three systems in production, written as problem, system and numbers. Anonymised at the clients’ request. Named references are available on the call.

Start with a fixed-price pilotSee the live one

Fixed price. Credited in full against a build.

An empty chair at a meeting table, an untouched glass of water and a closed folder in front of it

Case 01Financial services · back office

Document & QR extraction pipeline

Placeholder · not for release
Document captureQR extractionValidation rulesHuman reviewSystems integrationAudit trail
A scanner mid-pass over a stack of mixed paper documents
The problem

A back office was losing afternoons to manual data entry from scanned documents. Every question that touched a document meant someone finding it, reading it, and re-typing what they found into another system.

The cost never appeared anywhere. It showed up as slow answers and as capable people doing clerical work.

The system

Documents arrive exactly as they did before. The system extracts the fields, validates them against the rules the business already applies, and flags anything missing or inconsistent rather than guessing.

A person reviews and approves. Approved information moves into the business systems automatically.

How it runs6 steps
  1. Documents received
  2. Information extracted
  3. Details validated
  4. Structured output prepared
  5. Human review
  6. Business systems updated

This is where your team decides

The results
Minutes, not daysturnaround on document-bound questions
Zero silent errorsexceptions are flagged rather than passed along

Case 02Professional services · marketing

Multi-client content production system

Placeholder · not for release
Brand voice modellingResearch pipelineDraft generationFact checkingEditorial approvalMulti-client scaling
An editor's desk with two monitors showing draft layouts for different brands
The problem

One team was producing branded content across many clients. Quality held as long as the same person did the work, and drifted the moment it did not.

The system

Research, drafting and checks were systematised against each client’s own material and tone. Editorial judgment stays entirely human. Nothing publishes without an editor approving it.

How it runs6 steps
  1. Brief received
  2. Source material gathered
  3. Draft prepared
  4. Brand & fact checks
  5. Editor approves
  6. Published

This is where your team decides

The results
Many clients, one teamproduction capacity without added headcount
Consistent voicequality no longer depends on who is available

Case 03Media · production

AI audio generation stack

Placeholder · not for release
Audio generationSource approvalQuality checksProducer reviewOwn-account deployment
A producer in headphones reviewing a long audio timeline in a studio
The problem

Long-form audio was taking hours per finished piece, most of it production work rather than judgment.

The system

Audio is produced from approved source material, on the client’s own accounts, with review checkpoints before anything ships. Nothing reaches an audience without a person signing it off.

How it runs5 steps
  1. Source material approved
  2. Audio generated
  3. Quality checks
  4. Producer reviews
  5. Published

This is where your team decides

The results
Hours down to minutesper finished piece
On their own accountsno lock-in, full audit trail

The fourth one is on this page

The assistant answering your questions here is system 1b, live, running on the same stack we would build for you. It is the only case study you can test yourself before speaking to anyone.

Ask it something difficult
Visitor

Can extraction run on our own accounts, with an approval step before anything is filed?

Assistant

Yes. Everything runs on your API keys and your infrastructure, and a human review step sits before anything writes into a business system. Roughly how many documents a week are we talking about?

Placeholder · not for release

See one running on your own business

The pilot puts a working system on one real workflow or one acquisition gap, so the next case study is yours rather than someone else’s.

Start with the pilot, or ask the assistant anything first.

Start with a fixed-price pilotAsk the assistant first

Fixed price. Credited in full against a build. If the honest answer is no, we’ll tell you.