S / 17Services index

Vol. 03

Twelve services,
one workshop.

Each entry below is written from experience. If a service is listed, it is one we regularly deliver; if it is not, we do not offer it. The same small group of engineers is responsible for the whole practice.

Extreme close-up of copper traces on a printed circuit board illuminated in warm red — Fig. S — Trace, contact, tolerance

Service 01 / 12

Custom Software Development.

01 of twelve

What it includes: Domain modelling, backend and frontend engineering, integrations, deployment and long‑term maintenance of bespoke applications.
Common business use cases: Operational systems that no off‑the‑shelf product covers well; internal tools that need to encode a company's own way of working; specialised workflows in regulated or high‑volume domains.
Typical project stages: Discovery workshops and written architecture; small deployable slices behind feature flags; hardening under realistic load; production rollout and operational hand‑over.
Technical considerations: Choice of language and framework driven by the domain, not by the calendar. Emphasis on explicit interfaces, isolated failure modes and observability from day one.
Expected business value: Software that fits the business exactly, remains understandable as it grows, and can be operated by the client team without ongoing dependence on the original authors.

Service 02 / 12

Web Application Development.

02 of twelve

What it includes: React‑based applications, server‑rendered sites, progressive enhancement, authentication, accessibility and performance work.
Common business use cases: Customer‑facing portals; back‑office consoles; multi‑tenant SaaS interfaces; migrations from legacy front ends that have become difficult to change.
Typical project stages: Interaction and information design; component system; incremental delivery of user journeys; accessibility and performance audits; production release.
Technical considerations: TypeScript, React, Next.js and TanStack. Design tokens and typography treated as engineering artefacts, not afterthoughts.
Expected business value: Interfaces that are fast, accessible, testable, and pleasant to extend for the next team that inherits them.

Service 03 / 12

Enterprise Systems.

03 of twelve

What it includes: Line‑of‑business platforms integrating identity, finance, operations and reporting across an organisation.
Common business use cases: ERP‑adjacent workflows; case management; internal marketplaces; systems that connect several existing tools into one coherent process.
Typical project stages: Stakeholder mapping; data ownership analysis; phased build that replaces existing tools one workflow at a time; long tail of user adoption.
Technical considerations: Strong emphasis on identity, authorisation, audit and reporting. Event‑driven architecture where appropriate; boring, transactional systems where not.
Expected business value: A single, coherent surface for internal work, with a data model the organisation can rely on for reporting and compliance.

Service 04 / 12

Cloud Solutions.

04 of twelve

What it includes: Architecture, migration, provisioning and operation on AWS, GCP, Azure and Cloudflare, with cost and reliability as first‑class concerns.
Common business use cases: New systems that need a resilient production footprint; migrations from on‑premise or single‑region deployments; consolidation of unmanaged cloud sprawl.
Typical project stages: Landing‑zone design; environment and account topology; infrastructure as code; workload migration; observability and cost baseline.
Technical considerations: Terraform, Pulumi and platform‑native primitives. Segmented networks, private connectivity, and reproducible environments from the first commit.
Expected business value: Cloud footprint that is documented, reproducible and cost‑visible, and that can be handed to internal operations without a hidden knowledge tax.

Service 05 / 12

API Development and Integration.

05 of twelve

What it includes: Public and internal APIs, versioning, contract testing, third‑party integrations and long‑running message pipelines.
Common business use cases: Opening a system to partners; consolidating a fragmented internal API surface; integrating with payment, identity, logistics or industry‑specific providers.
Typical project stages: Contract design and review; specification (OpenAPI or gRPC); reference client and server; conformance testing; documentation and change process.
Technical considerations: REST, GraphQL, gRPC and event streams, chosen by workload. Explicit contracts, backwards‑compatible versioning, and generated clients where they help.
Expected business value: Interfaces that other teams can build against with confidence, and that can evolve without breaking the integrations already in production.

Service 06 / 12

DevOps and Infrastructure.

06 of twelve

What it includes: Delivery pipelines, environment management, secrets, observability, incident tooling and paved paths for internal teams.
Common business use cases: Organisations whose deploys have become slow or risky; teams that want on‑call to be sustainable; companies moving from manual releases to continuous delivery.
Typical project stages: Assessment of current pipeline and incident history; pilot on one service; extension across the estate; internal enablement.
Technical considerations: GitHub Actions, Argo, Terraform, OpenTelemetry, Prometheus, Grafana. Preference for open, replaceable components.
Expected business value: Deploys that are boring, incidents that are informative, and an on‑call rota that engineers can live with.

Service 07 / 12

Software Modernisation.

07 of twelve

What it includes: Assessment, incremental refactoring and re‑platforming of systems that have outgrown their original design.
Common business use cases: Applications whose changes have become slow, risky or expensive; systems on unsupported runtimes; ownership transfers where the original team is no longer available.
Typical project stages: Reading the code and the incident history; drawing an honest current architecture; sequencing changes that keep the system running while it is transformed.
Technical considerations: Strangler patterns, contract tests around legacy boundaries, and a strong bias toward changes that can be shipped in small, reversible increments.
Expected business value: A system that continues to serve the business while it is being modernised, with each change leaving the codebase more understandable than it found it.

Service 08 / 12

Data Engineering.

08 of twelve

What it includes: Data modelling, ingestion pipelines, warehouses, analytics interfaces and the operational discipline to keep them trustworthy.
Common business use cases: Organisations whose reports disagree with each other; product teams that need reliable event data; regulated environments where data lineage matters.
Typical project stages: Source‑of‑truth mapping; canonical schemas; ingestion pipelines with tests and monitoring; consumer interfaces (SQL, notebooks, APIs).
Technical considerations: PostgreSQL, ClickHouse, Kafka, DuckDB, dbt‑style transformations. Emphasis on schema discipline over tool proliferation.
Expected business value: Data that decisions can actually be based on, with a clear lineage from source to report.

Service 09 / 12

Cybersecurity Consulting.

09 of twelve

What it includes: Threat modelling, access design, secrets management, cryptography reviews, incident preparation and secure development practices.
Common business use cases: Products approaching a first serious security review; systems that handle personal or financial data; organisations preparing for compliance work such as ISO 27001 or SOC 2.
Typical project stages: Threat modelling; access and identity review; secrets and cryptography assessment; remediation plan; verification.
Technical considerations: OAuth 2.1, WebAuthn, hardware‑backed keys, SOPS, Vault. Preference for standards over bespoke schemes.
Expected business value: A security posture that can be explained, audited and defended, and that is compatible with continuing to ship product.

Service 10 / 12

Quality Assurance.

10 of twelve

What it includes: Test strategy, automation, exploratory testing, performance testing and release criteria that the team can actually meet.
Common business use cases: Teams whose release cadence is limited by test friction; products approaching a scale where manual testing no longer covers the risk; migrations that need a safety net.
Typical project stages: Risk mapping; test pyramid design; automation of the highest‑value paths; performance baselines; ongoing exploratory testing.
Technical considerations: Playwright, Vitest, Pytest, k6 and contract testing frameworks. Tests are treated as production code.
Expected business value: A release process that is trusted by engineering and by the business, and a defect profile that trends downward over time.

Service 11 / 12

Technical Consulting.

11 of twelve

What it includes: Architecture review, technology selection, hiring support, due diligence and second‑opinion engagements.
Common business use cases: Investment decisions; new‑platform selections; disagreements inside an engineering organisation that benefit from an outside view; interim technical leadership.
Typical project stages: Scoping conversation; document and system review; interviews; written recommendation with trade‑offs; follow‑up as required.
Technical considerations: Not tool‑specific. The deliverable is written analysis and a decision that the client can act on.
Expected business value: Independent, technically grounded advice, delivered in writing, without a downstream product to sell.

Service 12 / 12

Ongoing Software Support.

12 of twelve

What it includes: Long‑term maintenance, dependency and platform upgrades, incident response, and small change requests for systems already in production.
Common business use cases: Systems whose original team has moved on; internal tools that need a permanent home; products that require guaranteed response for critical incidents.
Typical project stages: Hand‑over and knowledge capture; service level definition; ongoing maintenance windows; scheduled review of dependencies and security posture.
Technical considerations: Whatever the system is built on. Support engagements are staffed with engineers who take the time to understand the code before changing it.
Expected business value: A predictable, documented arrangement for keeping important software healthy over years, not weeks.

Twelve services, one workshop.