Does a Michigan Service Business Really Need a Mobile App?

Every few months a Michigan service business owner asks me the same question. A contractor in Grand Blanc, a shop owner in Fenton, a med spa owner in Detroit metro. The wording changes, the question does not: "Should I get an app for my business?"

Here is the honest answer I give most of them. No, you probably do not need an app. You need a website that works well on a phone, and for most service businesses that is the harder thing to get right and the more valuable one to fix.

But "most" is not "all," and the app question deserves a real answer instead of a shrug. So in this post I will walk through what an app actually does for a service business, when it pays for itself, what it costs to build and run, and what I would do instead if you are not one of the businesses that needs one.

I have spent eighteen years building digital products, including apps, and most of the last several years working specifically with service businesses in Michigan and across the country. I have watched owners spend real money on apps that nobody opened twice. I have also seen a handful of cases where an app was the right call and made money. The difference between those two outcomes is almost always timing and repetition, not design.

What people mean when they say "app"

The word gets used loosely, so let's pin it down. When an owner says "app," they usually mean one of three different things, and they cost very different amounts.

The first is a native app. That is the thing you download from the Apple App Store or Google Play. It is built specifically for iPhone or Android, it can send push notifications, it can work offline, and it lives on the customer's home screen with your logo on it. This is what people picture when they say "app," and it is the most expensive of the three by a wide margin.

The second is a web app. It runs in the browser but behaves like software: a customer portal where someone logs in to see their appointment history, pay an invoice, or track a job. No download, no app store, works on any device. Most of what owners actually want from "an app" is this, whether they know it or not.

The third is a progressive web app, or PWA. That is a regular website with extra wiring so it can be installed to a home screen, send limited notifications on Android, and load fast even on a weak connection. It is a middle ground: much cheaper than a native app, more capable than a plain website.

The reason this distinction matters is money. Owners get quoted for a native app when the thing they described is a portal, and they get quoted for a portal when what they needed was a faster website. Match the tool to the job and half the confusion goes away.

What an app actually does for a service business

Strip away the sales pitch and an app does a few concrete things:

• It keeps your brand on the customer's home screen, one tap from their thumb.
• It can send push notifications, which get read far more often than email.
• It can hold saved preferences: address, job history, payment methods, so repeat customers book in seconds.
• It can collect payment on the spot and store cards for recurring work.
• It can run loyalty programs, referral codes, and membership perks without paper cards.

Now here is the part that matters. Every one of those things only produces money if the customer comes back often enough to use them. A homeowner who needs a water heater replaced once every ten years is not going to open your app twice, let alone weekly. A lawn care customer who pays every month from April through November might. A gym, a med spa with a membership plan, a detail shop with quarterly customers: those are repeat businesses where the math can work.

So the first question I ask an owner who wants an app is simple: how often does your average customer buy from you per year? If the honest answer is "once or twice," stop reading and go fix your website and your call response. If the answer is "six or more times," keep going, because an app might make sense.

The Michigan reality: most service work is episodic

Michigan has a particular shape to its service economy. A big share of it is home services built around our seasons: furnaces in November, air conditioning in July, roofs after storm season, gutters in the fall, snow plowing all winter. Each of those is a purchase a customer makes once or twice a year, not twelve times a year.

That does not make those businesses bad app candidates because they are "only" service businesses. It makes them bad app candidates because of frequency. The same homeowner in Flint who calls you twice a year will not open an app for you. What they will do is search for you again when the furnace dies, which is why local search, reviews, and your Google Business Profile matter more for them than any app ever will.

The exceptions around here are interesting. Med spas and salons in the Detroit metro and Grand Blanc run membership programs, so their customers come monthly and a booking app with stored cards removes real friction. Some detailers and lawn services sell prepaid seasonal packages, which is the same pattern. A few HVAC companies have service agreement plans, quarterly maintenance visits, where a portal that schedules the next visit automatically genuinely saves the office time.

If your business has a membership, a service agreement, or a prepaid package, write down how many customers are on it. That number, not your total customer count, is who an app would serve.

When an app actually pays for itself

Let's run the arithmetic honestly, because app vendors will not do it for you.

Suppose you run a med spa with 300 membership customers who each visit monthly. Suppose an app, done properly, gets 20 percent of them to book their next visit one week earlier than they otherwise would. That is 60 visits moved one week earlier every month. At an average ticket of $150, you have pulled $9,000 of revenue forward per month. You have not created new demand, you have accelerated it, but faster cash cycle and steadier schedule fill are real. Now suppose the app costs $25,000 to build and $800 a month to maintain. You are at a payback in a few months, and after that it is profit.

Now run the same math for a residential plumber. 1,800 customers in the database, average frequency 1.5 visits a year. An app gets 5 percent of bookings shifted earlier, call it 135 booking-events a year moved by a couple of weeks. At a $400 average ticket, that is maybe $25,000 of accelerated revenue a year, spread thin, against a $25,000 build and ongoing maintenance. The money is real but the payback stretches to years, and the same $25,000 spent on local search and faster call response would likely return more. The app is not a bad product. It is a bad fit for the frequency.

The rule: an app pays for itself when (number of repeat customers) times (extra visits per year the app produces) times (average ticket) is clearly larger than build cost plus a few years of maintenance. If you cannot make that equation work on paper with honest numbers, do not build the app. No amount of polish fixes a frequency problem.

What an app really costs

Vendors quote all over the map, so here are the real cost centers.

Design and build. A simple, well-scoped native app with booking, payments, and push notifications runs roughly $15,000 to $40,000 from a competent US shop. Anything quoted under $10,000 is either a template product or overseas labor with limited support, and either can be fine if you know that is what you are buying. A customer portal as a web app often lands in the same range but can sometimes be delivered on top of existing scheduling software for far less.

The two app stores. Apple charges $99 a year for a developer account, Google charges $25 once. The real cost is time: Apple reviews every submission and update, which adds days to every release and occasionally rejects builds for reasons that feel arbitrary. Budget patience, not just money.

Maintenance. Phones get new operating systems every year. Payment rules change. An app that is not updated starts to break within a couple of years. Budget 15 to 20 percent of the build cost per year for maintenance, forever. This is the number vendors forget to mention and owners discover at month fourteen.

Adoption. Getting 300 customers to download an app is a marketing project of its own. Expect maybe 20 to 40 percent of your active repeat customers to install it if you promote it well at the counter, on invoices, and by text. If only 60 people download it, rework the math above, because the equation shrinks with them.

What to do instead if you are not an app candidate

For most Michigan service businesses, here is where the same budget goes further.

First, make the mobile website fast and stupidly simple. Most service searches happen on a phone, often while the customer is standing in a flooded basement or staring at a dead furnace. Your phone number should be tappable at the top of the page. Your booking or estimate request should take under a minute. If your site takes more than a couple of seconds to load on a phone, fixing that beats any app.

Second, use text messaging. Text open rates crush email, and you can send appointment confirmations, review requests, and seasonal reminders (furnace check in October, AC tune-up in May) from scheduling tools without anyone building software. A reminder text to last year's furnace-inspection list in late September is the closest thing to an app's value that a one-or-two-purchase-a-year business can get, and it costs a fraction of the build.

Third, put rebooking on autopilot where you can. If you run service agreements or memberships, most scheduling platforms can automatically create the next visit or send the reminder. That is the actual job the app was going to do, already done.

Fourth, spend on showing up when they search. When the customer's water heater dies in the middle of January in Lapeer County, they are going to Google, not your app. Being the business that appears in the map pack with 200 recent reviews and answers the phone on the second ring is worth more than any home-screen icon.

If you do build: how to do it without wasting money

For the businesses where the math works, a few rules that keep the project honest.

Start with the web app, not the native app. Build the customer portal in the browser first: log in, see history, book, pay. It works on every device, costs less, needs no app store approval, and you learn what customers actually use before you pay for a native wrapper. If usage proves the demand, wrap it or rebuild native later. Plenty of businesses never need to.

Build one job, not ten. The apps that succeed in service businesses do two or three things extremely well: book, pay, and remind. Every additional feature adds build cost, maintenance cost, and customer confusion. If a feature does not remove friction from booking, paying, or remembering, cut it.

Plan the launch before you build. Decide now how customers will hear about it: a card handed over with every invoice, a text after each completed job, a counter sign, a line in your review-request message. An app nobody knows about is a subscription you pay for and nobody uses.

Own your data and your accounts. Whatever you build, make sure the customer database, the booking records, and the payment records live in systems you control and can export. Do not accept a deal where your entire customer relationship is locked inside a vendor's platform with no export.

Budget for year two and year three, not just year one. Write the maintenance number into the plan before you sign anything. An app is not a project, it is a pet: it needs feeding every year or it gets sick.

The middle path: a PWA

Before you sign a native app contract, ask about a progressive web app. It is your existing website upgraded so customers can add it to their home screen with your icon, it loads nearly instantly, and on Android it can send some notifications. iOS support for notifications and install is more limited, which is the honest caveat, but for many service businesses a PWA delivers 80 percent of the perceived benefit of an app at 20 percent of the cost, and it lives in the same codebase as your website instead of a second one.

A quick decision guide

Ask yourself these five questions, in order.

One: does my average customer buy from me six or more times a year? If no, stop here and invest in local search, reviews, and call response instead.

Two: do I have a membership, service agreement, or prepaid package with at least a couple hundred people on it? If no, an app has nobody to serve yet.

Three: would stored payment methods and one-tap rebooking measurably change my schedule or my cash flow? Run the equation from earlier with real numbers. If you cannot make it work on paper, it will not work in production.

Four: can I commit to the maintenance budget every year, and to promoting the app at every customer touchpoint? If not, do not build it.

Five: have I actually asked twenty customers whether they would use it? This is the step everybody skips and it costs nothing. Ask at the counter, ask by text. If fewer than half say yes unprompted, that is your answer.

If you get five yeses, an app is probably a good investment. If you get one or two noes, the money goes further somewhere else.

Where this leaves the average Michigan owner

Here is my honest summary after years of watching these decisions play out. The app question is usually a symptom of a different feeling: the sense that the business should be doing something more modern, more digital, more like the big brands. That feeling is worth listening to, but the answer to it is almost never "build an app." The answer is usually "answer every call, text every customer, show up when they search, and make the website fast."

Michigan service businesses win on reliability and response. The customer whose furnace died at 9 pm does not care whether you have an app in the App Store. They care whether someone, or something, answered when they called, whether the tech showed up when promised, and whether the invoice was easy to pay. Get those right across a couple of years and you will have a customer base that would download an app, at which point, and only then, the math will start to work.

If you want an outside look at where your money goes furthest, whether that is a website fix, faster call response, or (rarely) an app, book a growth assessment and we will walk through it together. And if you just want to know how your marketing stacks up right now, take the growth scorecard first. It takes a few minutes and it will tell you which of these gaps is costing you the most.