Uniphore · Product & GTM Strategy

Uniphore Marketplace Strategy

Determining whether and when to launch a marketplace.

Varun Murthy

The vision

Why even build a marketplace?

When fully operational and mature, a marketplace promises three things every platform wants:

</>

Developer engagementa thriving builder community

↻

Retentionstickier accounts, higher NRR

↑

Top-line revenuethird-party GMV & take-rate

However, kickstarting a marketplace is very hard, with multiple gates and steps to clear before it succeeds.

But marketplaces are hard

You have to solve a three-sided problem

A vibrant platform needs three balanced sides — supply, demand, and the governance that makes it trustworthy.

Supplyenough apps worth installing

Governancetrust, security & support — product · GTM · CS

Demandcustomers who actually adopt

Reframing the problem

Most marketplace discussions start with:

"Should we build a marketplace?"

The real question:

How do we accelerate developer adoption while increasing customer value and platform defensibility?

Marketplace strategy is downstream of an ecosystem strategy.

Executive summary

Build an ecosystem

1Focus on ecosystem creation, not marketplace creation.
2Launch a curated marketplace as the first ecosystem layer.
3Progress through gated phases with KPIs to guide further expansion.
4Treat the marketplace as an integrated platform play and not a standalone feature.

The objective: create a vibrant ecosystem that enables us to eventually collect marketplace revenue.

ECOSYSTEMThe marketplace is the first step

Have we earned the right?

Ecosystem readiness assessment

Developer demandMED-HIGH

Customer demandHIGH

Application supplyLOW

Distribution advantageHIGH

Governance advantageHIGH

Platform readinessMED-HIGH*

*Assuming mature APIs and SDKs.

The competitive reality

Three battlefronts at once

Click through each front to see the players in that space.

1 · CX

Uniphore owns the customer relationships and mindshare. There are other established app ecosystems.

2 · Horizontal enterprise AI

Already own installed base, billing & governance and are building agent marketplaces now. They are the real threat.

3 · Agentic pure-plays

Well-funded specialists going straight at the highest-value use cases.

Uniphore competes on all three fronts. GTM is informed by where we have earned the right to win - earned secrets in customer experience.

Genesys · ~1/3 of Cloud customers use ≥1 AppFoundry app

Salesforce · 29k+ Agentforce deals, 1,000+ agents

Sierra · $15B valuation / ~$150M ARR

The wedge

Use CX as a beachhead and expand into other use cases

Vertical solutions · by industry →

Horizontal solutions↓ span every industry

Energy

Financial Services

Insurance

Telecom

Healthcare & Life Sciences

Retail

Employee ProductivityEmpower employees and improve productivity

Field Workforce Assistant

Relationship Manager Copilot

Claims Adjuster Assistant

Store Associate Assistant

Care Coordinator Copilot

Store Operations Assistant

Process AutomationAutomate and orchestrate core business processes

Work Order Automation

KYC Onboarding Automation

Claims Processing Automation

Network Ticket Automation

Prior Authorization Automation

Order-to-Cash Automation

Analytics & InsightsTurn data into intelligence and actionable insights

Asset Performance Analytics

Fraud Detection & Insights

Loss Analytics & Insights

Network Performance Analytics

Patient Insights Analytics

Demand & Inventory Analytics

Customer ExperienceElevate customer engagement and satisfaction

Outage Communication Assistant

Customer 360 Engagement

Policyholder Service Assistant

Customer Care Automation

Patient Engagement Assistant

Personalized Marketing Assistant

↓ START HERE

Risk & ComplianceManage risk and ensure regulatory compliance

Environmental Compliance Monitor

Regulatory Reporting Assistant

Fraud Detection & Compliance

Data Privacy & Compliance

HIPAA Compliance Monitor

Policy & Risk Monitoring

Data Management & GovernanceUnify, govern and secure data across the enterprise

Operational Data Management

Financial Data Governance

Policy & Claims Data Management

Subscriber Data Management

Patient Data Governance

Product & Customer Data Management

Begin where the earned secrets are — Customer Experience. Win that beachhead, then earn the right to expand.Once CX supply is proven, the platform expands across every function and industry — horizontal reach, governed expansion.

Marketplace maturity model

Adoption compounds as the marketplace matures

Foundation — Uniphore ships first-party apps to prove the platform.Phase 1 · Prove Demand — partners build and customers adopt.Phase 2 · Prove Supply — customers & partners sustain supply and consume their own apps.Phase 3 · Prove Economics — ISVs join and can independently monetize their apps.

Phase 1 · Prove DemandPhase 2 · Prove SupplyPhase 3 · Prove Economics

Phase 1 — Prove Demand

Hypothesis

Customers will consume marketplace applications if discovery and deployment become frictionless.

Goal

Validate demand At this stage we don't need to worry about monetization or scale.

What we build

Catalog, search & discovery
Installation & app lifecycle
Certification badges

GTM focus

Beachhead is CX. We need to seed & prove demand at the point of highest pain first
Customer success & partner enablement
Design-partner programs

Internal dependencies & collaboration

Product
Engineering
Security & Trust
Customer Success
Design

Concierge — describe a problem, get matched agents ↗

Uniphore Agent Marketplace — Browse the governed catalog

Browse — the governed agent catalog ↗

Phase 1 · Prove DemandPhase 2 · Prove SupplyPhase 3 · Prove Economics

Phase 1 — Decision Point

Team

1 PM · 2 engineers · 1 designer · shared security & legal — governed by a monthly steering committee.

Investment

$1.5–2.5M Year 1 — most of it ecosystem activation, not engineering

SUCCESS

Attach > 20%

> 2 apps per account

Faster time-to-value

NRR lift > 2%

CSAT improvement

FAILURE

Attach < 10%

Low repeat installs

No expansion to other use cases

No retention improvement

Gate: succeed → fund Phase 2. Fail → keep as a lightweight catalog feature and stop.

Phase 1Phase 2 · Prove SupplyPhase 3 · Prove Economics

Phase 2 — Prove Supply

Hypothesis

Customers and partners will build reusable applications.

Goal

Validate ecosystem creation.

What we build

Publishing workflows
Analytics
Certification workflows
Governance tooling

GTM focus

Strategic SIs
Developer enablement
Customer champions & co-selling

Internal dependencies & collaboration

Engineering
Security & Trust
Partnerships
Developer Relations
Legal

Trust Office — governance & review command center

Trust Office — every agent reviewed & trusted before a customer sees it internal ↗

Phase 1Phase 2 · Prove SupplyPhase 3 · Prove Economics

Phase 2 — Decision Point

Team

Expand: partner manager · certification team · developer relations.

Investment

+$2–3M incremental

SUCCESS

Published applications

Cross-customer reuse

Supply growth rate

Publishing velocity

FAILURE

Apps stay private

Low reuse

Low publishing activity

Gate: only proceed if supply becomes self-sustaining.

Phase 1Phase 2Phase 3 · Prove Economics

Phase 3 — Prove Economics

Hypothesis

Developers will build because Uniphore provides valuable distribution.

Goal

Validate marketplace economics. The marketplace becomes a standalone business unit.

What we build

Billing & revenue sharing
Developer portal
Marketplace analytics

GTM focus

ISV recruitment
Developer conferences
Certification & community programs

Internal dependencies & collaboration

Finance
Legal
Sales
Partnerships
RevOps

Phase 1Phase 2Phase 3 · Prove Economics

Phase 3 — Decision Point

Investment

+$3–5M incremental

Revenue streams

Revenue share
Premium placement
Consumption pricing
Certification & training

SUCCESS

Active publishers

GMV

Revenue per publisher

Contribution margin

FAILURE

Low liquidity

Weak monetization

Stagnant supply

Gate: scale or retrench.

Governance · the operating model

Success depends more on governance than engineering

Monthly — KPI & investment gate · Quarterly — business review and new feature enablement with committee review.

Inside the Trust Office — the live governance review APIs · tools · evals · trust gate internal ↗

The real prize

A platform NRR lever — not a side P&L

Net revenue retention110% → ~114%

+$24M ARR run-rate by Year 3

~$37M cumulative revenue lift over 3 years

Expansion (NRR lift) — attached accounts adopt & expand faster

Retention — installed agents raise switching cost, lower churn

Premium first-party agents — direct new ARR

Marketplace take-rate — ISV GMV share (Phase 2+)

Services pull-through — every deployed app pulls implementation revenue

On a $300M ARR base, NRR is the real prize board-level number. The directly-attributable model (+$12.8M, payback Q4) is the conservative floor.

Risk & the one mitigation

Every risk routes to the same mitigation — staged capital

What could break this

!Hyperscaler consolidation

!Regulatory changes

!AI commoditization

!Weak developer engagement

!Weak customer demand

→

Phase 1$2.1M

→

Phase 2+$2.7M

→

Phase 3+$3.3M

3-yr total$8.1M

The model

Base case: breakeven in Year 1, +$12.8M over three years

Marketplace_Financial_Model.xlsx · Model BASE CASE · $K

($K)	Year 1	Year 2	Year 3
Recognized benefit	2,302	7,166	11,404
Program cost	2,100	2,700	3,300
Net	+202	4,466	8,104
Incremental ARR run-rate (EOY)	4,800	9,396	12,924

Payback ~Q4 (Y1 Q4) 3-yr net +$12.8M Benefit : cost 2.58× Per attached account 9× · ~6-week payback

Scenarios (3-yr net): Conservative +$4.5M · Base +$12.8M · Upside +$18M. Stage gates cap the downside at the Phase-1 tranche; benefits exclude services pull-through & defensive value.

Scope & what's next

Deliberately out of scope for this business case

Developer & ISV community DevRel programs, incentives, community governance — the mechanics of standing up a third-party developer ecosystem.

Pricing, packaging & take-rate Final monetization model for premium agents and Phase 2/3 marketplace economics.

Partner & ISV legal framework Agreements, liability, IP ownership & revenue-share terms.

Billing, metering & rev-share infra The systems to actually run marketplace economics at scale.

Certification at scale Operationalizing the 4E-L trust review as supply volume grows.

GTM motion & incentives Sales comp, CSM playbooks & co-sell mechanics for the marketplace.

Scoped out to keep Phase 1 focused on proving demand — each becomes its own workstream as we earn the right to the next phase.

ECOSYSTEM

Final recommendation

Don't build a marketplace.
Build an ecosystem.

Launch a curated marketplace as the first ecosystem layer. Earn the right to open the platform.

Validate demandValidate supplyValidate economics

Every successful marketplace in history earned the right to exist. Uniphore should do the same.

Salesforce and Microsoft are already building governed agent marketplaces — the category is forming now.

Explore the live Marketplace ↗ Enter the Trust Office internal ↗

Uniphore Marketplace Strategy

Why even build a marketplace?

You have to solve a three-sided problem

Build an ecosystem

Ecosystem readiness assessment

Three battlefronts at once

Use CX as a beachhead and expand into other use cases

Adoption compounds as the marketplace matures

Phase 1 — Prove Demand

Hypothesis

Goal

What we build

GTM focus

Internal dependencies & collaboration

Phase 1 — Decision Point

Team

Investment

SUCCESS

FAILURE

Phase 2 — Prove Supply

Hypothesis

Goal

What we build

GTM focus

Internal dependencies & collaboration

Phase 2 — Decision Point

Team

Investment

SUCCESS

FAILURE

Phase 3 — Prove Economics

Hypothesis

Goal

What we build

GTM focus

Internal dependencies & collaboration

Phase 3 — Decision Point

Investment

Revenue streams

SUCCESS

FAILURE

Success depends more on governance than engineering

A platform NRR lever — not a side P&L

Every risk routes to the same mitigation — staged capital

Base case: breakeven in Year 1, +$12.8M over three years

Deliberately out of scope for this business case

Don't build a marketplace.Build an ecosystem.

Don't build a marketplace.
Build an ecosystem.