Service · Websites and web apps

Client portal

A client portal is built around the questions your support desk fields every day: where is my order, could you resend the March invoice, I would like the same again. Every question a client answers alone is time handed back to your team. Take a plant hire firm: most of its calls are about return dates and delivery notes, and the day that information is online the switchboard can breathe. The client, meanwhile, gets an answer at nine on a Sunday evening rather than on Monday morning.

Orders
status and repeat in one place
ERP
figures come from your own systems
Two factors
or an existing work account
Documents
invoices, delivery notes, contracts

Where this service reaches

A portal is worth whatever load it lifts off people. That is the test we apply to each feature before letting it into the scope.

Put your scope to an engineer

Signing in

A one-time link by email, a second factor, or signing in with the client company Microsoft account for those who refuse another password. Sessions expire after a spell of inactivity.

Orders and jobs

What was ordered, at what price, how far along the delivery or the job has got, the tracking number, and a button to place the same order again without retyping it.

Documents

Invoices, delivery notes, certificates and contracts drawn from Sage, Cegid, Divalto or Business Central, downloadable as PDF and in Factur-X when the client accounting department asks for it.

Trading terms

Negotiated prices, discounts, credit allowance, outstanding balance and the name of the account manager, all on screen without writing to anybody.

Users and rights

Clients invite their own colleagues and decide who may see invoices and who may only order. Their bookkeeper never sees the basket; their storeman never sees the balance.

Notifications worth having

A message on each change of state, as a payment date approaches, or when a document is ready. A notification that prevents no phone call has no place here.

The way an engagement runs

The schedule mostly hangs on one question: can your business software expose its data through an API, or does that bridge have to be built first.

01

Reading the requests

We work through three months of incoming email and calls and sort the recurring questions. The portal exists to remove them.

02

Design

Roles, rights, sections and the flow of data between the portal and your systems, refresh frequency included.

03

Build

Interface, sign-in, links, notifications, then trials against the real records of a few willing clients.

04

Phased opening

We invite a first group, supply a one-page guide and measure how far the incoming volume drops.

A client portal handles personal data, so the GDPR applies in full. That means collecting only what is useful, logging who opened which document, hosting inside the European Union, signing a processing agreement with every provider involved, and having a procedure ready for access and erasure requests. Building that in from the start costs a fraction of adding it in a hurry, on the day a client puts the question in writing.

Questions and answers

They will, provided the portal solves a real problem: checking a status, fetching a document, repeating an order. An area offering only a profile page and an empty history holds nobody and is not worth building. A nudge helps too: send a link to the invoice inside the portal instead of an attachment.

Not for everything. Balances and availability need to be current to the minute, but invoice history can synchronise a few times a day. That split eases the load on the ERP and keeps the portal readable while the business system is in a maintenance window.

Usually not. A portal that behaves well in a phone browser does the same job without an install or a listing in an app store. An app earns its place when push notifications or offline use are needed, for instance by engineers out on the road.

Hardened sign-in, lockout after a run of failed attempts, a log of downloads, session expiry and encrypted traffic. Before opening, the portal goes through a security check and you receive the report along with the fixes applied.

It is measured. We record incoming volumes before opening, then again at one and three months, separating out the questions the portal is meant to absorb. If the figure does not move, clients are not finding the feature or it misses their need, and we correct rather than add.

Let us design your client portal

Tell us what your clients ask your team most often. We build the portal precisely around those questions.

When we are around
Weekdays, 8:00 to 18:00 CET; answers land inside one working day
Talking it through
A call on Teams or Google Meet, whenever writing is not enough

We set strictly necessary cookies only: they keep the site running and remember the city you chose. Nothing here is used for advertising or tracking. More in our privacy policy.