Mobile App ROI for Small Business: How to Calculate If It Is Worth Building

Most small business owners ask "should I build an app?" and get one of two useless answers. The Toronto agency answer is "yes, absolutely, here is an $80,000 quote" - usually for a dual-native Swift + Kotlin build the project does not actually need. The skeptical friend answer is "no, you do not need an app, just improve your website." Both ignore the math.

The real question is not whether to build an app. It is whether a $20,000 to $40,000 React Native + Expo build covering both the App Store and Google Play pays back inside 18 months for your specific business. That is the calculation this post walks through.

The right answer is: it depends on the ROI math for your specific business, which you can calculate before you commit a dollar. This post walks through exactly how to do that.

The Four Revenue Levers an App Pulls

A mobile app drives ROI through one or more of these four levers. If none of them apply to your business, you do not need an app. If two or more apply, the math usually works.

1. Recovered Commission and Platform Fees

If you currently sell through DoorDash, Uber Eats, Skip, Airbnb, Etsy, Amazon, or any other platform that takes 15 to 30 percent commission, every order shifted to your own app is recovered margin.

Example: a restaurant doing 200 weekly orders at $35 average ticket on DoorDash with 27 percent commission. If 30 percent of those orders shift to your own app, that is 60 weekly orders at $35 with no commission. Recovered margin: $565/week, or $29,000/year. A $25,000 app pays back in 10 months.

2. Reduced Customer Acquisition Cost (CAC)

Every customer you re-engage through push notifications is a customer you do not have to re-acquire through Meta ads or Google ads. If your CAC is $40 and your app drives 30 repeat purchases per year per active user that would not have happened otherwise, the math is significant.

Example: a fitness studio with $80 CAC, 400 active members, and 14-month average tenure. If app push notifications extend tenure to 17 months, that is 3 extra months of $200/month per member - $600 in additional LTV per member. Across 400 members, $240,000 in retained revenue.

3. Improved Repeat Purchase Frequency

App users buy 30 to 50 percent more often than web-only customers in retail and consumer service categories. That is a real, measurable lift.

Example: a retailer with $200 average annual revenue per customer. If app users buy 40 percent more often (so $280/year per app user), and 30 percent of customers install the app, that is $24/year in additional revenue per total customer. Across 5,000 customers, $120,000 annually.

4. Reduced Operational Costs

For service businesses (contractors, real estate, professional services), an app can replace tools you are currently paying for: scheduling software, CRM, lead tracking, customer communication, dispatch.

Example: a contractor paying $300/month for scheduling software, $400/month for CRM, $200/month for lead tracking, $150/month for SMS communication. That is $1,050/month or $12,600/year in software costs that a custom app replaces. Plus the time savings on team coordination.

How to Calculate Your Specific ROI

A simple framework that works for any small business considering an app.

Step 1: Estimate Annual Revenue Lift

Add up the revenue impact from each of the four levers that applies to your business. Use conservative numbers - assume 20 percent adoption of the app among your existing customers in year one, growing to 50 percent by year three.

Step 2: Estimate Build and Operating Cost

Build cost: based on scope. See our mobile app cost guide for realistic 2026 numbers.

Operating cost: 10 to 20 percent of build cost annually for maintenance, plus $99/year App Store, $25 one-time Google Play, $20 to $200/month backend hosting, and possibly $50 to $500/month for SaaS dependencies (push notification service, analytics, error tracking).

Step 3: Calculate Payback Period

Build cost divided by annual net revenue lift = years to payback. Under 18 months: build the app. 18 to 36 months: borderline, depends on confidence in the assumptions. Over 36 months: do not build.

Step 4: Stress Test

Cut your revenue assumptions in half. Does the math still work? If yes, build. If no, you are betting on best-case scenarios that probably will not materialize.

Real ROI Examples by Industry

Realistic ranges from app projects we have shipped or analyzed.

Restaurants

Build cost: $20K to $40K for a single location
Annual revenue impact: $15K to $35K (recovered DoorDash commission)
Payback: 8 to 18 months
ROI verdict: Strong for restaurants doing $400K+ annual revenue with repeat customers

Contractors

Build cost: $20K to $50K
Annual revenue impact: $30K to $150K (improved lead conversion + reduced software costs)
Payback: 4 to 12 months
ROI verdict: Very strong for contractors doing $500K+ revenue

Fitness Studios

Build cost: $25K to $60K
Annual revenue impact: $20K to $80K (extended member tenure)
Payback: 9 to 24 months
ROI verdict: Strong for studios with 200+ members and decent pricing

Real Estate Agents (Individual)

Build cost: $15K to $30K
Annual revenue impact: Hard to quantify - depends on client retention and referral
Payback: Often 24+ months
ROI verdict: Weak unless you are a top producer with strong existing database

Real Estate Brokerages

Build cost: $50K to $120K
Annual revenue impact: $80K to $300K (lead routing, team efficiency, data ownership)
Payback: 6 to 18 months
ROI verdict: Strong at 20+ agents

Retail (Independent)

Build cost: $25K to $60K
Annual revenue impact: $30K to $150K (loyalty + push + repeat frequency)
Payback: 6 to 18 months
ROI verdict: Strong for retailers doing $500K+ with established customer database

Local Service Businesses (single-location, sub-$300K revenue)

Build cost: $15K to $30K
Annual revenue impact: $5K to $15K
Payback: 24 to 48 months
ROI verdict: Usually weak. Invest in a stronger website and SEO instead

The ROI Killers

Common mistakes that turn a positive-ROI app into a money pit:

Overscoping

The MVP that grows into a 12-month, $80,000 build by accident. Set scope at the start, defend it aggressively, ship a real product in 8 to 12 weeks.

No Marketing Plan

Building an app and then "hoping people download it" is the most common failure mode. Plan and budget for launch marketing - QR codes, email campaigns, in-store signage, opt-in incentives. Budget $3K to $15K for launch.

Picking the Wrong Agency

A $25K project becomes a $75K project when you go to a downtown agency that bills you for a dual-native Swift + Kotlin build, a five-person PM layer, and a downtown lease. Pick a small focused team that ships your app as one React Native + Expo codebase to both stores. This is exactly the gap WebLaunch exists to close.

Building for the Wrong Customer Segment

Apps work best for repeat customers. If most of your business is one-time transactions (tourist-driven restaurants, one-time service jobs, seasonal businesses), the app math rarely works.

Underestimating Maintenance

Apps require ongoing care. App Store policy changes break things. iOS updates break things. Plan for the 10-20 percent annual maintenance cost or your app gets quietly broken within 18 months.

When the ROI Math Does Not Work

Be honest with yourself if any of these are true:

You have under 200 repeat customers
Your average customer transaction is small and infrequent (you sell something people buy once)
Your customers are primarily tourists or one-time visitors
You operate in a category where the app provides no obvious value over a website
You do not have an existing customer database to launch to

For these situations, the answer is usually "invest in a better website and SEO instead." A high-converting website that ranks for the right local searches will outperform a mediocre app on ROI every time. If you're still deciding which shape your project should take, our web app vs SaaS vs mobile app comparison walks through the trade-offs.

How to Validate Before You Commit

Before signing a six-figure build contract, validate cheaply:

Survey your existing customers. Would they install an app? What would make them install it? What would make them open it weekly?
Check your competitors. Who has an app? What do their reviews say? Are people actually using it?
Track your existing mobile web usage. If 70 percent of your traffic is mobile and bounce rate is high, an app has a real shot. If 90 percent of your business is in-person walk-ins, less so.
Run a 4-week no-code pilot. Build a basic Glide or Bubble version of the core flow. Get 30 to 50 customers to use it. Measure what they actually do. Then decide.

For more on validation, see our app idea validation guide.

Why WebLaunch Can Tell You Honestly

We get paid to build apps. But we get repeat business and referrals from telling clients honestly when an app is the wrong call. We have told plenty of small business owners "do not build this, here is what to spend the money on instead" - usually a better website, better SEO, or a no-code internal tool.

When we do recommend building, we recommend the scope that pays for itself, not the scope that maximizes our contract.