Keystone

The discovery call

Thirty minutes. No pitch. No slide deck. A structured diagnostic against the foundation of the methodology — Pre-Programme, Selection, gates, governance, testing, adoption — applied to wherever your programme actually sits.

The call is the conversation people leave saying "that was the most useful thirty minutes I've spent on this." It is also the call I won't take if it doesn't fit, because the alternative is wasting your time and mine.

01

What you get

A working diagnostic, not a sales pitch

By the end of the call you'll have:

  • A read on where your programme actually sits against the methodology — which stage it's in, which gates it's coming up to or has missed, which workstreams are governed and which aren't.
  • A specific call on the highest-risk thing about your current trajectory — not a list of generic concerns, a named risk that the conversation has actually surfaced.
  • One or two concrete suggestions for the next move — what to do this week, what to put in front of your Steering Committee, where to push back on your SI.
  • An honest answer on whether further engagement makes sense — sometimes yes, sometimes no, sometimes "you don't need me, you need someone else."

The methodology is published openly. The Command Centre is free to use. The call is where judgement gets applied to your specific programme — and judgement is the asset.

02

Who it's for

If your programme looks like this

  • Multi-site, multi-OpCo, mid-market or upper-mid-market organisation (typically £100m–£2bn revenue).
  • ERP or digital transformation programme — running, paused, in selection, or being scoped.
  • Often post-merger, multi-entity, or roll-up environment.
  • You're a programme sponsor, COO, transformation director, CIO, or the senior person whose name is on the line if the programme doesn't deliver.
  • You've been burned by, or are watching peers be burned by, generic SI methodologies — and you're looking for something more structured than another deck.

If you're a D365 Business Central partner, SI, or implementation practice considering adopting the methodology for your own delivery work, the call also works — different conversation, same thirty minutes.

03

Who it isn't for

Honestly, to save us both time

  • General ERP advice with no specific programme attached. The call is structured against your actual context. Without one, the conversation drifts and the diagnostic doesn't land.
  • Vendor sales conversations. If you're selling ERP software, integration tooling, change-management services or anything else, please use a different channel. This isn't the right introduction.
  • Recruitment. Not currently looking. If your context changes, that may too.
  • Free unbounded strategy consulting. The call is a diagnostic, not an open-ended advisory session. If your programme needs ongoing structured input, that's a different conversation, and we'll talk about it on the call if it fits.

No offence intended — clarity up front saves both of us the awkwardness of finding out twenty minutes in.

04

Before the call

Two things to have done

Both light:

  • Walk the Command Centre against your programme. Ten minutes is enough.
  • Identify the one most uncertain thing about your programme right now. It's usually where the diagnostic lands.

No pre-read, no NDA, no scoping form.

Pick a thirty-minute slot.

[ Calendar embed — Calendly — pick a time ]

Working hours UK time. If nothing on the calendar fits, drop me an email at [email protected] and we'll find something.

Open the calendar
05

If a call isn't right yet

Two alternatives