All posts

Your customer portal. Built around one job.

To build a customer portal, start with the one question customers email you most, show the answer live from the system that already holds it, and make sure every customer sees only their own records. Here is how it works, what to prepare, when to buy instead and how to roll it out.

For teams that answer
the same emails daily.

One job first, then the rest.

How to build a customer portal, step by step

A customer portal is a private, logged-in part of your website or app where each customer sees their own orders, documents, invoices or requests and can act on them without emailing you. It is not a second copy of your business software. It is a narrow window onto the systems you already run, with a login in front of it.

The portals that get used start small. They answer one question well, such as “where is my order” or “can I have that invoice again”, and they answer it with live data. The portals that get abandoned launch with ten half-working features and data that is a day old, so customers email anyway.

The order of work matters more than the technology. These five points are the short version, and each one stands on its own.

  • Pick one job: the question customers ask most becomes the first screen of the portal.
  • Connect the source: the portal reads from your ERP, CRM or order system, not from a copy kept by hand.
  • Lock the data: every query is checked on the server so a customer only ever sees their own records.
  • Keep login simple: an emailed sign-in link or company single sign-on beats another password to forget.
  • Launch to a few customers first, measure the emails that stop, then add the next job.

The cost hides in the inbox.

Why answering customers by email costs more than it looks

Without a portal, your team is the interface to your own systems. A customer asks for a delivery date, someone opens the order system, finds the record, copies the answer into an email and sends it. Each request is small. Together they fill the day of the people who know your business best.

The mistakes hide in the same place. An invoice goes to the wrong contact. A status is copied from the wrong order. A document is sent as an attachment and then lives in an inbox nobody controls. None of this shows up on a report, because nobody counts it.

You can measure it yourself in one week. Ask everyone who deals with customers to tally each request that only needed a lookup: a status, a document, a copy of something already sent. Note how long each took and how long the customer waited. The most common request on that tally is the first job for your portal, and the total tells you what the portal is worth.

Gather the inputs before you build.

What to prepare before building a customer portal

Most delays in a portal project are not about code. They come from questions nobody had answered yet: which system holds the truth, who at the customer may see prices, what a status means in plain words. Settling these first is the cheapest work in the whole project.

Pay special attention to how your existing system gives up its data. Some offer a modern API, some only a nightly export file, some nothing without the vendor’s help. That one fact shapes the design, the timeline and how live the portal can be.

  • The tally of customer requests, with the top one or two marked as version one.
  • The system that holds each piece of data, and how it can be read: API, export or database.
  • How a customer account maps to people: one login per company, or several with different rights.
  • The internal statuses and codes translated into words a customer understands.
  • The personal data involved and the privacy rules that apply, such as the GDPR.
  • One person who owns the portal and decides what stays out of the first version.

Buy, extend or build?

Custom customer portal or off-the-shelf: a simple rule set

Custom software is not always the right answer. Many helpdesk tools, accounting packages, CRM systems and shop platforms include a customer portal already. If yours does and it covers the job on your tally, switch it on. That is a setting, not a project.

Building pays off when the portal has to show data from more than one system, when the workflow is specific to how you operate, or when the portal is part of what customers pay you for. In those cases a ready-made portal forces you to bend the process to fit the tool, and the workarounds end up costing more than the build.

Use the rules below in order and stop at the first one that fits. They are deliberately blunt, because the common mistake is commissioning a custom portal for a job a built-in one already does.

  • Your current system has a portal that covers the top request: use it and build nothing.
  • The top request is only sharing files: a secure shared folder per customer is enough for now.
  • The data sits in one system with a good API but no portal: build a thin custom layer on top.
  • The answer needs data from two or more systems: build, since no single vendor’s portal will join them.
  • Customers need to act, not only look: approve, reorder, book or upload. Build around that action.
  • The portal is part of your product and brand: build, and treat it as a product with its own roadmap.

Where AI helps and where it stops.

Where AI belongs in a customer portal and where it does not

AI is useful in a portal for the messy, language-shaped work. It can let a customer ask a question in their own words and find the right order or document, summarize a long service history, or read an uploaded form and fill in the fields. Those are reading and understanding tasks, and current language models do them well.

AI should not decide who may see what. Access control, prices, balances and order statuses must come from plain, predictable code and your system of record, the same way every time. A model’s answer is a well-informed guess, and a guess is the wrong tool for showing one customer’s invoice to another.

The practical rule is to build the portal so that it works with no AI at all, then add an assistant on top that can only reach the data the logged-in customer is already allowed to see. If the assistant is unsure, it should say so and offer a way to reach a person.

Roll it out a few at a time.

How to launch a customer portal safely

Treat the first version as a minimum viable product: one job, working end to end, for real customers. Before anyone outside the team logs in, test the access rules on purpose. Sign in as one customer and try to open another customer’s record by changing the address in the browser. It should fail every time, because the check lives on the server and not only on the screen.

Then invite a small group of customers you know well and keep email open alongside the portal. Watch whether the lookup requests from that group drop. If they still email, ask why: the data may be late, the wording unclear or the login a hurdle. Fix that before inviting more people.

Widen access in steps and add the next job from your tally only when the first is used without help. Keep counting the same requests you counted at the start. That number, not the feature list, tells you whether the portal is doing its work.

  • Test with real data volumes and with customers who have several users and roles.
  • Log who viewed and changed what, so questions can be answered later.
  • Give customers an obvious way to reach a person from every screen.
  • Agree who updates the portal when the underlying system changes.

Questions. Answered.

Does a customer portal work with my existing ERP or CRM?

Usually, yes. What matters is how the system lets other software read its data: through an API, a scheduled export or direct database access. An API allows live data, while an export means the portal is only as fresh as the last file. Check this before anything else, because it shapes the whole design.

How long does it take to build a customer portal?

A first version built around one job is an MVP, and an MVP usually takes weeks rather than months. What adds time is the connection to your existing systems, the number of user roles and anything involving payments. A clear scope and a system with a good API shorten it considerably.

Is a customer portal worth it for a small business?

It depends on the tally, not on company size. If your team answers the same lookup requests every day, a portal pays for itself in freed time and fewer mistakes. If requests are rare or every one needs a conversation, a portal will sit unused and a shared folder or a good email template is the better choice.

How do you keep customer data secure in a portal?

Every request is checked on the server against the logged-in customer, so changing an address in the browser never reveals someone else’s record. On top of that come encrypted connections, sign-in without weak passwords, a log of who viewed what and regular backups. Security is designed in from the first screen, not added before launch.

Same emails every day? Let’s build a portal.

Tell us what you’d like to build or improve.