For boards, funders and programme owners who need a credible case, not an advocacy document. We appraise projects and programmes against a genuine do-nothing baseline (lifecycle costs, financial and wider benefits, who is affected and when) with assumptions, uncertainty and the distribution of value made visible.
The common thread: significant resources, more than one possible course of action, and an audience (board, funder or public) entitled to a case that would survive scrutiny.
A facility, fleet, plant or major asset is proposed. The purchase price is known; the lifecycle cost, the realistic benefits and the do-nothing comparison usually are not.
A platform, system replacement or automation programme promises efficiency. The benefits are plausible but unstructured, and at risk of being counted twice under different names.
A government or community programme must demonstrate net public value, including honest treatment of what would have happened without it.
Funders increasingly ask the additionality question directly: what does this money make happen that would not have happened anyway? The case must answer it credibly.
Consolidating, expanding or redesigning a service shifts costs and outcomes across different groups: some gain, some lose, and the case should say so.
Long-lived assets with benefits spread over decades and stakeholders, where timing, uncertainty and who ultimately pays deserve explicit treatment.
A project already delivered, and an honest question: did the benefits claimed in the business case actually arrive? Ex-post simply means after the fact, and it is how the next case gets better.
An appraisal engineered to justify a preferred option is not analysis. Experienced funders and review panels can tell. The cases that succeed are the ones that make their baseline, assumptions and losers visible before anyone has to ask.
No project creates value in a vacuum. It creates value relative to what would have happened anyway. That 'what would have happened anyway' is the counterfactual, and it is where every credible appraisal starts: usually a do-nothing case (the realistic trajectory without intervention, which is rarely standing still) and often a do-minimum case (the cheapest defensible alternative). Every benefit is then measured against that baseline, not against zero. The same discipline applies to the money itself: spending it here means not spending it elsewhere (the opportunity cost), so the appraisal asks not just 'is this worthwhile?' but 'is this the best available use of these resources?' Get the counterfactual wrong and every number after it is wrong in the option's favour.
The appraisal exists to serve a decision-maker with options, including the option of doing nothing.
The core call: does this intervention create net value against the counterfactual, and enough to justify committing the resources now?
Comparing genuine alternatives (including do-minimum) on consistent lifecycle costs and benefits, rather than one worked-up option against a straw man.
For programmes already running: whether the evidence supports expansion, continuation as-is, redesign or wind-down.
A submission to a board, funder or central agency whose baseline, additionality and assumptions are visible before the reviewer asks.
Where impacts fall unevenly across groups, regions or generations, the distributional summary puts that trade-off on the table explicitly.
Ex-post: whether the benefits claimed at approval actually arrived, closing the loop so the next business case starts from evidence, not habit.
Perspective and options are fixed before any modelling starts: the two choices that most determine whether an appraisal informs or merely advocates.
We agree the decision the appraisal serves and its perspective, whose costs and benefits count: the organisation's, the funder's, or society's more broadly. The same project can appraise differently under each, so the choice is made openly at the start.
The realistic options are defined, always including do-nothing (the genuine trajectory without intervention) and usually do-minimum. The baseline is agreed before benefits are discussed, not fitted afterwards.
The groups affected (beneficiaries, cost-bearers, and those affected indirectly) are identified, so the distributional picture is designed in rather than bolted on.
Costs and benefits are evidenced against the source hierarchy: measured data where it exists, comparable evidence and benchmarks where it does not, and clearly labelled assumptions where neither is available.
The appraisal model is built across the whole lifecycle, comparing each option against the baseline, with every input sourced and every causal assumption traceable to the impact map.
Key assumptions are tested for how much the conclusion depends on them, and impacts are broken down by stakeholder group, so the recommendation carries its own uncertainty honestly.
Findings are reported with the method statement, so a sceptical reviewer can follow every step from raw assumption to headline measure, and challenge any of them.
How benefits will actually be measured after go-live: indicators, owners and review points, the benefits-realisation plan that makes a future ex-post review possible.
An appraisal draws on demand, technology and causal evidence from the streams beside it, and hands its benefits-realisation plan to the systems that will track it.
Owns: counterfactual and options · lifecycle costs and benefits · additionality · distributional analysis.
The option being appraised is a product or technology investment.
Build, buy and adopt economics for products and technology.
That stream shapes the investment options; the appraisal tests whether the chosen one creates net value.
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.”
Having a preference is normal; engineering the analysis to protect it is where cases fail. Our approach makes the baseline, assumptions and evidence sources visible, then lets the comparison land where it lands. If the preferred option genuinely stacks up, it emerges with a far stronger case than advocacy could have produced, and if it does not, you find out before the money is committed rather than after.
No. The discipline comes from public-sector appraisal practice (counterfactuals, additionality, distributional analysis) but it applies equally to boards weighing capital projects, technology transformations and funding decisions. Private-sector cases fail for the same reasons public ones do: no honest baseline, benefits counted twice, and losers left out of the picture.
After delivery, when there is a genuine appetite to learn, and ideally when the original case included a benefits-realisation plan to measure against. An ex-post review tests whether the claimed benefits arrived, why any didn't, and what that means for the next case. Organisations that never look back tend to approve the same optimism repeatedly.
What would have happened anyway, without the intervention. It is usually expressed as a do-nothing case (the realistic trajectory with no action, which is rarely 'everything stays the same') and often a do-minimum case, the cheapest defensible alternative. Every benefit in the appraisal is measured against that baseline, because a benefit that would have arrived regardless is not a benefit of the project.
The same benefit claimed twice under different names: for example, counting a productivity gain and also the wage uplift that flows from that same gain, as though they were separate. The cost and benefit register prevents it structurally: every effect gets exactly one entry, one source and one valuation, so overlaps have to be reconciled rather than quietly accumulated.
Net present value converts all future costs and benefits into today's dollars (reflecting that a dollar in ten years is worth less than one now) and reports the net result; positive means the benefits outweigh the costs on that perspective. The benefit-cost ratio expresses benefits per dollar of cost, which helps when comparing options of different sizes. Neither is automatic: measures are chosen for what the decision needs, and a ratio computed from weak evidence is precision theatre.
Then it is not forced into a number. Some effects (confidence, cohesion, amenity) can sometimes be valued with established non-market methods, and many cannot. Where the evidence will not support quantification, the appraisal says so and treats the effect qualitatively but visibly: described, attributed and weighed in the recommendation. An honest 'unquantified but material' is worth more to a reviewer than an invented dollar figure.
A description of the intervention, the decision and decision-maker (or funder) it serves, the options being considered, your current view of the baseline, the timeline, the main stakeholder groups, and what evidence already exists. That is enough to scope the work honestly, including telling you if a full appraisal is more than the decision needs.
Not in their specialist or statutory form. Where an appraisal touches environmental, health or legal impacts, those assessments belong with qualified experts in each field. We structure the economic appraisal around their findings and work alongside them, not in their place.
The benefits-realisation plan turns the case into something measurable: indicators, owners and review points for the benefits claimed. From there, benefits tracking can be built into a governed measurement layer, and, where attribution genuinely matters, a later econometric evaluation can test whether the intervention caused the outcomes the case predicted.