What Is a Client Portal, & What Does One Cost?
Client portals explained: what they do, when a business needs one, real UK build costs and timelines, and buy-vs-build guidance from a team that ships them.
Stop emailing PDFs and status updates by hand: a client portal gives each customer (or partner) a logged-in place for their documents, jobs, invoices, messages or project progress. In the UK, a focused custom portal typically costs around £20,000-£50,000; deeper multi-role portals with payments and document workflows commonly land £50,000-£120,000+; thin configurations on existing SaaS tools can sit far lower when your process fits the template. Those are market ranges across UK product shops - not a Code23 quote. After Blueprint we set a fixed band for your scope, fixed change scopes priced before work starts, with agentic delivery holding comparable implementation at roughly half a traditional bench cost.
What a client portal is (definition block) and the problems it solves
What is a client portal?
A client portal is a secure, account-based website (or app) where each client sees their own information and actions - files, orders, bookings, tickets, statements - instead of chasing updates over email or shared drives.
It solves three recurring pains:
- Inbox archaeology. “Can you resend the latest proposal?” becomes a self-serve download.
- Status theatre. Clients stop phoning for “where are we?” because the job timeline is visible.
- Handoff risk. Documents, approvals and payments live in one place with an audit trail, not in someone’s Sent folder.
Portals sit next to SaaS products in shape - auth, roles, admin - but the commercial job is usually serving your existing clients, not acquiring strangers. Cost context for the wider product family: SaaS development cost UK. Hub: SaaS platforms.
What should a client portal include?
A serious portal should include reliable login, role-aware views, the documents or records clients actually need, clear status, and an admin path so your team can help without a developer - messaging and payments only when they remove a real email or invoice loop.
Off-the-shelf vs custom: when SaaS portals stop fitting
Can I build a client portal without custom development?
Yes - many teams start on HubSpot, SharePoint, clienteling tools, or vertical SaaS portals when their workflow matches the product. Custom development becomes rational when permissions, branding, document rules or integrations refuse to fit without brittle workarounds.
Stay on SaaS when:
- One or two roles, standard file sharing, light branding is enough
- Your process matches the vendor’s happy path
- You will accept their data model and export limits
Go custom when:
- Clients, staff and partners need different objects and permissions
- Documents have retention, watermarking or approval rules the SaaS cannot express
- Payments, job systems or CRMs must sync both ways without Zapier spaghetti
- White-label or multi-brand experiences matter commercially
Buy-vs-build is not ideology. It is whether the template fights your margin. Timeline siblings for lean custom cuts: MVP build time. Mobile-heavy variants sit nearer app development cost UK.
What a custom portal costs in the UK
How much does it cost to build a client portal?
| Shape | Typical UK market range | What you are usually buying |
|---|---|---|
| Configured SaaS / low-code | Often £2,000-£15,000 setup + licence | Template portal, light branding, limited logic |
| Focused custom portal | £20,000-£50,000 | Auth, roles, core records/docs, thin admin |
| Payments + workflows | £50,000-£120,000 | Invoicing or checkout, approvals, richer audit |
| Multi-org / deep integration | £120,000+ | Complex permissions, many systems of record |
Those figures are UK market orientation. Hosting, licences and care sit on top. Our extras rate on scoped work is transparent fixed change bands; ongoing ops can sit on Support & Growth when you want eyes on uptime after launch.
Timeline orientation: a focused custom portal with ready owners often lands in a similar band to lean product MVPs - weeks to a few months depending on integrations - detail in MVP build time. Agent-assisted Build compresses scaffolding and CRUD; permission design and document policy still need human judgement.
The features that matter: auth, documents, payments, messaging, admin
Five surfaces decide whether the portal reduces work or creates a second inbox.
Auth. Magic links for consumers; SSO and invites for B2B. Password reset and session hygiene are boring and non-negotiable.
Documents. Versioning, permissions, preview, and retention beat a dump of PDFs. If legal needs an audit of who downloaded what, say so in Map.
Payments. Invoices, card capture, or both. Portal payments fail when finance and product disagree on refund rules.
Messaging. Threaded messages with attachments help; a chat toy that nobody monitors hurts. Prefer routes your team already staffs.
Admin. Impersonation-with-audit, password resets, document overrides, and job status edits. Without admin, every exception becomes a developer ticket.
Skip vanity dashboards until the five above work on mobile. Clients open portals on phones between meetings.
A portal build in practice
In our experience a typical engagement looks like this: Map the client jobs (download, approve, pay, ask), Blueprint auth and the minimum object model, Build the logged-in surfaces under senior-directed agents, Harden permissions and file handling, then Launch with a small pilot cohort before rolling every account. Across 350+ projects since 2005 we have seen portals fail when they mirror the internal CRM screen-for-screen - clients need their language and their next action, not your ops chrome.
Worked pattern (composite from portal-shaped builds, not a named client case study): a services firm drowning in “please resend” emails ships document access + invoice status first; messaging lands second; fancy analytics wait until the inbox volume drops. That sequence beats a six-month portal that launches with empty widgets.
When email is still the client portal, the next conversation belongs under SaaS platforms.
