For leadership weighing recurring revenue, platforms, marketplaces, licensing or productised services. We map customers, payers, partners, revenue, cost, incentives, dependencies and scale, to determine whether the current or proposed model can create and retain durable value, before its complexity is scaled.
Select the situation you recognise. Each opens the structural diagnosis behind it.
Scaling multiplies whatever structure exists: a sound model compounds value, and a structurally flawed one compounds cost, complexity and dependency at exactly the same rate.
A business model, in plain terms, is the structural answer to three questions: how the business creates value, how it delivers that value, and how it captures some of the value as revenue and profit. Unit metrics can look healthy while the structure underneath is quietly wrong: the wrong participant carrying the cost, an incentive that weakens as volume grows, a dependency that hands bargaining power to someone else, a cross-subsidy nobody has made explicit. We analyse the model as a whole system: every participant, every flow of value and money, every incentive that has to keep holding for the model to work. Proposed models are treated as hypotheses with an evidence plan and stage gates, not as strategies to be admired.
Model choices are conditional, not fashionable. Each structure works under specific conditions, and the analysis states which conditions apply to you.
Predictable revenue bought with continuous delivery obligations and a transition trough. Works when value is genuinely ongoing, not when billing wishes it were.
Revenue tracks value delivered, easing adoption, at the cost of volatility and a permanent incentive to measure what customers actually use.
Powerful economics after liquidity, punishing before it. Works when both sides gain more than the take rate costs them, sustainably, without subsidy.
Scale through others' capital and effort, traded against control, margin share and the risk of training future competitors.
Standardisation economics on service expertise. Works while the package covers enough cases without quietly re-becoming bespoke.
Layered models that monetise the same assets in multiple ways: each layer needs its own economics, and the cross-subsidies between them need to be chosen, not discovered.
New models are hypotheses. The process ends with an evidence plan and stage gates, not a leap.
Every participant, value flow, payment flow and obligation in the model as it actually operates, including the informal arrangements the org chart doesn't show.
The structural questions applied systematically: who receives value, who pays, what drives cost, what scales, who must stay motivated, where value leaks or concentrates.
Revenue model, cost and asset structure, operating leverage, incentives, network and liquidity dynamics, cross-subsidies, dependencies and bargaining power, quantified where evidence allows, ranged where it doesn't.
GateA current-state verdict: which structural properties are strengths, which are faults.
Candidate structures (subscription, usage, marketplace, licensing, managed service, data/API, hybrid) compared under your conditions with trade-offs stated, not just upside.
Staged change design: how existing customers migrate, what the new model takes from the old one and when, which capabilities must exist first, and what option value each stage preserves.
GateA transition only proceeds where the trough is funded and reversible stages exist.
The assumptions that carry the model are named, and each gets an evidence plan: what will be tested, at what stage, and what result advances, holds or stops the change.
Business model economics is the structural layer: most engagements route into or out of the specialist streams that examine one part of the structure in depth.
Owns: participant mapping · incentive analysis · model alternatives · transition design.
The structure is sound but the per-unit numbers inside it need proving.
Contribution, cost-to-serve and payback at unit level.
The model defines the units; unit economics tests whether each one earns its keep.
Payment Processing Cost Reduction. An ecommerce retailer was losing a significant percentage of revenue to payment processing and invoice platform fees. Web Lifter redesigned the entire sales and payment workflow, replacing Stripe and Paycove with a direct Westpac PayWay integration and a custom-built invoicing platform. The new architecture reduced transaction costs, streamlined operations, and delivered immediate profit improvements without requiring any increase in sales volume.
Read the case“We can't recommend Web Lifter highly enough … a digital partner who could understand our operations, connect the dots between marketing and backend systems, and deliver real results.”
Narrower and more testable. We analyse one thing (the structural economics of how the business creates, delivers and captures value) and every claim comes with the evidence it rests on and the test that would validate it. The output is a model verdict with stage gates, not a vision deck.
A recurring-revenue shift is exactly the change that deserves structural analysis, because it looks like a billing change and is actually a model change: continuous delivery obligations, a transition cash trough, different retention economics. The engagement scales to the decision: one model change is a focused piece of work, not an everything review.
Both. Roughly half of the value is in mapping the model you already run: most established businesses carry cross-subsidies, dependencies and incentive drift that nobody has made explicit. The other half is testing a proposed change against that honest current state.
How profit responds when revenue grows. High operating leverage means costs stay put as volume rises, so growth is progressively more profitable, but downturns hurt more. Low leverage means costs grow with every unit, so margins are steadier but scale adds less. Knowing which your model has changes how you fund it, price it and grow it.
One part of the business funding another: profitable segments carrying weak ones, the core funding the new venture, one side of a marketplace paying for the other. Cross-subsidies aren't wrong; unexamined ones are. The analysis makes every subsidy explicit so it becomes a choice with a size and a time limit.
As a hypothesis. Its critical assumptions are named (willingness to pay, incentive alignment, liquidity thresholds, delivery costs) and each gets an evidence plan and a stage gate. The recommendation is never 'launch it'; it's 'here is the cheapest sequence of tests that tells you whether to'.
Migration is designed, not assumed. The transition principles cover who moves, when, on what terms, and what happens to those who won't, because a new model that strands the customers funding the old one fails structurally before it fails commercially.
By quantifying it rather than fearing it. Every new model takes something from the old one; the questions are how much, how fast, and whether the exchange is favourable. Staged transitions with gates preserve the option to slow down or stop if the exchange turns out worse than modelled.
A current-state participant and value-flow map, revenue and cost architecture, incentive analysis, a dependency register, compared model alternatives, a target-model recommendation, transition principles and a validation roadmap with stage gates, walked through with the leadership team.
The diagnostic is the broad entry point that finds which economic question matters most; this is the deep engagement when that question is structural. If you can already articulate the model decision, start here. If the constraint could be pricing, profitability or demand instead, start with the diagnostic.