JR
1 / 14
joyride
Customer & Competitive
Onboarding · Deck 2
Audience Profiles · Competitive Landscape · March 2026
Who we're building for
2 / 14
Four people who feel this problem. Four different ways in.
Primary champion
PMM Lead / GTM Operator
Feels the pain most acutely. Determines whether the product gets adopted.
Economic buyer
CFO / CEO
Controls the budget. Thinks in financial outcomes and R&D return.
Product champion
VP / Head of Product
Owns the roadmap. Wants to know that what the team builds actually lands.
Sales champion
Sales Leader
Manages a team constantly playing catch-up on product knowledge.
These are hypotheses. PMM as primary champion is the working model. VP Product may prove stronger given organizational authority. Watch for this in the first ten conversations.
Primary champion
3 / 14
PMM Lead / GTM Operator
Managing more releases than capacity allows.
Has built systems out of Notion, Slack, and Google Docs because nothing purpose-built exists. Good at the job. Frustrated by overhead that prevents doing it well.
"We shipped 40 features last quarter. I could tell you how each one was activated. I couldn't tell you which ones actually moved the needle."
How to open
"You're already doing this work. Joyride makes it possible to do it well at the speed your product team is moving."
What they fear
Being seen as a bottleneck. Losing quality as velocity increases. Budget absorbed by product or engineering.
What a win looks like
Their team activates more releases without burning out. Their work is visible to leadership.
Never open with
Efficiency, automation, or headcount. This person needs to hear that Joyride makes their job better.
Economic buyer
4 / 14
CFO / CEO
Invested heavily in engineering. Can't see what it returned.
Not in the weeds of the launch process. Increasingly skeptical that shipping more features is the right lever for growth. Cares about whether the investment is working.
"We spent $8M on engineering last year. I can tell you our overall ARR growth. I cannot tell you which of the 200 features we shipped drove it."
How to open
"You're investing heavily in engineering. Joyride tells you what that investment is actually returning."
What they fear
An R&D investment that doesn't translate into measurable outcomes. Not being able to answer the board.
What a win looks like
A credible R&D ROI story at the release level. GTM costs not scaling linearly with engineering output.
Never open with
The team experience or workflow details. This buyer thinks in financial outcomes — start there.
Product champion
5 / 14
VP / Head of Product
Ships good work. Uncertain it's translating.
Spends significant time prioritising what to build. Once a feature ships, the feedback loop is weak. Gets aggregate analytics but not release-level signal.
"We shipped a major pricing change six months ago. I still don't have a clear picture of whether it drove expansion or just created confusion. The data exists. It's just not connected."
How to open
"You're making bets every quarter. Joyride tells you which ones paid off."
What they fear
Building the right things but having them land badly. Not being able to make a credible case for product ROI.
What a win looks like
Release-level data. Prioritisation conversations grounded in outcome data. Smoother GTM handoff.
Never open with
GTM coordination or the sales enablement angle. Lead with the product feedback loop.
Sales champion
6 / 14
Sales Leader
Every week something ships. Every week reps find out too late.
Manages a team constantly playing catch-up on product knowledge. Sees releases as pipeline triggers — but only if the rep knows about them and knows which accounts they matter for.
"I find out about a big product release the same way my reps do — in the all-hands. By the time we've figured out which accounts to target, two weeks have gone by."
How to open
"Your reps should be the first to know what just shipped and exactly which accounts it matters for."
What they fear
Reps showing up to renewals without knowing what shipped. Missing product-led expansion opportunities.
What a win looks like
Releases generate outreach within days of shipping. Product-led expansion becomes a systematic motion.
Never open with
The PMM workflow or activation system. This buyer thinks in pipeline and revenue.
Competitive landscape
7 / 14
The landscape is crowded. None of them govern the full arc.
Others optimise pieces. Joyride governs outcomes.
Pendo / Amplitude
Product analytics — what happened after launch
Productboard / Notion
Planning and documentation — before launch
Highspot / Seismic
Sales content — downstream of the release
Appcues / UserPilot
In-product onboarding — one slice of adoption
LaunchDarkly
Feature flags — infrastructure, not activation
Joyride
The full arc — intent → activation → impact
Adjacent tools
8 / 14
Pendo & Amplitude
Product analytics
What they do
Instrument product usage after a feature launches. Tell you what happened: who used the feature, how often, where they dropped off.
Where they stop
They tell you what happened. They don't tell you whether the release was activated well, whether the right customers saw it, or whether it drove pipeline and retention.
How Joyride frames it
Pendo tells you what happened after a release landed. Joyride governs how it lands and connects it to what it was worth. Most Joyride customers will continue using Pendo — it feeds signal into the Release OS.
Adjacent tools
9 / 14
Highspot & Seismic
Sales enablement
Where they stop
Start downstream of the release. Help distribute content about it. Don't govern activation or whether it moved the business.
Joyride frame
Highspot organises content. Joyride starts at the release and determines what content needs to exist, for which accounts, and whether it worked.
Productboard & Notion
Product planning and documentation
Where they stop
They document the plan. They don't execute activation, surface customer relevance, or connect releases to business outcomes. Plans go stale.
Joyride frame
Notion holds the plan. Joyride is what happens when the plan needs to become action — and when you want to know whether it created results.
Adjacent tools
10 / 14
LaunchDarkly
Feature flag management
Where they stop
Infrastructure, not activation. Controls the technical on/off switch. No view of GTM readiness or business impact.
Joyride frame
LaunchDarkly flips the flag. Joyride picks up from there.
Appcues & UserPilot
In-product onboarding
Where they stop
One slice of adoption — in-product discovery. No internal enablement, no account relevance targeting, no downstream outcome measurement.
Joyride frame
Appcues shows customers what shipped. Joyride governs the full arc around it.
DIY / AI Agents
Bespoke internal tooling
Where they stop
Solves for the moment. Doesn't accumulate context. Release 47 knows nothing from Release 12. Maintenance debt grows with velocity.
Joyride frame
The question isn't whether you can build something for release one. It's what the system knows by release fifty.
What Joyride owns perceptually
11 / 14
No existing tool governs the release-to-impact journey as a system. Others optimise pieces. Joyride owns the outcome layer.
We own
The release lifecycle as a system
Context that persists and compounds over time
The connection between product output and business outcome
The outcome layer above the tools that already exist
We explicitly do not own
Product analytics (Pendo, Amplitude)
Sales content management (Highspot, Seismic)
In-product onboarding UX (Appcues, UserPilot)
Feature flag infrastructure (LaunchDarkly)
Project management (Notion, Asana)
We integrate with them. We don't duplicate them. Joyride governs how releases move across those systems and turn into measurable results.
Handling objections
12 / 14
The five you'll hear most.
"We already use Pendo for this."
Pendo tells you what happened after a release. It doesn't govern activation or whether it drove pipeline. Joyride starts earlier and ends later. Most customers keep Pendo.
"We have a launch process in Notion."
A Notion doc is a plan. Plans go stale. Joyride is the system that makes the plan real and tells you whether it worked.
"We're going to build something internally."
Internal agents solve for today's release. They don't accumulate context. The question isn't whether you can build something for release one. It's what the system knows by release fifty.
"We don't have budget for another tool."
Joyride makes the tools you already pay for produce measurable results. The question is whether the cost of under-activating product is larger than the cost of fixing it.
"This overlaps with our CRM."
Joyride isn't a CRM. It pushes release-level signal into Salesforce. The CRM records outcomes. Joyride generates the signal that makes them legible.
ICP
13 / 14
The right customer. For now.
Primary ICP — directional, not locked
High-velocity SaaS companies, 1,000+ employees.

Engineering velocity outpacing GTM capacity. Overloaded PMM function. Fragmented launch coordination. No release-to-impact visibility.
The more useful qualifier
Companies that can justify paying $150K+ to avoid a headcount hire. Employee count is directional. This is the real test.
Secondary ICP
AI-native companies with extreme shipping velocity from day one, where the gap exists structurally before PMM infrastructure is in place.
Not our customer yet
Very early startups without structured PMM.
Low-velocity product organisations.
Companies where R&D ROI is not a leadership concern.
The first twenty discovery conversations will sharpen everything in this deck. Pay attention to what's surprising.
Keep in mind
14 / 14
Everything in this deck is a hypothesis grounded in the strategy — not a confirmed map of the market.
What we know
The problem is real. The gap between engineering output and business results is widening. The competitive landscape is fragmented and misaligned.
What we're learning
Who the right champion is. Whether the pricing supports the ICP. What objections come up most. What breaks when velocity doubles.
The first twenty discovery conversations will sharpen everything in this deck.
Joyride · Customer & Competitive · Deck 2 of 2 · March 2026
← →