// Service · Client portals

Client portal development that ends the email chase.

A secure place your customers log in to: files, forms, approvals, updates, invoices and messages in one thread instead of scattered across inboxes and shared drives. Built around the way you already deliver work, scoped and quoted before anything is built.

// Why bespoke

Most businesses do not need more software, they need one front door

Delivery usually falls apart in the gaps. A document sits in someone's inbox, an approval never arrives, an invoice gets queried three weeks late, and your team spends its week chasing rather than delivering. Generic project tools rarely help, because they are built for internal teams rather than for the people paying you. A client portal fixes the handover points. Customers see exactly where their job is, what you need from them and what they owe. You see what has been sent, opened, signed and paid. Everything lives against the record instead of a person's memory, so holidays and staff changes stop being a risk. The measurable return is usually admin time. Count the hours a week your team spends resending files, chasing signatures, answering where are we with this, and reconciling payments. For most firms that is a day a week across the business. A portal does not remove all of it, but it removes the repetitive part, and it does it without adding another per-seat subscription. There is a second, quieter benefit. A portal makes your delivery look organised at exactly the moment a client is deciding whether to use you again. Clients rarely leave because the work was poor. They leave because the experience around the work felt chaotic.

// What we build

What a client portal usually needs to do

01

Accounts, access and permissions

Secure logins, invited users, teams and role-based access so a client sees their work and nobody else's. Single sign-on and two-factor where the data warrants it.

02

Files, forms and approvals

Document requests, uploads, e-signature style approvals, structured onboarding forms and version history, all timestamped against the job.

03

Progress, invoices and messaging

Milestones and status your clients can read at a glance, invoices and card payments, plus a message thread that keeps the whole conversation in one place.

04

Notifications that do the chasing

Automatic reminders for outstanding documents, unsigned approvals and overdue invoices, on your schedule and in your tone, so nobody on your team has to send the awkward third email.

05

Reporting and internal views

An internal dashboard showing every client, every outstanding action and every stalled job, so account managers start the week knowing where the blockages are instead of digging through inboxes.

06

Integrations with the tools you keep

Xero, QuickBooks, Stripe, Google Workspace, Microsoft 365, your CRM and your website forms. The portal becomes the client-facing layer over systems you already trust rather than a replacement for all of them.

// Compare

Off-the-shelf portal vs bespoke client portal development

Plenty of SaaS products offer a client portal module. This is the comparison worth making before you commit either way.

Portal module in a SaaS toolBespoke client portal
Upfront costLow or bundledA project cost, quoted per build
Ongoing costPer seat or per client, per monthHosting plus optional care plan
BrandingTheir interface with your logoYour brand end to end
Workflow fitTheir idea of a projectYour stages, your approvals, your terms
Client experienceAnother login your clients half-rememberPart of your own website
Data and exportsWhat the vendor exposesYour database, exportable at any time
Best whenYour delivery is standard and low volumeDelivery is your differentiator
// How this connects

The portal and the website should be one system

A portal works best when it sits behind the same site that wins the work. An enquiry becomes a lead, a lead becomes a proposal, the proposal becomes a project the client can log into, and the invoice is paid in the same place. We build the public site and the private portal together, which is why most portal projects start as a bespoke web design or custom software conversation. It also keeps the security story simple. One codebase, one hosting arrangement, one set of access rules and one team to call when something needs changing, rather than a website agency and a software vendor pointing at each other.

// Queries we optimise for
client portal development UKbespoke client portalcustomer portal developmentsecure client login areacustom customer portal softwareclient dashboard development UK
// FAQ

Questions about client portal builds

How much does a client portal cost?+
We do not publish a price list, because the number depends entirely on what the portal has to do. After a scoping call you get one written proposal with a fixed price and a fixed timeline, and nothing is charged until you accept it.
How long does a portal take to build?+
A first working version is typically four to eight weeks. We deliberately keep release one small so real clients use it quickly, then extend it based on what they actually do with it.
Can it sit on our existing website?+
Yes. The portal can live on a subdomain or a /portal path on your current site, sharing your branding and login. If the existing site is holding you back, we will say so rather than build on sand.
Is client data secure?+
Row-level access controls, encrypted storage, audit trails and UK or EU hosting as standard. Every account only ever queries its own records, enforced at the database rather than in the interface.
Can it connect to the tools we already use?+
Usually. Stripe, Xero, QuickBooks, Google Workspace, Microsoft 365, calendars and most modern CRMs expose APIs, so the portal can read and write instead of forcing double entry.
Who owns the portal once it is built?+
You do. Full ownership of the code and the data, exportable at any time, no per-seat licence and no lock-in.
When is a client portal the wrong answer?+
When you have a handful of clients and a tidy shared drive, when the real problem is that your process is undefined rather than badly supported, or when a portal module inside a tool you already pay for would cover ninety percent of it. We would rather point you there than sell a build you do not need.
Will our clients actually use it?+
They use it when it saves them something. Portals fail when they add a login without removing an email. We design around the two or three moments a client genuinely cares about, usually approvals, documents and paying, and we send them straight into the right screen by link rather than expecting them to remember a URL.
Can clients pay through the portal?+
Yes. Card and direct debit through Stripe, with invoices raised from the job record and reconciled back to Xero or QuickBooks, so paying is one click rather than a bank transfer someone has to match later.
// Next step

Get a fixed quote for your build.

Five-minute brief, no phone tag, no vague hourly rates. If a package fits, we'll say so - if it doesn't, we'll tell you that too.