“Website” and “app” get used almost interchangeably these days, and most of the time it doesn’t matter — until you’re the one paying for it. The two are built to do genuinely different jobs, and knowing which one you actually need can save you from paying for the wrong thing, or worse, discovering six months in that what you bought can’t do what your business needs.
What a website is built to do
A website — sometimes called a brochure site — is mostly one-way. It tells people who you are, what you do, and how to get in touch. Someone lands on a page, reads it, and either calls you, emails you, or leaves. The content might change occasionally (new photos, a blog post, updated pricing), but visitors aren’t logging in, storing anything, or getting different results depending on who they are.
Most small businesses in Nelson, Tasman, and Marlborough need exactly this, and nothing more. A cafe, a builder, a hairdresser, a landscaper — their website’s job is to convince someone to pick up the phone or walk in the door. That’s a website’s job, and it’s a job it does well.
What a web app is built to do
A web app is two-way. People log in, enter data, and get something back that’s specific to them — a booking, an account balance, a job status, a quote. Underneath, there’s a database keeping track of who’s who and what belongs to whom, and business logic deciding what happens next.
Some examples that come up a lot for small NZ businesses:
- A booking or scheduling system — customers pick a time, staff see it appear in a calendar, nobody’s double-booked
- A customer or member portal — clients log in to see their own job status, invoices, or documents
- An internal job-tracking tool — replacing a shared spreadsheet that three people keep overwriting
- A custom quoting tool — someone enters their details and gets a real, calculated price back, not just a “get in touch”
- A simple inventory or stock system — tracking what’s on hand across one or more locations
None of these are exotic. They’re the everyday tools that get bolted together out of spreadsheets, email chains, and sticky notes because nobody realised a proper (and these days, affordable) alternative existed.
How to tell which one you need
Ask yourself a few questions:
- Does anyone need to log in? If customers or staff need their own account with their own data, that’s an app, not a website.
- Are you storing and looking up information? Bookings, orders, job records, memberships — if the site needs to remember things and act on them later, that’s app territory.
- Is there a spreadsheet or email chain doing this job right now, badly? That’s usually the clearest sign. If three people are editing the same spreadsheet, or the same information gets typed in twice, a small custom tool often pays for itself fast.
- Does the outcome depend on who’s asking? A brochure page shows the same thing to everyone. An app shows Sarah her bookings and Dave his — because it knows the difference.
If you answered no to all of these, you need a website — and a good one is genuinely enough. If you answered yes to even one, it’s worth at least having the conversation about a custom-built tool instead of duct-taping another workaround together.
The cost conversation has changed
Custom apps used to be squarely the domain of businesses with real budgets — think tens of thousands of dollars and months of development, which put them out of reach for most small operators. That’s shifting. AI-assisted development means a lot of the groundwork that used to eat weeks of a developer’s time now takes days, and that saving shows up in the quote. It doesn’t mean every idea is now a weekend project, but the gap between “what a website costs” and “what a simple, genuinely useful app costs” has narrowed more than most business owners realise.
The honest answer
Most businesses only need a website, and that’s not a consolation prize — it’s the right tool for the job. But if you’ve been quietly patching together spreadsheets, group chats, and sticky notes to run a part of your business, it’s worth asking whether that’s actually a job for a small, purpose-built app instead. It’s a different build to a website, priced and scoped differently, but it’s no longer the enterprise-only expense it used to be.