2 acquired companies
Disparate tech stacks created massive redundancies with no integration strategy
Unified foundations and shared primitives for payment systems spanning five business verticals and three revenue streams.

Spotify’s commerce ecosystem spanned subscriptions, ads, merch, podcasts, and licensing, and the systems moving money had grown fast and in parallel. Finance ran on nine pay-out tools across five verticals and three revenue streams, with no shared way of talking about any of it.
At its core, this was a language problem. The foundational move was to give the organization a shared vocabulary strong enough that the systems underneath could finally talk to each other.
Disparate tech stacks created massive redundancies with no integration strategy
Teams built bespoke solutions for each unique user type which limited scale of any tool
Data was unable to flow through the ecosystem causing a reliance on manual reconciliation

Disparate onboardingEach product had its own onboarding tool. Launching something new meant first finding the right entry point, then learning a workflow that did not connect to the systems around it.
Complexity concentrated in payouts, where every vertical relied on its own bespoke tooling.
Nine tools assessed with a jobs-to-be-done lens across ownership, capabilities, and dependencies.
User scale ranged from individual creators to enterprise clients needing white-glove support.
Less mature areas ran on manual spreadsheets; others used configurable tools with real reuse potential.
Almost no tooling overlap between payins and payouts beyond the general ledger.
That gap became the opening to connect both sides and improve end-to-end data flow.
Use-Case Framework gives teams a structured way to navigate the commerce ecosystem. By mapping the full lifecycle of a business model (what is sold, how, to whom, and how it’s fulfilled, paid for, and accounted for) it clarifies the services and capabilities needed to go to market. Pre-approved, scalable “Golden Paths” let teams fast-track decisions. Configurable but less mature paths were flagged for further discovery, while unsupported approaches were marked as off-road, surfacing risks and dependencies early.
Every business model reads across four groups: how money comes in, how revenue is shared, how money goes out, and the scale it has to work at.
Pay in
Segment
Consumer
Business
Product
Digital
Physical
Purchase
Subscriptn.
Usage
OTP
Fulfillment
Immediate
Deferred
Revenue
Supply
Reseller
Affiliate
Marketplace
1st party
Cost
Rev share
Commission
Fixed
Pay out
Segment
Creator
Enterprise
Top-tier
None
Payment
Immediate
Advanced
Deferred
Claims
Scale
Volume
High
Mid
Low
Market
Mature
Mid-tier
Emerging
Through the financial tooling work I positioned design as a real partner in UI, systems, and strategy. I worked to establish the approach of simplifying both our process as well as the tool itself so that we can scale fast and do more with less.
A shared language across 3 divisions connecting product, finance, and engineering decisions.
Clearer golden paths and earlier visibility into dependencies accelerated go-to-market timelines.
Reduced complexity by streamlining flows across the ecosystem.