When a mobile app is what lets you scale

We’ve written before that most businesses asking for an app need a website first, and we stand by it. An app is the wrong tool for getting found. But there’s a point in a growing business where an app stops being a vanity project and starts being the thing that lets you handle more customers without more work. This is about that point.

Scaling is about repeat, not reach

Getting found is a website’s job. Scaling is a different problem: taking the customers you already have and getting more from each of them, more often, without your costs climbing in step.

That’s where an app earns its place. An icon on someone’s home screen is a standing invitation. They don’t have to remember your web address or search for you again. They tap, and they’re back. For a business that lives on people returning, a café with its regulars or a gym with its members, that shortcut is worth real money.

What an app does that a website can’t

A few things a phone does well, and a browser does poorly or not at all:

• Push notifications that actually get seen. Not marketing noise. A message that a slot has opened up, an order is ready, a subscription is about to renew. The right nudge at the right moment, without paying for an ad to reach your own customers.
• Working offline, or on a weak connection. If people use your product on the move, an app keeps going where a website stalls.
• Speed and feel. A well-built app is quicker for the things people do over and over, because it isn’t reloading a page every time.

None of this replaces your website. It sits on top of it, for the people who have already chosen you.

The economics of scaling

Here is the part that makes an app a scaling tool rather than just a cost. Once it’s built, serving the thousandth customer costs almost nothing more than serving the hundredth. The effort is in the build. After that, it runs.

That’s the same logic behind the other things we build for growing businesses. An AI agent answers the same questions a hundred times a day so you don’t have to, and costs the same whether it handles ten enquiries or ten thousand. Software that does a job once and then repeats it for nothing is how a small team serves a large number of people. An app is one of the clearest examples.

Build it small first

The mistake is to treat the app as a giant launch, stuffed with every feature you can dream up, delayed for a year. That’s how app budgets get burned.

The version that scales you is usually small. It does the one or two things your regulars would open it for, and does them faster and better than your website can. You ship that, watch how it gets used, and grow it from there. We build for both app stores from one codebase, so you aren’t paying twice to reach everyone, and the smallest useful version costs a fraction of the everything-at-once one.

The order that works

For most businesses the sequence is steady. Get a fast website bringing people in. Once you have a base of customers who use you often, and something an app would genuinely do better for them, build the app for those people. If you’re weighing it up, tell us what you’re trying to do and we’ll tell you plainly whether you’re at that point yet.