Client portal
A client portal for web developers: what to show, and who will actually use it
Last checked
A small-business owner paying $150 a month for website care cannot see what they are paying for. Nothing breaks, so nothing happens in their inbox. That is the moment the retainer gets questioned. A client portal is the fix: a page, under your name, that shows the work.
Will clients log in?
Most will not, and that is fine. The portal is not there to be visited weekly. It exists for the day a client asks "what am I paying you for?" and you send a link instead of writing a defence from memory. Incidents and updates can still reach clients by email. The portal is the proof behind the email.
What a client should see
- Their site's uptime, as a figure and a history, not a graph they have to interpret.
- Updates you performed: what changed, when, and that a backup came first.
- SEO trend. One score and its direction, from a regular audit.
- Invoices: what is paid, what is due.
- A request form, so "can you change the opening hours?" arrives as a task on your board, not as a text.
Leave off anything that needs a glossary. If a client has to ask what a line means, it does not belong in the portal.
White-label, and what each Bluprent plan includes
The portal carries your logo and colors, not Bluprent's, on the plans that include white-labeling. Availability by plan:
| Plan | Client portal | Your logo and colors | Your own domain | Automated reports |
|---|---|---|---|---|
| Free | No | No | No | No |
| Solo | Yes | No | No | No |
| Studio | Yes | Yes | No | Yes |
| Concierge | Yes | Yes | Yes | Yes |
Prices and limits are on the pricing page. The portal reads the same record as everything else, so uptime from monitoring, audits and invoices appear without anyone copying them over. That is the practical point of keeping the client and the site in one record.