Think Build Implement Repeat
Web Development

Does Your Business Actually Need a Customer Portal?

Last updated:

The test is repeated questions

Portals are frequently built because competitors have one. The justification that actually holds is simpler: are customers repeatedly contacting you for information you already hold in a system?

Order status, invoices, documents, appointment history, service records. If your support inbox is full of those requests, a portal removes them. If it is not, a portal will sit unused.

Build the three things, not the account area

The commonest mistake is scoping a general customer account with everything in it. Look at what people actually ask for and build those three things well.

  • The top three requests from your support log, and nothing else
  • Read-only first — showing information is far cheaper than allowing changes
  • One user type initially; role hierarchies multiply the work
  • Login that people can actually complete, with sensible recovery

Understand what you are committing to

A portal is not a page, it is an application. Accounts, permissions, data protection, security patching, and support for users who cannot log in. Budget 15–25% of the build annually and someone's ongoing attention.

If that maintenance is not affordable, the portal is not affordable, and it is better to know before the build than eighteen months into a decaying system.

Cheaper alternatives worth checking first

Proactive notifications remove most status enquiries without any login. Emailed documents with secure links remove most document requests. A well-designed public tracking page with a reference number removes the rest.

In several projects we have scoped, the honest recommendation was notifications rather than a portal, at a fraction of the cost.

Adoption decides whether it was worth it

  1. Tell customers it exists, repeatedly, in the messages they already receive
  2. Link directly to the relevant page rather than to a login screen
  3. Make password recovery painless, because most portal abandonment is a forgotten password
  4. Measure active users honestly, and be willing to conclude it is not being used

Frequently asked questions

What does a customer portal cost?

A focused read-only portal over existing data typically £25,000–£60,000. Anything with transactions, roles or document upload is considerably more.

Can we use an off-the-shelf portal?

Sometimes, particularly if your operational system offers one as a module. That is usually cheaper and worth checking before commissioning a build.

How do we handle security?

Authentication on every request, strict scoping so one customer cannot see another's data, tested adversarially. This is the failure mode that matters most in portals.

What if adoption is low?

Measure early. If usage after three months is negligible, the honest answer may be that notifications solved the problem and the portal was not needed.

Keep reading

Customers asking for information you already hold?

Sometimes the answer is a portal and sometimes it is notifications. Tell us what they ask for and we will say which.

Book a free 30-minute call Get a project estimate WhatsApp us

Related services

What we build for problems like this one

Web DevelopmentCustom Software Development