Client portal software for small businesses in the UK

What does a client portal actually do for a small business?

A portal replaces the parts of your service that currently run on email threads, shared drives and "can you resend that?" messages. The common pieces are a login, an onboarding flow, document upload and storage, a message thread tied to the job, a progress view, and payment or approval steps.

The value is not the software. It is removing the chasing. If your team spends half its week answering status questions, re-sending documents and reminding clients to sign things, a portal turns that into a page the client can check themselves, with reminders that go out without anyone remembering to send them.

For MRM Group, a UK property development and investment company, we built an authenticated internal command centre for clients, deals and tasks, with client and deal workspaces, agreement-before-payment flows, document handling, task workflows, reminders and audit history, plus operational reporting with human approval at sensitive financial-promotion and AI decision points. You can read what was built in the MRM Group case study, or the plain-English explainer on what a client portal is.

Off-the-shelf portal software or a custom build?

Most small businesses should try an existing tool first. Subscription portals are cheap to start and immediate. The point where they stop working is when your process does not match theirs and you start inventing workarounds: a spreadsheet alongside the portal, a separate tool for payments, manual copying between systems, or a role the tool cannot represent.

If you are weighing this up more broadly, we have written it out in custom software vs SaaS and no-code vs a custom build.

How much does a custom client portal cost in the UK?

These are our bands. Larger custom projects are priced separately, and every build is scoped around what the business needs and already has.

Payment defaults to 50% upfront and 50% on launch for projects, the audit in full, and retainers monthly in advance. The signed scope controls. Running costs such as hosting, software and AI usage are paid directly to the providers from your own accounts, so you can see and control them. More detail sits on client portal pricing and audit pricing.

What pushes the price up

• More than one role. Admins, clients, staff and partners each need their own view and permissions.
• Money moving. Payments, invoices and agreement-before-payment flows need checking and audit history.
• Integrations with your CRM, accounting or scheduling tools.
• Migrating existing client data in, rather than starting clean.
• White-labelling, so each of your clients sees their own brand.
• AI features, which need approved source material and a human review step.

When a client portal is not the right choice

We turn work away on these grounds regularly, so it is worth saying plainly.

• An existing tool already fits. If a subscription portal does the job without workarounds, keep paying the subscription. A custom build only pays back when the workarounds are costing you hours every week.
• Your process is still changing week to week. Building a system around a process you are still inventing means paying twice. Settle the process on paper first.
• You need it next week. Portals take three weeks to three months from a signed scope. We will not promise a delivery date before a scope is signed.
• Clients will not log in. If your customers deal with you by phone and will never use a login, a portal moves the chasing rather than removing it. Automated follow-up may do more, which is covered in lead follow-up automation.
• The real problem is the CRM. Sometimes the portal is a symptom and the data mess is the cause. Start with CRM migration instead.

Cheaper first steps: connect the tools you already own with automation before building anything new. See automating business processes and, if you are already using Zapier, Zapier vs custom automation. Zapier counts each successful action step as a task, and at the plan limit new runs are held unless extra tasks are paid for (Zapier help centre), which is often the point where small businesses start looking at a build.

How we build a portal, step by step

1. Audit. We map how the business runs, the tools it uses and where work gets stuck. Available as a paid audit at £3,000 plus VAT with a written report in 10 working days, credited against the build when the deposit is paid within 14 days.
2. Design. A written scope covering systems, integrations, permissions and success measures. Nothing is built before this is agreed.
3. Build. Inside your own accounts, keeping what already works.
4. Test. Real cases, edge cases and failure paths, before anything touches a customer.
5. Launch. In stages, with the team trained and documentation handed over.
6. Improve. Review the numbers and agree the next changes, optionally on a monthly retainer.

Our advice on sequencing: start with the one journey that causes the most chasing, connect only what that journey needs, then add the rest once people are actually using it. The full method is on our approach page.

What goes wrong with portals, and how to avoid it

TMMB Academy, a TikTok Shop academy, came to us with a fragmented funnel and operating processes, rising software subscriptions and no single system. We built one portal with role-specific workspaces for admins, coaches, creators, sales, assistants and brands, covering onboarding, creator performance, subscriptions and payments, course modules, calls, messages, community resources, brand deals, deliverables and operational alerts. The implementation ran for more than 60 days. TMMB was able to take on greater capacity, improve scalability and retention, and reports generating six figures within roughly two to three months (client-reported, shared with permission). The detail is in the TMMB Academy case study.

Three failure patterns we see repeatedly:

• Permissions as an afterthought. Multi-role portals leak data when roles are bolted on late. Decide at design stage who sees what.
• Automation with no human in the loop. Keep a person on decisions about money, legal commitments, complaints and messages sent in your name. In Moffatt v Air Canada (2024), the airline was held liable for wrong fare information its chatbot gave a customer, and the argument that the chatbot was responsible for itself was rejected (American Bar Association summary).
• Slow responses outside the portal. Harvard Business Review's "The Short Life of Online Sales Leads" (2011) found firms contacting a web lead within an hour were nearly seven times as likely to qualify it as those waiting an hour longer, and more than 60 times as likely as those waiting 24 hours or more, across 2,241 US companies audited (HBR, 2011, US data). A portal is for existing clients; the enquiry side needs its own handling.

If you want AI inside the portal, we keep it limited to approved information, make it say when it does not know, hand over to a person, and tell people they are automated. Our own Agentryx platform works this way: AI turns a call summary into tasks and a draft follow-up email for a person to check, not to send unchecked.