Capptan

Project summary: A merger had left us with two incompatible student information systems. We needed a consolidation path that preserved historical data, maintained service continuity, and met accreditation requirements.

Our stakeholder group included board members, clinical leads, compliance officers, and end users — each with different technical literacy and different success criteria. This team navigated that stakeholder landscape as well as any vendor I have seen. They adjusted their communication register depending on the audience without losing the substance. They managed expectations honestly throughout. And they delivered a system that each group can point to as meeting their requirements. That breadth is genuinely uncommon.

Project summary: Our connected vehicle platform needed to handle telemetry data from an expanding EV fleet while supporting over-the-air update orchestration. No off-the-shelf platform handled both requirements well.

I came into this engagement as a sceptic. We had been through a failed implementation with a previous vendor and I had high standards for what evidence of competence looked like before I would trust a partner with our core systems. This team earned that trust progressively — through the quality of the discovery documentation, the rigour of the technical proposals, the consistency of the sprint deliveries, and ultimately the stability of the production system. I no longer lead with scepticism when recommending them.

Project summary: A previous engagement had delivered something that worked in staging and struggled in production. We approached this project with greater rigour in vendor selection as a result.

We had worked with three agencies before this engagement. The comparison is not flattering to the others. What distinguished this team was a systematic approach to understanding the problem before proposing a solution — something that sounds obvious and is practiced far less often than it should be. The delivery phase ran to schedule, the codebase is clean enough that our internal engineers made positive comments during handover review, and we have not logged a critical incident in five months of live operation. We intend to use them for our next phase of work.

Project summary: Customer expectations had reset and our conversion funnel data showed precisely where we were losing them. We needed a commerce platform capable of delivering the experience our competitors already had.

The technical quality of the final deliverable is the easiest thing to point to. The automated test coverage is thorough, the deployment pipeline is reliable, the documentation is genuinely useful rather than ceremonially produced. But the metric I keep returning to is the number of post-launch conversations we have not had to have. No incident calls at two in the morning. No emergency patches. No retrospective discussions about what went wrong. The absence of those events is the evidence I would show to someone considering this vendor.

Project summary: Evolving open banking obligations required us to rebuild our API layer from the ground up. The architecture needed to be compliant by default, not bolted on after the fact.

We gave this team an aggressive timeline, a technically complex scope, and a client-side project team that was stretched thin and not always available at the speed the engagement required. They absorbed all of that gracefully. Where they needed input they were precise about what they needed and when. Where they could proceed independently they did. The result was a delivery that landed on time despite the constraints on our side, which I regard as evidence of genuine professional maturity.

Project summary: As a technology business ourselves we apply the same scrutiny to our vendor selection that our clients apply to us. We needed a delivery partner who could meet a standard we would be comfortable being measured against.

The integration layer was the part of the project I was most concerned about going in. Our system landscape is complex, several of the upstream APIs we relied on were poorly documented, and two third-party vendors had a history of unpredictable response times on integration questions. This team managed all of that. They documented what the upstream vendors could not, built resilience into the integration architecture where the upstream behaviour was unreliable, and delivered a solution that works as specified in production. I could not have asked for more.

Project summary: Our engineering capacity was committed to maintaining existing systems and could not absorb a net-new build of this complexity. An external partner with the right skills was the only viable option.

We had worked with three agencies before this engagement. The comparison is not flattering to the others. What distinguished this team was a systematic approach to understanding the problem before proposing a solution — something that sounds obvious and is practiced far less often than it should be. The delivery phase ran to schedule, the codebase is clean enough that our internal engineers made positive comments during handover review, and we have not logged a critical incident in five months of live operation. We intend to use them for our next phase of work.

Project summary: B2B customer churn was concentrated among accounts that had complained about portal usability. We needed a complete redesign of the self-service experience before the next contract renewal cycle.

The thing that retrospectively seems most significant is how little drama there was. Complex technology projects tend to accumulate incidents, escalations, and tense conversations. This one did not. Problems were surfaced before they became incidents. Scope changes were handled with process rather than conflict. Risks were managed rather than avoided. That level of maturity is rare in my experience and it made the delivery feel almost effortless from our side, which I know it was not from theirs.

Project summary: Claims fraud detection had been rule-based for years and we were losing ground to more sophisticated patterns — we needed a machine learning model built on our own historical data.

We ran a structured RFP with seven vendors. Three made it to the technical evaluation stage. This team won on the strength of their technical proposal, their domain knowledge, and frankly on the quality of the questions they asked us during the process. A vendor who asks good questions in the sales phase tends to ask good questions during delivery too. That hypothesis proved correct. The project is now live, performing above the KPIs we agreed, and our stakeholders are genuinely impressed.

Project summary: Claims fraud detection had been rule-based for years and we were losing ground to more sophisticated patterns — we needed a machine learning model built on our own historical data.

We ran a structured RFP with seven vendors. Three made it to the technical evaluation stage. This team won on the strength of their technical proposal, their domain knowledge, and frankly on the quality of the questions they asked us during the process. A vendor who asks good questions in the sales phase tends to ask good questions during delivery too. That hypothesis proved correct. The project is now live, performing above the KPIs we agreed, and our stakeholders are genuinely impressed.