Measuring return on investment
Return on investment should compare the incremental value created with the full cost and risk of the decision. Gross sales, usage and supplier-reported savings are supporting metrics, not ROI.
Return on investment should compare the incremental value created with the full cost and risk of the decision. Gross sales, usage and supplier-reported savings are supporting metrics, not ROI.
Define the counterfactual
State what would happen without the investment. A new website should be compared with the current channel mix; a KDS with the existing printer workflow; an app with a strong mobile website. Without a credible alternative, ordinary sales may be incorrectly credited to the new tool.
Use a complete value model
| Value | Examples |
|---|---|
| Incremental contribution | New profitable orders that would not otherwise occur |
| Channel savings | Verified reduction in commission or manual labour |
| Risk reduction | Fewer duplicate orders, outages or compliance failures |
| Capacity benefit | More orders fulfilled without damaging quality |
| Avoided replacement | Extended useful life of existing systems |
Count full cost
Include setup, licences, hardware, integration, support, internal time, training, adoption, incident recovery, financing and exit. Use actual invoices and payroll evidence where possible. Separate sunk cost from future cost when deciding whether to continue.
Calculate several measures
- ROI: net benefit divided by investment cost.
- Payback period: time until cumulative net cash benefit covers cost.
- Contribution uplift: incremental contribution after channel-specific cost.
- Risk-adjusted value: expected result under conservative probabilities.
- Operational guardrails: refunds, late orders, support and staff workload.
Use ranges rather than false precision
Model conservative, central and upside scenarios. Vary adoption, incremental share, contribution, support cost and failure rate. Show which assumption changes the conclusion. A result that depends on one optimistic input is not robust.
Review after implementation
Compare the approved business case with actual cost and outcome at fixed intervals. Record supplier changes, scope additions and operational side effects. If the investment does not meet the gate, decide whether to repair, reduce scope, replace or stop.
Practical next step
Take one recent digital investment and rebuild its business case using actual cost, a clear counterfactual and three scenarios. Exclude any sales that cannot reasonably be attributed to the change.
Separate cash, accounting and strategic returns
A project can improve cash flow without creating accounting profit, or reduce risk without an immediate sales increase. Report cash payback, contribution, fully loaded profit and risk reduction separately. Do not combine them into one unexplained percentage.
Control attribution
Use pilots, phased rollouts, comparison periods and holdout groups where practical. Adjust for seasonality, menu changes, opening hours and external events. Supplier dashboards may use their own attribution window; preserve raw business data and label modelled benefits as estimates.
Record negative outcomes
Include training disruption, duplicate subscriptions, customer confusion, staff turnover, increased complaints and technical debt. A review that reports only intended benefits cannot support the next investment decision.
Require an evidence pack
Keep the approved scope, baseline extract, invoices, supplier reports, operational metrics and calculation workbook together. Record any scope change after approval. This allows the business to distinguish a genuinely weak investment from one whose target moved during delivery.
Related guides
- Business Planning and Finance — the main guide for the wider topic.
- Budget Planning for Digital Investment — the broader guide that frames this implementation.
- Prioritising investments by impact — a closely related operational control to review alongside this page.
- Phased rollout strategies — a closely related operational control to review alongside this page.
Sources and date checked
Guidance checked: 24 July 2026. Recheck official guidance, local requirements and supplier documentation before changing a live operation.
Operational, legal and platform requirements can change. Recheck official guidance and supplier documentation before altering a live service.
Related practical guides
Business Planning and FinanceBreak-Even Analysis for a Takeaway AppAn app breaks even only when the additional contribution it creates or protects exceeds the full cost of building, launching and operating it. Do…Read guide →
Business Planning and FinanceData Protection for Restaurant Customer DataA takeaway needs customer information to accept, prepare, deliver and support orders. Data protection is not a reason to avoid useful systems, bu…Read guide →
Delivery ManagementComplaint Handling for Delivery IssuesA useful complaint process resolves the customer’s immediate problem, protects staff from improvised promises and produces evidence that can impr…Read guide →
POS and Kitchen SystemsHow to Choose a Receipt PrinterChoose a printer by the job, environment and supported connection—not by speed claims alone. A customer receipt, kitchen ticket, packing slip and…Read guide →
Restaurant AppsApp Administration FeaturesThe administration system is where the business keeps the customer promise truthful. It deserves the same scrutiny as the public app.Read guide →Online OrderingDietary Requirements on Digital MenusVegan, vegetarian, halal, gluten-free and other dietary descriptions can help customers choose, but they are claims that need defined standards a…Read guide →Connect customer ordering with operations and profit
Use the wider guide library to check the menu, kitchen, fulfilment, payment and financial implications of each decision.
Browse all practical guides