Platform
Your client, informed.
The client portal is the front door for the people you serve. Your client sees what was cleaned, when, by whom, with the quality-control photos attached — per site, live. They stop calling to ask, and the monthly “what did we actually do?” meeting gets shorter because the answer is already on screen.
Client portal
Why clients stay
The proof, live
What was done, when, by whom, with the evidence attached. The client does not have to take your word for it.
The invoice, matched
The bill lands with the proof already accepted, so the correction cycle shortens.
The report, self-serve
Completion rates and response times per building, generated from the work that was done. The monthly review starts from a document both sides trust.
What the client sees
Delivered services
Every completed visit, per site, with the task, the time and the worker.
Quality evidence
The checklists, the time-stamped photos and the sign-offs, attached to the visit.
The budget, visible
Service consumption against the agreed budget, so the client is never surprised.
The report
Completion, response times and inspection scores, dated as the work happened.
From “trust me” to “here is the record.”
The client portal turns the relationship from assertion to evidence. When the client can see the work, the proof and the numbers themselves, the conversation changes — from “did you do it?” to “let’s look at the report.”
FAQ
Questions we get asked
What can the client see?
The visits that were delivered, with the task, the time and the worker; the quality evidence attached to each one — checklist, photos, sign-off; service consumption against the agreed budget; and the reporting, dated as the work happened. It is the record of what was done, not a summary of it.
Is the portal per-site or per-portfolio?
A client sees their own sites — whether that is one building or a portfolio of them. How their access is divided up is a question of how the contract is set up, and it is one of the things settled when the portal is configured rather than assumed.
Can the client add requests?
The portal shows what was delivered and the proof behind it; it is not a request queue. If your contracts need the client logging reactive jobs themselves, that is worth raising on the demo — it is a scope question, and better settled before you commit to it than discovered afterwards.
How is access controlled?
Access is per user and per role: a client sees their own sites and nothing that belongs to another customer. The same role-based access that governs your own team governs theirs — see security and data for the wider picture.
Goes well with
Give your client the record.
Thirty minutes, live product, no slides. Bring the client question you answer most often and we will show you where the answer already is.