Interactive capturing
Breathe life into your demos, and momentum into your deals.
About Walnut
Walnut is a codeless demo platform that lets sales teams capture, personalize, and share interactive product demos—without developers or designers—turning every pitch into a high-impact experience.
My contribution
I led the design of Interactive Capturing—using research to define the problem, collaborating with product and engineering to overcome technical barriers, and delivering a seamless solution that brought real product interactions into every demo.
Competitive analysis
We found Walnut was stuck in the middle—more flexible than basic tools, but not interactive enough for high-stakes live demos. This led to a strategic shift: invest in deeper interactivity to make demos feel truly alive, responsive, and ready to close deals.
The Problem
Sales demos missed the real product’s animations and interactions, making them feel static and unconvincing—more like a slideshow than a live experience
Design vision
My design inspiration for this experience was rooted in a metaphor: Capturing a demo is like a trip to the supermarket. You’re not just grabbing items at random—you’re making intentional choices to gather everything you need for a perfect result while avoiding clutter.
The Analogy
​The “Cart” – Capturing pages is like placing key ingredients into your cart: you’re collecting the building blocks of your demo.
The “Bags” – Capturing interactions is like sorting the items in your cart into organized bags: the flows, behaviors, and details that make your demo feel alive and dynamic.
​​
This analogy shaped the design language and UX logic. I created a visual and interaction system that mirrored the layering process—starting with broad capture for pages - large pop-in, and shifting modes to refine the experience with the mini-pop-in.​
Capturing experience
User journey
Design and prototyping
Designing the capture extension meant balancing a seamless UX with complex technical constraints—all within a tiny browser-side real estate. The challenge was to clearly separate page vs. interaction capture, without overwhelming users.
Editing experience
Once all pages and interactions are captured, the experience shifts from gathering to crafting.
Everything the AE has collected is now seamlessly “thrown” into the Walnut editor, where the real magic happens: editing, structuring, and shaping the story
User journey
Once the capture phase is complete and content flows into the editor, the AE moves into shaping the demo experience—and that includes deciding how captured elements behave:
​
Hover: When the user hovers over an element, something happens—a tooltip appears, a button glows, a panel shifts.
​
Hover+ Click: For layered interactions—where hovering gives context and clicking triggers an additional response
​
Hover+ Link: When the click action leads to a new screen (different URL/page), but the hover still provides value.
Design and prototyping
If capturing is the shopping trip, editing is where you head to the kitchen and start cooking. The challenge was turning a bag of raw ingredients—pages and interactions—into a clear, structured demo that tells a compelling story.
Impact
Although the feature is still being adopted, early indicators show strong positive momentum—both in user behavior and business value. Here's a snapshot of its potential and emerging impact
18
New companies joined Walnut after previously opting out due to the lack of interaction support
23%
Increase in user satisfaction, based on post-capture and editing experience surveys
31%
More demos created per week, indicating smoother workflows and higher AE engagement
3 out of 4
AEs reported feeling more confident going into a live demo, thanks to the new interaction depth
5%
Reduced support tickets related to capture/edit confusion—indicating a clearer, more intuitive flow
Two Worlds, One Seamless Flow
The capturing and editing experiences were almost like two separate products—each with its own complexity, mindset, and technical depth. Yet they had to work together flawlessly to deliver a smooth, end-to-end journey for AEs.
​
This was made possible through close collaboration with developers, PMs, the VP Product, PMM, and CS teams—aligning vision, overcoming constraints, and ensuring that what we built was both technically sound and user-centric