The Engagement Blueprint
This is the five-phase structure we teach inside the program for shaping an analytics engagement from first conversation to renewal. It's shared here as a reference, not a template to fill in blindly. Every client relationship bends it a little.
Why a blueprint at all
Most scope creep starts before the project does
A lot of engagement problems, the ones that show up later as unpaid extra work or a client who quietly stops trusting your recommendations, trace back to something that never got defined at the start. Not because anyone was careless. It's just easy to skip the structural questions when a client is excited to get started and you're excited to get paid.
The blueprint below is the version of that structure we work through with cohort members, phase by phase, against their own real proposals.
Framing the ask
What the client says they want and what they actually need are frequently two different things. This phase is about a short set of framing questions before any analysis starts: what decision is this supposed to inform, and what happens if the answer comes back inconvenient?
Scoping the deliverable
Defining format, boundaries, and what's explicitly out of scope. A one-page scope document that both sides sign off on tends to prevent more disputes than a lengthy contract nobody rereads later.
Structuring check-ins
Deciding cadence and format ahead of time, rather than reacting to whatever the client asks for mid-project. Weekly async updates, a biweekly call, or a milestone-based structure, chosen deliberately based on project length and client involvement.
Translating the analysis
Reporting formats that read as decisions rather than data dumps. This is where the recommendation memo structure from the program gets applied directly to a real client deliverable.
Closing or extending
How the engagement ends, or how it evolves into something ongoing. Planning this conversation ahead of time, rather than improvising it in the final week, changes how it tends to land.
How it's used in the program
Applied to your own pipeline, not a case study
During weeks five and six, cohort members bring a real upcoming proposal or an engagement currently in progress and run it through these five phases with feedback from the group. The goal isn't a perfect document. It's a habit of asking these questions before scope gets fuzzy, not after.
Some analysts find they're already doing three of the five phases well and just need language for the other two. Others rebuild their entire proposal template around this structure. Both are common outcomes.
Want to walk through the blueprint against your own work?
That's exactly what weeks five and six of the program are built for. Get in touch if you'd like to know more about how it fits your current client mix.
Ask a question