Discovery Demos - unifying two products into one buyer experience.
roleLead Designer
Research
User Testing
Prototyping
companyConsensus
platformDesktop
Mobile
timeline2024 - 2026
overviewConsensus made its name helping sales teams send personalized product demos that buyers explore at their own pace and enable an organic discovery process within the buying group. However helpful though, buyers increasingly wanted to actually interact with the product. In 2024, Consensus acquired ReachSuite, a startup that had two solutions to give buyers the “hands on” product sandbox experience they have been asking for.
This project was the first stages of integrating ReachSuite’s Dynamic Tours and Simulations into Consensus’s demo creation workflow and demo player experience. I led user research and usability tests while collaborating with PMs, Engineers and designers from multiple teams to release the first version of the Discovery Demo Builder and Discovery Demo feature.
highlightsLed research initiatives and usability tests
Identified gaps between how sales teams worked and how the platform supported them.
Designed a cohesive buyer journey
Delivered a scalable demo experience adaptive to real-world sales conversations.
Balanced analytics with flexibility
Maintained engagement visibility while enabling multi-demo workflows.
research & discoveryWhen ReachSuite first joined Consensus in 2024, their small team of 3 brought with them a solid read on the core pain points and unmet needs of their users. However, the product was still new to me and I know the importance of building my own understanding from the ground up.
After a couple of weeks of dissecting the ReachSuite app, I set up 30 minute calls with two internal CSM’s and two sales reps who had been using and promoting the softwares features for several months. In the same timeframe, I met with 4 users on ReachSuite’s Client Advisory Board (CAB). Here is a distilled breakdown of those interviews:
What the app does well
What the app doesn’t do so well
so, we asked ourselves…Placeholder
design approachI mapped out the parts of the app that the Playlist feature would affect—demo creation, email, analytics and the demo player. It had two distinct users: the seller creating, tracking and sharing the playlist, and the buyer watching and sharing content within the buying group.
The design solution had to support how sellers create and share a playlist, how engagement is tracked across multiple demos, and how buyers view and share the content
key decisionsfinal solutionThe multi-demo playlist made it so sales teams could present multiple products within a single buyer experience, aligning the platform more closely with how buying groups actually evaluate software.
outcomeThe Playlists feature shipped and adoption was strong, now with 87% of all DemoBoards sent using the multi-demo Playlist feature.
But post-release feedback showed view rates started dropping as new stakeholders brought into the buying group weren’t discovering the “Now Playing” and “All Demos” tab.
Visually, the tab didn’t stand out enough in the top right corner of the screen. This contradicted the insights we got from user tests ran through usertesting.com. As a result, stakeholders weren’t discovering all the content in the playlist.
following upThe PM and I followed up on the feedback and put together a low cost design solution to the discoverability issue. I removed the “Now Playing” and “All Demos” tab at the top right and added them as similarly organized sections in the playlist and maintained the visual focus with highlighted features.
reflection