For operators who suspect blended averages are hiding weak units. We model revenue, discounts, variable cost, cost-to-serve, acquisition and retention down to contribution (at the level decisions are actually made) so leadership can scale, reprice, redesign or stop with evidence.
Each of these usually means the average is hiding a spread: strong units quietly funding weak ones. Select a symptom to see what it signals.
Left on blended averages, the business keeps funding the wrong units: strong products subsidise weak ones, the loudest customers get the most capacity, and every growth push amplifies losses somewhere in the mix.
First we define the unit (the thing the decision is actually about): a customer, order, project, subscription, service, SKU, location, channel, transaction or cohort. Then we model its economics in one consistent chain: revenue, less discounts and refunds, less direct and variable costs, less the service cost that can be attributed to it, less acquisition and onboarding, adjusted for retention and lifetime effects, down to contribution. Contribution is the plain-language heart of it: what each unit genuinely leaves behind to cover shared fixed costs and profit. And because the common fear here is arbitrary cost allocation, every line is graded (direct evidence, attributable cost, allocation, sample or proxy) so you can see exactly how solid each number is and test the ones that are judgement calls.
Unit economics isn't the decision. It's the evidence the decision deserves.
Which customers to pursue, keep, reprice or renegotiate: based on contribution after cost-to-serve, not revenue alone.
Where acquisition budgets earn their payback, and which channels are buying volume the economics can't support.
Where scope, inclusions and minimums should move so the offer stops leaking contribution.
Aligning commissions and targets with contribution, so the sales engine stops being paid to win unprofitable work.
Where service effort is concentrated enough that automation or redesign pays for itself.
What to scale, reprice, redesign or exit, with strategic portfolio roles flagged, not steamrolled.
Inputs are practical: revenue and transaction data, cost and labour information, retention and acquisition data, validated with the people who live the numbers.
Agree what's being decided, choose the unit that matches it, and set the questions the model must answer.
GateAgreed unit definitions and decision questions
Collect revenue and transaction data, cost and labour information, and retention and acquisition data, and record what's missing.
GateData coverage and gaps stated honestly
Model each unit from revenue to contribution, grading every line: direct evidence, attributable cost, allocation, sample or proxy.
Walk the model with operators and leadership, challenging allocations, surfacing strategic portfolio roles the numbers alone can't see.
GateStakeholder-validated model, contested assumptions resolved or flagged
Deliver scale, reprice, redesign or exit recommendations with the leakage register and a model you keep and re-run.
Unit economics is the evidence layer other decisions draw on. Select a pathway to see what hands over where.
Owns: unit definitions · contribution · cost-to-serve · CAC, LTV and payback · leakage · break-even.
The unit is sound but priced wrong.
Prices, packages, tiers, discount governance, migration.
Receives contribution floors and leakage evidence to price against.
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.”
No. Your accountant reports what happened for compliance; this models which units create value so decisions can be made. We don't prepare financial statements, tax filings or statutory accounts. We build decision-grade analysis on top of the records you already keep.
No. Blind cost cutting is explicitly out of scope. Some low-contribution units deserve repricing, some deserve redesign, some play a strategic role worth funding knowingly, and some should stop. The recommendation depends on the evidence and the unit's role, and the call stays with leadership.
Whatever the decision is about: a customer, order, project, subscription, service, SKU, location, channel, transaction or cohort. Most engagements model more than one, because the interesting answers usually sit where two views disagree: a profitable product sold through an unprofitable channel, say.
By grading every line of the model: direct evidence, attributable cost, allocation, sample or proxy. Allocations are sometimes unavoidable, but they're shown, justified and testable, never hidden. If a verdict flips when a soft allocation moves, we tell you the verdict is soft too.
It gets flagged, not executed. Some units open doors, anchor relationships or feed other units' demand. The analysis makes the subsidy explicit and sizes it, so keeping the unit becomes a deliberate, priced decision rather than an accident of averages.
CAC (customer acquisition cost) is what it costs to win one customer. LTV (lifetime value) is the contribution that customer generates over the whole relationship. Payback is how long the customer takes to earn their acquisition cost back. Together they tell you whether growth spend is an investment or a leak.
Revenue and transaction data, cost and labour information, and retention and acquisition data, in whatever state it's honestly in. Part of the work is mapping what the data can support and marking what it can't. Perfect data isn't a prerequisite; stated assumptions are.
No. The consultation asks your unit type and data availability, nothing more. Data exchange is scoped inside the engagement, on agreed terms.
No. The Unit Economics and Profitability Calculator runs immediately and anonymously, with every assumption visible. An optional free account lets you save scenarios and compare units side by side.
It depends what the model finds: pricing problems route to Pricing & Monetisation, volume-dependent costs to Scale, Capacity & MES, planning questions to Demand Forecasting, structural questions to Business Model Economics, and data plumbing to Data Engineering.