← Blog
Web Development
November 3, 2026 · 4 min read

Website or web app? Choosing the right scope

Both open in a browser, but budget, timeline and upkeep differ widely. Three questions tell you which one you need.

Web Development

Half the requests we receive open with “we need a website”. As we talk, some turn out to need a web app and others a single-page marketing site. The difference isn't a technical footnote; it changes the timeline and cost several times over. Here is how we draw the line and what we recommend in each case.

Where the line falls

A website informs: who you are, what you sell, how to reach you. A web app does work: users sign in, enter data, complete a task. Anything that takes bookings, tracks orders or produces reports is an app.

A restaurant makes the difference clear. A page showing the menu, address and opening hours is a site: you write the content and visitors only read. If the same restaurant wants to take table bookings, things change. The system has to know which tables are free, never give one table to two parties, send a confirmation and handle cancellations. On screen the difference is a small form; behind it sits a different project altogether.

Three questions to decide

  • Will visitors sign in? Accounts bring permissions, password resets and data security with them.
  • Who creates the content? If only you write it, it's a site; if users produce data too, it's an app.
  • Does anything get calculated or talk to another system? Payments, stock and calendar integrations are app work.

If all three answers are “no”, a well-designed site is enough and can launch in a few weeks. A single “yes” means you should plan the scope as an app.

What drives time and budget

A marketing site usually takes 2–4 weeks, because most of the work is design and content. In an app, every screen has rules behind it: who can see what, what happens when someone enters bad data, what becomes of an order if payment fails halfway? Each rule has to be designed, built and tested. That is why an app on the scale of a SaaS MVP takes 8–16 weeks. Budget, too, grows with the number of those rules, not with the number of pages.

Upkeep after launch

The difference doesn't end on launch day. A site is light to maintain: content gets updated and the underlying software is refreshed now and then. With the admin panel you change text and images yourself. An app is a living system and needs regular attention:

  • User data has to be backed up and protected, and that responsibility continues after launch.
  • Integrations need updating whenever the payment, calendar or shipping services they rely on change.
  • Users ask questions, report bugs and request features; someone has to respond.
  • The server is monitored, because when the app stops, the work stops with it.

Ask about upkeep too

When you request a quote, ask what post-launch maintenance covers as well as what the build costs. We deliver every project with a bug-fix period; after that, a monthly maintenance agreement is available.

A middle path: site first, app later

If you're unsure, start small: launch the site first and leave the app for phase two. A properly built foundation allows that move. For the restaurant it works like this:

  1. 1

    The site goes live with the menu and contact details; a phone number or a simple enquiry form is enough for bookings.

  2. 2

    For a few months you watch the requests: how many people ask to book, on which days and times, with what questions?

  3. 3

    If the demand is real, the booking system is added on top of the same site, now shaped by actual need.

This path has one condition: mention phase two on day one. If the site is built on a foundation that can take an app later, the move is an extension; if it's built on an off-the-shelf template, it means starting again.

Common mistakes

  • Saying “just a small member login”. The login screen is small; the password resets, permissions and data security that follow are not.
  • Starting with a large app before you know anyone will use it. Measuring demand with a simple site first is far cheaper.
  • Describing scope by page count. “A ten-page site” says nothing; what a visitor can do says everything.
  • Leaving upkeep out of the plan and ending up with a system nobody looks after.
The costliest mistake is commissioning a site where an app was needed, then rewriting it six months later.

Preparing for the first call

  • Write everything a visitor should be able to do as a verb: reads, fills in a form, books a slot, pays.
  • Note your answers to the three questions, with a short reason for each.
  • List the work you do by hand today; which parts move into the system defines the scope.
  • Separate what must be there on day one from what can wait.

With that list in hand, we can settle which one you need in the first call and then send a week-by-week schedule. Often the right answer isn't one or the other but the right order: a site first, an app when its time comes.

Work with us

Have a project in mind?

Describe your idea in a few sentences. We'll review it and come back shortly with scope, timeline and budget.