Product
launches.
Turn a reveal into a repeatable, interactive presence moment across many locations.
The opportunity
Design for the moment that matters.
What breaks today
Launch films create excitement but cannot respond to the questions that determine adoption. Live tours reach few locations and are expensive to repeat.
The presence pattern
A spokesperson, designer or digital host appears beside the new product, delivers the core story and adapts the demonstration to each audience.
Design requirements
Make it useful before making it magical.
- 01
Keep the product primary
Presence should direct attention toward the real offer, not compete with it as a separate spectacle.
- 02
Connect intent to action
Every story or conversation should lead naturally to comparison, configuration, appointment or purchase.
- 03
Design service continuity
Preserve context when the experience moves from AI to advisor, store associate or follow-up channel.
Operator runbook
Design the complete service—not only the scene.
- 01
Frame the service
Brand and product marketing teams should document the intended audience, room, session length, approved content or knowledge, human escalation path and the current baseline for launch participation.
- 02
Invite with clarity
Before the product launches experience begins, explain why the presence is there, whether it is live, recorded or AI-assisted, what it can do and how a participant can leave or reach a person.
- 03
Operate the moment
A spokesperson, designer or digital host appears beside the new product, delivers the core story and adapts the demonstration to each audience. The operator should be able to observe state, recover the session and protect the physical activity already happening in the room.
- 04
Close the loop
End with a visible next step, capture only consented information and record launch participation, feature comprehension, qualified follow-up. Review failures and handoffs before repeating or expanding the experience.
Pilot scorecard
Prove a real outcome in the room.
Launch participation
Define the starting event, completion event and current-workflow baseline for launch participation. Count only observable outcomes.
Feature comprehension
Review feature comprehension by audience, session stage and operator. Use the pattern to find where confidence is gained or lost.
Qualified follow-up
Set a minimum threshold for qualified follow-up before launch. Name the owner and recovery action when a session misses it.
Decision gates
Know when presence is—and is not—the answer.
Presence must earn the room
If the same product launches outcome can be achieved by a well-designed phone, kiosk or conventional video call with equal trust and clarity, use the simpler tool.
The boundary must stay visible
Do not launch product launches until participants can identify the role, source, live or synthetic state, information boundary and human fallback without guessing.
The operation must survive novelty
Brand and product marketing teams should be able to run, pause, recover and measure the experience repeatedly. Do not scale while success depends on a founder or engineer standing beside it.
Evidence status. This page is a product-design field brief, not a claim that Reality Relay has already produced the stated customer outcome. Replace the hypothesis with measured pilot evidence before presenting it as proof.
Build the first pilot
Start narrow enough to learn.
For Product launches, begin with one real environment, one defined audience and one repeatable interaction. Establish who operates the experience, what information or tools it can access and exactly when a person must take control.
Reality Relay Platform coordinates content, session state, approved intelligence and operations. Reality Relay Spaces give the experience a calibrated physical endpoint with intentional scale, eye line, sound and grounding. The pilot should earn expansion by improving the scorecard above—not by novelty alone.
- Primary audience
- Brand and product marketing teams
- Experience family
- Retail & commerce
- First decision
- Choose the room, baseline and accountable operator
- Expansion rule
- Scale only after the scorecard beats the current workflow