Fine-tune the use casePick the one closest to you
A product program forteams facing
The product is ready to ship. Is the rest of your company?
Usually not. Engineering hits the date, the release notes go out, and Sales, Support and Marketing meet the new your product at the same time as the customers do. This program aligns what your launch teams know, believe and do before launch day, in four one-hour team sessions.
Make it for your team
Execution readinessExample scores for a team like yours. Add your website to estimate your own. Measured once your team plays. Ready at 80.
Where it usually breaks42Today88/ 100After the 4 team sessions
Ready to executeShared knowledgeHigh riskThree teams give three answers to "what changed?"
Shared convictionMedium riskThe release is seen as Product's launch, not theirs
Shared practiceHigh riskNo agreed answer to the question a customer will ask on day one
4 sessions~50 min each8–12 people per teamNo facilitatorThe gap
What you'd typically hear if five of your product people answered alone.
SESSION 1 · FILL THE GAPSAnswered alone
Finish the sentence: when a customer asks me what the new release changes for them, I…MMira…name the one thing it changes for them, and what stays the same.
JJonas…send them the release notes.
AAylin…say I will check with Product and get back to them.
TTomas…list everything that is new.
RRosa…I haven't seen it yet myself.
What it costs you if nobody notices
Shared knowledgeThe customer hears three releasesWhen Sales, Support and Marketing describe the release differently, the customer concludes that nobody knows what shipped.
Shared convictionNot my launchA team that sees the release as Product's event does not prepare for it, and meets the first hard question live.
Shared practiceDay one goes badlyWithout practice, the first question about what changed, or what broke, gets an improvised answer, and that answer travels.
The program that closes the gap
Four one-hour sessions. Sales, Support and Marketing, one answer to every launch-day question, before launch day.
Session
Shared knowledgeShared convictionShared practice
S1Know what shipsAgrees what changes for customers, what does not, and what each team says about it.
Shared knowledge1Agree what the release changes for customers2Agree the one fact about the releaseShared conviction3Decide alone, then alignShared practice4Sort real customer questions into the one correct response…5Rehearse how each of you answers a customer who asks what…
DemoS2Make it your launchShows you whether each team believes the release is theirs, and what they fear it will cost them.
Shared knowledge1Quiz each other on what Acme Cloud's release actually…Shared conviction2Agree the five real costs if your team fails to make the…3Decide as the CPO would, then see if your team would back…Shared practice4Sort real customer moments into the right team response5Rehearse how your team answers a customer who asks what…
DemoS3Answer the launch-day questionsAnswers the same customer questions about the release alone, compares and aligns on the answers.
Shared knowledge1Align on the one answer every team gives when a customer…Shared conviction2Align on the one answer to give when a customer asks what…Shared practice3Match the same six launch-day customer questions to the one right answer4Put the steps of answering a launch-day customer question…
DemoS4Handle day onePractises the hard moments: the feature that is not there, the thing that broke, the price question.
Shared knowledge1Agree the exact facts your team must know to handle day…Shared conviction2Decide how to handle a day one customer problemShared practice3Put the steps for handling a day one problem in the right…4Rehearse how you'd respond to a customer who hits a missing feature
DemoPlay it yourself · a short demo · one exercise from session 3 · Make the Call
Alone first. Then the team agrees on one answer.
This is a taste, not the whole session. “Answer the launch-day questions” runs 4 exercises with your own team, on a call or in a room. Here is one of them, on the real screens, played with four AI teammates, so you can feel how a session works.
Answer the launch-day questions · Make the Call00:00MJLSYouAlign on the one answer to give when a customer asks what the release changes for themOn screen: Reframe each of these 4 customer questions as the one answer you would give alone
You are playing with 4 AI teammates. Every screen opens on its briefing: read it, then tap I’m ready.
Readiness intelligence · what you'll see as teams play
Know which of your launch teams can answer the launch-day questions the same way, and where you should step in, before the customers ask them.
Your company › Readiness intelligence › The whole company ready for a releaseSales, Support and Marketing answer every question about the release the same way on launch day
Readiness index88%Ready+46 pts25% participation + 25% progress + 50% alignment · Ready at 80
Shared knowledge48 → 88Shared conviction37 → 71Shared practice44 → 80
Participation94%23 of 24 people played at least once
Progress75%3 of 4 planned sessions completed
Alignment41% →78%75 of 96 points aligned
Failed alignment pointsWhere you should step in
The missing export questionNot aligned in 16 of 40 playsShared knowledgeYour support team · 30 people
Is this release my launch too?"Not yet, we still have concerns" in 2 playsShared convictionYour account managers · 15 people
Your launch teams could play this next week. Add your website to make it yours.
- 01 · 5 minConfirm the assumptionsCheck what we inferred about you and edit any text in place. Your edits are locked.
- 02 · 1 link per teamInvite your teamAny browser, any device. No account, nothing to install.
- 03 · after each playWatch readiness fill inYou see who played, what they agreed, and where to follow up.
Used by teams at
Free until you play live · ISO 27001 · EU data
Free until you play live · ISO 27001 · EU data