One private portal where every client sees their own documents, requests and updates.

A portal does not stop people emailing you. It gives the answer somewhere to live, so the same question does not need answering twice.

These are examples rather than a fixed set. Which sections a portal carries depends on the business, and most start with a focused few.

Illustrative interface · Sample data

Each customer only ever sees inside their own account.

Security and compliance requirements are scoped per project. Where a specific standard or certification is required, we confirm what applies and design the scope around it.

Illustrative interface · Sample data

Building fewer modules well is normal and usually better. A portal can grow later without being rebuilt.

What comes across depends on the records you hold today. We look at the real data early, so the scope reflects the work involved.

How much your customers use a portal depends on them, on your business and on how you introduce it. What design controls is the effort involved — and that is what we design for, starting with the least willing user.

The portal

Yours. It runs under your name and your domain, and it is not shared with anyone else.

The data

Yours. Your customers’ information belongs to your business.

The code

Handed over as agreed in scope, so you are not locked to us to make changes.

Where it runs

Your hosting account where you want that, so you keep the keys.

What happens after launch

Support and further work are a choice, not a condition of keeping it running.

The portal is yours outright — built for your business, owned by your business, running under your name. Branditify builds systems rather than renting them.

1. 01A conversationWe ask what your customers currently have to email or phone you for. That question usually defines the whole portal.A shared idea of whether a portal is even the right thing.
2. 02Shaping the scopeWhich modules you actually need, who signs in, what they each see, and what it has to connect to.A written scope with what is included and what is deliberately left out.
3. 03DesignThe client side is designed first, because it is the side that has to be obvious. Then the team side behind it.Screens you can react to before anything is built.
4. 04Build and connectThe portal is built, your systems are connected where they can be, and your existing customers are brought in.A working portal with your real accounts in it, still private.
5. 05A small first groupA few friendly customers get access before everybody does, so problems surface while they are small.Fixes based on real use rather than assumptions.
6. 06Open it upThe rest of your customers are invited, at whatever pace suits you, with your team ready behind it.A portal in normal use, and a plan for what comes next.

Each step moves at the pace of the scope and of information coming back from your side, so the timetable is agreed once the scope exists.

What is a client portal?

A client portal is a private, signed-in area where each of your customers can see and do the things they currently have to email or phone you about — their documents, the status of their work, requests, approvals, updates and, where relevant, invoices. Each customer sees only their own account.

Why would my business need one?

Because the same questions come back to your team repeatedly, and the answers live in one person’s inbox. A portal gives those answers a permanent place your customer can reach without asking, and gives your team one place to send and receive things instead of email threads.

What would my customers actually see?

A home screen for their account showing where things stand and anything waiting on them, plus a small number of sections such as documents, requests, uploads, approvals, updates and history. The exact set depends on your business — most portals start with four or five.

What would my team control?

Everything the customer sees. Your team publishes documents and updates, decides who on the customer’s side can see what, assigns incoming requests to a person, sets the state a customer can see, and keeps internal notes the customer cannot see.

Can different customers see different things?

Yes, and this is the default rather than an add-on. Access is by account first, so one customer can never see another customer’s information. Within an account, individual people can be given different access — an owner and a finance contact do not need the same thing.

How is a client portal different from a CRM?

A CRM is for your team: leads, deals and follow-ups, and your customer never signs in to it. A client portal is for your customer: their own account with what you have shared and what you need back. Businesses commonly keep the CRM and add a portal alongside it.

Can it connect to our existing CRM, ERP, payment or storage tools?

Usually yes, and how depends on the system. Some allow a live connection, some a scheduled copy, some work in one direction, and some keep their data in-house — in which case the portal holds it. We confirm what each existing tool can expose before defining the connection.

Can you work with our existing website?

Yes. A portal is normally a signed-in area on your own subdomain, or a section inside your current site if it can support it. Your public website does not have to be rebuilt for a portal to exist.

Can our existing client data be brought in?

Yes. Existing accounts, contacts and documents are gathered, de-duplicated, checked by you as a sample and then loaded before anybody is invited. How much work that is depends on how tidy the records are.

Does it work on mobile, and do we need an app?

It works on a phone browser and is designed for that first. No app is needed — customers open a link and sign in. It can be added to a phone’s home screen if you want it to feel like an app, and a real app remains a separate decision later.

Who owns the portal, the data and the code?

You do. The portal runs under your name and domain, your customers’ data belongs to your business, and code is handed over as agreed in scope. It is yours outright rather than licensed from us.

Can Branditify build only the modules we actually need?

Yes, and that is usually the right way to do it. A portal with four sections that people use beats twelve that they do not. Modules can be added later without rebuilding what already works.

Looking for a different system? These are the closest:

What is the project process for building a client portal?

A conversation about what your customers currently have to ask you for, then a written scope, then design of the client side first, then the build and connections, then a small pilot group of customers, then opening it to everyone. Timelines depend on scope and are agreed once the scope exists.

What happens if different clients need different access?

That is handled at three levels: which account a person belongs to, what role they have within that account, and whether an individual document or section is shared with them. Your team sets all three, and can change them at any time.

Will our customers find it complicated?

They should not have to learn anything. The first sign-in is an invitation email and one password screen, and it opens on a single screen showing where things stand. Email notifications continue for customers who never sign in, and your team can act on a customer’s behalf.

We already use email, WhatsApp and a shared drive. Why change?

You do not have to stop using them. A portal adds the thing those tools cannot do: a permanent record attached to a customer account, which the customer can reach themselves and which does not depend on one person still working with you.

Is a client portal the same as billing or invoicing software?

No. Some portals show invoices and payment status because customers ask for them, but they show what your accounting system already knows. Creating invoices, tax handling and collections belong in accounting software, not in the portal.

Is this a Branditify product, or is it built for us?

It is built for you. Branditify designs and builds the portal around your business, and your business owns it outright — one system that is yours, rather than a plan or a seat count.

How is security handled?

Access is account-based with individual sign-ins, so people see only what your team has shared with them, and access can be removed when someone leaves. Security and compliance requirements are scoped per project. Where a specific standard or certification is required, we confirm what applies and design the scope around it.

Which kinds of business do client portals suit?

Any business whose customers need documents, status, approvals or paperwork moving back and forth — suppliers, manufacturers, professional practices, service businesses and education among them. The modules change with the business; the idea stays the same.

Can we start small and add to it later?

Yes, and most businesses should. A portal built around the two or three things your customers ask for most can be extended once you can see how it is actually used.

What can we review before we start?

Our selected software work, our client projects and the interfaces we have published — enough to judge the systems thinking, the interface craft and the execution behind a Branditify build. From there your portal is scoped around your customer journey, the access each person needs, the tools you already run and the work your team has to manage.