Client Portal: Build or Buy?

Clients now expect to find things for themselves: where their project stands, their documents, their invoices. A client portal gives them that, and it saves your team many emails. The question is whether to rent a portal or build one. This article gives you a clear way to decide, with the limits of each option.

What is a client portal?

A client portal is a private space on the web where your clients log in. Inside, each client sees only their own information. Most portals do some of these things:

• Show progress. The status of an order, a project or a request.
• Hold documents. Contracts, reports, quotes and invoices in one place.
• Receive things from the client. Files, forms, approvals or a new request.
• Let clients manage their account. Contact details, users and preferences.

A good portal has two effects. Your clients get answers at any hour, without waiting for you. Your team stops answering the same questions by email.

What does ready-made portal software do well?

Ready-made portal software is a product you rent, usually for a monthly fee. For many businesses, it is the right start.

• It is fast. You can open a portal in days, sometimes in hours.
• It costs little at the start. There is no build cost, only a subscription.
• The basics are included. Logins, file sharing, messages and often payments.
• Someone else maintains it. The vendor (the company that sells the software) handles updates and security.

If your needs are standard and a ready-made product covers them with only small compromises, buy. A custom portal has to earn its place.

Where does ready-made portal software stop?

The limits appear when your business grows, or when the way you work is not standard.

• Your brand. You can usually add a logo and a colour. But the layout, the wording and sometimes the web address stay those of the vendor. Clients feel they have left your company.
• Your process. The software decides the steps. If your work has its own stages, approvals or rules, you have to bend your process to fit the tool.
• A fee per user. Many products charge per team member, per client or per portal. The cost goes up each time your business grows.
• Your data in someone else's product. Client data lives in a system you do not control. Check how you can export it, and what happens if the price changes or the product closes.
• Connections to your other tools. If the portal does not share data with your other software, your team copies information by hand.

None of these limits is a reason to build on its own. But when two or three of them cost you time or clients, it is worth doing the maths.

When does building your own portal pay off?

There are three clear cases.

• The portal is part of what you sell. Clients use it every week and judge your service by it. A portal that looks and works like your business becomes a reason to stay with you.
• Your process is your edge. If clients choose you for the way you work, the portal should follow that way, step by step.
• The fees no longer make sense. With many clients or many users, the subscription over a few years can become higher than the cost to build and maintain your own portal.

Your clients never see your internal tools. They see the portal. For them, the portal is your company.

Building also has real costs, and you should know them. There is a cost at the start. Design and build take weeks. After launch, the portal must be updated, monitored and kept secure, like any software. In return, you own the code, the accounts and the data, and there is no licence fee per user.

What is the middle path?

Build or buy is not always a choice between two extremes. Your team may be happy with its CRM (the tool that tracks your clients), its accounting software and its project tool. The only problem is that clients cannot see inside.

In that case, build only the part the client sees. A custom portal reads the data from the tools you already use, through an API (a way for two programs to share data) or an export. Clients log in to a space that carries your brand. Your team keeps working as before.

• A smaller project. You do not replace any system, you add one layer on top.
• Less risk. Nothing changes for your team on the first day.
• No double entry. The portal shows the data that already exists, so nobody types it twice.

This is often the best first step. We describe the same idea for other tools in custom business tool or off-the-shelf software. And if your client data still lives in a spreadsheet, read when a spreadsheet stops being enough first.

Which questions should you ask before choosing?

• What do clients ask for most? List the questions that arrive by email and phone. The portal should answer those first.
• How many people will use it in two years? Count clients and team members, then work out the subscription at that size.
• Does our process fit the product? Try your real steps in a free trial, not the demo example.
• Can we get our data out? Ask for a full export in a format you can use.
• Which tools must it connect to? Check each one before you sign.
• Who owns what? The code, the accounts and the data should have a clear owner.
• What does it cost to keep running? Ask for the cost per year, for both options.

The bottom line

Buy a ready-made portal when your needs are standard and the number of users is small. Build your own when the portal is part of your service, when your process is specific, or when fees per user grow faster than your revenue. And look at the middle path first: a portal with your brand, on top of the tools you keep.

If you want an honest view on your own case, see how we design and build customer portals and other custom business tools. We will tell you when a ready-made product is enough.