Conquest Capital

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

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 trading platform had been extended incrementally for seven years. Latency was degrading, technical debt was compounding, and a clean rebuild was no longer optional.

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: Warehouse management inefficiencies were adding cost and introducing errors at a rate that was becoming visible to clients. A modernised WMS was the agreed solution internally — we needed a partner to build it.

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: Warehouse management inefficiencies were adding cost and introducing errors at a rate that was becoming visible to clients. A modernised WMS was the agreed solution internally — we needed a partner to build it.

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.

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

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

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: Multi-touch attribution across our media mix had become the most-requested capability from every client in our portfolio. We could not deliver it without rebuilding our data layer.

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: Our growth into new markets required a multi-currency, multi-language commerce platform that our previous vendor had promised but never delivered.

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 dealer network management system had not been meaningfully updated in eight years and was actively impeding our ability to support our distribution partners effectively.

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: We needed to connect our factory floor systems to our ERP to give operations management real-time visibility into production status, waste, and throughput.

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.