Personalization opportunity
They signed up. The first screen still looks like someone else's demo.
Show an example that looks like their world, not a stock screenshot.
Step 1 · Signals
What do we know about this person?
Declared
Role, use case, or industry named at signup, and an empty or sample workspace.
Example eligibility rule
Load a relevant example when the customer declared a supported role or use case, the workspace contains no customer data, and no first-value event has occurred. Use a blank start when they selected "start from scratch" or when no trustworthy example matches.
Step 2 · The need
What’s really going on?
Account created. Dashboard, sample data, or "welcome to the platform" with stock examples from another industry or role. They cannot tell if this will work for them. Direction would give them a first job. Confidence is showing a result that looks like theirs.
Avoid this assumption
A product tour is not proof. This case makes the result feel credible and relevant. "They logged in to an empty screen, not what they came to do." chooses the first action they should take.
Step 3 · Worth it?
Do the math before you build.
The first session must make the product's value believable. A recruiter could see a sample candidate pipeline, while a support lead could see a sample queue with routing rules. Both are testable against the same blank slate.
Reach
How many eligible people can you reach in the chosen channel and time period?
Cost
What will content, delivery, QA and ongoing maintenance cost?
Return
What incremental outcome would cover that cost, and what is it worth?
Planning inputs, not measured results. Estimate reach × incremental outcome rate × value per outcome, then subtract cost. Use a range and a consistent time period.
Step 4 · The response
Pick how you help.
Example format: Content
A first screen with one example result in their world, then the first action.
Compare lighter and deeper responses
Choose the lightest response that solves the need.
Assist: Offer useful help
Keep the empty state. Swap sample names and screenshots for their use case.
Adapt: Change a meaningful part
A first screen with one example result in their world, then the first action.
Transform: Tailor the journey
Pre-built workspace or sample project for that role, skippable, with a way to start blank.
What to watch out for
- Loading a noisy demo dataset they cannot delete.
- Guessing the use case from email domain and being loudly wrong.
- Calling the tour "personalized" because it used their first name.
Step 5 · The moment
Did it help? A/B test it.
Control
Generic empty state or sample data.
Treatment
Use-case-aware first proof, with a holdout.
Success measure
First key action in-session (not tour completion).
Guardrail
People who wanted a blank slate and felt the example was in the way.
Win or lose, record what worked, for whom and why. What you learn becomes the next signal.
Tools that can deliver the response
- Appcues In-product engagement platform for building targeted flows, tooltips, checklists, and announcements without engineering.
- Pendo in-app guides Product experience platform combining usage analytics with in-app guides targeted by user or account segments.
- Userpilot In-app flows, checklists, and multi-channel workflows targeted by behavior and segment, built without code.
- Mutiny B2B website personalization tool that identifies visiting companies (via IP/firmographic match) and swaps page content (headlines, proof, CTAs) by account, segment, or industry. As of April 2026 it relaunched as an AI GTM agent, expanding beyond the original website-personalization product.
Try the framework on another situation
They logged in to an empty screen, not what they came to do. Make the first screen about what they said they wanted.
An engineer landed on a page written for a buyer, or the reverse. Show proof that matches who's actually looking.
Work through it in the hub
Score your personalization program, explore more customer situations, and compare the tools that can deliver them.
.svg)
