"We want an app" is one of the most common opening lines we hear. It's also, more often than not, the wrong first ask. This isn't a blog post about apps being bad — we build them for a living. It's about spending your first rupee where it creates the most value.
Start with the job, not the format
Ask what the customer actually needs to do: buy something? Book a slot? Track an order? Talk to you? Almost every one of these jobs can be done excellently with a well-built website — often better, because there's no install step, no app store review and no platform fee.
The honest framework we use
- One-time or occasional use (a service, a product, an event) → website, always.
- Frequent, repeat use (daily orders, ongoing tracking, habit-forming utility) → app starts making sense.
- Need push notifications to drive engagement → app (though web push is a decent middle ground).
- Need camera, sensors or offline access → app.
- Need to reach customers who never visit a store or website → app + marketing.
The real costs people forget
A website is a few weeks and a clear scope. An app means two store listings, review cycles, version updates, device-fragmentation testing and a support channel for crashes and compatibility. None of these are deal-breakers — they're just costs that should be justified by the job the app does.
Build the cheapest thing that proves the value. Upgrade the format when the data says the job needs it.
The pragmatic path most clients take
- Launch a fast, conversion-focused website — usually with booking or ordering built in.
- Validate demand with real traffic and real sales.
- Build an app only when repeat usage or notifications justify it — often as a companion to the website, sharing one backend.
The good news: done right, step one isn't wasted. The same design system, backend and brand work carry straight into the app. We structure projects so nothing gets thrown away.
Want to talk through what your business actually needs? Start the conversation.