Skip to main content
Back to Operational workflows

“Our trade customers ring up to place orders and check their account.”

Customer portals, part of Operational workflows: a place your clients and trade customers log in to order, track and download, connected to the systems behind it.

A portal is worth building when customers keep ringing for order status, re-keying prices from old PDFs, or emailing documents that should sit on an account. We design one operational workflow first, connect it to your accounts or ERP, and deliver it in phases. Discovery is quoted, the build has a fixed scope, and you own the code and data.

Or send your project details

What it does for your business

The business side first. The software comes later.

  • Customers help themselves

    Order history, account balances, outstanding documents and delivery status on a page they can reach without ringing your team.

  • Built to how you trade

    Contract pricing, credit limits and approval steps built to match how you trade, rather than forced into a standard shop.

  • One place for documents

    Invoices, statements, certificates and contracts published per account, so the right customer sees the right file.

  • Yours at the end

    The code, data and cloud account belong to you, with phases that let you stop or change direction after each one.

What it has done for clients

Exhibit 1. Operational systems built around a customer’s rules
The cost todayWhat changesProof
A contract customer required digital orders and invoices by a deadlineOrders received and checked, invoices returned in the customer’s format, all on one operations screenEverything Boxed
Staff, hire customers and contractor crews each needed to see only their own sitesA control system with scoped access, delivered in phases and owned outright by the clientHalo Traffic

Source: Revitt client work, 2025 to 2026.

How the work runs

  1. 1

    Free call

    Who will use the portal, what they do today and which systems hold the answers.

  2. 2

    Discovery

    A short, quoted phase that defines the first workflow, the data it needs and the systems it must connect to.

  3. 3

    First phase

    A fixed-scope release delivered to the plan, tested with real accounts and orders.

  4. 4

    Later phases

    Further workflows added in order of value, with the code, data and cloud account yours throughout.

Questions

Should we build a portal or buy one?

If a product already fits how you trade, we will say so and set it up. A build makes sense when contract pricing, approvals or connections to an old ERP are specific to you.

What does it connect to?

Usually your accounts package or ERP, your order system and your document store. We connect to what you run rather than replace it.

How is it priced?

Discovery is quoted first and ends in a fixed price for the first phase. Later phases are quoted as they are agreed, so you can stop after any one of them.

Who owns it?

You do: the code, the data and the cloud account. It is written so another team could take it on.

Can you show a portal you have built?

Our published work includes an operational ordering and invoicing system for a supplier with a large contract customer, and a control system with separate access for customers and contractors. We can show you the workflow and access controls relevant to your project.

Start with discovery

Book a free call and describe the workflow the portal must handle first. We quote a short discovery that ends in a fixed scope and price for the first phase.

Max RevittFounder and Director

Tell us about the job

These details help us assess the work and come back with a useful first step. You do not need a finished specification.

Prefer to talk? Book a free call.

Send your project details

We will reply within one business day.

Who will use the portal, what should they be able to do, and which systems must it connect to? Include any deadline.