ROI of a Digital Product: What It Is, the Formula and How to Calculate App Payback

ROI (Return on Investment) is a metric that answers the question “how much did I earn on every dollar I put in”. The formula is: ROI = (gain from the investment − cost) / cost × 100%. For an app, website or internal system, ROI shows whether development will pay off and when: for example, an ROI of 50% over a year means the product returned the whole investment plus half of it on top.

ROI in simple terms

Imagine you bought a coffee machine for the office for $1,000. The company used to spend $120 a month on takeaway coffee; now it spends $30 on beans and milk. That’s $90 saved a month, or $1,080 a year. ROI for the first year: (1,080 − 1,000) / 1,000 × 100% = 8%. The machine paid for itself in about 11 months and generates pure benefit after that.

A digital product works the same way, except the “coffee machine” is development, and the “savings” are new sales, staff hours saved, fewer errors and fewer lost leads.

The ROI formula and how to read it

ROI = (Gain − Cost) / Cost × 100%

• ROI above 0 — the product returned the investment and earned on top.

• ROI equal to 0 — break-even.

• ROI below 0 — still in the red. For a new product this is normal in the first months; what matters is that the figure grows.

ROI is always calculated for a specific period: a month, a year, three years. “ROI of 200%” without a period means nothing. For digital products a sensible horizon is 2–3 years: development is a one-off large expense, while the benefit accumulates month after month.

Related metrics: payback period, ROMI, LTV/CAC

• Payback period — how many months it takes for accumulated benefit to equal the investment. Owners often find this clearer than a percentage: “the app will pay for itself in 8 months”.

• ROMI — return on marketing investment: what advertising spend brought in. It is calculated separately so the effect of the product and the effect of promotion don’t get mixed up.

• LTV / CAC — for products that sell subscriptions or services: how much a customer brings in over their lifetime versus how much it costs to acquire them.

What to include in costs

The most common mistake is to put only the development cost into the formula. An honest picture includes everything you will pay over the chosen period:

• Development: analysis and specification, design, programming, testing, launch.

• Support and development after launch: fixes, updates, new features. We covered this in detail in how to calculate the cost of supporting a product after launch.

• Infrastructure: servers, storage, domains, paid services and APIs, SMS, payment fees.

• Rollout: staff training, data migration, the time it takes the team to get used to a new process.

• Marketing — if the product is sold to external customers.

What to include in gains

Gains come in two kinds, and it is worth converting them into money even if that takes some assumptions.

Direct gain — new money:

• additional sales through the app or customer account;

• a higher average order value (recommendations, upsells);

• repeat purchases and customer retention;

• subscription revenue if the product is sold as a service.

Indirect gain — money saved:

• staff hours no longer spent on manual work (multiply hours by the hourly cost);

• fewer errors, returns, penalties and lost leads;

• dropping paid third-party services and licences;

• faster order processing — serving more customers with the same staff.

If a gain is hard to estimate, estimate it conservatively and write down the assumption. A calculation with clear assumptions is more useful than no calculation at all.

Example: calculating the ROI of a booking app

Let’s take a hypothetical example: a chain of five beauty salons orders a web app for online booking with a customer account and an admin panel. The numbers are illustrative, to show the method.

Costs:

• development — $12,000 (one-off);

• support, hosting and services — $600 a month.

Gain per month:

• 24/7 online booking and reminders reduce no-shows and add bookings — +$1,500 in margin a month;

• administrators spend less time on calls — around $700 saved a month.

Total gain — $2,200 a month.

ROI for the first year:

• costs: $12,000 + $600 × 12 = $19,200;

• gain: $2,200 × 12 = $26,400;

• ROI = (26,400 − 19,200) / 19,200 × 100% ≈ 37.5%.

ROI over two years:

• costs: $12,000 + $600 × 24 = $26,400;

• gain: $2,200 × 24 = $52,800;

• ROI = (52,800 − 26,400) / 26,400 × 100% = 100%.

Payback period: net gain per month is $2,200 − $600 = $1,600. The $12,000 development cost pays back in $12,000 / $1,600 ≈ 7.5 months.

Note that over one year the ROI looks modest, while over two years the product has already doubled the investment. That’s why judging a digital product by its first three months is a mistake.

How to increase ROI before development even starts

1. Start with an MVP. A first version with the key scenario costs a fraction of the full product and starts paying back sooner. If the hypothesis doesn’t hold, you lose little. Read more in What Is an MVP.

2. Automate the most expensive things first. Work out where the business loses the most money and hours, and address exactly those.

3. Don’t build extras. Every “just in case” feature increases both development and support, but not the gain.

4. Plan a maintainable architecture. A cheap but poorly built product eats ROI through costly rework and downtime.

5. Set up analytics from day one. Without data you won’t know the real gain and will argue on gut feeling.

6. Choose the right payment model. For a product that will keep evolving, Time & Material works well: you pay for work actually done and can change priorities based on data.

Common mistakes when calculating ROI

• Counting only development and forgetting support, infrastructure and rollout.

• Too short a horizon. A product that pays back in 8 months looks “unprofitable” in a quarterly report.

• Optimistic gains. “Sales will double” is a hope, not an assumption. Use conservative figures and scenarios: bad, base and good.

• Ignoring the alternative. Compare not with zero but with what happens without the product: the same manual processes, rising staff costs, customers leaving for competitors.

• Not recalculating after launch. ROI before launch is a forecast. After 3–6 months, plug in real data and adjust the development plan.

FAQ

What is a good ROI

There is no universal benchmark: it depends on risks and alternatives. As a rule of thumb, ROI should exceed the return on risk-free investments (such as a bank deposit) over the same period, with a margin for risk. For internal automation, payback within 1–2 years is usually considered a good result.

How do you calculate ROI before the product launches

With a forecast: estimate costs from the quote, and gains through assumptions (how many hours will be saved, how many extra orders will come in). Calculate three scenarios: pessimistic, base and optimistic. If the product pays back even in the pessimistic scenario, the decision is solid.

What is the difference between ROI and ROMI

ROI evaluates any investment as a whole; ROMI covers only marketing investment. For an app you can calculate both: the ROI of the whole project and the ROMI of the ad campaigns that bring users to it.

Should taxes and depreciation be included

For a “build or not” decision, a simplified calculation is usually enough. For financial reporting and investors, ROI is calculated more precisely, with taxes, depreciation and discounting (NPV and IRR). It’s best to involve a finance specialist here.

How long does it take for an app to pay off

It depends on the task. Internal systems that save staff time often pay off in 6–18 months. Products sold to customers pay off once they gain enough paying users, which is why they are launched as an MVP to test demand before large investments.

Want to know whether your product will pay off? Take a look at our case studies and request a proposal — we’ll estimate the development cost, help you calculate the gain and suggest which version to start with to reach profit sooner.