Break-Even Analysis for a Takeaway App
An app breaks even only when the additional contribution it creates or protects exceeds the full cost of building, launching and operating it. Downloads, registered users and gross app sales are not enough.
An app breaks even only when the additional contribution it creates or protects exceeds the full cost of building, launching and operating it. Downloads, registered users and gross app sales are not enough.
Define the decision
Decide whether the analysis is for a new app, replacement of an existing app, or continued annual investment. Compare the app with the best realistic alternative, which may be a strong mobile website rather than doing nothing.
Build the full cost base
| Cost category | Include |
|---|---|
| Initial | Setup, design, data migration, integrations, testing, store accounts and launch support |
| Recurring | Licence, hosting, support, updates, analytics, notification and payment services |
| Internal | Menu administration, campaign work, support, finance reconciliation and supplier management |
| Adoption | Landing pages, packaging, incentives, staff communication and paid media |
| Exit | Data export, loyalty migration, store transfer, replacement and overlap period |
Calculate incremental contribution
For each genuinely incremental order, start with net sales and subtract food, packaging, payment, delivery, incremental labour, promotion and support costs. Do not count an order as incremental if the same customer would probably have ordered through the website or another owned channel. Marketplace displacement can create savings, but only where the customer actually changes channel and the app does not add a new cost or discount.
Use a transparent formula
Break-even incremental orders = total app cost ÷ contribution per incremental app order.
If total year-one cost is £18,000 and contribution per genuinely incremental order is £6, the app needs 3,000 such orders. This is an illustrative calculation, not a benchmark. If only half of measured app orders are incremental, the business needs 6,000 observed app orders at the same contribution.
Model scenarios
- Conservative: low adoption, high support, little marketplace displacement.
- Central: evidence-based adoption and normal operating cost.
- Upside: stronger repeat use, but without assuming unrealistic perfect migration.
- Stress: store delay, integration issue, extra discount or supplier price increase.
Set a time boundary and stop rule
Calculate monthly cash movement and cumulative break-even, not only an annual total. Define the point at which the business will repair, reduce scope, replatform or retire the app. Sunk cost is not a reason to keep funding a weak product.
Use operational guardrails
An app that increases orders while raising refunds, late deliveries or kitchen overload may destroy value. Track contribution, repeat-order cohorts, support contacts, opt-outs, failed payments, marketplace mix and service quality together.
Practical next step
Build a one-page model with total cost, contribution per order, percentage of orders judged incremental, expected monthly orders and a conservative break-even month. Record every assumption and who owns the evidence.
Validate the model with operational evidence
Before approval, trace every assumption to a current source: signed supplier quotation, app-store account cost, payment statement, promotion budget, staff estimate and observed channel contribution. Separate committed cost from optional roadmap work. If the supplier bundles several products, allocate only the costs that would disappear if the app were not pursued.
Run the model by cohort and location. An app may be viable in a branch with strong repeat demand but weak elsewhere. Include users who install but never order, customers who switch from the website, account-support contacts and loyalty balances. Review break-even after the first stable quarter, not during the launch incentive period.
Use a decision record
- Approved cost ceiling and contingency
- Expected incremental share and evidence
- Contribution range and key sensitivities
- Monthly adoption and service guardrails
- Owner of store, data and supplier accounts
- Repair, replace and retirement triggers
Related guides
- Business Planning and Finance — the main guide for the wider topic.
- Cost Analysis for Digital Operations — the broader guide that frames this implementation.
- Total Cost of Running Online Ordering — 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 FinanceEmployment Law for Delivery DriversA contract that calls a driver “self-employed” does not settle their legal status. A takeaway should assess the real working arrangement, separat…Read guide →
Business Planning and FinanceDynamic pricing for peak periodsPeak pricing can protect capacity and contribution, but it should not be used to disguise operational failure or surprise customers. Start with n…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 →Business Planning and FinanceMeasuring return on investmentReturn on investment should compare the incremental value created with the full cost and risk of the decision. Gross sales, usage and supplier-re…Read guide →
Restaurant AppsCustom-Built Restaurant AppsA custom app is justified when the business has a valuable requirement that available platforms cannot meet and can fund the product throughout i…Read guide →
Online OrderingHow to Handle Busy PeriodsA busy period becomes damaging when orders enter faster than the kitchen, packing area or delivery operation can complete them. The solution is n…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