Bontouch

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.

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 legacy LMS had been built for a classroom-first world. Hybrid delivery had exposed its limitations and student satisfaction scores had reflected that for two consecutive years.

The project brief was ambitious and we had received proposals ranging from two to five times our eventual budget from other vendors. This team came back with a proposal that was commercially realistic and technically credible — and then delivered against it. That alignment between proposal and outcome is not something I take for granted. I have been on the other side of it enough times to know it requires both honesty in the sales process and discipline in delivery. We experienced both.

Project summary: Integration between our clinic management system and our patient-facing app had been a recurring failure point. We needed an engineering partner who could own the integration layer end to end.

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: Several years of incremental development had left us with a platform that was technically functional but strategically limiting. A structured rebuild was the agreed path forward.

Six months after go-live our platform is processing three times the transaction volume we specified in the original brief. The architecture choices made during discovery accommodated that growth without remediation work. That is the difference between a team that designs for what you tell them and a team that designs for what you are likely to need. We are in conversation about a Phase 2 engagement and I expect to be using this partnership for several years.

Project summary: Our audience data was fragmented across eight tools with no single identity layer. Personalisation had become impossible without first solving the data foundation.

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: The project had a board-facing delivery date tied to a strategic initiative. We needed a partner who would treat that date as their own, not ours.

The project brief was ambitious and we had received proposals ranging from two to five times our eventual budget from other vendors. This team came back with a proposal that was commercially realistic and technically credible — and then delivered against it. That alignment between proposal and outcome is not something I take for granted. I have been on the other side of it enough times to know it requires both honesty in the sales process and discipline in delivery. We experienced both.

Project summary: Our competitors had been investing in technology for two years and we needed to close a meaningful gap quickly without compromising on the quality of what we shipped.

Twelve weeks from kickoff to live production deployment for a project of this complexity. I would not have believed that was achievable if I had not watched them do it. The velocity came from genuine engineering discipline — clear requirements, short feedback loops, automated testing, and a team that communicated internally without the overhead that slows most agencies down. The product has been live for four months with no critical bugs and one minor patch. We are already in scoping conversations for phase two.

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.

Project governance was one of the things that impressed me most. We had a dedicated project manager who ran tight fortnightly sprints with clear acceptance criteria, a shared backlog that gave us full visibility at all times, and a change request process that was fair and transparent. Nothing slipped through the cracks, no bill shock at the end, and the final delivery matched the original scope document almost perfectly. In my experience that kind of discipline is genuinely uncommon.

Project summary: Our creative production workflow was entirely manual and we were spending more time on process administration than on ideas — automation was long overdue.

The thing I appreciate most in retrospect is that they were honest when something was harder than expected. Twice during the project the team came to us proactively to say that a particular component needed more time to do properly and explained why cutting corners would create problems later. We gave them the time. Both decisions were correct. The resulting product is solid and we have had none of the post-launch instability that plagued our last two technology projects.

Project summary: Our existing platform had grown organically over several years and the accumulated technical debt was beginning to affect both performance and our ability to ship new features.

Twelve weeks from kickoff to live production deployment for a project of this complexity. I would not have believed that was achievable if I had not watched them do it. The velocity came from genuine engineering discipline — clear requirements, short feedback loops, automated testing, and a team that communicated internally without the overhead that slows most agencies down. The product has been live for four months with no critical bugs and one minor patch. We are already in scoping conversations for phase two.