.webp)
In presales, we're constantly asked to prove our value. But how do you measure the impact of a team that doesn't directly close deals? This is the trouble facing demo engineering teams.
In this episode of the Presales Collective Podcast, hosts Jack Cochran and Matthew James sit down with Micah Joel, a veteran demo strategist with over 25 years of experience, including his time leading Salesforce's Q Branch demo engineering team. The conversation tackles one of the most critical challenges facing presales leaders today: proving the ROI of demo engineering through metrics that actually matter to executive leadership.
Listen to the full episode now!
The Measurement Challenge in Presales
Peter Drucker famously said, "What gets measured gets done." Yet in solutions engineering and presales, measuring impact remains notoriously difficult. Unlike sales teams with clear revenue metrics or customer success teams with retention rates, demo engineering teams often struggle to quantify their contributions in ways that resonate with senior leadership.
This gap becomes particularly problematic when demo engineering leaders need to justify headcount, secure budget, or simply defend their team's existence during tight economic times.
Start Simple: The Time-Saved Formula
When asked where to start with measuring demo engineering impact, Micah's answer is refreshingly straightforward and simple … but just because something is simple doesn’t mean it isn’t valuable.
"Ask an SE what they hate doing the most. They tell you. You sit down, you do it yourself, and you time yourself doing it. Then you create a tool that solves that problem—does it in a minute instead of half an hour or an hour. Then you roll that tool out, and every single time someone presses that button, you pat yourself on the back with 30 minutes saved or an hour saved."
This approach provides several advantages:
- It's defensible. You have a clear baseline (time before) and a clear result (time after).
- It's measurable. Every time someone uses your tool, you can track that usage and multiply it by time saved.
- It translates to dollars. Solution engineers are expensive resources. Saving an hour of SE time has a concrete dollar value.
"Every time a solution engineer saves an hour, you're saving, I don't know what is it, 100 bucks or whatever," Micah explains. "And if there's hundreds of solution engineers, every time they click that button you're saving a significant amount of money for that organization."
Beyond Time: Measuring Demo Environment Value
While tool usage is straightforward to measure, quantifying the value of demo environments themselves presents a more nuanced challenge. How do you measure the delta between giving an SE a completely empty environment versus a fully configured demo?
Micah's solution: ask the people who actually use them.
At Salesforce, his team surveyed hundreds of SEs with a simple question: "How much time do you think the demo environment that you have saves you?" Responses ranged dramatically from two hours to two weeks.
"We did a bit of, I'll admit, controversial math," Micah says, "but we came up with a way to measure the value of the demo environment. We came up with an answer that every time someone spun up a demo environment that we'd created, they were saving themselves two and a half hours."
While conservative, this estimate multiplied across thousands of environment provisions created substantial documented value. More importantly, it provided qualitative insights into SE satisfaction and job stress which are critical factors for retention.
The Hidden Value: What You Enable vs. What You Do
Beyond direct time savings, demo engineering teams enable capabilities that would otherwise be impossible or impractical. Micah shared a compelling example: organizations that require SEs to know JavaScript purely to configure demo environments may be filtering out otherwise exceptional candidates—relationship builders, master storytellers, or industry veterans who haven't needed to learn that particular technical skill.
"You're stepping over people who would otherwise be great SEs because they can't do that one thing that the demo environment needs," Micah notes. "That's the perfect use case for demo engineering—offload the technical piece of that job so that your SEs can focus on customers and relationships and storytelling."
This benefit is harder to quantify directly, but connects to metrics senior leadership deeply cares about: reducing time-to-productivity for new hires, improving retention, and expanding the talent pool.
Speaking the Language of Leadership: Think Top-Down
Perhaps the most critical insight from the conversation is this: demo engineering may nominally be a function of solution engineering, but it affects the entire company. Marketing uses demo environments for events. Recruiting uses them for candidate interviews. Engineering sometimes tests with them. Yet the team footing the bill cares most about what demo engineering does for them specifically.
Rather than thinking about just how to make your presales team better at demoing, shift your thinking to how to get product to market in the best way possible. This Product to Market (P2M) thinking is how you provide true value to an organization as a demo engineer.
"If you put your management hat on and start thinking in that direction, you frame what you're doing in their terms," Micah advises. "If you only explain the technology side of it, they won't get it. But they will understand: 'We need to grow our revenue 15% this year without growing our cost 15%—how do we do that?'"
This top-down thinking means understanding what senior leadership is measured on:
- Productivity and cost efficiency: Can we grow without proportional headcount increases?
- Visibility: What are our teams actually doing? What are they selling?
- Time to revenue: How quickly can we monetize new products after launch?
- Retention: Are our people satisfied? Are we losing institutional knowledge?
Micah shared an example of unexpected metric value: tracking which products are actually being demoed. "Solution engineers aren't always demoing the things they're supposed to be selling," he explains. This visibility helps leadership understand gaps between strategy and execution.
The Go-to-Market Speed Advantage
One of the most powerful metrics for demonstrating cross-functional value is time-to-demo for new products. How long after a product is released can solution engineers effectively demonstrate it?
"If you can look at—and I think that's the area that has the biggest revenue impact, especially upstairs—for them to look and go, 'We have a new product, we need to start getting revenue from that new product as soon as possible, this team is a big part of that.'"
This metric bridges demo engineering value into product strategy and revenue generation—languages that executive leadership speaks fluently.
Building a Brand That Provides Political Capital
Metrics alone don't ensure organizational survival. Micah emphasized the importance of cultivating relationships and goodwill across the organization, particularly with the SE teams you support.
At Salesforce, his team embraced the "Q Branch" metaphor from James Bond. These are the nerds who support agents in the field. This framing positioned them as enablers and support rather than corporate overhead.
"Find a metaphor that you think works for your business—is it race car drivers and their pit crew? Is it astronauts and mission control?" Micah suggests. "Make that every piece of marketing that your team puts out references that kind of language so that people see you as this team holding things up from the bottom."
This goodwill provides cushion when things go wrong. "When that happens, I find that they'll defend you all the way up. They'll say, 'Oh yeah, this team's amazing. Yeah, one flub—it doesn't matter. They saved me all this time, they helped me win this deal.'"
Practical Takeaways for Presales Leaders
If you're building or managing a demo engineering function, here's what you can implement immediately:
1. Start with the simplest measurement: Identify the most time-consuming SE tasks, build tools that solve them, and track every usage. Multiply time saved by usage frequency and translate to dollar value.
2. Survey your users regularly: Ask SEs directly how much time they think you're saving them. Include open-text fields for qualitative feedback. Track satisfaction across tenure to identify retention risks.
3. Think like your CFO: Frame every metric in terms of what senior leadership is measured on: growth without proportional cost increases, time to revenue, retention, and productivity.
4. Track product demo adoption: Measure how quickly new products can be demonstrated after release. This bridges demo engineering into revenue strategy.
5. Document qualitative wins: Capture testimonials and success stories. These humanize your metrics and provide powerful advocacy when budgets are tight.
6. Build a compelling brand: Create a metaphor that positions your team as essential support rather than corporate overhead. Make it memorable and reinforce it consistently.
7. Expect to adjust: Commitments made at the beginning of the year will change. Keep measuring consistently so you can demonstrate value even when original targets need revision.
The Bottom Line
Demo engineering teams occupy a unique position in the go-to-market organization. They don't close deals directly, yet they enable every customer-facing conversation. Proving this value requires thinking beyond traditional presales metrics. It demands speaking the language of cost, efficiency, and strategic enablement.
As Micah concludes: "Think from the top down. Think about how management looks at what you do and how you will frame what you do in terms of things they care about. Explain how you're benefiting the business, explain how you're helping them toward the numbers that they stated at the beginning of the year. Think about it from their point of view and frame everything you're doing that way."
Frame your demo engineering organization as the critical key of bringing your project to market.
Join the Presales Collective Slack community at presalescollective.com/slack and join the #presales-podcast channel to stay updated on future episodes and join the conversation after each show. Follow the PSC LinkedIn page for upcoming events and information.
