Client portals
Half the calls your office takes are one question: where's it up to? A portal answers that question all day without anyone picking up, and it collects approvals and payments while it is at it.
Fig A · Status, approval and payment in the one place the customer already is: their phone
What it covers
Answers, approvals, paymentsHow it's built
Your domain, your lookThe portal runs on your domain, in your branding, so what the customer experiences is your business being organised, not a third-party app with your logo squeezed in. It reads from the same records as your day board and ledger (sheets 02.2 and 02.3), which is why it never needs updating by hand.
Each customer sees exactly their own jobs and documents, nothing else. Payments go through the gateway you choose, straight to you; we never sit in the money path. It works on any phone browser, because that is where your customers actually are.
What it replaces
The status callsThe status calls, the re-sent attachments, the "did you get my quote?" follow-ups, and the awkward chase for payment. The office stops being a switchboard and the customer stops wondering. Both sides get their afternoon back.
Asked every time
Common questionsWill our customers actually use it?
There is nothing to adopt: no app to install, no account to create, no password to forget. They tap a link in a message they were getting anyway. Take-up follows when the portal is the easiest way to the answer.
Whose payment gateway is it?
Yours. Stripe, Square, or whatever your bank provides; the portal hands the customer to your gateway and records the result. Funds settle to you on your gateway's terms. We never hold or route money.
Can builders use it for progress claims?
Yes. Staged claims, variation approvals and running documents suit the format well. The portal presents whatever your process is; it does not impose one.