The method
The Captivate Framework
Four stages, one accountable team, in this order: Clarify → Capture → Craft → Amplify.
Frameworks in this category usually describe a workflow. This one describes a refusal — specifically, a refusal to hand your argument to anyone who was not there when it was made.
Why this exists
The Captivate Framework was not reverse-engineered from a finished case study. It came from a failure that repeats so reliably in this industry that you can predict it: a client approves a sharp strategy, a separate production company is briefed, and what comes back is competent, expensive and one degree less true than the thing that was approved.
Nobody is at fault, which is what makes it durable. The strategist did their job and left. The crew did their job and were never told what the work was arguing. The seam between them has no owner.
Dana Reeves founded Reeves Media Group to own that seam. Every stage below exists to prevent one specific way the argument degrades — named, in each stage, as "the seam this guards."
The seam is the product.
A method built around the failure between strategy and production.
The stages
Selected stage: Clarify. Decide what you are actually saying, and to whom, before anything is produced.
Clarify
Decide what you are actually saying, and to whom, before anything is produced.
Clarify is research and argument. We work out what you know that your market does not, who specifically needs to hear it, and what claim you are prepared to defend in front of an analyst. The output is a written position, not a mood board. Everything downstream is built to serve it, and we do not move on until you can say the argument back in one sentence.
You get
- A written positioning and message architecture
- Named audience segments and the questions each one is actually asking
- The editorial argument every asset will ladder up to
The seam this guardsProduction briefs that describe a deliverable but never state a point of view.
It ends where it starts
Amplify is not a finish line. What the market does with the work — which argument travelled, which one landed flat, which question kept coming back — is the raw material for the next Clarify. Run once, the Captivate Framework produces a strong asset. Run repeatedly, it produces a position.
Seeing it run
Client work appears here only with permission from the client it belongs to, tagged to the stages it demonstrates. We do not illustrate a method with an anonymised outcome — a framework you cannot check is just a diagram.
Bring us a project you are considering and we will walk you through which stage it starts at and what the first two weeks look like.
Which stage are you actually stuck in?
Most teams think they have a production problem. More often the argument was never settled, and production is where that becomes visible. Thirty minutes is usually enough to tell the difference.