Sales Demo Kit

Interactive toolkit to simplify accessibility for non-technical buyers.

In 2021, I led the design of AudioEye’s first Sales Demo Kit—a lightweight, visual tool that helped Sales communicate the value of an invisible accessibility product. By creating two mock websites to demonstrate accessibility issues side by side, paired with a clear script, we gave reps a fast, effective way to show what AudioEye does—no engineer needed.

The kit rolled out company-wide, became a key part of onboarding, and boosted Sales confidence in pitching accessibility to non-technical prospects. It turned a behind-the-scenes product into a tangible story that teams could finally tell with clarity.

Introduction & Product Context

0 1

AudioEye is a digital accessibility platform that automatically remediates issues that can make websites difficult—or impossible—to use for people with disabilities. It’s powerful tech, but almost everything happens behind the scenes. That’s great for users, but tough for Sales.

When I joined this project, the Sales team had one big challenge: they couldn’t show what the product did. Most prospects couldn’t see the value because there was literally nothing to see. Instead, reps would point to the optional toolbar or lean heavily on Solutions Engineers to explain the technical side. This led to confusion, delayed decisions, and lost momentum in sales conversations.

We needed to change that. The goal was to create a demo experience that made AudioEye’s impact visible and real—something Sales could confidently use to tell the story on their own.

0 2

Problem Space

Business Goals & Success Metrics

 🎯 Business Goals

  • Help Sales communicate AudioEye’s core value clearly and independently

  • Shorten the sales cycle by reducing reliance on technical teammates

  • Educate non-technical prospects on accessibility in a way that feels approachable

📈 Success Metrics

  • Adoption of the demo kit by Sales

  • Increased confidence during client conversations

  • Fewer handoffs to Solutions Engineers

Research Insights

I kicked off the project by digging into how Sales was currently pitching the product:

  • Interviewed 3 Sales reps

  • Observed mock sales calls

  • Reviewed the workarounds and scripts they were using

Here’s what stood out:

  • Sales leaned on the toolbar to show something, even though it wasn’t the product’s core value

  • Prospects didn’t understand what accessibility meant or who it impacted

  • Technical language often made things worse, not better

“People just don’t get it—AudioEye works, but they can’t see it.” — Sales Rep

0 3

Solution Space

Core Concept

I pitched a solution focused on storytelling over specs: two identical-looking mock websites, one with AudioEye and one without. Each site looked the same visually, but the experience was completely different depending on whether accessibility issues were present. (Figure 1)

Figure 1: Mock Sites Before & After AE Installation

Figure 2: Snapshot of Sales Script

What We Built

We created a fictional eCommerce site called “Emeralds,” then introduced three common accessibility issues:

  1. No “Skip to Content” link

  2. New windows are opening without warning

  3. Redundant alt text on linked images

In the second version of the site, AudioEye was installed, and those issues were automatically fixed. This gave Sales a clear, side-by-side experience to show prospects exactly what was happening, without needing to get technical.

Supporting Tools

  • Designed a conversational Sales script to explain what was happening and why it mattered (Figure 2)

  • Validated the fixes with our engineering team

  • Kept the demo under 10 minutes to fit naturally into Sales calls

Testing & Iteration

We ran the initial version by the Sales team. They loved the concept, but we quickly learned:

  • Some of the fixes were too subtle and needed more visual cues

  • Sales still felt uneasy explaining technical details without backup

So we adapted:

  • Tightened the script to focus on clarity and outcomes

  • Suggested adding screen reader recordings (in future versions) for better depth

  • Streamlined the demo flow to focus on before/after moments

0 4

Outcome & Impact

🚀 Company-Wide Launch

Rolled out company-wide and showcased during a Tech Showcase.

🧭 Sales Onboarding Integration

Became a key part of onboarding for new Sales reps.

💬 Boosted Sales Confidence

Sales reported higher confidence and better call flow with the demo.

🗣️ This finally makes the product feel real.” — VP of Sales

0 5

Long-Term Vision

This project launched as an MVP—but it laid the foundation for a long-term solution. Our roadmap included:

📅 Post-launch testing with real users via Fable

🧰 A DevTools cheat sheet for technical prospects

✨ Expanding the demo with additional issue types and scenarios

📹 Short screen reader recordings to highlight invisible improvements

0 6

Reflections & Learnings

This project reminded me how essential storytelling is in design, especially when your product is invisible by default. It also reinforced the value of tight cross-functional collaboration: PMs, Engineers, and Sales all had a seat at the table, and that made the outcome stronger.

  • Simplicity builds confidence—internally and externally

  • You don’t need a perfect dataset to ship something meaningful

  • Sales enablement is a user experience, too

Above all, I learned that when you make the invisible visible, you unlock new clarity—not just for your users, but for your team.