Designing Consultancy Engagements That Actually Deliver

Traditional consultancy engagements bill against activity: hours, days, workshops, slides. The incentive is to produce more activity, not better outcomes. The client ends up with a beautiful 60-page strategy document and nothing changes on the ground.

We deliberately structure PVP consultancy engagements against measurable outputs instead — implemented systems, signed-off policies, trained staff, mobilised funding. The deck is a by-product of the work, not the deliverable.

Most of our consultancy engagements run as time-boxed sprints. Four to eight weeks, one well-defined question, a written recommendation at the end. The question has to be specific enough that the client can actually act on the answer.

Vague briefs get turned into specific briefs before we sign. 'Help us grow' becomes 'Should we open a Karachi office before March, and what does the first 90 days look like if we do?' That second brief is something we can answer.

When ongoing consultancy is the right fit, we use a retainer — but every retainer cycle has its own scope and its own deliverable. The retainer isn't a licence to bill; it's a continuing commitment to ship something concrete every month.

If we get to the end of a cycle and haven't shipped, the next cycle doesn't start until we agree why. Most consultancy relationships die slow deaths because no one asks that question.

Clients who work with us this way tell us the same thing: it doesn't feel like a consultancy engagement, it feels like having a senior operator on call. That's deliberate. The structure produces the feeling.

Bring us a brief — vague or specific — and we'll turn it into something we can both commit to. That conversation is free.