Personalization opportunity
They keep doing it the hard way.
Show the easier way while they're still doing it by hand.
Step 1 · Signals
What do we know about this person?
Connected
Repeated export, reorder, or manual steps that map to an unused feature.
Example eligibility rule
Trigger only after the same manual workaround occurs at least three times in 30 days, the mapped capability remains unused, and the user has permission to try it. Reset the count after adoption or dismissal.
Step 2 · The need
What’s really going on?
A user exports a CSV every Friday, reorders by hunting, or copies a workflow by hand. A feature, plan, or integration would remove that repeated work. They have never been shown it at a moment when the benefit is obvious.
Avoid this assumption
An "upgrade to Pro" banner on every page is not this. This is a prompt at the moment of the workaround.
Step 3 · Worth it?
Do the math before you build.
This is expansion with a conscience: you are not upselling a stranger, you are offering a shorter path through a job they already do.
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 contextual offer with a 30-second preview of the capability.
Compare lighter and deeper responses
Choose the lightest response that solves the need.
Assist: Offer useful help
A one-line tip next to the workaround: "there's a faster way".
Adapt: Change a meaningful part
A contextual offer with a 30-second preview of the capability.
Transform: Tailor the journey
A trial of the capability in-flow, with a clear way back.
What to watch out for
- Prompting on the first occurrence. Wait for a pattern.
- Pitching a paid plan before showing the job-to-be-done.
- No "already using a different tool for this" escape.
Step 5 · The moment
Did it help? A/B test it.
Control
No prompt, or the global upsell banner.
Treatment
In-moment prompt tied to the workaround.
Success measure
Capability adoption, then expansion revenue or retained usage.
Guardrail
Prompt dismiss rate and support tickets calling it spam.
Among accounts that met the repeated-workaround rule, compare the contextual prompt with no prompt. Track capability adoption and retained use, not just prompt clicks.
Win or lose, record what worked, for whom and why. What you learn becomes the next signal.
Tools that can deliver the response
- Pendo in-app guides Product experience platform combining usage analytics with in-app guides targeted by user or account segments.
- Appcues In-product engagement platform for building targeted flows, tooltips, checklists, and announcements without engineering.
- Customer.io Event-triggered lifecycle messaging across email, push, SMS, and in-app, built on a customer profile and behavior-data layer.
- Iterable Cross-channel journeys (email, SMS, push, in-app) built from a single visual studio, triggered by real-time customer behavior.
Try the framework on another situation
You have their history. Next time still starts from scratch. Ask to save one useful default, when it would actually help.
They're using it less. The reply is a coupon. Find out what changed. A discount isn't a diagnosis.
Work through it in the hub
Score your personalization program, explore more customer situations, and compare the tools that can deliver them.
.svg)
