Consultancy
Advice on architecture, delivery and why the software isn't shipping.
Advice you can act on
Sometimes the right first step is not a build. It is an honest read on the system you have, the delivery that has stalled, or the decision that will be expensive to unmake later. Our advice stands on having run these problems, not on having read about them.
If you know which decision you are facing, start there. If you only know that something is wrong, start with Delivery Diagnosis.
Architecture
Which platform, which boundaries, buy or build: the decisions that are expensive to change once software is live. We help you make them with the trade-offs in the open, and put the reasoning in writing so it outlives the project.
More on ArchitectureSoftware Delivery
Release day is the day the organisation dreads. We design the process that changes that: branching, releases, environments and testing, built to be followed and boring on purpose.
More on Software DeliveryBusiness Analysis
Nobody has written down how the operation actually runs, or scoped the work properly. We get it out of people's heads and into requirements a team can build from.
More on Business AnalysisDelivery Diagnosis
For when software is late and nobody can say why. We look at the codebase, the process and the team, name the real blocker, and give you a plan you can run with or without us.
More on Delivery DiagnosisSee all four case studies, including the three above.
Where the advice comes from
We tell them as they happened, because the method in them is the one we bring.
Making releases boring at a UK high-street retailer
A major retailer was rolling back 45% of its e-commerce releases. Merge-time feature gating and one shared release process took deployment success to 95%, and the tooling built to run it is still the core of that process ten years on.
Read the retail case study72,000 households, one regulator's deadline
A rule change extended compost collections to every household in the country. A team of three analysed a 310,000-customer base, resourced the collection rounds and ran the rollout to 72,000 of them inside the regulator's 12-month deadline.
Read the rollout case studyHalving the invoicing behind 310,000 customers
A national operator was billing through 10 to 12 billing types and thousands of separate prices for the same services. Consolidating them cut manual invoicing from 20 hours a week to 10, and became a review that has run every year since.
Read the billing case studyFive stalled branches to a release every six weeks
A rail technology supplier had five features finished, five branches, and no release in months. A gated release process shipped five releases in the following six months.
Re-architecting a monolith for 99.999% availability
A call-recording software vendor had won banking business its architecture could not sustain. A ground-up rebuild on event sourcing gave it a platform designed for 99.999% availability and thousands of simultaneous calls.