Why the contractor model wasn't enough

Before JJPH stepped in, the client had done what many organisations do when facing a complex programme: they hired an experienced contractor and hoped the expertise of one individual would be sufficient to manage the complexity.

It rarely is. Not because contractors aren't skilled, but because a single person working without institutional backing, without a delivery system behind them, and without formal accountability structures simply cannot carry the full weight of a multi-market technology transformation. When difficult situations arise, and in a programme of this scale they always do, there is no structure to absorb them. Decisions stall. Relationships fracture. Progress stops.

This is the gap that PMaaS was built to fill.

Triage first, planning second

Within days of being engaged, JJPH's Project Manager was embedded directly inside the client's business. The first two weeks were entirely focused on understanding what had gone wrong and what needed to happen to recover.

That meant a full health assessment across all four market workstreams, mapping stakeholders, identifying requirements gaps, reviewing the status of the implementation partner relationship, and rebuilding the risk register from the ground up. By the end of week two, the executive team had something they hadn't had in months: a clear picture of where the programme actually stood, and a credible path forward.

For many of them, it was the first time they felt confident the programme could succeed.

Resetting the relationship with the implementation partner

One of the most significant issues JJPH inherited was the deteriorated relationship between the client and their external technology partner. Without strong independent delivery leadership, the engagement had become transactional and adversarial. Accountability was blurred. Reporting was inconsistent. Neither party was performing at their best because neither party had clarity on what was expected of whom.

JJPH stepped into that space as the client's independent delivery authority, not replacing the implementation partner, but providing the coordination layer that had been missing. We rebuilt a clear RACI, worked with the client's commercial team to reset the scope of works, and introduced a structured engagement cadence that restored productive working relationships within four weeks.

This is something a contractor simply cannot do. Operating as a genuinely independent delivery layer, protecting the client's interests while managing external partners toward a shared outcome, requires the authority and accountability that only comes with the PMaaS model.

Building a governance framework that actually worked

The previous delivery approach had attempted to manage four distinct markets as a single global rollout, which had contributed significantly to the programme's struggles. Each market had its own regulatory environment, operational requirements, technical integrations, and commercial nuances. Treating them as one was creating conflict at every level.

JJPH restructured the programme into four dedicated market workstreams, each with its own delivery plan and accountabilities, operating under a unified governance framework that gave the executive team consistent visibility across the whole programme. Weekly steering committee reporting was introduced with clear RAG status across every workstream. Decisions that had been sitting unresolved for weeks started getting made.

Delivering four market launches, in sequence

With governance restored and the implementation partner performing, JJPH drove execution across all four markets in a deliberate sequence. Australia launched first as the anchor market, with lessons captured and applied to each subsequent launch. New Zealand followed, then Canada and the United Kingdom in parallel.

Every launch required end-to-end coordination across technical integration, user acceptance testing, content migration, payment gateway configuration, logistics provider onboarding, and go-live support, across multiple time zones and with multiple external parties involved. JJPH held the delivery thread throughout.

Every market went live on schedule.

‍