This is the most common conversation we have on a first call with a Charlotte business owner. Someone's competitor launched an app, or a customer asked whether there's an app, and now it feels like a gap. Sometimes it is. Often the honest answer is that an app would cost twenty times more than the thing that would actually move revenue.
We build apps for a living and we still talk people out of them regularly. So here's the framework we use, plus the numbers behind it.
The one distinction that settles most of it
A website's job is to get you found and get you contacted. An app's job is to get you used again.
Those are different jobs, and the data splits cleanly along that line. Roughly 97% of consumers check a business's online presence before visiting or buying, and about 46% of Google searches have local intent. That's discovery, and it happens on the open web. Nobody finds your HVAC company by browsing the App Store.
But once people are your customers, attention lives inside apps. Users spend the large majority of smartphone time in apps rather than mobile browsers, and app sessions convert meaningfully better than mobile web sessions in retail. That's retention, not discovery.
The rule: if you're trying to be discovered by new customers, build the website. If you already have customers who would use something weekly, an app starts to make sense. If you have neither, an app won't create demand that isn't there.
Four questions that decide it
Answer these honestly. If you can't say yes to at least two, we'd tell you to fix your web presence first.
- Do the same people come back at least weekly? Gyms, salons with standing appointments, restaurants with regulars, field crews, membership programs: yes. Roofers, wedding photographers, estate attorneys: almost never. A once-a-year purchase does not survive on a home screen.
- Does it need something only a phone can do? Camera and computer vision, offline use in a basement or a job site, background location, biometrics, Bluetooth hardware, real push notifications, Apple Wallet passes. If your idea is really "our website but in an icon," that's not an app requirement.
- Are you trying to get found, or trying to get used? Apps are terrible discovery channels for local businesses. You pay to acquire every single install.
- Does it save you money or labor internally? This is the most underrated yes. A dispatch and proof-of-delivery app used by twelve technicians can pay for itself in a quarter even if no customer ever sees it.
The retention number you should see before you commit
Median mobile apps retain roughly 4% of installs at day 30. Strong performers in most categories land around 5–8%. That number isn't a reason to avoid apps, but it is a reason to be specific about who yours is for.
Apps that beat those benchmarks have a reason to be opened that the browser can't replicate: a scheduled workout, a loyalty balance, a shift assignment, a saved order. We watch this closely in our own products. ChinCheck and Mara both live or die on whether someone opens them again in week two, and that discipline is what we bring to client scoping.
What each option actually costs in 2026
| Option | Typical market cost | Timeline | Best when |
|---|---|---|---|
| Marketing website | $3k – $10k | 2–4 weeks | You need to be found, trusted, and contacted. Local SEO, service pages, reviews, a booking or quote form. |
| Website + installable web app (PWA) | $8k – $20k | 4–7 weeks | Repeat customers and light functionality (accounts, ordering, loyalty) without store submissions. |
| Native app, both stores | $10k – $50k+ | 6–14 weeks | Phone hardware, offline, reliable notifications, or an app your operations depend on. See our full cost breakdown. |
Add to the app column: $99/year for the Apple Developer Program, $25 once for Google Play, hosting, and roughly 15–20% of build cost per year in maintenance. Websites have real upkeep too, but it's a different order of magnitude.
The middle option nobody explains properly: PWAs
A progressive web app is a website that can be installed to a home screen, run full-screen without browser chrome, cache content for offline use, and send push notifications. It skips app store review entirely, which is a genuine advantage if you ship weekly. On Android, PWAs are excellent and the install prompt is nearly frictionless.
On iOS, be clear-eyed about the limits as of 2026:
- Push requires installation. Web push works on iOS 16.4 and later, but only after the user adds the site to their Home Screen. A Safari tab gets nothing. That funnel step alone costs you most of your audience.
- No real background work. iOS doesn't support Background Sync, Periodic Background Sync, or Background Fetch for web apps, and there's no announced timeline. Anything that needs to update while closed is off the table.
- No premium notification surfaces. Time Sensitive alerts that break through Focus, Live Activities on the Lock Screen, and provisional (quiet) notifications are native-only.
- You're not in the App Store. No store listing, no ratings, no "search our name and find the app."
One clarification, since bad information persists here: Apple briefly disabled Home Screen web apps for EU users in a beta of iOS 17.4 and reversed that decision in March 2024. Home Screen web apps still work in the EU. That's not a reason to avoid PWAs.
A PWA is a strong first step when your feature list is mostly screens, accounts, and payments. It's the wrong tool when your product depends on the camera, on offline reliability, or on notifications that have to arrive.
"Can I just wrap my website in an app?"
Technically yes. Practically, Apple rejects apps that are little more than a repackaged website under its minimum-functionality rules, and even when a wrapper passes review, users can tell. It feels like a browser wearing a costume, and it earns the deletion it usually gets. If you want the app to survive, at least one thing in it has to be better than the website: saved payment, offline access, a scanner, a real notification, one-tap rebooking.
How we'd call it for common Charlotte businesses
- HVAC and plumbing. Website for customers, internal app for the crew. Dispatch, photos, signatures, and offline job notes. The internal side is where the money is.
- Restaurants. Website plus online ordering first. An app is worth it once you have enough repeat volume to justify owning the channel, which we work through in detail in our restaurant ordering app cost guide.
- Salons, barbers, med spas. Usually a booking platform plus a great website. Consider an app once memberships and rebooking rates justify it.
- Gyms and studios. Genuine app territory. Class booking, check-in, streaks, and progress are habit features, and habit is what apps are for.
- Professional services. Website, almost always. Spend the app budget on local SEO and a faster intake process instead.
Do you need both eventually?
Most businesses that end up with an app keep the website doing the heavy lifting on acquisition. The site earns the search traffic and the trust; the app carries the relationship afterward. Sequencing matters more than choosing: web first, app when repeat usage is proven. Building both at once is how small budgets get spent producing two mediocre things.
Get a straight answer for your situation
Tell us what you're trying to do and we'll tell you which of the three options fits, with a fixed quote and timeline if it's an app. If it's a website or an off-the-shelf tool, we'll say that on the first call and point you somewhere useful. We're a Charlotte app development studio that would rather be right than booked.