A customer portal makes sense when customers keep asking the same things: where is my order, send me the invoice, how much do I owe, how many points do I have. Here is which businesses actually benefit from a portal, what features it can have, whether to build it on the web or as an app, and what to put in the first version.

Which businesses need a customer portal

A portal is useful when the relationship with a customer lasts longer than one purchase and the customer has something to check: statuses, documents, history, a balance.

Typical examples:

  • A B2B supplier. Business clients order regularly and need invoices, statements, reconciliations and order history.
  • A subscription or membership service. A gym, courses, an internet provider: sessions left, renewal date, payments.
  • Made-to-order work. Furniture, renovation, printing: order status by stage, design approval.
  • Logistics. Where the shipment is, when it arrives, which documents come with it.
  • A store with regular buyers. Order history, one-click reorder, rewards.

Say you supply packaging to cafés. A manager spends half the day answering in WhatsApp: “when will it arrive”, “send the invoice”, “what’s our balance”. A portal where clients see this themselves takes the routine off the manager, and clients don’t have to wait for a reply.

One-off purchases don’t need a portal. If a customer comes back once every few years, they won’t remember their password, and it is simpler to send them a link to the order status.

Typical customer portal features

Choose features based on the questions customers ask most often.

  • Orders and statuses. A list of orders, the stage of each, the expected date.
  • Documents. Invoices, statements, contracts, delivery notes to download.
  • Payments and balance. Pay an invoice, see what is owed or prepaid.
  • History. What was ordered and when, repeat a past order.
  • Rewards and discounts. Points balance, personal prices, promo codes.
  • Requests and support. Submit a request, ask a question, follow the reply.
  • Profile. Contacts, delivery addresses, company details, employees with access.
  • Notifications. A message when an order status changes or an invoice is issued.

You almost certainly have most of this data somewhere already: in your accounting system, a CRM, spreadsheets. So the main work is usually not the portal screens but reliably pulling data from where it lives. If you don’t have a single system of record yet, it may be worth getting your internal house in order first, as covered in a custom CRM for small business.

Customer portal on the web or in an app

A web portal opens in a browser on any device, nothing to install, and everyone sees updates immediately. For most needs, especially business clients who work with documents at a computer, that is enough.

A mobile app makes sense when customers use the portal often, from their phones, and push notifications matter: delivery, bookings, store rewards. An app costs more, has to be published on the App Store and Google Play, and needs updates for new phone OS versions.

A common sensible path is to start with a web portal that works well on phones, and build an app once you see that customers come back regularly. More on choosing in website, app or Telegram bot.

Security and roles

A portal holds customer data: names, phone numbers, orders, amounts, documents. A mistake here costs more than on an ordinary website.

What to discuss with the developer:

  • Login. Phone number with a code, email and password, or both. Limits on login attempts.
  • Roles. A business client may have several employees: the accountant needs documents, the buyer needs orders, the director needs everything. Your side too: a manager sees their own clients, an admin sees everyone.
  • Access separation. Each customer sees only their own data. It sounds obvious, but this is exactly where the nastiest bugs happen, and it must be tested on its own.
  • Backups and an activity log. Who changed what and when.
  • Where the data lives. On a server registered to your company.

Before launch, ask for one simple check: can one customer, by changing something in the page address, see another customer’s orders or documents?

If you store sensitive data, such as medical or financial records, check the storage requirements with a lawyer. And decide in advance what happens to access when a client’s employee leaves: who turns it off and how fast.

What to put in the first version

The first version of a portal should answer the two or three most common customer questions, and nothing more. To find them, ask your managers to write down what customers ask for a week.

A sample set for the supplier from the example above:

  1. Login by phone number.
  2. A list of orders with statuses.
  3. Downloadable invoices and statements.
  4. The current balance owed.

Rewards, online payment, roles for the client’s employees and an app can come in the second version. If you start with a prototype, customers can click through the portal screens before development and tell you what is missing. Why that is cheaper than writing code straight away is explained in prototype and first version.

Common mistakes

  • A portal for its own sake. It was built because “everyone has one”, but there is nothing inside worth logging in for. A month later nobody uses it.
  • Data that doesn’t match reality. Statuses are updated by hand, managers forget, and the customer sees “in progress” on an order delivered long ago. After a couple of those, they go back to messaging you on WhatsApp.
  • Complicated sign-up. A long form and email confirmation scare people off before they see any benefit.
  • Nobody told the customers. The portal launched, but managers keep answering in chats. Put the link in every invoice and order message.

How to order a customer portal

  1. Describe who your customers are and what they ask most often.
  2. List where the data lives today: accounting system, CRM, spreadsheets, chat history.
  3. Decide who will log in: only customers or their employees too, and which roles you need inside your company.
  4. Split features into the first version and “later”.
  5. Ask for a quote with separate lines for integrations and for roles and access.

For reference, a customer portal is priced as a web service, and at NOVO that work starts with a prototype from $300, a first version from $1,200 and a turnkey project from $3,000. More on the web services page.

In short

  • A portal is worth it when the relationship lasts and customers have something to check: statuses, documents, balance, rewards.
  • Pick features based on the questions customers ask managers most often.
  • The main work is usually integration with your accounting system, CRM and spreadsheets, not the screens.
  • Start with a web portal that works well on phones. An app makes sense for frequent use and push notifications.
  • Discuss roles, access separation and backups before development, and test them before launch.