Website or app first? What to build with a small budget in 2026

A boutique owner in Gurugram sat across from me with a number in her head and a knot in her stomach. She had about ₹60,000 saved to "go digital", a WhatsApp full of orders, and one nagging question that two different people had answered two opposite ways. Her cousin, who works in tech, told her to build an app — "everyone's on their phone, you need an app." A freelancer she'd met told her to build a website first. She'd been stuck for three weeks, not spending the money, quietly losing customers to a competitor who'd just launched a neat little online store.

I hear a version of this every single week. And the honest truth is that the question she was asking — "website or app?" — is the wrong question. It sounds like a choice between two similar things, like deciding between two phones. It isn't. A website and an app do different jobs, cost wildly different amounts, and solve different problems. Asking which to build first without knowing which problem you actually have is how good businesses waste lakhs.

So this post is the conversation I had with her, written out in full. No jargon, real 2026 prices in rupees, and the honest trade-offs — including a third option most owners have never even heard of that often beats both. By the end you'll know exactly which one your business needs first, why, and roughly what it should cost. If you want the ground-level numbers on the app side specifically, I've written a separate deep dive on how much it really costs to build an app in India; this post is about the decision that comes before that one.

First, the one question that actually settles it

Forget "website or app" for a minute. Ask yourself this instead:

Where does my next customer decide to buy from me?

Sit with that. Not where they pay — where they decide. Almost every small business falls into one of two camps, and the camp you're in is the whole answer.

Camp 1 — You have a discovery problem. New customers don't know you exist yet. They find you by searching Google ("boutique near me", "birthday cake Noida", "physiotherapist in Indirapuram"), by tapping a link in your Instagram bio, by clicking a WhatsApp forward from a friend, or by asking an AI assistant. They then decide whether you're real, what you cost, and whether to reach out. The bottleneck is being found and being trusted by strangers.

Camp 2 — You have a loyalty problem. People already know you. Your challenge is getting the same customers to come back more often, order faster, and not drift to someone else. Think of a tiffin service with monthly subscribers, a gym with members, a salon with regulars, a kirana with daily buyers.

Here's why this decides everything: a website is a discovery tool. An app is a loyalty tool. A website is your address on the open internet — the place Google, Instagram and AI answers can send a stranger to learn about you and decide. An app is a shortcut on the phone of someone who already chose you and wants to come back with one tap.

You cannot keep customers you never got. That's the trap. Building an app to "increase loyalty" when you don't yet have a steady stream of new customers is like printing beautiful loyalty cards for a shop that has no signboard and no address. Most small businesses on a tight budget have a discovery problem first. Which is why, for most of you, the website comes first — and it isn't close.

What a website, an app, and "both" really are (plain English)

Before we price anything, let's be clear about what these words even mean, because a lot of confusion is just fuzzy definitions.

A website is a set of pages that open in any phone or computer browser — Chrome, Safari — with no download. You have a web address (yourshop.com), and anyone can reach it instantly by tapping a link. It's the one piece of your online presence that you own. Instagram can restrict your account tomorrow; Google can change what it shows; but your website is yours, like the deed to a shop.

A native app is a separate program a customer must download and install from the Google Play Store (Android) or Apple App Store (iPhone). It lives as an icon on their phone. It can do deeper phone things — reliable push notifications, tighter camera and location use, working fully offline — and it feels premium. But it's a second product: a different codebase, app-store approvals, and constant upkeep so it doesn't break when phones update.

And then there's the option almost nobody tells small-business owners about — the installable website, or PWA (progressive web app). This is an ordinary website, built a certain way, that a customer can "Add to Home Screen" and then open like an app: its own icon, full-screen with no browser bar, pages that still load with no signal, and push notifications on Android and on iPhones running recent software. In plain words, a website that behaves like an app, without living in an app store. We'll come back to why this matters so much for tight budgets.

Hold these three in your head. Most owners think the choice is A or B. For a large share of you, C quietly wins.

The decision, by the kind of business you run

Theory is nice; let me make it concrete. Here's how the "found-and-bought vs opened-every-day" test plays out across the businesses I actually work with. Find the row closest to yours.

Notice the pattern. The vast majority of small businesses are in a discovery-first situation, and their honest first build is a website (or an installable website). The businesses that genuinely need an app early are the ones where the app is the product itself — delivery, marketplaces, daily-habit tools. If that's you, building the app first is right, and you should read the honest signs your business is actually ready for an app before you commit. For everyone else, an app is something you earn the right to build by first proving people come back.

The real 2026 costs — with nothing hidden

Money is where this decision gets settled for a small budget, so let me put honest numbers on the table. All prices are real and current for 2026; I'll show the sticker and the recurring cost, because the recurring cost is the part that quietly hurts.

What a website costs

You have three broad ways to get a website, at three price levels:

• Do-it-yourself builder. Tools like Shopify (for shops) or Wix (for general sites). Shopify's Basic plan is about ₹1,499 a month — roughly ₹1,769 including 18% GST — and it runs a promotional ₹20/month for the first three months (Shopify India pricing). Fair warning on the fine print: Shopify's Basic plan adds a 2% fee on each sale if you use a third-party payment gateway. Cheap to start, easy, but you're renting.
• WordPress (own it yourself). Domain plus hosting is roughly ₹5,000–15,000 a year. More freedom, a bit more fiddling.
• Done-for-you designed site. A proper small-business website built for you is commonly a ₹15,000–60,000 one-time build plus ₹5,000–15,000 a year to keep it hosted and running. This is what most owners actually want: someone hands them a finished, fast, good-looking site.

So the realistic all-in for a solid small-business website is ₹15,000–60,000 up front and ₹5,000–15,000 a year after. The key thing: once it's built well, a website mostly sits there and works. Low drama.

What a native app costs

A native app done properly — one that doesn't feel like a cheap wrapper, works on both Android and iPhone, and won't embarrass you — typically starts around ₹1.5–5 lakh and climbs with every serious feature (payments, logins, live tracking, chat). That's the build. Then come the parts owners never budget for:

• Apple charges $99 a year — about ₹8,000 — just to keep your app on the App Store. Stop paying and your app disappears (Apple Developer Program).
• Google charges a one-time $25 — about ₹2,000 — to open a Play Console account (Google Play Console).
• Maintenance is not optional. Phones get OS updates constantly, and an app that isn't updated slowly breaks. Budget for ongoing developer time, not a one-and-done payment.

And there's a 2026 rule that catches almost every first-timer by surprise. If you open a new personal Google Play account, Google now requires you to run a closed test with at least 12 real people for 14 continuous days before your app is even allowed to go live to the public (Google Play testing requirements). Twelve real humans who install it and keep it for two weeks. That's a genuine hurdle for a small shop that just wanted to "put an app out" — and it exists for good reason (it keeps junk off the store), but nobody warns you.

Here's the two side by side:

Read that "customer effort" row twice. Every extra step between "interested" and "using it" loses people. A stranger will tap a website link in a second. Asking that same stranger to go to an app store, search your name, download 40 MB, and install — to try a shop they've never bought from — is a wall most will not climb. That single fact is why discovery lives on the web.

Why "we'll just build both" usually backfires

The owner with ₹60,000 asked the natural question: "Can't I just do both to be safe?" On a small budget, doing both at the same time is usually the worst choice of all. Here's the honest reasoning.

Both aren't one project — they're two products, each needing design, building, testing and, forever after, maintenance. Split a small budget across two and you get two thin, half-maintained things instead of one that's genuinely good. Worse, the app you rushed launches into an empty room: no repeat customers waiting, no reason for anyone to download it, so it sits at a handful of installs while you keep paying to keep it alive. I've watched more than one owner spend a lakh-plus on an app that ended the year with fewer downloads than they have WhatsApp contacts — because the discovery layer underneath it was never built.

"Both" is the right destination for many businesses. It's the wrong starting line. The safe version of both is a sequence, not a simultaneous spend — which is the whole next section.

The right sequence: earn the app

Here's the order I'd give almost any small business with a limited budget. Each step earns the next.

Step 1 — Get discoverable (do this first, always). A fast, honest website; a Google Business Profile so you show up on Maps and local search (this is free and shockingly underused); and a WhatsApp catalogue so enquiries turn into orders in the app your customers already live in. WhatsApp isn't a nice-to-have here — India has the largest WhatsApp user base in the world, over 15 million businesses use WhatsApp Business tools in the country, and roughly 73% of Indian businesses use it to talk to customers (WhatsApp business statistics). Point all of it at the website you own.

Step 2 — Convert and learn. Make that website genuinely good at turning a click into an enquiry or sale, and watch what customers keep asking for. Do they want to reorder easily? Track a booking? Get reminded? Those repeated asks are your app's future feature list, handed to you for free by real people.

Step 3 — Only now, consider the app. Once you have steady discovery and a base of repeat customers who'd genuinely use an app, add one — and even then, ask whether an installable website (PWA) gets you 90% of the benefit at a fraction of the cost. When you do build the native app, it launches to customers who are already waiting for it, not to silence.

This order matters because it lets each rupee prove itself before the next one is spent. It's the same "cut it down, ship the core, let reality tell you what's next" thinking I use for software products in what to build first so you don't waste three months — the discipline is identical whether you're building a boutique's web presence or a SaaS.

The middle path most owners never hear about: the installable website

Now the option that changes the maths for a lot of you. Remember the PWA — the website that can be "installed" to a home screen and opened like an app? In 2026 this has quietly become good enough to be the right answer for a big slice of small businesses, and almost nobody in the "you need an app!" crowd will tell you it exists.

Here's what a well-built PWA gives you today:

• An icon on the customer's home screen — the "app feeling" — with no app store involved.
• Full-screen, no browser bar when opened, so it looks like an app.
• Works offline for pages already loaded — a menu, a catalogue, a loyalty card that opens even in a weak-signal basement.
• Push notifications — on Android fully, and on iPhones since iOS 16.4, once the customer adds it to their home screen (PWA push on iOS). Apple has kept leaning in: on iOS 26, sites added to the home screen now open as web apps by default.

And it costs close to a website, not close to an app. No ₹1.5-lakh second codebase. No Apple ₹8,000 a year. No 12-tester Play Store wait. No 40 MB download standing between an interested stranger and your shop.

Let me be equally honest about the limits, because I promised no hype. A PWA can't reach every deep phone feature a native app can. Its offline powers are real but more limited. And on iPhones specifically, push notifications only work after the customer has manually added it to their home screen — and fewer people do that than tap "install" on Android, where the prompt is smoother. So if your business truly depends on aggressively reaching iPhone users with notifications many times a day, a native app still wins.

But for the common cases — a shop, a menu, a bookings page, a catalogue, a simple loyalty card, a content hub — a PWA covers the large majority of what owners actually want from "an app", at a fraction of the cost and with zero download friction. For a business staring at "₹25,000 for a website vs ₹2 lakh for an app", the installable website is very often the grown-up answer for 2026. You do not need a native app just to have your icon on someone's phone.

A full worked example: the boutique with ₹60,000

Let me take the Gurugram boutique owner and price out her three honest paths, in rupees, so you can see the reasoning end to end. Her situation: a WhatsApp full of orders, an Instagram following, no website, and one recurring pain — customers keep asking "do you have this in blue / what's the price / is this still available", and answering each one by hand is eating her evenings.

Path A — Build a native app first (her cousin's advice). A proper shop app for Android and iPhone: realistically ₹1.5–2.5 lakh to build well — already three to four times her budget. Then Apple's ₹8,000 a year, Google's one-time ₹2,000, the 12-tester, 14-day wait before it can even launch, and ongoing upkeep. Worst of all: her problem is that new customers must find her and existing ones must self-serve answers — and an app helps with neither for strangers, because they'd have to download it first. Verdict: wrong problem, wrong price. This is the ₹2-lakh mistake.

Path B — Build a website / installable store first (the honest choice). A designed shop website with her catalogue, prices, and a WhatsApp-order button — built as a PWA so regulars can add it to their home screen. Roughly a ₹25,000–40,000 build plus ₹8,000-ish a year to run, comfortably inside ₹60,000 with money to spare. She sets up a free Google Business Profile so "boutique in Gurugram" starts finding her, links the store in her Instagram bio, and puts the catalogue on WhatsApp. Now strangers can discover her, every "what's the price / is it available" question is answered by the site itself, and repeat customers tap an icon to reorder. Verdict: solves the actual problem, fits the budget, leaves room to grow.

Path C — Both at once. Split ₹60,000 across a rushed website and a rushed app and she'd get two mediocre things, an app with near-zero downloads, and double the maintenance headache — for a business that hadn't yet proven a single repeat-order pattern. Verdict: the tempting trap.

She went with Path B. Within a few weeks her evenings were quieter — the site answered the price-and-availability questions for her — and she was showing up when people searched for boutiques nearby. The plan was always to add a proper app later, once she had a real base of repeat buyers who'd use it. That's the point: she didn't say no to an app. She said "not first." She earned it instead of gambling on it.

The mistakes I see most often

A few honest patterns, so you can skip the expensive lessons:

• Confusing "impressive" with "useful." An app feels more serious than a website, so owners over-spend on the app and under-spend on being found and being fast. Customers don't care which one is more impressive; they care whether they can find you and buy without friction.
• Ignoring the recurring cost. People compare a website's price to an app's build price and stop there. The real comparison includes the years after — Apple's yearly fee, updates, breakages. An app is a subscription to maintenance, not a purchase.
• "Everyone's on mobile, so I need an app." Everyone on mobile is exactly the argument for the web — because the mobile browser is where people land from Google, Instagram and messages. Mobile-heavy behaviour is the norm in India, and most of that mobile activity is browsing and messaging, not opening a small shop's downloaded app.
• Treating Instagram as the whole plan. Social is where the attention is, and you should absolutely sell there. But you rent your presence on Instagram — the algorithm and the platform decide your fate. A website is the piece you own, and increasingly it's what Google's AI answers and assistants quote when someone asks about a local business. Sell on social; anchor it to a site you control.
• Skipping the free wins. A Google Business Profile and a WhatsApp catalogue cost nothing and often move the needle more than an expensive build. Do the free things before the pricey ones.

So what should you actually do?

Strip it all down and here's what I'd tell you over chai, the way I told that boutique owner:

• Answer the one question: where does my next customer decide to buy? If it's strangers finding and choosing you, you have a discovery problem — build the website first. If it's the same people coming back daily, and that habit needs to live on their phone, an app can come sooner.
• For most small businesses, the order is: get discoverable (fast website + Google Business Profile + WhatsApp catalogue) → convert and learn → then add an app, or an installable PWA, once real repeat customers are waiting for it.
• Consider the PWA seriously. For a shop, menu, catalogue, bookings or loyalty card, an installable website gives you most of the app feeling at close to website cost, with no store gatekeeping. In 2026 that's the right middle path for a lot of you.
• Never do "both" at once on a small budget. Do them in sequence so each rupee earns the next.
• Spend where the buying decision happens — being found, being fast, being trustworthy — not where the excitement is.

The whole mistake in "website or app?" is that it treats a hammer and a screwdriver as rivals. They're not competing; they do different jobs, and one almost always comes first. Get found, turn interest into sales, prove people come back — and then build the app, on top of a business that's already working, for customers who are already yours.

If you'd like a straight answer for your specific business — which one you need first, whether a PWA gets you there for a fraction of the cost, and what it should honestly run you — that's exactly the kind of thing we help owners think through at the Studio, where a small-business site starts at ₹9,999. But whether you work with us or not, do this one thing before you spend a rupee: figure out which problem you actually have. Discovery or loyalty. Get that right, and the "website or app" question answers itself.