A laptop showing a simple customer form

Customer portals & self-service

The portal your customers keep asking for

They want to look it up. Instead they have to ask you.

Today

  1. 1Customer emails to ask
    someone moves it
  2. 2You look it up and resend
    someone moves it
  3. 3Their copy is an inbox

Rebuilt

  1. 1They see their own data
  2. 2Requests land in workflow
  3. 3Documents self-served
The same process, before and after. The left column is where the time goes.

How it runs today

  • Customers email or phone for order status, copies of invoices, or a certificate from last year.
  • Your team looks it up in an internal system and sends it back manually.
  • Documents are attached to emails, so the customer's copy is wherever their inbox is.
2 more →
  • Requests arrive in whatever format the customer chose, and get re-keyed.
  • Larger customers ask for a portal in every review, and it never gets built.

Signs it costs more than you think

  • A meaningful share of your inbound is customers asking for information you hold.
  • Procurement teams at your larger clients are frustrated by the lack of self-service.
  • You lose renewals partly on "they're hard to deal with" rather than on price or quality.
2 more →
  • Your team spends time on lookups that generate no revenue and no goodwill.
  • Customers keep their own shadow spreadsheet of what you've done for them.

What it becomes

  • Live view of orders, jobs, documents, certificates and invoices
  • Structured request and quote submission that lands directly in your workflow
  • Multi-level access — site, region and head office, with the right visibility each
  • Self-service document and report download, branded as yours
  • An API for the customers who want to integrate rather than log in
The full picture, and what it connects to →

A portal is not a website; it is a controlled window onto data you already hold. Customers see their own orders, jobs, documents, certificates, invoices and history — live, without asking — and can raise a request in a structured form that lands in your workflow rather than in an inbox. Access follows a real permission model, so a site manager sees their site and head office sees everything. The benefit that actually shows up in the numbers is twofold: the lookup contacts largely stop, and the account becomes measurably stickier because the customer's own operational history now lives in your system. Where a large client wants machine access rather than a login, the same data goes out through an API.

  • The operational systems that hold the jobs, orders and documents
  • Finance, for invoices, statements and payment
  • Your workflow, so a portal request is a first-class piece of work
  • Identity, so customer users are managed properly rather than by shared logins

The first release

One customer-facing view — usually order or job status plus documents — live for a pilot group of customers in about a week. Pick the pilot customers who complain most; they are the ones who will tell you what's missing.

Want this as a one-pager?

We'll send a single page on this process — what it costs to leave alone, what the rebuilt version does, and what a first release would involve. No sequence, no wizard.

One email about this process. Nothing else.

Others in customer

Let's build

What's your AI Nirvana?

Tell us where you want to go. We'll bring the team, build the product, and grow it with you — and you own it.

  • You own the IP
  • US-based team
  • Reply within 1 business day