Payback Period Explained: Is This Product Worth Building?

Before you fund a product, you want to know how long your money will be at risk. The payback period answers that question in one number: the months it takes for the cash a product brings in to repay the cash you put in. It's the easiest investment metric to explain to a spouse, a partner or a finance team. It is also easy to get wrong, because the inputs are guesses and the metric ignores everything after break-even. This guide walks through the payback period formula, a realistic worked example with uneven cash flows, the discounted version, customer-level payback, and the traps that make a product look better or worse than it is.

The payback period formula

The Corporate Finance Institute defines payback period as how long it takes a business to recoup an investment. For even cash flows, the formula is:

Payback period = Initial investment ÷ Cash flow per period

When cash flows are uneven, which is almost always the case for a new product, CFI's method is:

Payback period = Full periods before recovery + (Unrecovered cost at start of the next period ÷ Cash flow in that period)

In plain words: count the whole months until you're nearly even, then add the fraction of the next month it takes to finish the job.

What counts as the investment

Most payback errors start with an incomplete investment figure. Include:

• Design and development, including any additional platforms.
• Accounts and fees. For example, the Apple Developer Program costs $99 a year, and a Google Play developer account has a $25 one-time registration fee.
• Legal and admin: company setup, terms of service, privacy policy.
• Launch marketing and any paid pilots.
• Running costs you pay before revenue arrives, such as hosting, tools and support.
• Your own time, if you give up paid work to do this.

What counts as cash flow

Monthly net cash flow is revenue minus every recurring cost. Payment processing is one you can look up: Stripe charges 2.9% plus 30 cents per successful domestic card transaction in the US. Subtract that, plus hosting, tools, support, ongoing marketing and any revenue share. What's left is the number you divide by.

Worked example: a product with a ramp

Here's a realistic shape. A small business invests $30,000 all-in in a new customer-facing app. Month 1 loses money (launch costs exceed early sales), then revenue climbs.

Illustration, not a prediction: the cash flows below are invented to show the method. Your numbers depend on your market, pricing and execution.

The running total turns positive during month 9. Apply the formula:

1. Full months before recovery: 8.
2. Unrecovered cost at the start of month 9: $6,500.
3. Cash flow in month 9: $7,000.
4. Payback = 8 + (6,500 ÷ 7,000) = about 8.9 months.

Notice what happened. A product that eventually nets $8,000 a month would have a "simple" payback of under 4 months ($30,000 ÷ $8,000). The ramp more than doubles it. When someone quotes you a payback period, ask whether it includes the ramp.

Discounted payback: the more honest version

A dollar next year is worth less than a dollar today, because you could have used it elsewhere. CFI notes that the simple payback period doesn't discount future cash flows. The discounted payback period fixes that by shrinking each future month's cash flow before you add it up:

Discounted cash flow in month n = Cash flow ÷ (1 + monthly rate)^n

Pick a rate that reflects what your money could earn elsewhere, or what it costs you to borrow. Using 1% a month on the same example:

Illustration, not a prediction: same invented cash flows, discounted at 1% a month.

Discounted payback = 9 + (1,539 ÷ 6,790) = about 9.2 months, a few weeks longer than the simple version. For short paybacks the gap is small. For products that take two or three years to break even, it grows quickly, and it is the version to show a lender or investor.

Where payback period misleads

CFI lists the metric's main weaknesses: it ignores cash flows after the payback point, so it says nothing about total return, and the simple version ignores risk and the time value of money. Here is what that looks like in practice.

It can favor the smaller, weaker project

Illustration, not a prediction: two invented projects with flat cash flows over 24 months.

Project A pays back sooner. Project B is worth more by month 24. If cash is tight and risk is high, A might still be the right choice. If you can afford the wait, B wins. Payback alone can't tell you which. Pair it with total net over a sensible horizon, or with return on investment, which we cover in the business case for an internal app.

It assumes the product survives

A payback period of 18 months assumes you are still operating in month 18. Base rates say that's not a given. According to the US Bureau of Labor Statistics, of new establishments that opened in 2014, about 79.7% were still open after one year and about 69.3% after two. The longer your payback, the more survival risk you carry.

It hides churn

If customers cancel quickly, the monthly cash flows in your model won't hold. A product that adds customers but loses them just as fast shows up as a flat line that never pays back. Model churn explicitly, or you'll overstate every month after launch.

Customer payback: the second number to check

Product payback tells you when the whole investment comes back. Customer payback tells you whether each new customer is worth winning. It's often called CAC payback:

Customer payback (months) = Cost to acquire one customer ÷ (Monthly revenue per customer × Gross margin)

Illustration, not a prediction: if you spend $300 in ads and sales time to win a customer who pays $99 a month at an 80% gross margin, customer payback is 300 ÷ (99 × 0.8) = about 3.8 months.

If a typical customer stays longer than the customer payback, growth funds itself over time. If they leave sooner, each new customer loses you money, and faster growth makes it worse. That's why retention matters so much. ChartMogul's analysis of more than 2,100 SaaS businesses found that only 2.7% of companies with average revenue per account under $10 a month had net revenue retention over 100%, compared with 41.1% of those above $500 a month. Low-price products have to work much harder to keep customers long enough to repay them.

How to cut the payback period before you build

You can change the payback period before you write any code, because you control the biggest inputs:

• Shrink the investment. Launch one platform first, with the smallest feature set that can win a paying customer. See MVP scope and web, iOS or Android first.
• Shorten the wait. Line up pilot customers before launch, so month 1 isn't month zero. Our first 100 customers plan shows how.
• Raise the price. Fewer customers at a higher price reach break-even faster and usually churn less. See pricing your app.
• Fix the build price. An overrun adds straight to the investment line. A fixed fee removes that uncertainty. More in fixed-fee vs hourly development.
• Decide your stop rule. Write down the month and the cash number at which you will stop or change course.

A quick payback checklist

1. List every cost before launch, including your time.
2. Estimate monthly net cash flow for 24 months, with a ramp.
3. Include churn in the customer count behind each month.
4. Calculate simple payback and discounted payback.
5. Run a downside case at half your expected revenue.
6. Compare net at 24 months, not just payback, across options.
7. Set a stop date.

If the downside case never pays back and would hurt you to lose, don't build yet. Keep validating, or find a cheaper way to test. For the full scenario tables, see does an app pay for itself.

How Ottomind can help

A fixed build price makes the investment line of your payback model a known number. Ottomind Studio gives every project a fixed price after a scoping call, with UX/UI design included; focused MVPs start from $25,000. We target a focused v1 in production within about four weeks of scope sign-off, which shortens the wait before month 1. You own your GitHub, cloud, domain and app-store accounts from day one.

After launch, optional monthly plans are Care at $1,000 a month, Team at $4,500 and Dedicated at $12,000, with no minimum term. Put whichever plan you choose into your monthly costs, or take the product in-house at launch. The studio intake gives an AI-assisted stack recommendation and estimate in minutes, which gives you a real number for the top of your payback model.