Loading case study…
Founder at Dusted
This case study was created from an episode of the Product Marketing Adventure Podcast. It has been adapted into Dusted's case study format to preserve and showcase the guest's real-world experience. Written to preserve the voice of the true author, Emily Pick.
I had only been at Docebo for about two and a half months—my first enterprise public company and my first time in the learning and development space. Docebo is a learning platform serving enterprise audiences for both internal use cases (employee training, compliance, onboarding) and external ones (customer education, partner and franchise training).
Our CRO brought in a former mentor to run a full end-to-end pipeline analysis across lead sources, progression, and backend lead-gen systems. One clear finding stood out: a specific segment was closing at a rate six to seven percent lower than our benchmark.
The drop-off was happening after the demo stage. Our hypothesis was straightforward: we were not telling the market the right message and were not meeting buyer expectations once they reached a demo.
Spread the word and give this marketer’s work the audience it deserves.
Share this case study with your network
I needed to investigate what this segment expected when they came in, why we won or lost opportunities, whether outcomes changed by persona, company size, or industry, and how our past product reality and future roadmap should shape what we leaned into or avoided. The request landed around noon on a Friday. Pre-AI, gathering win-loss data, NPS trends, call insights, and industry signals alone would have taken days or weeks before any real analysis began.
I started by defining the exact inputs required: win-loss data, NPS scores over time, customer conversation insights, and external industry/voice-of-market signals.
Next I curated and cleaned those inputs so they were usable. I used existing automations and agents to surface six-month NPS sentiment trends for the segment, sliced win-loss interviews by segment/persona/use case, ran natural-language queries across Gong calls for expectations, demo reactions, questions asked, and stage progression, and gave Perplexity Enterprise Pro tight parameters (trusted analysts, influencers, Reddit, Substacks, podcasts) to map industry expectations and gaps.
I spot-checked continuously for hallucinations by following each tool’s audit trail back to source calls, pages, and stats. I then consolidated everything into a single context document and fed it to a custom GPT. Using tight prompting practices, I iteratively queried the data to produce a full messaging audit—how we positioned today versus prospect expectations, discovery pains, and questions—without knowing every answer in advance. The goal was clear recommendations and a format consumable by demand gen and our SDR/BDR teams.
I shipped the output the same afternoon for validation, reviewed it with sales, product, and other stakeholders (only minor tweaks needed), and handed the updated messaging, use-case needs, personas, KPIs, value drivers, and industry variations to demand gen so they could begin refreshing ads and top-of-funnel assets. We kept everything else constant so we could treat it as a natural before/after test and planned to iterate as results arrived.
I signed off around 2:00 p.m. the same Friday with a complete messaging audit and recommendations ready for my boss’s first review—roughly two hours of elapsed time. He later told me the depth and turnaround far exceeded expectations; the team had assumed the work would take a full week even with our tools.
We surfaced real disconnects: places we were over-positioning on capabilities that were not current strengths (and sometimes competitor differentiators) and under-emphasizing areas where we led and buyers already cared. The deliverable included updated messaging, persona KPIs, value drivers, and vertical-specific framing.
After quick stakeholder validation we began updating ads and top-of-funnel assets. Quantitative pipeline lift is still early, but the process compressed what used to be weeks of manual gathering and analysis into an afternoon, gave us higher confidence in the inputs through systematic spot-checks, and created a repeatable playbook we can run again as results come in—potentially even faster next time.
Founder at Dusted
Founder at Dusted
Anna Startseva set out to launch ServiceNow’s AI-native ITSM solution as a solo PMM. She aligned stakeholders, researched buyers, built a Messaging House, and used grounded AI tools to scale messaging, enablement, sales Read more
Senior Manager, Marketing Operations in Technology & Software
The author set out to eliminate missing event and webinar context by tracing approvals, connecting intake, Asana, Google Drive, Slack, and Dust, and deploying agents to distribute briefs, update tasks, and escalate unres Read more
Senior Manager, Marketing Operations in Technology & Software
The author set out to connect Asana’s project planning with Slack’s existing conversations, reducing missed updates and manual follow-up. They linked projects to channels and built Dust workflows to create channels, surf Read more
Comments
No comments yet. Be the first to share what you think.