Client portals

A custom client portal for your business.

We design and build secure client portals that give your customers one place for their requests, projects, documents and invoices — tailored to the way your business works, not a packaged product you bend to fit.

  • Built around your business
  • Secure and reliable
  • Ongoing support
Illustration
Custom functionalityBuilt for your needs
Secure and privateAccess checked on every request
Integrates with your toolsConnected to the systems you use
Scalable as you growStart small, extend later
Ongoing supportFrom the team that built it
Why a client portal

A better way to manage your customers.

A client portal gives your customers a simple, secure place to submit requests, follow progress, find their documents and talk to your team — instead of a long email thread and a call to whoever is in today.

  • Too many emails, and messages that get lost
  • Information spread across different tools and inboxes
  • Requests that are hard to track from start to finish
  • Customers chasing for updates they cannot see
  • Re-sending documents you have already sent
  • Manual admin that grows with every new customer

With a client portal, you can:

  • Let customers submit requests online, with a reference
  • Keep communication in one place, against their account
  • Give access to documents and updates at any hour
  • Let customers track progress and status themselves
  • Take the repetitive lookups off your team's desk
  • Give customers a clearer, more professional experience

A client portal keeps everything organised and gives your customers a better experience.

Key features

Everything you need, tailored to your business.

Every portal is scoped to what your customers need to do. These are the pieces most are built from — yours may need three of them, or all six.

Customer accounts

Secure sign-in for each customer, with password reset and multi-factor sign-in where the data justifies it.

Request management

Requests raised against an account, with a reference, an owner and a status they can see.

Project updates

Progress, milestones and next steps your customers can check without having to ask.

Document access

Contracts, reports and files, current version first, delivered through a permission check.

Invoices and payments

What is owed and what is paid — and online payment through your own provider, if you want it.

Integrations

Data from the systems you already run — accounts, CRM, stock — rather than typed in twice.

Depending on what your customers need, a portal can also include a personal dashboard, order history and reordering, different roles within a customer's company, and subscription renewals.

Use cases

Built for different businesses.

Service businesses

Manage customer requests, bookings and ongoing work in one place.

Agencies

Give clients access to their projects, files and updates.

SaaS and software

A secure account area for the customers of your product.

Internal portals

Controlled access to tools and information for staff or partners.

Straight answers

What a portal project includes.

Part of the project

  • Discovery: who signs in, what they may see, and what they may do
  • Interface design for the screens your customers will use unaided
  • Secure authentication, password reset and account management
  • Role-based access, enforced on the server for every request
  • The features agreed in your scope, built and tested
  • Testing with real customer scenarios before launch
  • Handover: source code, documentation and a support arrangement

Separate, and quoted separately

  • Integrations with your accounts, CRM or stock system — scoped on their own
  • Payment processing charges, which are between you and the processor
  • Migrating historic documents or records, before we have seen them
  • Ongoing customer support — the portal is the tool, your team still answers
  • Any claim that a portal is compliant with a particular standard
  • Native mobile apps in the app stores

If you want the portal to show live data from another system, plan the integration at the same time. Retro-fitting one is always more work than building it in.

Security and privacy

Built with privacy and access control in mind.

Everything behind the sign-in belongs to a customer of yours, so it is built to that standard.

Proper authentication

Hashed passwords, secure sessions and multi-factor sign-in where the data warrants it.

Permissions on every request

Checked on the server each time — never by hiding a link.

Protected customer data

Parameterised queries, validated input, CSRF protection and rate-limited sign-in.

Files served, not exposed

Documents delivered through a permission check, not a guessable URL.

An audit trail

Who signed in, what they opened and what they changed.

Backups and monitoring

Automatic backups, a restore tested before launch, and monitoring after it.

Our process

From idea to a client portal that works.

In stages, starting small, so your customers are using something useful early.

  1. 1. Discover

    How your business works, who signs in, and what the portal has to solve.

  2. 2. Plan

    The features, workflows, access levels and technical approach — and what waits for version two.

  3. 3. Design

    Screens your customers can use with no training, in your brand.

  4. 4. Develop and test

    Built, connected and tested as a customer would use it, awkward cases included.

  5. 5. Launch and support

    Customers invited in stages, then monitored, supported and improved with you.

Ongoing support

A long-term partner for your client portal.

A portal is the most visible software a business runs: when it stops working, your customers notice first. Monitoring, updates and a named contact are part of the arrangement we agree with you, not an upsell after the first problem.

  • Ongoing support and maintenance
  • Security updates and monitoring
  • Faults in what we built, fixed
  • Help with new requirements, quoted first
  • Backup and restore checks
  • A named person who knows your portal
Common questions

Client portal questions

The questions businesses ask before commissioning a portal. If yours is not here, ask us directly.

What can a client portal include?

Whatever your customers need to do without having to contact you. Most portals combine a few of these: secure accounts, requests with a reference and a status, documents and files, project updates, invoices and online payment, order history, and data from systems you already run.

We help you choose the two or three that would take the most work off your desk, and build those first.

How long does it take to build a client portal?

It depends on the scope, so we give you a timeline with the quote after discovery rather than a figure on a web page. What moves it most is the number of distinct things a customer can do, and whether the portal reads live data from other systems.

A small first version reaches your customers sooner — and it is the version that tells you what to build next.

Can you integrate the portal with our existing systems?

If the system has an API or a reliable export, usually yes. This is worth deciding early: a portal that reads live data is a different piece of work from one where somebody uploads a file each month, and the second is much harder to upgrade into the first. See API integrations.

Will our customers be able to manage their own account?

As far as you want them to. Updating their details and resetting a password are the usual starting point; where a customer is a company with several people, roles decide who in that company sees and does what.

What a customer may change themselves, and what still goes through your team, is agreed during discovery.

Do you provide ongoing support?

Yes. Monitoring, security and dependency updates, fixes to what we built and a named contact are agreed with you as a support arrangement. New features are quoted before any work starts.

How much does a client portal cost?

It depends on what your customers need to do in it, and we quote it after discovery rather than from a price list. What moves the figure most is the number of distinct things a customer can do, and whether the portal has to read live data from systems you already run.

A first version that does two or three things well is considerably cheaper than one that does everything.

Can our customers pay through it?

Yes, with a payment provider you hold the account with. The portal shows what is owed and takes the payment; the money goes to you directly and the card details never touch your systems or ours.

What about GDPR?

A portal usually holds personal data, so how long records are kept, who may see them, and what happens when someone asks for their data are questions to settle during discovery. We build what you decide — access control, audit trails, deletion — but we are not lawyers and do not certify anybody's compliance.

Ready to build?

Let's create a client portal for your business.

  • No obligation
  • Talk to a real person
  • Practical advice
Chat with us