Product Strategy · Initial thinking

Three options. One recommendation.

Three potential directions for the long-term Product Strategy in Pillar 3, with the value each could create, the watch-outs we need to be aware of, and the decision we need to make next.

Author
Blake Moseley
VP of Product
Audience
Paul Archer
CEO
Scroll
A note from Blake · For Paul

What this is, and what it's for.

This document is the output of the strategy work I've been running since the workshop with you and Joe in late April.

The question I've been working through is simple: once we deliver Brilliant Basics as Pillar 1 and the AI-native rebuild as Pillar 2, what does Pillar 3 become? What is the long-term Product Strategy for Duel?

Before going further, a framing point worth being explicit about: the Product Strategy sits above the Operating Model. The Operating Model is how Product and Engineering execute: the cadences, the rituals, the decision rights. The Product Strategy is what we're executing toward. The Operating Model cannot do its job properly until we've decided where we're pointing it.

The reason I think this matters now is because the long-term product strategy cannot sit separately from the work we are doing today. It needs to guide the decisions we make now, particularly as we move into the platform rebuild. Engineering need to understand what we are ultimately building towards so the foundations we put in place now are the right ones. If we only optimise for Brilliant Basics and the rebuild in isolation, we risk making short-term decisions that have to be undone later.

For Product, the long-term strategy gives the team a clear direction of travel. It helps us understand which problems matter most, which capabilities we should prioritise, and how the work we are delivering now compounds into something bigger over time. It also gives me the ability to lead the team with more clarity, so we are not just delivering features in sequence, but making deliberate choices that build towards a future version of Duel.

It also gives us a stronger, clearer story externally. Not because Series B should define the strategy, but because a strong product direction helps show where Duel is going, why that direction matters, and how the platform can compound in value over time.

To answer this properly, I've worked through every major input we have: the board mandate, the runway, the operating model, the company strategy, the philosophical anchors you've set, the decisions already locked in, and the signals coming from the team.

I then developed a wider set of long-term strategic options and stress-tested each one in detail, using Claude as a strategic sparring partner across dozens of iterations. The goal was not to create something that simply sounded compelling, but to pressure-test the logic, challenge my own bias, and get to options that hold up under scrutiny.

What follows is the distilled version: three potential options for Pillar 3, which I'd love to workshop with you. These are not decided recommendations at this stage. They are options designed to help guide the conversation around what could become our long-term Product Strategy, what we want Duel to become, and what strategic direction gives us the strongest foundation for the future.

I've included the value, impact, opportunity, risks and trade-offs for each option, along with my current recommendation at the end. I've deliberately preserved the trade-offs so we can challenge the thinking properly, rather than just rubber-stamp a direction.

It's worth reading this once from start to finish. Then we can work through it together and align on the bet we want to make.

Blake Moseley · VP of Product · Duel
Honest about today

The platform works. We let customers down in teeny tiny ways.

Not in catastrophic ways. In small, consistent ways across almost every account.

01Money

Money data isn't trustworthy

Reported numbers differ between brand accounts. Finance can't reconcile because the underlying data has discrepancies.

02Data

Data is not consistently trusted

Reporting drifts. Reconciliation needed in parallel.

03Adoption

Shipped features not adopted

AI moderation, nurture. The work landed, the value did not.

04Tracking

Affiliate and tracking issues

Brands feel tracking issues before we do. Back foot.

05Bugs

P3 bugs sit in the backlog

Affecting every brand. Priority logic does not promote them.

06Operating

Everything lands on P&E

Every ticket reaches us as noise. We cannot focus.

"

Death by a thousand cuts.

The cumulative effect on brand trust, and on our team's ability to lead, is massive.

Paul Archer
The targets

Expected is the floor.
Remarkable is the ceiling.

Today we sit below the expected line. We are in the red. By Black Friday 2026 we want to be firmly at Expected or above. Brilliant Basics is the bridge.

Remarkable
Where advocacy lives
Customers feel pulled forward. The product is the reason they're winning at advocacy. Premium narrative the market can't ignore.
↑ The gulf we cross with Brilliant Basics ↑
Expected
The floor every paying brand deserves
Data right. Money right. Features adopted. The baseline a brand of our size has every right to expect.
↑ Brilliant Basics closes this gap ↑
Disappointing · Today
Where we are now
Money drifts. Bugs age. Product firefights. The platform works but the experience is sub-expected.
The sequenced path

Three pillars. One sequence.

Three pillars are how we close the gap between today's platform and the long-term strategy. Each one solves a specific problem we face today; together they sequence the build to the future Duel needs to become.

Pillar 1 fixes what's broken now and brings us back to the expected experience. Pillar 2 re-architects the platform in parallel so we accelerate without waiting. Pillar 3 is the long-term product strategy this document is here to decide, built on the foundation Pillars 1 and 2 lay. Click any pillar below for the detail.

Sequencing visual Today
May '26 Jul Sep Nov Jan '27 Mar May Jul Sep '27
Pillar 1 · Brilliant Basics May → Nov 2026
Pillar 2 · AI-Native Rebuild Jul → Dec 2026
Pillar 3 · The Long-term Platform Nov 2026 → Sept 2027
Pillars 1 and 2 run in parallel from July to November 2026. Pillar 3 begins as Pillar 1 closes and continues through Sept 2027.
What it is

The foundational delivery phase. Close the gap between today's experience and what every paying brand should expect. Wrap up the in-flight work, ship the fixes the platform needs to be reliable, and clear the runway for Pillar 2 to build on top of stable ground.

What it does
  • Fixes the money-data discrepancies Finance can't currently reconcile
  • Drives adoption of features already shipped (AI moderation, nurture)
  • Closes the P3 bug backlog affecting every brand
  • Stabilises the affiliate and tracking pipeline so brands don't surface issues before we do
  • Reduces the noise reaching P&E so the team can run Pillar 2 in parallel
Architectural considerations
  • Money-data layer needs a single source of truth across brand accounts
  • Reporting layer needs reconciliation primitives baked in, not bolted on
  • Customer-visible features need adoption telemetry from day one
  • Bug triage must auto-promote breadth-affecting issues, not depend on manual escalation
  • Nothing here can block Pillar 2; Pillar 1 fixes ship behind feature flags where they touch the rebuild path
What it is

A parallel re-architecture phase that rebuilds the platform to be AI-native, stable, and fixable. Designed to run alongside Pillar 1 rather than after it, so the runway window isn't wasted.

What it does
  • Replaces the legacy monolith with a service-oriented architecture
  • Introduces AI primitives (agent orchestration, retrieval, generation) as first-class platform citizens, not features bolted onto a non-AI core
  • Stabilises the brand-account model so multi-brand setups behave predictably
  • Improves fixability: observable, testable, locally reproducible
  • Sets up the data backbone Pillar 3's compound modules will build on top of
Architectural considerations
  • Service boundaries chosen to match Pillar 3's module shape (Discovery, Community, Habit, Wallet, Loyalty, Firewall, Content), so the rebuild lands the foundation Pillar 3 needs
  • The Advocate Identity Graph becomes the canonical record for advocate data
  • AIDA orchestration runs as a platform service, not a feature
  • Brand-safe baseline is a kernel-level primitive, applied once, inherited everywhere
  • Money-data layer is unified: same numbers across every surface
  • AEO (Agent Engine Optimisation) baked in from the start so the platform surfaces inside AI agents and MCPs without retrofitting later
What it is

The Pillar 3 question is what the platform becomes beyond the rebuild. The shape is what this document is here to decide. Pillar 3 builds on Pillar 1's reliability and Pillar 2's AI-native re-architecture, but the strategic direction (Option 1, 2 or 3) is what determines its long-term form.

What it does
  • Activates the Advocate Identity Graph at full scale across every customer
  • Surfaces Duel inside any channel, any app, any AI agent. Channel-agnostic by design.
  • Establishes the data moat that makes the platform difficult to replicate
  • Earns the Series B narrative the company takes to market
Architectural considerations
  • SDK-first, headless: capabilities ship as primitives that brands can compose into their existing stack
  • Channel-agnostic by design: the platform surfaces wherever the advocate or brand is, including AI agents and MCPs (AEO)
  • Scalable Advocate Identity Graph: the data backbone that powers whichever strategic direction we choose
  • Cross-brand intelligence flows through the platform without leaking individual brand data
  • Architecturally flexible: the foundational choices made here have to support all three strategic options so we are not locked in before the decision is made
Why three · The work behind them

How we got to three long-term product strategy options.

Before I put the three options in front of you, I wanted to give some context on the work behind them.

This is not a brainstorm or a set of loose ideas. It is the distilled output of the strategy work I've been running over the past few weeks, following the workshop with you and Joe in late April.

I've worked through the major inputs that should shape our long-term Product Strategy: the runway, the board mandate, the company strategy, the operating model, the decisions already locked in, the philosophical anchors you've set, and the signals coming from the team.

From there, I developed a wider set of potential strategic directions and stress-tested each one against where Duel is now, where we need to get to, and what we need the platform to become over time.

The audit trail below shows how I got to the three options, and why two were ruled out.

The three strategy options · At a glance

Same foundation.
Three different shapes.

Three different shapes for the product strategy, on top of the same Brilliant Basics foundation and the same AI-native rebuild. Each delivers different value, faces a different watch-out, and earns a different Series B narrative.

01Option 01

Brand Advocacy Operating System.

A brand-facing compound platform. Foundation plus seven modules brands compose. Each module makes the others more valuable.

Build time~12 months
DifficultyMedium
PatternRippling, Stripe, Snowflake
Series B storyCompound startup multiples
Watch-outDistraction from compound
02Option 02

ARM replaces CRM.

A new category: Advocate Relationship Management. Built on the same compound foundation but architected for a fundamentally different system of record. The hardest to build.

Build time~18 months
DifficultyHardest
PatternHubSpot (category creation)
Series B storyCategory-creation multiples
Watch-outLonger sales cycle, harder build
03Option 03

Three layers, three paths.

Combine Options 1 and 2 with a rails layer underneath. Rails work like Stripe for payments: Duel's core primitives (identity, AI orchestration, money data) exposed as APIs that other platforms plug into and pay us as they use. Three commercial paths off one product. The longest build of the three.

Build time~24 months
DifficultyLongest, broadest surface
PatternHubSpot + Stripe + compound
Series B storyThree patterns stacked
Watch-outThree motions, limited team
Common to all three

Duel shows up wherever the advocate or brand is.

Whichever option we choose, the platform is channel-agnostic by design. We integrate wherever advocates already live and wherever brands already operate. Every option below carries this through.

Wherever the advocate is

Activated in the surfaces they already use.

Email, SMS, in-app, social, partner platforms, AI (AEO) agents and MCPs. We integrate; we don't compete for the channel slot.

Wherever the brand operates

Plugs into the brand's existing stack.

Any commerce platform, any CRM, any marketing system. The Duel ecosystem ships as SDKs and APIs the brand composes.

Personalisation at scale

Experiences that motivate each advocate.

Every signal feeds the Advocate Identity Graph. The platform turns that into personalised experiences for each advocate, matched to what they actually care about. Personalisation at scale is the engine: advocates receive experiences that motivate them, and that motivation becomes the value they bring back to the brand.

01
Option 01

Brand Advocacy
Operating System.

The compound platform brands compose into their advocacy programme. The Rippling playbook, applied to brand advocacy.

The bet Duel builds a brand-facing compound platform on top of one anchor object: the Advocate. A Foundation layer (Advocate Identity Graph, AIDA orchestration, brand-safe baseline, Insights, trustable money data, Agent Engine Optimisation or AEO) plus seven modules brands compose. Each module shares the same data, the same admin, the same login, so each new module makes the others more valuable. SDK-first, headless, channel-agnostic. The OS lives wherever the advocate or brand is. This is the playbook Rippling used to compound HR into a category-defining platform, applied to brand advocacy.
Build time
~12 months
Foundation + 7 modules, shipped iteratively
Engineering effort
Medium
Same compound stack across modules
Difficulty
Medium
One motion · one buyer · one anchor object

Value · What it delivers

For the brand (customer)
Radical operational efficiency.

One platform replaces 4 to 7 vendors. One renewal, one team, one set of metrics. The Rippling pattern: one admin, one login, one source of truth.

For the brand (customer)
Trustable ROI the CFO can sign off.

Data isn't stitched across vendor boundaries. CFOs get one defensible number across the programme, the same way finance teams trust Rippling for headcount and spend.

For the advocate
Personalisation at scale.

Every signal feeds the Advocate Identity Graph. Advocates receive experiences matched to what they actually care about, not generic brand campaigns. Recognition, rewards, and content all fit the individual.

For the advocate
A coherent experience everywhere.

Channel-agnostic by design. Whatever surface an advocate uses (any app, any channel, any AI agent), the relationship with the brand feels continuous, not fragmented across seven different programmes.

For Duel
NRR by structural expansion.

Every additional module is an expansion event at near-zero CAC. Rippling's playbook applied to advocacy: cross-sell into the same customer, unlock new pricing tiers.

For Duel
A compounding moat.

Each new brand strengthens the Advocate Identity Graph. Each new module deepens the cross-brand intelligence layer. The platform can't be replicated module-by-module from the outside.

Impact · The trajectory through 2030

100+
Enterprise brands

On the compound platform by 2030, growing from today's 36 Tier 1 customers.

120%+
NRR target

Closing the 62-point gap from today's 58% through structural module expansion.

6x
GAV growth

Per-brand benchmark drawn from Charlotte Tilbury's Magic Stars Academy nurture programme.

20x
ARR multiple

The valuation multiple compound startups command, with Rippling, Stripe, and Snowflake as the reference set for Series B framing.

How it works

The architecture

Brands compose modules into their own apps, dashboards, marketing stack. Each module makes the others more valuable. SDK-first, headless.

Click any module to see what it does, why it matters, and the key capabilities.

Discovery

What it does

Discovery uses social listening to find people who are already posting about the brand on social networks but are not yet part of the advocacy programme. These organic brand lovers are surfaced in real time, pre-validated, and invited into the programme directly through the channels they already use.

Why it matters

Most advocacy programmes recruit from existing customer lists. Discovery taps into the much larger pool of people who are already advocating for the brand without being asked. They are pre-warmed: they love the brand already. Pre-validation lets us separate the high-value advocates from those with potential to be nurtured into high-value status, so brands invest attention where it will compound.

Key capabilities

Social listening across networks, real-time brand mention tracking, pre-validation scoring to identify high-value advocates, identification of nurture-track potential advocates, automated invitation flows through the advocate's own channels.

Community

What it does

Creates spaces where advocates engage with the brand and with each other. Themed cohorts, peer-to-peer messaging, recognition feeds, brand-moderated discussion.

Why it matters

Advocates become more loyal, more active, and more valuable when they connect with other advocates. Community turns one-to-one relationships into network effects.

Key capabilities

Themed cohort creation, peer messaging, brand-moderated discussions, recognition feeds, network telemetry, role-based participation.

Habit

What it does

Habit is the gamification layer of the platform. Streaks, missions, levels, achievements, leaderboards, and progression mechanics turn engagement from a one-off action into habitual behaviour. Advocates come back because the platform itself is satisfying to use, not because there is a reward waiting at the end.

Why it matters

Reward-driven engagement runs out the moment the reward stops. Habit builds intrinsic motivation that sustains itself: the gamified loops keep advocates active across the platform even when no immediate payout is on offer. Habitual users are the most valuable users, and they are the cheapest to retain.

Key capabilities

Streak mechanics, mission and challenge systems, progression and levelling, achievements and unlock states, social leaderboards, behaviour-shaping reinforcement loops tuned by AIDA, notification and surface cadence that supports the habit without nagging.

Wallet

What it does

Wallet is the platform's points and credits ledger. It tracks every unit of value an advocate earns and spends: points, credits, redemption tokens, exclusive access, perks, store credit. Every issuance and redemption is recorded in one trustable system.

Why it matters

Without a clean ledger, reward becomes a Finance nightmare and a UX problem for the advocate. Wallet gives the platform one source of truth: every point issued, every credit redeemed, every perk unlocked, reconcilable across brand accounts. The ledger is what makes reward programmable rather than ad hoc.

Key capabilities

Points and credits issuance, redemption tracking, multi-unit handling (points, credits, tokens, store credit), treasury controls, balance and statement views for advocates, reconcilable reporting integrated with the brand's finance stack.

Loyalty

What it does

Tracks each advocate's contribution to the brand, ranks them, surfaces who matters most, and gives advocates a visible status arc to climb.

Why it matters

People work harder when their contribution is recognised. Loyalty makes the relationship status visible, motivating, and ownable.

Key capabilities

Contribution scoring, tier definition, milestone unlocks, advocate profile pages, status surfacing across surfaces.

Firewall

What it does

Firewall protects the platform and the brand on two fronts. First, it filters out fake advocates, AI-generated profiles, and platform abusers, so rewards only flow to real humans. Second, it analyses every piece of content for NSFW material and brand-safety alignment, so only advocates who complete challenges properly and produce content as per the brief get rewarded.

Why it matters

One fake advocate or AI-generated submission undermines the integrity of the whole programme and pays out budget that should have gone to real contributors. One off-brand piece of content can cost the brand more than the programme has paid out all year. Firewall makes both threats addressable in real time, so the brand is protected and platform abusers do not get rewarded.

Key capabilities

Bot and AI-profile detection, fake-advocate filtering, NSFW content analysis, brand-safety content classification, brief-compliance checking, conduct policy enforcement, escalation workflows, full audit trail.

Content

What it does

Captures advocate-generated content, structures it, clears rights, and licenses it back for the brand to use across owned, paid, and partner channels.

Why it matters

UGC is the highest-converting, lowest-cost creative brands can use. Content turns advocate output into a usable, rights-cleared asset library that compounds over time.

Key capabilities

Capture flows across surfaces, rights clearance, content organisation and tagging, licensing controls, distribution to brand channels and ad platforms.

Foundation layer
Advocate Identity GraphWho they are, across every channel
AIDA OrchestrationStrategy and intelligence
Brand-safe BaselineThe trust layer
InsightsWhat the data is telling us
Trustable Money DataOne source of financial truth
AEOAgent Engine Optimisation · How Duel surfaces inside AI agents and MCPs

Opportunities

  • NRR recovery is structural: each module shipped expands the existing book without new-logo dependency.
  • SDK-first, channel-agnostic architecture means Duel surfaces wherever the advocate or brand is, including AI agents and MCPs.
  • The compound moat strengthens with every additional brand on the platform. Same playbook Rippling used in HR.
  • Defends Duel's category leadership in advocacy software.

Risks & watch-outs

  • Big-customer distraction. If a major enterprise (Target-scale) asks for an ARM-style platform deal before the compound modules are mature, the team could get pulled into building Option 2 instead. The biggest threat to Option 1 is choosing to please one large customer at the cost of finishing the compound platform for everyone else.
  • Sequencing pressure. Shipping Foundation plus seven modules inside the current runway envelope is not feasible. The order modules ship in is the load-bearing decision: get it wrong and the compound effect doesn't land for any customer.
  • Foundation underbuilt. If Brilliant Basics and the AI-Native rebuild ship without the right Foundation primitives in place (Advocate Identity Graph, AIDA, money layer, AEO), Pillar 3 has to retrofit them. That delays the compound effect by months and burns engineering trust.
  • Narrative ceiling. Compound-startup is a known pattern. Some investors will ask for bigger category language than "compound." Option 2 positioning solves this, which is why the recommendation pairs Option 1 execution with Option 2 framing.
Duel is the operating system of brand advocacy, the way Stripe is the operating system of payments.
A day in 2030

The CMO at Bath & Body Works opens Duel for the morning review.

Habit shows 67% daily-active advocates. Wallet cleared $2.1M in October. Content generates millions of usable UGC. The CFO attends the advocacy review because the numbers are load-bearing.

02
Option 02

ARM replaces CRM.

A new category, owned by Duel. The HubSpot playbook: name a category, define its primitives, and become the platform every retail brand runs on.

The bet Duel does not just sell advocacy software. We name and own a new category: ARM (Advocate Relationship Management). CRM was built for the transactional era (leads, deals, opportunities). ARM is built for the relational era (advocates, contributions, reputation, value created). Same humans, different orientation, different system of record. The HubSpot parallel matters: HubSpot did not displace Salesforce by competing on CRM features. It named and owned a new category (inbound marketing), then expanded outward. ARM follows the same playbook. This is the hardest of the three options to build. A new system of record means new data primitives, new workflows, new admin surfaces, and a long category-creation arc before revenue catches up.
Build time
~18 months
New system of record · category-creation arc
Engineering effort
High
New primitives, workflows, admin · all from scratch
Difficulty
Hardest
Hardest build · longest sales cycle · category to invent

Value · What it delivers

For the brand (customer)
A platform decision, not a feature decision.

ARM replaces the CRM line item, not the advocacy line item. CMOs and CEOs buy it as a system of record for retail customer relationships, not as a marketing tool.

For the brand (customer)
Built around relationships, not transactions.

CRM was designed for leads, deals, and pipeline. ARM is designed for advocates, contributions, and reputation. Brands stop measuring customers in dollars-per-deal and start measuring them in value created together.

For the advocate
Recognised as a person, not a lead.

ARM treats advocates as humans with contributions, reputation, and intrinsic motivation, not as records in a sales pipeline. The relationship is bidirectional and built to last.

For the advocate
Personalisation at scale.

Channel-agnostic by design. Advocates engage on the surfaces they already use (any app, channel, or AI agent), and receive experiences tuned to their actual interests, not generic brand campaigns.

For Duel
Category-creation premium.

First-mover in a new category. Investors pattern-match against HubSpot's arc: name "inbound marketing," own it, expand outward. ARM earns the same shape of multiple.

For Duel
Industry narrative leadership.

Duel names, defines, and owns the category. Every analyst report uses Duel's language, the same way every inbound conversation cites HubSpot.

Impact · The trajectory through 2030

10x
Contract value

Average ARM contract vs current ACV. Multi-year, platform-level, displaces the CRM line item.

15–20
ARM logos by 2030

Fewer, deeper customers. Each is a public reference for the new category.

1st
Category owner

Duel names, defines, and owns ARM as the new system of record for retail brands. First-mover advantage in a new category.

25x
ARR multiple

Category creation commands the premium multiple. HubSpot's peak reference is the anchor for Series B framing.

How it works

The paradigm shift

Same humans, different orientation, different system of record.

Yesterday's era · 1999+
CRM
Built forTransactional relationships
Primary objectDeals and leads
Primary eventPipeline movement
Primary metricRevenue closed
BuyerVP Sales
PatternSalesforce / HubSpot
The relational era · 2026+
ARM
Built forRelational connections
Primary objectAdvocates and people
Primary eventContribution and reputation
Primary metricValue created together
BuyerCMO or CEO
PatternDuel (the new category)

Opportunities

  • The cleanest articulation of advocate-first inversion at category level.
  • Investors pattern-match against HubSpot's category-creation arc: name a category, own it, expand outward.
  • Inbound demand from analysts and conferences that pick up the ARM term.
  • Channel-agnostic by design: ARM surfaces inside any brand stack, any channel, any AI agent.

Risks & watch-outs

  • The hardest of the three to build. New system of record means new data primitives, new admin surfaces, new workflows. Much heavier engineering than Option 1's compound expansion.
  • Different buyer (CMO or CEO, not VP Marketing): longer, more political sales cycle.
  • Different budget pool (CRM, not advocacy): displaces an incumbent line item rather than finding new spend.
  • Risk of zero ARM logos closed in year one; category creation can look like marketing language until the first major reference lands.
Duel is to retail advocacy what HubSpot is to inbound marketing. They named the category, owned it, and built ARM as its system of record.
A day in 2030

Every conversation about retail customer relationships is a conversation about ARM. And ARM is Duel.

HubSpot's playbook applied to retail: name the category, own the language, become the platform every analyst report reaches for. ARM has a definition, an owner, and a category-creation arc that compounds for a decade.

03
Option 03

Three layers,
three commercial paths.

Combine Options 1 and 2 with an infrastructure rails layer beneath. Rails work like Stripe for payments: Duel's core primitives (identity, AI orchestration, money data) exposed as APIs that other platforms plug into and pay us as they use. One product, three ways to monetise.

The bet Do not choose. Combine Option 1 (compound modules in the middle), an infrastructure rails layer (Foundation rails at the bottom for partners), and Option 2 (ARM as the top layer) into a single layered platform. Three commercial paths: brands ready for the full stack buy ARM (top); brands not ready buy compound modules (middle); partner platforms (agencies, complementary tools, smaller competitors) integrate Duel's Foundation rails through APIs (bottom).
Build time
~24 months
Three commercial paths to stand up properly
Engineering effort
Very high
Three product surfaces · three motions · three buyers
Difficulty
Longest
Broadest surface · longest arc to revenue

Value · What it delivers

For the brand (customer)
Buy what fits, upgrade later.

Three entry points: the full ARM platform at the top, individual compound modules in the middle, or just the API rails at the bottom. Brands pick the layer they're ready for and grow into the others.

For the brand (customer)
Lowest barrier to entry, highest ceiling.

Smaller brands and partner platforms can start with the rails alone. Enterprise brands can buy the full ARM stack. The same platform serves both ends of the market without forcing one to fit the other.

For the advocate
More brands, one identity.

Because Duel powers more of the advocacy industry, an advocate's Identity Graph compounds across the brands they support. Personalisation gets richer as more brands plug in.

For the advocate
Personalisation at scale, everywhere.

Channel-agnostic across every layer. Whatever surface or partner platform an advocate uses, the experience is tuned to their intrinsic interests, not generic.

For Duel
Broadest TAM.

Three customer types served at once: ARM brands, module brands, partner platforms. The full advocacy industry monetised at every level, on one shared foundation.

For Duel
Three Series B patterns stacked.

Investors pattern-match against HubSpot (category creation), Rippling (compound), and Stripe (infrastructure rails) simultaneously, on one investment thesis.

Impact · The trajectory through 2030

3
Revenue streams

ARM contracts, module subscriptions, API and rails fees. Three shapes off one product.

5x
Surface area

vs Option 1. Three sales motions, three buyer personas, three product surfaces.

30x
ARR multiple

Three patterns layered: category-creation, compound-startup, and infrastructure-rails multiples stacked in one investment thesis. The theoretical premium of the three options.

100%
Industry coverage

Duel monetises every level of the advocacy stack: ARM at the top, modules in the middle, rails at the bottom. The only platform serving the entire industry.

How it works

The three layers

One product, stacked three ways. Customers self-select into the layer that fits.

Top layer
ARM
The system of record. Brands ready for the full stack buy this.
Platform contractsCMO / CEO buyer
Middle layer
Compound modules
Seven modules. Brands not ready for the full stack buy what they need.
Module subscriptionsVP Marketing buyer
Bottom layer
Foundation rails
Primitives exposed through APIs. Partner platforms integrate them under their own UIs.
API + usage feesDeveloper-led

Opportunities

  • Largest TAM of the three options. Duel monetises at every level of the advocacy industry.
  • Three-pattern story earns the strongest theoretical Series B multiple, if execution lands.
  • Foundation engineering investment is shared across all three commercial paths.
  • Cross-sell between layers: partners upgrade to modules; module customers upgrade to ARM.

Risks & watch-outs

  • Three commercial paths is more surface area than the current team (7 engineers + 1 data engineer + 4 PMs) can execute against the current runway.
  • Partner-platform sales motion is a 12+ month investment Duel does not currently run.
  • Three half-built motions deliver less than one fully built motion.
  • Pattern-matching against three categories at once may dilute the story rather than amplify it.
Duel monetises every level of the advocacy industry. Three patterns stacked: HubSpot's category arc, Rippling's compound playbook, and Stripe's infrastructure rails, all on one shared foundation.
A day in 2030

Bath & Body buys the full ARM stack. A smaller DTC brand buys just modules. A competitor integrates the rails.

Duel monetises at every level of the advocacy industry. Three distinct customer journeys, one Duel. The platform is the industry.

Side by side

How the three options compare.

Hover any row to highlight it across columns. Use the toggles below to hide an option for a direct head-to-head comparison.

01 BAOS
02 ARM
03 Combined
The bet
Brand-facing compound platform. Foundation + 7 modules brands compose.
A new category: ARM. Compound primitives re-imagined as a system of record for retail.
Three layers, three commercial paths. Foundation rails + modules + ARM.
Value delivered
Replaces 4–7 vendors. CFO can trust ROI. NRR by structural module expansion. Channel-agnostic.
Category creation premium. Larger contract values. CMO / CEO conversations. Channel-agnostic.
Broadest TAM. Three revenue streams. Cross-sell between layers. Channel-agnostic.
Build time
~12 months
~18 months
~24 months
Difficulty
Medium
Hardest to build
Longest, broadest surface
Series B story
Compound-startup multiples (Rippling, Stripe, Snowflake).
Category-creation multiples (HubSpot).
Three patterns stacked (HubSpot + Rippling + Stripe).
Market position
OS of brand advocacy. Pattern: Rippling, Stripe.
Names and owns ARM in retail. Pattern: HubSpot.
Monetises every level. Pattern: HubSpot + Rippling + Stripe.
Watch-outs
Pull-away risk from ARM-style deals. Compound is multi-year.
Hardest engineering build. Longer sales cycle. Different buyer.
Three motions exceeds current team capacity. Half-built motions deliver less.
The recommendation

Option 1 execution.
Option 2 positioning.

Build the compound platform exactly as Option 1 describes, using the Rippling-style playbook applied to brand advocacy. Position it externally as ARM replaces CRM, using HubSpot's category-creation arc as the reference. Take both stories to the Series B narrative. Park Option 3 as 2027-onward optionality.

Execution motion
OPTION 01

Compound platform.

Foundation + 7 modules. Sold to enterprise retail via the existing referral motion.

+
Strategic positioning
OPTION 02

ARM replaces CRM.

The Series B narrative, the AI-native keynote framing, and the HubSpot-style category-creation arc.

=
The hybrid
THE CALL

Cleanest path,
biggest story.

Modular execution today. Category language for tomorrow.

What happens next

The next step.

One session matters most: Lock the Bet, with Paul and Joe. Everything else flows from there.

Session 5 · Up next

Lock the bet.

Working session with Paul, Joe, and Blake to decide the strategic direction for Pillar 3.

When
By Tue 19 May 2026
How long
60–90 minutes
Who
Paul, Joe, Blake
Where
Working session
Before the meeting

What I need from Paul and Joe.

P

Paul

CEO
  • Read this document end-to-end
  • Form a view on the recommendation: hybrid, pure Option 1, pure Option 2, or Option 3
  • Decide how aggressive AI-native ambition should be in 2026
  • Confirm the philosophical anchors that go into the pitch (advocate-first inversion, Advocacy Flywheel, Three True Levers)
  • Note any red flags or modifications, no holding back
J

Joe

Engineering
  • Read this document end-to-end
  • Validate engineering scoping for the recommendation inside the 5.8-month runway
  • Validate the AI-native rebuild assumptions for Pillar 2
  • Flag technical risks the recommendation does not address
  • Confirm the Pillar 1 → 2 → 3 sequencing is feasible with current team
What we walk away with

A ratified strategic direction.

One of three outcomes lands. All three keep the work moving forward.

A

Ratified

The hybrid recommendation (Option 1 execution + Option 2 positioning) is locked as the direction. Move straight into Session 6.

B

Modified

Paul reframes specific elements. Recommendation rewritten with his input. Underlying analysis stays valid; smaller rework than it sounds.

C

Replaced

Paul lands on a different option (pure Option 2 or pure Option 3). Recommendation flips. Document supports either alternative.

After the product strategy direction is aligned

Three more sessions land the final strategy.

06
Wed 20 May 2026

Stress-test the direction

Take the aligned strategy and pressure-test it against every commitment we've made: the 5.8-month runway, the board mandate, the operating model, and our customer promises. The goal is to find where it strains and decide together what to defend, what to refine, and what to acknowledge as an honest watch-out. Output: a sharpened, more resilient version of the strategy.

07
Mon 25 May 2026

Sharpen the strategic narrative

Define the precise language for the parts of the story that need to be air-tight when an investor, customer, or analyst hears them: the defensibility thesis, how the compound mechanics work, the AI-native specifics, the advocate-first framing, and the Series B investment story. Output: a written narrative the team can use consistently across every audience.

08
By Fri 29 May 2026

Test it with the audiences that matter

Take the finished narrative outside this room. Run it past a lighthouse customer to check it lands commercially, a friendly investor to validate the Series B angle, the wider exec team to confirm internal alignment, and a board dry-run to rehearse the formal ask. Output: confidence the story holds, or named gaps to close before it goes live.

Let's lock the bet, together.

Blake Moseley · VP of Product, Duel · blake@duel.tech