How to choose client portal software

Every vendor will tell you clients cannot see each other's data. The question that separates them is where that rule lives. If isolation is enforced in the interface — by hiding links and filtering lists — then the rule is only as good as the last screen someone built. If it is enforced in the data layer, the database itself refuses to return another client's row no matter what the request asks for.

A concrete way to ask it: what happens if a signed-in customer edits the record ID in the URL to one belonging to another customer? You want an answer about the database, not about the menu.

Branding runs on a spectrum, and vendors use the phrase white label for all of it. At the shallow end you upload a logo and it appears in the corner of the vendor's interface. At the deep end the workspace carries your client's colors and logo at its own subdomain, and the vendor's name appears nowhere.

Which end you need depends on whether the portal is yours or your client's. An agency handing a portal to a customer usually needs the deep end. A contractor giving homeowners somewhere to watch their job usually does not, and paying for it is waste.

Portals are where disputes get settled — what was approved, when the scope changed, who said the equipment was collected. That only works if the record keeps its history.

Ask whether an edit overwrites the previous value or adds an entry alongside it, and whether an administrator can quietly remove one. Software that overwrites cannot support an insurance claim or a billing dispute, and you will not discover that until the day you need it. An append-only audit log is the property to ask for by name.

Per-seat pricing is the most common model and the easiest to misjudge. The published rate is usually pitched at office staff, but the people who make a portal worth having — technicians, drivers, crew — are the ones you add last and in bulk.

Count every person who will need a login, including the ones you would add in year two, then re-run the comparison. Check whether your customers consume seats too: a portal that charges per client login behaves very differently at fifty clients than at five.

A standalone portal is a second place to type things. Jobs get entered in your operations system and re-entered for the customer to see, and the two drift — at which point the portal is worse than nothing, because your customer is reading a stale version with your name on it.

Ask whether the portal reads from the same records the rest of the business works in, or from a copy. If it is a copy, ask what keeps them in sync and what happens when that breaks.

Vercid answers the checklist this way: isolation is enforced in the database with row-level security rather than in the interface; each client workspace renders fully in its own brand at its own subdomain; every change is written to an append-only audit log; seats are priced in three role-weighted classes so deskless crew are affordable to include; and the portal reads the same live records as dispatch and inventory, because it is not a separate system.

For background, see what a client portal is and how multi-tenant software keeps clients apart. For what an engagement costs, see how Vercid is priced.