Project Engagement

This is the core of how I work with organisations, and it starts in the same place every time: what's the actual pain point, and what outcome are you trying to reach? Not the RFP template, not the framework — the real problem underneath it. Everything that follows, including the scope itself, gets built from that answer, which is why no two Project Engagements look quite the same. Some run to a few weeks. Some run for months. The size follows the problem, not the other way round.

Once the problem's genuinely understood, I put a defined Statement of Work in front of you — scope, deliverables, timeline, cost — so there's no ambiguity about what you're buying before you buy it. This is also where P.A.C.E., the framework I've built from over two decades of doing this work, earns its keep: Payments & Portfolio Management, Architecture, Commercialisation and Execution, run as four genuinely connected disciplines rather than four separate workstreams that happen to share a cover page.

What it typically looks like

• Running or advising an RFP process, from requirements through to vendor selection

• Technology and platform selection — payment gateways, acceptance infrastructure, core processing

• Platform and architecture audits: what you actually have, what it's really costing you, and what to do about it

How it runs Scoped, agreed and delivered against a defined Statement of Work — structured as genuine project consulting. You know what you're getting, and when, before we start.

Tell me the problem, and I'll tell you honestly what solving it actually requires.

Get in touch to discuss this option