All work stories
Anonymized case studyDigital assets / Two-sided marketplace

Separating revenue engines in a digital-asset marketplace

A two-sided digital-asset marketplace had a working financial model for buyer acquisition, seller participation, subscriptions and transaction commissions. A follow-up revenue note challenged whether specialized platform services were attached to the right economic driver.

Revenue-model development and extension reviewFinancial model
Fictional two-sided digital-asset marketplace connecting project onboarding, customer access, several transaction services and a reconciliation team.
Original concept illustration. No client data shown.
CONFIDENTIAL BY DESIGNWhy you won’t see the client workbook

Financial models contain pricing, salaries, conversion assumptions, funding plans and other sensitive data. I do not publish client workbooks, identifiable screenshots or proprietary inputs—especially where an NDA applies. This page uses an anonymized summary and original concept art to explain the business decision and my modeling approach.

Acquire → retainBuyer engine

Marketing, acquisition cost and churn determine the active customer base before revenue is calculated.

Buyers ↔ sellersNetwork balance

Demand and seller participation must grow together for a two-sided marketplace to remain usable.

Orders + valueTransaction bases

Fixed fees follow activity counts, while value-linked commissions follow transaction value and mix.

Operations → capitalDecision bridge

Costs, cash, financing, KPI and valuation stay connected to the operating assumptions.

WHY THIS WASN’T A TEMPLATE EXERCISE

The model had to respect
how the business actually moved.

The supplied formula-linked workbook connects buyer growth and churn to sellers, new and repeat orders, subscriptions, transaction mix, costs, statements, funding, KPI, break-even and valuation. The reconstruction keeps later revenue requests visibly separate from the implemented engine.

01

An active customer was not a universal revenue driver

Subscriptions, trading activity, payment processing, conversion, project onboarding and partner services could each depend on a different combination of users, projects, frequency, transaction count or value.

02

Recurring access and transaction income ran on different clocks

Buyer and seller subscriptions followed active accounts, while commission revenue required actual order activity. Combining them would hide whether growth came from access or use.

03

A fee per order behaved differently from a share of value

The same order count could produce a different result when average value or service mix changed. Both commission bases had to remain visible before they were consolidated.

04

The two sides of the marketplace had to stay in balance

Buyer acquisition could expand demand, but seller participation determined whether the network could support it. A simple ratio was useful for planning while still remaining an assumption to test.

05

The extension note went beyond the implemented revenue schedule

The workbook visibly separated subscriptions and several transaction categories, but not every requested issuer, cash-out, conversion or referral stream appeared as a dedicated module. The gap needed to remain explicit.

06

Valuation sat downstream from operating choices

Acquisition, churn, order mix, costs, working capital and financing all affected cash flow. A discounted value could only be as dependable as those linked planning assumptions.

MODEL ARCHITECTURE

From operating activity
to a decision-ready view.

Each layer has one job. Together they keep the commercial story, unit economics and cash consequences on the same timeline.

01

Marketing and buyer acquisition

Marketing spend and acquisition cost create new buyer cohorts rather than applying one top-line growth rate.

02

Churn and active buyers

New buyers, prior active accounts and churn reconcile into the population available for subscriptions and repeat activity.

03

Seller participation

A separate active-seller bridge keeps the supply side of the marketplace visible alongside buyer growth.

04

New and repeat orders

First purchases and recurring activity follow different drivers before combining into total marketplace orders.

05

Subscription revenue

Buyer and seller access fees use their own active populations and pricing assumptions.

06

Service mix and transaction value

Orders and gross transaction value are allocated across distinct activity types so the mix can change independently from total volume.

07

Fixed and value-linked commissions

Per-order fees and percentage commissions are calculated separately, then reconciled into transaction revenue.

08

Costs, people and investment

Direct costs, operating expenses, payroll, assets and capital expenditure carry the operational consequences of the growth plan.

09

Statements, funding and valuation

Integrated statements, sources and uses, financing, break-even, KPI and cash-flow valuation connect operations to the capital decision.

10

Revenue-extension register

The review layer keeps proposed issuer, conversion, cash-out and partner streams outside the base model until each has a defined trigger, volume, price, cost and timing rule.

WHAT THE ANALYSIS SURFACED

Useful answers,
without exposing client data.

The takeaways are intentionally qualitative. Exact assumptions, calculations and outputs remain inside the confidential client model.

Reconstructed insight

Retention became valuable only through a defined behavior

An active account could support a subscription, an order or several specialized services. The model became clearer when each outcome followed its own adoption and activity path.

Generalized project pattern

The same marketplace value could create different revenue

Changing the mix of trading, processing and partner activity could change commission income even if total transaction value stayed constant.

Reconstructed insight

Fixed and variable commissions created different sensitivities

More small transactions favored per-order fees, while fewer larger transactions could favor value-linked pricing. Keeping both layers visible exposed the trade-off.

Generalized project pattern

Seller subscriptions diversified revenue but did not solve liquidity

Recurring seller fees could reduce dependence on transaction income, yet the marketplace still needed sufficient buyer demand and activity to remain useful to sellers.

Reconstructed insight

Unimplemented requests were more useful as a gap register

Naming a future revenue stream did not make its calculation complete. Recording its economic base and missing evidence prevented a planning request from being mistaken for an existing module.

Generalized project pattern

A valuation output was a traceable scenario, not a result

The decision view improved when value could be traced back to acquisition, retention, transaction mix, margins, investment, working capital and financing assumptions.

MODELING APPROACH

The working system
behind the answer.

  • Marketing, customer-acquisition and churn schedule
  • Active-buyer and active-seller operating bridge
  • New-customer and repeat-customer order schedules
  • Buyer and seller subscription-revenue schedules
  • Service-mix, order-allocation and transaction-value schedules
  • Fixed per-order and value-linked commission schedules
  • Direct-cost, operating-expense and payroll model
  • Capital expenditure, assets, working-capital and financing schedules
  • Integrated income statement, cash flow and balance sheet
  • Dashboard, charts, break-even, KPI, sources-and-uses and valuation views

CASE CONFIDENTIALITY

This anonymized case explains the buyer, seller, order, subscription, commission, cost, funding and model-extension logic without naming the client, company, people, projects, issuers, partners, location or dates. Exact customer, pricing, churn, order, transaction-mix, fee, cost, staffing, asset, financing, ownership, forecast, KPI and valuation assumptions remain private because client work can be confidential or NDA-protected. No workbook, worksheet, formula, chart, screenshot, source document, file name, logo, interface, proprietary term, token, issuer or identifying project detail is reproduced. The sources were reviewed as planning evidence, not as a recalculation, financial-model audit, accuracy certification, legal assessment or proof of implementation. The illustration is an original fictional marketplace rather than a real platform, client asset, transaction network or operating result.

CUSTOM PROJECTS START AT $2,500 USD

Need a financial model?
Or the complete business package?

The final fee reflects the agreed scope, complexity and deliverables. Combined packages are quoted individually.