02
Platform build and modernisation
Engineering delivery, in phases that each stand alone. Every phase ends with something running in production and something you could hand to another team.
Commercial terms
Fixed-fee phases. The readiness diagnostic defines the phases and their order; without it, the first phase is discovery. Each phase is separately priced and separately decidable.
Not the right fit if
- A request to add capacity to a design that is already failing structurally
- Staff augmentation — this is a scoped delivery, not bodies by the hour
- A pure cloud-migration exercise with no data or reporting problem behind it
The problem
Claims and financial platforms accumulate a second system alongside the first: scheduled shell scripts that replicate data, reconcile invoices and produce partner reports, understood by one person and documented nowhere.
That estate works until it does not. A schema change breaks a script silently, a report drifts, and the only way to find out is a customer complaint.
Replacing it in one heroic migration is how projects fail. This is delivered in phases, each of which reduces risk on its own.
What we actually do
- Change-data ingestion from operational systems into a warehouse, with schema history preserved
- Warehouse and semantic-layer modelling: facts, dimensions and the views the business actually queries
- Orchestration that replaces cron and shell: dependencies, retries, alerting on staleness and failure
- Partner, OEM and reimbursement reporting delivered as scheduled files, reconciled against source
- Migrations paired with tested rollbacks, and restores rehearsed and timed
- Access control designed as roles and row-level policies, not a shared connection string
What you get
What you get.
Everything produced is written down and handed over. Nothing lives only in someone's head, and nothing depends on us to keep running.
- A working ingestion and transformation pipeline, deployed and monitored
- Documentation of the model and the pipeline graph, in the repository rather than a wiki
- A reconciliation report proving the new path matches the old one before the old one is retired
- A retirement plan for the legacy estate, sequenced so nothing depends on a big-bang cutover
- Runbook for the failures that actually happened during delivery
Who it is for
Next step
A thirty-minute scoping call. Bring the problem rather than a specification.