Software engineering and IT consulting, delivered against a written scope

We take a written specification and deliver working software against it. Engagements are scoped as fixed-scope phases with named deliverables, so the client can see what has been produced before the next phase starts. Work covers browser applications, cross-platform mobile clients, and the HTTP and message-driven services behind them, including database design, background processing and the automated tests that keep a release repeatable.

A consulting engagement produces a document, not an opinion in a meeting. We read the code, the infrastructure definitions and the incident history, interview the people who operate the system, and return a written assessment: what the architecture actually is, where it constrains the business, what it costs to run, and the options with their trade-offs stated plainly. Recommendations are ranked by effort and risk so the client can decide what to act on.

We build and hand over the operational layer: environments described in Terraform so they can be rebuilt, container images and deployment manifests, pipelines that test and ship on merge, and the metrics, logs and alerts that make a production incident diagnosable. Integration work connects ERP, CRM, billing and partner systems through documented interfaces with retry, idempotency and reconciliation designed in rather than added after the first failure.

Rewrites that stop the business are not modernisation. We work incrementally: characterise the existing system and its data, put an interface in front of it, move capability out behind that interface in slices, and keep both paths running until the old one has nothing left to do. Data migration is treated as an engineering deliverable in its own right, with reconciliation reports proving that what arrived matches what left.