What the day must produce
The session is a decision workshop. It ends with seven outputs: a core value proposition, three message pillars, ideal-customer boundaries, an alternatives map, a claims register, a talk track with objection responses, and a one-week validation plan. A pleasant conversation that produces none of these is a failed session.
Decision rules in force all day
- Evidence beats preference. If it can't be shown, proven, demonstrated, or explained plainly, it cannot become a leading claim.
- The Decider decides. When debate runs long, the Sponsor/Decider makes the call.
- Every promise needs a boundary.
- No unsupported elegance. Pretty language without proof is discarded.
- The value proposition becomes the control system. Website copy, collateral, and talk tracks will eventually map back to it. It is not a tagline, and the day does not produce one.
Required roles in the room
- Sponsor / Decider — makes trade-offs; decides what leads and what stops leading; prevents the session from becoming an admiration exercise.
- Revenue Voice — brings market reality: what people ask, misunderstand, compare, hesitate over, and what causes them to buy.
- Delivery Voice — protects feasibility; flags promises that sound good but create operational risk.
Keep the room small enough to decide. Too many voices slow the work and soften the conclusions.
The day
| Time | Segment | Purpose |
|---|---|---|
| 0:00–0:15 | Welcome, decision rules, definition of done | Align the room around outputs and authority |
| 0:15–0:45 | Language wall | Capture customer triggers, fears, questions, misunderstandings, and desired outcomes — in customers' words |
| 0:45–1:15 | Offer hierarchy | Sort every offer into core, growth, supporting, or distracting |
| 1:15–1:45 | Alternatives ladder | Identify what customers choose instead, and where those options fail |
| 1:45–2:15 | Ideal customer boundaries | Define best-fit, non-fit, and refer-out customers |
| 2:15–2:30 | Break | Reset |
| 2:30–3:15 | Message pillar build | Select three differentiators; define promise, mechanism, proof, and boundary for each |
| 3:15–3:45 | Draft value proposition live | One sentence and one paragraph, built from the day's decisions |
| 3:45–4:20 | Claims register | Approve, qualify, or remove claims; assign proof owners |
| 4:20–4:45 | Talk track and objections | Build staff-ready language and responses to the top objections |
| 4:45–5:00 | Validation plan and assignments | Define the one-week test and who owns it |
The standard at close
The session succeeds only if it produces decisions. A prettier description of the business is not enough. The output is a clearer business system: one lead story, stronger audience focus, cleaner claims, better proof, and messaging staff can actually use.
The first version of the value proposition is treated as a testable hypothesis, not a finished artifact. The one-week validation loop — using the language in real conversations, logging what customers repeat back, what confuses them, and what objections recur — produces version two.