Data, decisions & AI automation

Turn what you already record into decisions you can act on.

The data exists. It sits in five systems that disagree, and nobody trusts the numbers enough to decide anything with them. Meanwhile staff retype the same information between screens and read documents by hand — work a machine has been able to do for two years.

HOW YOU KNOW

You have this problem if…

If none of these sound like your organisation, this is probably not the domain you need — and we will say so rather than sell you into it.

  • !The monthly board pack takes a week of somebody's life to assemble
  • !Staff retype information from one system into another as a job description
  • !Two departments quote two different numbers for the same thing
  • !Documents pile up waiting for a human to read and key them in
WHAT WE BUILD

Systems we have built in this domain.

WHO ARRIVES WITH THIS

Leadership teams flying blind. Operations drowning in manual data entry. Organisations reporting to regulators, boards or donors.

  • Data pipelines and a warehouse that reconciles your systems into one truth
  • Executive and operational dashboards with numbers people actually trust
  • Regulator, board and donor reporting generated instead of assembled
  • Document processing with AI — invoices, IDs, forms, contracts, receipts
  • Classification, triage and routing that removes queues of manual sorting
  • Forecasting for stock, cash, demand and risk
  • AI assistants answering questions over your own data, with the audit trail intact
TYPICAL STACK
PythonPostgreSQLClaude APIVector searchScheduled pipelinesMetabase / custom dashboards

The stack is a consequence of the problem, not a preference. Where you already run something else, we work in what you have rather than forcing a rewrite you did not ask for.

HOW IT RUNS

Scoped before it is priced. Written down before it is built.

Every engagement in this domain starts the same way: a paid technical discovery that ends in an architecture, a fixed scope and a fixed price. You own that document either way.

01

Technical discovery

1–3 weeks · Fixed fee

Every engagement that involves building something new. This is where we start.

02

Fixed-scope build

Scoped in discovery · Milestone-based

A defined system with a clear boundary: a core platform, a payments engine, a mobile product.

03

Embedded engineering

Monthly, rolling · Per engineer, per month

Organisations with a technical team that needs depth, speed or a skill they do not have in-house.

04

Run & evolve

Ongoing · Monthly, under an SLA

Any system the organisation now depends on, whether we built it or inherited it.

Tell us what is breaking. We will tell you what it would take to fix it.

Bring us the problem