---
title: "Customer portals"
url: "/services/customer-portals"
canonical_url: "https://revitt.co/services/customer-portals"
summary: "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."
---

# Customer portals

> 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.

## What it does for your business

- **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 we deliver

- **Trade ordering**: Repeat orders, contract pricing and the product list a logged-in customer is allowed to see.
- **Account and invoice view**: Balances, invoice history, statements and payment status pulled from your accounts package.
- **Document exchange**: Upload and download for contracts, certificates and delivery notes, tied to the right account.
- **Operational workflows**: Approval steps, exception queues and internal tools fed from the same data, so staff work from one place.

## Process

01. **Free call**: Who will use the portal, what they do today and which systems hold the answers.
02. **Discovery**: A short, quoted phase that defines the first workflow, the data it needs and the systems it must connect to.
03. **First phase**: A fixed-scope release delivered to the plan, tested with real accounts and orders.
04. **Later phases**: Further workflows added in order of value, with the code, data and cloud account yours throughout.

## FAQs

**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.

## Case studies

- https://revitt.co/case-studies/everything-boxed
- https://revitt.co/case-studies/halo-traffic

## Next step

- [Book a call](https://revitt.co/book.md)
- [Send a brief](https://revitt.co/contact.md)