7 signs your business is ready for an app (and 3 signs it isn't)

A business owner messaged me last month with one line: "Everyone in my field has an app now — I think I need one." No mention of what the app would do. No mention of whether her customers had asked for it. Just the feeling of falling behind.

I get some version of that message every week. And my honest answer is almost never a straight yes or no. Because "should I build an app?" is the wrong first question. An app isn't a trophy you win for being a serious business. It's a tool with a running cost, a maintenance burden, and a brutal retention problem — and it only pays off for a specific kind of business at a specific moment.

So this post is the checklist I wish more owners had before they spent the money. Seven honest signs that you're genuinely ready for an app, and three signs you should wait and do something cheaper first. I've spent 15 years building apps, SaaS products and websites, and I've watched owners on both sides of this line — the ones for whom an app quietly became the backbone of their business, and the ones who paid for a beautiful app that sat on a shelf. The difference was almost never budget. It was readiness. Let's find out where you stand.

First, the hard truth about apps

Before the signs, you need to feel the stakes. Because the app industry's marketing hides them.

Here's the number that should shape your whole decision: close to half of the apps people install are uninstalled within the first 30 days. AppsFlyer's uninstall research and the retention data compiled by Business of Apps both land in the same uncomfortable place — roughly 46–48% of installs are gone within a month, and average day-30 retention sits in the single digits. In plain English: for a typical app, out of 100 people who download it, only a handful are still using it a month later.

That's not a reason to never build an app. It's a reason to build one only when you have something that beats the average — a real reason for people to keep it. An app doesn't create loyalty. It amplifies loyalty that already exists. If the loyalty isn't there yet, the app just gives people one more icon to delete.

There's a second hidden cost: getting the thing published is more work than owners expect. A Google Play developer account is a one-time fee of about $25, and an Apple Developer account is about $99 every year — you can confirm both on Google's Play Console signup and Apple's Developer Program pages. And since late 2023, if you register a new personal Google Play account, you must run a closed test with at least 12 real testers who stay opted in for 14 continuous days before the app can go public. Google documents this on its own help pages; it was 20 testers until they lowered it to 12 in December 2024. None of this is hard, but it's real time and real money that "just get an app made" never mentions.

Keep both of these in mind — the retention cliff and the publishing hoops — as you read the signs. They're why readiness matters more than ambition.

The 7 signs your business is ready for an app

You don't need all seven. But the more of these that are clearly true, the safer your money is. Read each one honestly — the trap is talking yourself into a "yes" you don't have yet.

Sign 1: You already have repeat customers who come back on their own

This is the most important sign, so it's first. Do people already return to you without being chased? The same customers reordering, rebooking, coming back next month?

If yes, an app has something to amplify. It can make that repeat visit faster and stickier, and give your best customers a home for the relationship. If no — if almost every customer is a one-time visitor — then an app has nothing to hold on to, and it'll hit that day-30 cliff like everyone else.

The honest test: look at your last three months. What share of your revenue came from repeat customers versus brand-new ones? If a meaningful chunk is repeat, that's a green light. If it's nearly all first-timers, fix retention with simpler tools before you spend on an app.

Sign 2: Your customers already deal with you on their phones

An app lives on a phone. So the question is: are your customers already doing business with you on their phones — and is that starting to strain?

For most Indian small businesses, the honest answer is "we live on WhatsApp." India is WhatsApp's single largest market — DataReportal's Digital 2025 India report puts Indian WhatsApp users in the hundreds of millions — and for a huge number of shops, clinics, coaches and D2C brands, WhatsApp is the storefront, the order book and the support desk all at once.

That's a green sign, with a catch. If you're already drowning — chats you can't keep up with, orders lost in a scroll of messages, the same catalogue pasted twenty times a day — an app can organise the chaos. But if WhatsApp is handling everything comfortably, you may not need an app yet; you might just need a proper WhatsApp Business catalogue. Readiness here isn't "customers use phones." It's "the phone channel I already have is overflowing."

Sign 3: There's a specific, repeating task the app would remove friction from

Vague apps fail. The apps that stick do one repeated job noticeably better than the current method. So name the job.

Is it ordering (a tiffin service, a bakery, a store)? Booking (a salon, a clinic, a coaching class)? Reordering the same thing (a pharmacy, a supplies business)? Tracking (deliveries, service status)? Learning (a course, a coaching batch)? If you can finish this sentence cleanly — "customers will open my app to ______, again and again" — you have a real reason to build. If the best you can do is "to see our stuff" or "to stay updated," that's a website's job, not an app's.

The honest test: would a customer do this task at least a few times a month? Daily and weekly tasks belong in an app. Once-a-year tasks belong on a website.

Sign 4: Your current workaround is costing you real, countable money or time

An app should replace something that's actively costing you — not just add polish. So add up the cost of how you do it today.

Missed bookings because your calendar lives in three places. Hours every week manually confirming orders on WhatsApp. Staff time spent answering the same "where's my order?" question. Customers who drifted away because reordering was annoying. Each of these has a rupee value if you sit down and estimate it. When the annual cost of the workaround starts to look like the cost of building and running an app, the app stops being a luxury and becomes an obvious investment.

If you genuinely can't point to a countable cost — if the current way works fine and nothing's leaking — then the app is a "nice to have," and nice-to-haves are exactly the apps that end up unused. (If you want to size the build against that cost, I've written a full breakdown of what an app really costs to build in India in 2026.)

Sign 5: You can give people a genuine reason to keep it on the home screen

This is the sign owners skip, and it's the one the retention data punishes hardest. An app takes up space, memory and a slot on someone's phone. What's the ongoing reason not to delete it after the first use?

Good reasons: they order from you often, they track something live, they earn or track loyalty points, they get their bookings and history in one place, they get useful reminders they actually want. Weak reasons: "it looks nice," "it has our brochure," "they can contact us." If your app is essentially a website in an icon, people will treat it like a website and delete the icon.

One honest note on the "reminders" reason: an app can reach people directly through push notifications, which is a real advantage over channels you pay for per message. But only people who opt in get them, and opt-in rates have been falling — in 2025 they averaged roughly 67% on Android and 56% on iOS across apps (Batch's benchmark). So push is powerful, but it reaches maybe half to two-thirds of your users, and only if you don't annoy them. Plan for that, don't assume it.

Sign 6: You have the operational capacity to keep the promise an app makes

An app makes an implicit promise: this business is organised, responsive, and here to stay. If you can't keep that promise, the app hurts you more than no app at all.

Can someone answer questions that come through it, reasonably fast? Can you fulfil orders it takes, reliably? Will someone keep the content — prices, menu, availability, batch dates — up to date? An app with stale information and slow replies broadcasts "this business is asleep" to every customer who opens it. I've seen a beautiful app do genuine damage because nobody was minding it. Readiness isn't just about the customer wanting the app. It's about you being able to run it after the excitement of launch fades.

Sign 7: You have a small budget for after launch, not just to build

Most owners budget for the build and stop there. The ones who succeed budget for the life of the app.

After launch you'll have store fees (that one-time ~$25 Google, ~$99/year Apple), usually a small care or hosting plan (commonly ₹500–₹2,000 a month), and occasional updates — because phones, Android and iOS all change every year, and an app that isn't touched for a long time eventually breaks or gets pulled. This doesn't have to be expensive, but it has to be planned. If your entire budget goes into building and there's nothing left to keep it alive, you're funding a firework, not a tool. (If you're weighing an owned build against a monthly no-code subscription, my no-code vs custom breakdown lays out the three-year maths honestly.)

The 3 signs you're NOT ready (yet)

"Yet" is the key word. None of these means "never." Each just means there's a cheaper, smarter step to take first — and taking it will make your eventual app far better.

Not-ready sign 1: You haven't proven anyone wants this

If you're still guessing whether people want what you're offering, an app is the most expensive possible way to find out. You'd be building a polished product for a demand you haven't confirmed.

Prove it cheaply first. Run the ordering or booking through a WhatsApp Business catalogue and a simple website. Watch what real people actually do for a few weeks. If the same customers keep coming back and start asking for something faster or more organised — that is the moment you're ready, and you'll build a sharper app because you'll know exactly which one job it must nail. Building before that proof is how owners end up with a gorgeous app and no users.

Not-ready sign 2: Your customers need you once, not again and again

Some businesses are genuinely one-and-done, or once-a-year. A wedding photographer. A house painter. A business someone hires, uses, and won't need again for a long time.

For these, an app fights its own nature. Nobody keeps an app for a service they'll use once. What these businesses actually need is to be found and trusted at the moment of need — which is a website's job, backed by good reviews and search visibility. Spending on an app here means paying to build something your customers have no reason to keep. Put that money into a strong website and getting found on Google instead. If a customer will only ever open the thing once, it shouldn't be an app.

Not-ready sign 3: You want the app mainly for prestige

This is the quiet one, because it hides behind good-sounding reasons. "It looks professional." "My competitor has one." "It'll make us seem bigger." These are feelings about status, not jobs for the app to do.

An app built for prestige has no repeating task at its heart, so it hits the retention cliff and sits unused — and an unused app you're paying to maintain is worse for your image than no app, because the few who download it see a ghost town. If you want to look more professional to customers, a clean, fast website does that better, cheaper, and for everyone who finds you — not just the tiny share who'd download an app. Build an app when a job demands it, not when your ego does. (I say this as the founder of an app studio: I'd rather talk you out of the wrong app than sell you one you'll regret.)

Score yourself: the honest tally

Here's the whole checklist on one screen. Be strict with yourself — the point is to protect your money, not to reach a "yes."

How to read your tally: if five or more rows land clearly in the green column — and especially if Sign 1 (repeat customers) and Sign 3 (a specific repeating task) are both green — you're genuinely ready, and building will likely pay off. If you're mostly in the right-hand column, you're not ready yet, and the smartest spend is proving demand and strengthening your website and WhatsApp first. If you're split down the middle, fix the red rows before you build; every red row you fix now is a problem you won't be paying to discover after launch.

A worked example: Anjali's tiffin service

Let me make this real, because a checklist only clicks when you watch it run. This is a composite of businesses I've seen, with the reasoning laid out honestly.

Anjali runs a home tiffin service in Pune. She has about 60 regular subscribers, takes orders and payments on WhatsApp, and sends the week's menu as a broadcast every Sunday. She's tired of it: the Sunday menu triggers 40 back-and-forth chats, people forget to pause when they travel, and she loses an hour a day just confirming and reconciling. She's wondering if an app is the answer. Let's run her through the checklist.

• Repeat customers? Green. Her whole business is repeat — subscribers who reorder weekly. This is the strongest possible version of Sign 1.
• Already on phones with you? Green, and overflowing. WhatsApp is straining under the volume. Classic Sign 2.
• A specific repeating task? Green. "Customers will open the app to see this week's menu, pause or edit their plan, and pay." That's a clean, repeated job — done multiple times a week.
• A countable cost today? Green. An hour a day of her time, plus the subscribers who quietly drop off because pausing is a hassle. That's real money and real churn.
• A reason to keep it installed? Green. They order and manage a live subscription in it — exactly the home-screen reason that beats the retention cliff.
• Capacity to run it? Amber. It's just her. The app must reduce her work, not add a channel she has to monitor on top of WhatsApp. So the design has to replace the chaos, not sit beside it.
• Budget for after launch? Amber. She has some money to build but hadn't thought about ongoing costs. Once she sees the small monthly care figure and the store fees, it's easily affordable — but she needed to plan it.

Anjali scores five clear greens and two ambers she can fix by design and planning. She's ready — and crucially, she now knows what to build: not a generic "tiffin app," but specifically a menu-and-subscription manager that kills her Sunday chat storm and lets people pause themselves. That focus is worth more than any feature list. She should build the one job brilliantly, keep it native so it's a real Play Store app her subscribers trust, and plan the small monthly upkeep from day one.

Now flip one detail. Imagine Anjali had only 8 customers and wasn't sure the tiffin idea would even grow. Same passion, same skills — but no proven repeat base. Then the honest answer flips: not ready yet. She'd spend her limited money proving demand on WhatsApp and a simple site first, and build the app once the subscriber base and the friction were both real. Same business, different stage, opposite answer. That's the entire point of readiness.

"So should I just build a website instead?" — often, yes

For a lot of owners reading this and landing in the "not ready" column, the disappointment is real. So let me be direct about the alternative, because it's usually a better first move, not a consolation prize.

A website does the jobs an app can't and most owners actually need first: it gets you found on Google, answers "who are you and can I trust you," shows your work and reviews, and takes enquiries or bookings — from everyone, with no download required. A WhatsApp Business catalogue handles a surprising amount of ordering and support with zero friction. Between a decent website and a well-run WhatsApp, many small businesses have everything they need for a year or more — and every month you run them, you're gathering the exact evidence that tells you whether, and what kind of, app to build later.

An app is the deepening of a relationship you already have, not the start of one. Website and WhatsApp start the relationship; the app deepens it once there's something worth deepening. Get the order right and you never waste money. Get it backwards — app first, before the relationship exists — and you pay to learn a lesson the checklist could have given you for free.

Once you're ready: the boring prep that decides success

Say you've scored your greens and you're genuinely ready. Before you commission anything, do this unglamorous groundwork — it's what separates the apps that thrive from the ones that limp.

1. Write the one job in a single sentence. "Customers open this app to ______." If you can't, you're not ready to brief anyone. This sentence is your whole spec's backbone.
2. List only the screens that serve that job. Resist the urge to add everything. The app that does one thing brilliantly beats the app that does eight things adequately — and it costs far less to build and maintain.
3. Decide the build route on purpose. No-code to test, a template/AI-assisted build for a real owned app at a small price, or full custom only if your logic is genuinely unusual. My no-code vs custom guide walks through which fits which business.
4. Set up your own store accounts in your name. The Google Play (~$25 once) and Apple (~$99/year) accounts should belong to you, not your developer. This is your business's identity on the stores — never rent it.
5. Plan the 12-testers step into your launch. If it's a new personal Play account, line up a dozen willing testers and block out two weeks before you promise anyone a launch date.
6. Budget for the life of the app, not the birth. Care plan, updates, and the human who keeps it fresh. An app is a plant, not a monument — it needs watering.

Do this prep and your build goes faster, costs less, and launches into a business that's ready to run it. Skip it, and you'll pay for the education later, in public.

The honest bottom line

An app is one of the most powerful tools a small business can own — when it's the right tool for a real, repeated job, in the hands of a business that has the loyalty and the capacity to keep it alive. In that case it deepens your best relationships, cuts your daily friction, and gives you a direct line to the people who already love what you do.

But it is not a rite of passage, and it is not a cure for a business that hasn't yet earned repeat customers. Against a 30-day cliff that swallows roughly half of all installs, the app that survives is the one built for proven repeat behaviour — not the one built to prove you're serious. Count your green signs honestly. Fix your red ones first. And if the answer today is "not yet," take that as good news: you just saved money and bought yourself a much better app later.

If you'd like a second opinion before you spend anything, you can describe your business in plain English and get an honest read on whether an app is the right move — plus a real blueprint and live mockups in minutes, free, with a fixed price from ₹9,999 and real, owned code if and when you decide you're ready. I'd genuinely rather tell you to wait than sell you an app you'll regret. You can start there whenever the signs line up.