When a marketing website is not enough: the signs you need a web app or portal

By Ranjit Bhinge, founder of Blur Studio · Updated · 9 min read

Short answer: A marketing website is a set of pages people read: it explains what you sell and collects an enquiry. A web app is software you use in a browser to do a task, usually after you log in, and it keeps data that belongs to each user. You need an app or portal (a private area where customers or staff log in) when people must see their own information, when work moves through steps, or when your team keeps copying data from one place to another. If none of that is true, a good site and a form are enough.

Ranjit Bhinge

You have a website that looks fine, but customers keep asking for things it cannot do, and you want to know whether to add a tool, build an app, or leave it alone.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Short version: stay with a marketing site while its only job is to be read and to collect enquiries. Move toward an app when visitors need to log in, see their own records, or push work through a series of steps that your site cannot track. Most businesses reach that point in small steps, and the first step is rarely a full custom build.

What a site does well, and where it stops

Hostinger, a web hosting company, describes a website as pages of static information in a fixed place, like a brochure, and a web app as a software program you use to get a task done (Hostinger tutorial, updated March 2025). Bubble, a no-code app builder, puts it in a similar way: a site is a group of related pages that visitors read, while in an app users log in, manage their own data, and see the page change with that data (Bubble blog, 2026). Both are sellers of related services, so treat the framing as a guide and not a standard.

A marketing site does these jobs well: explain your offer, show proof, rank in search, take a call or form request. It stops being enough when the job becomes "remember this person and show them their own stuff". A few plain terms I will use:

  • Database: an organised store of records, such as customers, quotes and jobs, that software can read and change.
  • Portal: a private area of a site where a customer, client or staff member logs in to see their own records.
  • Dashboard: one screen that summarises live numbers from your records.
  • API: a doorway that lets one piece of software ask another for data or send it data.
Marketing websiteWeb app or portal
Main jobBe read, collect an enquiryLet people do a task with their own data
VisitorsAnyone, all see the same pagesKnown users who log in and each see different content
DataMostly fixed content, a form that sends an emailRecords that people create, edit and track
InteractivityLimitedHigh: changes appear as users act
BuildPages, a CMS (content management system, the editor behind the pages), a formBack end, database, rules about who can see what
UpkeepContent and software updatesOngoing testing, backups, user support, security

The table follows the comparison in Hostinger's tutorial. Real products are often both: an online shop has product pages (the site) and a cart, account and checkout (the app).

Seven signs a site is no longer enough

Score yourself against this list. Each sign comes with the cheapest thing to try first, because a full build is the last answer and not the first.

  1. Customers ask "where is my order, quote or file?" They want to look it up themselves. First try: a shared status page or a tool that sends status emails. Build when you have many customers and each needs different information.
  2. You need logins. Anything private, such as invoices, signed documents or project files, needs an account per person. First try: a ready-made client portal tool (below). Build when the tool's rules do not match how you work.
  3. Work moves through stages. A request becomes a quote, then a booking, then a job, then an invoice, and someone has to chase each step. First try: a CRM (a customer relationship management tool, software that tracks every lead and customer) with a pipeline. See CRM for a small business.
  4. You calculate things. Prices depend on size, distance, options or a customer's own rates. First try: a quote form with fixed choices. Build when the rules have exceptions that only your system can know. See building a quote calculator.
  5. Your team copies data between tools. Someone retypes form answers into a spreadsheet, then into accounting. First try: an automation tool. If the automations break often or multiply, read when Zapier automations need custom software.
  6. You need a live view of the business. Owners want one screen: jobs open, money owed, leads by source. First try: reports from the tool that already holds the data.
  7. The spreadsheet has become the business. More than one person edits it, it has colour codes only one person understands, and a mistake costs money. See how to know you have outgrown spreadsheets.

One or two signs usually mean "add a tool". Four or more, especially if your own rules are the reason the tools do not fit, usually mean a custom app is worth pricing.

Three examples of the move

Client portal

An agency, accountant or contractor shares files, approvals and invoices with each client. A shared folder works with five clients. With fifty it becomes a support job: wrong links, old versions, nobody sure which file is final. A portal gives each client one login and one view. Ready-made options exist: SuiteDash, a client portal and business management tool, lists unlimited clients and staff on every plan, from $19 a month billed monthly, with storage caps per plan (100 GB on the lowest) (its pricing page, November 2026). Content Snare, a tool for collecting documents and answers from clients, lists plans from $35 a month billed annually, with 20 active requests and 2 users on that plan. Check both pages, since plans change. More on this in client portals and how to create one for an agency.

Quoting tool

A form that emails you the details is a website feature. A tool that asks the right questions, applies your price rules, saves the quote against the customer, sends it, and reminds you three days later is an app. Start with the form, then see instant quote software before building.

Dashboard or internal tool

If the only users are your staff, the case for building is often stronger, because you control who logs in and you do not need public sign-up, branding or marketing pages. An internal tool that replaces five spreadsheets is a common first build. See replacing five spreadsheets with one customer database.

The middle path: keep the site, add the app beside it

You rarely need to rebuild the marketing site. A common setup keeps the marketing pages where they are and puts the app on a subdomain, for example app.yourbusiness.com, with a "Log in" link in the site header. The site keeps ranking and loading fast, and the app has its own database and rules. The two can share a data trail: a form on the site creates a record in the app. The how-to for that link is in connecting your marketing site to your own app or database.

What goes wrong when you bolt an app onto a page builder or a WordPress theme instead:

  • Logins, permissions and per-user data are added by plugins from different authors, and each plugin update can break another.
  • Private data and public pages share one admin area and one set of backups, so a content editor can see more than they should.
  • The site slows down because every page carries app code.
  • When you outgrow it, the data sits in plugin-specific tables that are hard to move.

No-code or custom?

No-code builders such as Bubble can be a fair way to build an app yourself. Bubble's pricing page (November 2026) lists a Free plan, Starter at $32 a month billed annually, Growth at $119 and Team at $349 a month billed annually, with usage measured in workload units (its unit for the server work an app does, 175,000 a month on Starter) and plans bought per project. That suits an early version you will change often. It starts to hurt when usage-based bills grow, when you need a feature the platform does not offer, or when you want the code itself. The library covers that choice: Bubble alternatives, Bubble agency or custom code and buying a tool or building custom software.

There is no general price or timeline for "a web app" worth quoting, because a single range would not hold across small businesses. Cost depends on the number of user types, the rules, the integrations and who owns the result. Read custom software development cost and how long custom software takes, and get written scopes from two builders.

A worked example, with made-up numbers

Take an imaginary pest control company. It gets 60 web enquiries a month. Each one is retyped from an email into a spreadsheet (5 minutes), a quote is built by hand (15 minutes), and customers phone to ask for the quote status (3 calls a month per 10 quotes, 5 minutes each).

  • Retyping: 60 x 5 = 300 minutes.
  • Quote building: 60 x 15 = 900 minutes.
  • Status calls: 18 x 5 = 90 minutes.
  • Total: 1,290 minutes, about 21.5 hours a month.

First fix, with no custom code: a form that writes straight into a CRM and a quote template. That might remove the retyping and half the quote time. The remaining hours show whether a portal or calculator is worth building. If the leftover work is small, stop there. If the owner still spends most of a week on rules the tools cannot hold, that is the case for custom. These numbers are invented to show the method. Use your own.

Decision rules

  • Stay with a site if visitors only read, call, or send a form, and your team handles the rest in one tool without copying.
  • Add a ready-made tool if one sign fits and a published product does that exact job. Notion, a workspace and notes tool, lists an external guest limit of 10 on its Free plan, with guests seeing only the pages shared with them (its pricing page, November 2026), and Airtable, a spreadsheet-style database, does not charge for read-only collaborators or form submissions. For a handful of clients a shared page or form may be all you need.
  • Use no-code if you are testing an idea and expect the rules to change.
  • Build custom if you have several signs, rules that tools cannot hold, real volume, and a wish to own the result.
  • Do nothing yet if you cannot name one task the app would remove. A list of "features" is not a reason.

What to check before you build

  • Who owns the code and data? Get it in writing. See who owns custom software code you paid for.
  • Who can see what? Per-user data must be locked by user, not just hidden on screen. Supabase, a database service, says a table in an exposed schema without row level security (rules that decide which rows each user may read or write) can be read and written by any role that has a grant on it (its row level security docs, November 2026). Ask how your builder handles this. The library page on an exposed database fix shows what going wrong looks like.
  • Where are the backups? An app holds data you cannot recreate. See keeping a site healthy after launch.
  • Who runs it after launch? Apps need ongoing testing and updates, which Hostinger lists as a main difference from a plain site.

Who should skip this

Skip the app if your goal is simply more leads from search, if you have fewer than a handful of customers who need private access, or if your real problem is a slow follow-up process that a CRM and a reminder would fix. An app on top of a broken process only makes the broken process faster.

How I'd approach this

I would write down the three tasks that cost the most time and ask of each: could a ready-made tool do this, or does it depend on rules only we hold? Anything the first answer covers, buy. Keep the marketing site as it is, and put any app on its own address beside it.

First-week plan: on day one list every place a customer's data is typed (form, email, spreadsheet, accounting). On day two count the minutes each week your team spends moving it. On day three try the cheapest fix for the biggest block. By day five decide: stop, no-code test, or get two written scopes for a custom build. If it ends in scopes, ask each builder who owns the code, where the data lives and what a restore looks like.

If the answer is custom, Blur Studio builds that version, including web apps, portals and the connections to your CRM and calendar, and keeps them running afterwards: see what that includes.

For a closer look, see moving a Bubble marketing site to a faster stack.

For a closer look, see building a client portal for your agency customers.

Questions people ask

What is the difference between a website and a web app?

A website is a set of pages people read, the same for every visitor. A web app is software in the browser that people use to do a task, often after logging in, with data that belongs to them. Many products are both, such as an online shop with product pages and a checkout. The table in this article compares them side by side.

Do I need a web app if I only have a quote request form?

Usually no. A form that sends the details to your team is a normal website feature. Think about an app only when quotes are calculated by rules, tracked through stages, or shown to customers after login. Start with the guide on a quote request form that sends details to your team.

Can I turn my WordPress or page-builder site into an app?

Plugins can add logins and simple member areas. They get fragile when there are many user types, per-user data and business rules. A safer pattern keeps the site as it is and builds the app beside it on a subdomain. See connecting a site to your own app or database.

Is a client portal a website or a web app?

A web app. It needs a login for each client and shows each one their own files, invoices or status. You can buy one ready-made, or have one built. The library has a guide to client portals and a page on custom client portal cost.

How much does a web app cost?

No honest single range covers it, because cost depends on user types, rules, integrations and ownership. Use the library pages on custom software development cost and build time, and ask for written scopes from at least two builders.

Should I use a no-code tool like Bubble or have it custom built?

No-code is a fair choice for a first version you expect to change. Custom code makes more sense when usage-based bills grow, when the platform cannot do what you need, or when you want to own the code. Compare in Bubble agency or custom code.

What is a progressive web app, and is it a middle option?

A progressive web app is a web app that can be added to a phone's home screen and behave a bit like an installed app. It can be a good fit when staff or customers use it from phones. The trade-offs against a native app are covered in mobile app vs web app for a small business.

Will adding an app hurt my website's search rankings?

Not if the app lives on its own address, such as a subdomain, and the marketing pages stay as they are. Problems come from rebuilding the whole site or loading app code on every marketing page. Check any plan against page speed problems on marketing sites.

More in this topic: Websites: custom builds, portals, lead capture and site care (9 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…