Despark

Project summary: Our agents were spending more time managing data across disconnected systems than managing relationships. We needed a unified platform to give them that time back.

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.

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: Our internal product thinking was strong but our execution capability in this specific technology domain was limited. We needed depth, not generalism.

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: Our agents were spending more time managing data across disconnected systems than managing relationships. We needed a unified platform to give them that time back.

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: 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.

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: 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 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: An international expansion required multi-currency, multi-language, and multi-warehouse capabilities that our existing platform could not support without a fundamental re-architecture.

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: 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.

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 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.

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: 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.

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.

The engagement started with a discovery workshop that immediately signalled this team was different. They pushed back on two of our assumptions in the first session with evidence and a better alternative. That kind of intellectual honesty is rare and it set the tone for the whole project. Deliverables were consistently ahead of schedule, code reviews were taken seriously, and the final product is something we are proud to show enterprise clients during due diligence calls.

Project summary: An international expansion required multi-currency, multi-language, and multi-warehouse capabilities that our existing platform could not support without a fundamental re-architecture.

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.

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: Guest experience scores had plateaued and our data showed that friction in the pre-arrival and in-stay digital journey was the primary cause — we needed a purpose-built guest app.

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.