We build bespoke client portals in fourteen days at a fixed price: a secure place where your clients check status, exchange documents and complete forms, and a dashboard where your team sees what is outstanding. A portal earns its place by being easier for the client than emailing you. That is the whole design brief, and it is where most portals fail.
What a client portal costs
| Route | Typical cost | Fits when |
|---|---|---|
| Off-the-shelf portal software | A monthly fee, often per user or client | Clients mainly download documents |
| Portal or admin system, UK agency | £8,000 to £25,000 | Your own process, status and roles |
| Integrated multi-team build | £15,000 to £30,000+ | Connected to CRM, finance or case management |
We are not one of those rows. We build one fixed scope in fourteen days for £999 or £1,999, with a full refund any time before we start. A portal with documents, status and forms fits the Starter App. Several client types, approval chains or complex rules usually need the Advanced App.
What a portal is actually for
Not everything. Portals work for the things email handles badly.
| Task | Portal | |
|---|---|---|
| A quick question | Better | Worse |
| Finding a document from last year | Awful | Better |
| Uploading something sensitive | Risky | Better |
| Checking status without asking | Impossible | Better |
| Signing something | Awkward | Better |
| Proving who saw what and when | Impossible | Better |
Keep email for conversation. Move the rest.
What we build
- Secure document exchangeEncrypted, access-controlled, revocable, audit-trailed.
- Status visibilityThe single feature that stops the phone ringing.
- Onboarding and formsCollected once, in a guided flow, rather than over six emails.
- Approvals and signatures
- Notifications when something changesSo clients log in because there is a reason to, not to check.
- An internal view for your teamWho has done what, what is outstanding, what is overdue.
Every build also includes user accounts, testing on real devices, store submission, accounts in your name and 30 days of support. The full list is on what's included, and how we handle data is on security.
What's not included
Who this suits, and who it doesn't
It suits accountants, solicitors, agencies, consultancies, schools and service firms whose clients keep asking "where are we up to?" and keep emailing attachments. Too many phone calls is usually the trigger.
It does not suit a firm whose clients only need to download the odd document. A shared folder or off-the-shelf portal does that for less.
Why portals fail
How the fourteen days work
- Day 1
Kick-off and scope
We go through your goals, your users, and the one job the app has to do. Everything that is not that job goes on a version-two list.
- Days 2 to 3
Design
Screens, flows, and the look of the thing. You review and revise until you sign off. Nothing gets coded until you have.
- Days 4 to 10
Build
Front end, backend, accounts, notifications, admin dashboard. You see working builds as they land rather than a reveal at the end.
- Days 11 to 12
Test and fix
Real devices, real data, edge cases. This is where most of the unglamorous work happens.
- Days 13 to 14
Submit and launch
Store listings, screenshots, privacy details, and submission to the App Store and Play Store. Then 30 days of support while your first users arrive.
The full process is on how we work. More on portals for professional services firms.
Common questions
How much does a bespoke client portal cost in the UK?
Published UK pricing for portal and admin systems runs from about £8,000 to £25,000, with integrated multi-team builds at £15,000 to £30,000 and above. We build one fixed scope in fourteen days for £999 or £1,999.
Bespoke portal or off-the-shelf portal software?
Off-the-shelf if your clients only need to download documents and the per-user fees stay small. Bespoke when the portal has to show your own process, status and data, or when it needs to connect to the systems you already run.
Why do most client portals fail?
Because they are built for the firm rather than the client. If the portal is slower than sending an email, clients will send an email. It has to be genuinely easier for them, not just tidier for you.
Is a portal more secure than email?
Considerably, if built properly. Email attachments sit in inboxes indefinitely, get forwarded, and cannot be revoked. A portal gives you access control, an audit trail, and the ability to withdraw access.
Do clients actually use them?
They use them for the things email is genuinely bad at: finding a document from eight months ago, checking status without asking, and uploading files securely. Keep email for conversation.
Who owns the portal and the client data?
You do. The code, the database and the accounts are in your name, and the client data sits in a database in your name, not in a portal vendor's system.