Reverse Demo Activation Loop
Make prospects operate the product while you solve their real workflow and capture friction.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 100%
Before the call, ask the prospect to choose a real task, prepare the relevant data, and describe the desired outcome. On the call, the prospect shares their screen, creates an account, imports their own material, and operates the product while the guide points to the next action through annotations. The goal is to finish the user's actual workflow, not to narrate features. Because the prospect performs each step, the session creates both activation and procedural memory. Meanwhile, the guide records every hesitation, missed control, confusing label, and failed action. Those observations go directly to engineering, which removes repeated friction before subsequent calls. Repeating this cycle progressively reduces the number of assisted demonstrations required and moves the product toward reliable self-service.
Origin
Clay used reverse demos while converting a sales-led product into self-service, reducing activation from seven or eight demos to one or zero over roughly eight to twelve months.
Core principles
- 01Demonstrate value by completing the prospect's real job, not touring features.
- 02Make the prospect perform the actions so usable muscle memory develops.
- 03Use every activation call as a live usability study.
- 04Record both the actions users take and the controls they miss.
- 05Shorten the assisted journey by engineering recurring friction out of the product.
How to run it
- 1
Collect the Real Job
Before the meeting, ask the prospect to bring a real dataset or work item and describe the outcome they need.
Pro tip Request enough context in the booking email to prepare for likely obstacles.
Watch out A hypothetical exercise produces weaker activation and weaker research evidence.
- 2
Put the User in Control
Have the prospect share their screen, create the account, and operate the product themselves.
Pro tip Use visual annotation to indicate the next control without moving the user's cursor.
Watch out Taking over the screen conceals whether the interface is understandable.
- 3
Complete the Core Workflow
Guide the user through the recurring actions required to reach their desired result during the session.
Pro tip Prioritize the smallest complete workflow that proves value.
Watch out Do not substitute a broad feature tour for completion of the user's job.
- 4
Capture Friction Live
Record every confusing step, missed button, hesitation, and workaround while the user proceeds.
Pro tip Pay special attention to actions the user does not discover independently.
Watch out Do not let note-taking prevent you from helping the user succeed.
- 5
Transfer Feedback Immediately
Share concrete observations with engineering while the interaction is fresh and connect each issue to its user impact.
Pro tip Include the user's attempted action and expectation, not just a proposed UI fix.
Watch out Delayed, generalized feedback loses the behavioral detail engineers need.
- 6
Engineer Toward Self-Service
Fix recurring friction, run more reverse demos, and monitor whether users need fewer assisted sessions.
Pro tip Track activation by completed workflow rather than attendance or feature exposure.
Watch out Do not optimize only for shorter calls if users stop reaching meaningful value.
In the wild
A prospect booked through Calendly, received an email asking them to bring a dataset, and described the desired enrichment result. During the call, the prospect shared their screen, created a Clay account, uploaded a CSV, and clicked through the workflow while Anand used Zoom annotations to guide them and recorded friction for an engineer.
→ The prospect frequently completed the real enrichment task within 30 minutes, became activated, and supplied actionable UX feedback.
Common mistakes
Giving a Feature Tour
Showing controls without completing the user's recurring workflow creates shallow familiarity rather than activation.
Driving the Product for the User
When the presenter clicks, the team cannot see what the user would discover or miss independently.
Failing to Close the Feedback Loop
The method loses its compounding value if recorded friction never reaches engineering or changes the product.
Is it for you?
Best for
It is best for early self-serve software with a concrete core workflow that can produce meaningful value during one guided session.
Not ideal for
It is not ideal for products that require lengthy implementation, sensitive production access, or outcomes that cannot appear during a short call.
From the transcript
“I would not recommend you demo the product to them. Like they should sign up for your demo and they should sign up to the…”
“And more importantly, you get learnings. You get to see all the buttons they click, and more importantly, the buttons they don't click.”
“But I my goal is to solve their whole problem, not just like show them features.”
From the episode
$500M Founder Shares Unorthodox Growth Tactics (That Worked!)