Their work, and only theirs
01Each customer sees their own jobs, their own history and their own documents. The boundary is enforced in the query, so there is no version of the page that leaks somebody else's.
Back home
What we build
Customer portal development
A login of their own, showing their work and nothing belonging to anybody else. It turns a reporting obligation into something you can sell against, and it stops the phone ringing for status updates.
You probably need this if
- Your team spends real hours answering where is my order
- Reports go out as email attachments that somebody assembles by hand
- Customers ask for a system you do not have, and it costs you the tender
- Every client wants their numbers cut a slightly different way
What customer portals usually includes
You decide what they see
02Field by field, not page by page. They can watch the work progress without ever seeing what it costs you.
Documents in one place
03Signed job sheets, certificates, photos and reports attached to the record they belong to, and downloadable without anyone digging through an inbox.
Reports that send themselves
04Daily or weekly summaries compiled per customer and sent on time, including on quiet days, so silence is never mistaken for a missing report.
Their own users
05Your client adds and removes their own people. You are not the help desk for somebody else's staff changes.
Branded as yours
06It looks like part of your company, because to your customer it is.
What changes
The status calls stop
The information people were phoning for is in front of them, updated as the work happens.
It becomes a reason to pick you
Turning up to a tender with a working client login is a different conversation from promising better communication.
Reporting stops being a job
Nobody assembles the weekly summary any more, and it goes out at the same time whether or not anybody is in.
Questions we get about this
Can different customers see different things?
Yes, and that is usually the point. Visibility is set per role and per field, so one client can see photos and costs while another sees only volumes and dates. The rules live in the system rather than in somebody's memory.
Can it connect to the systems we already run?
Normally yes. If your accounting package, ERP or scheduling tool has an API, a database or an export, the portal reads from the same records rather than becoming another place to keep them up to date.
Who owns the portal and the data in it?
You do. The code, the data and the accounts. We will host, monitor and maintain it for as long as you want us to, and hand the whole thing over the day you would rather we did not.
Also worth reading
Custom Operations Software
One screen your team works from, instead of eleven tabs and a shared spreadsheet nobody trusts.
Also worth reading
Systems and API Integration
You keep what already works. We build the layer that makes it agree.
Tell us how your version of this works.
Twenty minutes on the phone and you get a straight answer about whether software fixes it, including no.