Dreamoval Ltd.

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.

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

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

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.

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: 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: Track-and-trace capability had gone from a differentiator to a table-stakes requirement and our platform had neither. We needed to close the gap before our next enterprise tender cycle.

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.

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

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

What made the most difference in practice was the quality of the engineering judgment on this team. Not the ability to execute a specification — that is a baseline expectation. The ability to recognise when a specification was suboptimal, explain why, propose an alternative, and support the client in making a decision about it. That consultative dimension elevated the output beyond what the brief described and resulted in a product that is more fit for purpose than the one we had originally specified.

Project summary: Digital service standards required all citizen-facing applications to meet accessibility and performance benchmarks that our inherited systems failed. Remediation was not viable — we needed a replacement.

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 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 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: Dynamic pricing had been a manual process for years. We knew the revenue management opportunity was significant but lacked the technical capability to build the models and connect them to our booking engine.

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.