Loading case study…
Head of Market Intelligence at Klaviyo
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, Mindy Regnell.
Klaviyo is best known as a CRM for B2C businesses—we’re building the autonomous CRM that lets marketers scale their efforts, though it’s generally described as marketing automation software. I run the market and competitive intelligence program here and have been at Klaviyo about two years. I’ve been in e-commerce for 15–20 years and doing competitive intelligence for nearly a decade. Prior to my arrival there was no formal CI program; I was brought on specifically to stand one up. The market is extremely crowded: email platforms, SMS, WhatsApp, CDPs, reviews, and more sit alongside multiple product lines, geos, and segments. Internally I keep a slide that’s just a smattering of competitor logos—and it still isn’t exhaustive.
It was immediately clear we had far too many competitors to solve for one-by-one. Getting even a reliable shortlist of top competitors proved hard. Sales reps—especially new hires spread across geos and segments—faced an overwhelming landscape. Regional teams in EMEA and APAC routinely ran into smaller local players (300–1,000 customers) that a small CI team could never cover with individual battle cards, while global “tier-one” competitors still demanded deep coverage. Without a scalable system, onboarding would stay chaotic and regional reps would feel unsupported.
Spread the word and give this marketer’s work the audience it deserves.
Share this case study with your network
I drew inspiration from Chris Anderson’s book The Long Tail and built what I call the long-tail competitive framework: instead of chasing every logo, I bucket competitors into a small number of durable categories defined by their root underlying pain and trade-offs.
Step 1 was ruthless self-understanding—what makes Klaviyo fundamentally different. I talked with sales engineers, fellow PMMs, and executives to surface origin stories and technical nuances that competitors can’t easily copy.
Step 2 examined the pains those competitor types inflict on customers (maintenance burden of open-source, rigidity of pure SaaS, Franken-stack integration debt from acquisitions, etc.), always viewed through the lens of our own differentiation.
Step 3 clustered competitors into categories (ideally fewer than five primary ones) based on pains that are core to who they are and therefore unlikely to change. I deliberately ignored pure edge cases (e.g., pure-play B2B tools) and left sub-flavors for later.
Step 4 pressure-tested the categories first with people who know the platform well, then with brand-new BDRs/SDRs in week three—the ultimate clarity check.
Step 5 secured buy-in by positioning the framework differently for each stakeholder: regional leaders heard “your team will finally be covered against the long tail of local players”; global leaders heard “reps will ramp faster because knowledge transfers across the category.” I previewed with senior sales leaders before wider roll-out.
Once approved I built framework-level battle cards first (category definition, why a buyer chooses it, how to spot membership, key messaging, discovery questions, objection handling, and a running list of known players). Only then did I deepen the true tier-ones, reusing the same root-pain insights. Enablement started with company-wide competitive training that showed both global and region-specific 2×2 maps (happy space always upper-right), then embedded the framework into onboarding so new hires learn categories before any single logo.
Core artifact is the long-tail battle-card template I created and share widely in the CI community—each card captures category definition, buyer rationale, diagnostic checklist, messaging, objections, and a living competitor list. I visualize the landscape on Gartner-style 2×2 grids (global view plus EMEA/APAC/country slices) so reps immediately see which logos matter in their theater. For research I use Perplexity as a starting engine but always verify primary sources, especially competitor support docs. Gong’s AI surfaces real objection language from calls that I then refine human-in-the-loop; I never let AI write the battle card itself. An optional Excel cheat-sheet eventually maps every known competitor to its framework card.
I stood the entire framework up in my first three months; a segment GTM colleague later called it one of the most valuable things I delivered. More than two years later we are still using the same system. Reps onboard faster because they learn durable categories rather than an endless logo list; confidence on one competitor transfers to others in the same bucket. Regional teams finally feel covered without requiring a battle card for every 500-customer local player. The framework has become the shared language across sales, CS, and product marketing and continues to absorb new product lines and geos without breaking.
Head of Market Intelligence at Klaviyo
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.