A smiling man in an orange suit sits in a white armchair with a laptop on his lap, against a cobalt-blue wall with pink circles.

Client portal development

One secure place where your clients log in, see their file, documents and status, and handle for themselves what now goes through email and phone.

A client portal takes the question of where things stand out of your inbox, and gives your clients a place of their own that belongs to your brand.

Investment
Quoted per project, after a free call
First version
One core flow, sharply scoped
Form
Web application on your own domain

When a portal pays off

A portal earns its keep when the same information keeps going back and forth. These are the signs to look for.

  • Clients email or call to ask how far along their job, order or file is.
  • Quotes, invoices and documents go round as attachments, and nobody knows which version is the latest.
  • Your team retypes details the client could have entered themselves.
  • Clients want to check something or pass something on outside office hours too.

Who it is for

For service providers, wholesalers, rental businesses, agencies and other companies with returning clients, where each client needs to see or do something: a file, a project, orders, invoices or reported issues.

If you have dozens to thousands of clients who may each see only their own data, that is exactly the job of a portal.

Features

What a client portal can do

No portal needs everything. These are the building blocks we put the first version together from.

  • Sign-in and accounts

    Signing in with email and password or with a one-time link, with two-step verification where the data calls for it. Clients invite their own colleagues.

  • Roles and permissions

    Every client sees only their own data. Within a client, you decide who may view, who may order and who may approve.

  • Documents

    Quotes, contracts, reports and invoices in one place, with the latest version on top. Uploading works in both directions.

  • Status and progress

    Where a job, order or request stands: which steps are done and what is still to come.

  • Self-service

    Changing details, booking an appointment, reporting an issue or approving something, without anyone having to retype it.

  • Messages and notifications

    A message attached to the file instead of a separate email, and a notification as soon as something is ready.

The trade-off

Off-the-shelf software or custom?

An honest answer saves you money. If buying is wiser than building, you will hear that in the first call.

Off-the-shelf software fits when

  • Your CRM, accounting package or industry software already has a client area that does what you need.
  • Your process looks like that of most businesses in your sector.
  • You mainly want to share invoices and documents, without steps or rules of your own.
  • The look and the address of the portal matter little.

Custom fits when

  • Your process has its own steps, exceptions or calculations that no package knows.
  • The portal has to bring together data from several systems.
  • The portal is part of what you sell, and so has to belong to your brand.
  • A package charges you per user, and at your numbers that no longer adds up.

Often it is a combination: the package stays the source for invoices or stock, and the portal is the window your client sees.

Integrations

A portal is rarely an island. The data usually lives somewhere already, and the portal fetches it from there or writes it back.

  • Accounting and invoices, so clients see their invoices and payment status.
  • CRM or ERP, as the source for client data, orders or stock.
  • Payments, for example through Mollie or Stripe.
  • Email and calendar, for notifications and appointments.

What is not always possible

Not every system offers a usable integration, and some integrations release only part of the data. We find that out before we agree a price, not during the build.

Security and privacy

A portal holds client data. That makes security a design decision, not an afterthought.

  • Data is separated per client in the database, not just hidden on screen.
  • The connection is encrypted, and passwords are never stored in readable form.
  • Permissions per role and, where needed, a log of who changed what.
  • Storage in the EU where possible, and a data processing agreement at delivery.

Our own work

The parts of a portal, in two products of our own

Two products of our own, not client projects. Both contain the parts a client portal runs on: accounts, roles and data separated per company.

Approach

From first call to a portal in use

  1. Intro call

    A free 30-minute call about your process and about what clients ask you now.

  2. Scoping

    Which single flow solves the most? We pin down the first version, with integrations, scope and price.

  3. Design and build

    First a clickable prototype you can show to a few clients. Then interface, code and integrations.

  4. Putting it to use

    Testing with real users, live on your own domain, and a plan for what comes next.

Investment

What a client portal costs

We quote every portal per project. After the first call you know what the first version costs, before anything is built.

What drives the investment

  • The number of flows in the first version: viewing only, or also requesting, approving and paying.
  • How many systems are connected, and how good their integrations are.
  • The number of roles and the rules on who may see what.
  • Whether existing data has to be moved over.
  • Security requirements, such as two-step verification and a log.

What it costs

Quoted per projectAfter a free 30-minute call. We agree scope and price before we start.

  • Hosting, licences for connected systems and maintenance are agreed separately.
  • A small first version keeps the investment manageable. After that you extend step by step, each with its own price.
Discuss your client portal

Further reading

More on apps and portals

Part of our serviceApps and web applications

Frequently asked

Good to know

Clear answers to the questions we hear most about how we work, pricing and working together.

What is the difference between a client portal and a web app?

A client portal is a web app with one purpose: giving your clients a private place of their own. Technically it is the same kind of software. The difference lies in who logs in and what they may see.

How long does it take to have a client portal built?

That depends on the number of flows and integrations. After scoping you get a schedule with a delivery date for the first version. We start small on purpose, so you have something in your hands sooner.

Can the portal be connected to our accounting package or CRM?

Often it can, if the system has an API to connect to. Not every app can be connected, and some integrations are limited. That is why we check before you get a quote.

Where is our clients’ data stored?

We agree that up front: where the data is stored, who can reach it and how the backups run. The data stays yours. A data processing agreement is part of the delivery.

Who owns the portal after delivery?

After full payment, ownership of the design and the custom code we make for your project passes to you, as described in the assignment. Existing components and tooling we build with stay ours; you get a perpetual licence to use them as part of the portal. Third-party software keeps its own licence. The full policy is on the Intellectual property page.

Does the portal work on a phone too?

Yes. The portal works in the browser on phone, tablet and computer. A separate app from the App Store is only needed when the phone itself has to do the work, for example for notifications or the camera.

What if we want more later?

The first version is built for that. New flows, roles or integrations are added as follow-up work, each with its own defined scope and price.

Get started

Have something in mind? Let’s make it.

Book a free 30-minute intro call. We’ll show you how we would approach your idea.