IT EXPERT-PK

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

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

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

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: Unplanned downtime had become our single largest cost driver and our data showed that predictive maintenance could address the majority of it — if we had the right infrastructure to act on 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.