Stop Answering The Same Four Questions.
Where is it, what did I approve, can I have that document again, what do I owe. Four questions that consume a working day a week in most offices, all answerable by a portal the customer can reach themselves — with the approval trail living somewhere both sides can see, which is worth more than the time it saves.
The Symptoms, Before the Diagnosis.
Status calls are a job
Someone in the office spends a meaningful share of the week telling customers what is happening, reading it off a system the customer could have read themselves.
Approvals are disputable
Scope was agreed on a call or in a text, and when the invoice lands the two sides remember it differently. Without a shared record, the argument is about memory.
Documents get re-sent forever
Certificates, reports, warranties and invoices are re-emailed on request, sometimes in the wrong version, and there is no single place either side can go to find the current one.
Enterprise customers expect it
Larger clients increasingly want a link rather than a phone call, and a vendor who cannot provide one starts to feel like the harder option on the bid list.
Client & Customer Portals, in Scope.
Scope is set against your operation, not against this list — but this is the shape of a build in this line.
Job status, self-serve
What is scheduled, what is in progress, what is complete — in the customer's language rather than your internal job states, drawn live from the same records your office works from.
Approvals with a record
Quotes, scope changes and sign-offs approved in the portal, timestamped and attributed, so what was agreed is a document rather than a recollection.
Documents in one place
Reports, certificates, photos and invoices tied to the job they belong to, current version visible, available whenever the customer looks rather than whenever someone re-sends them.
Access control that survives scrutiny
Each customer sees their own records and nothing else, with permissions enforced at the data layer rather than trusted to the screen — the failure mode here is the one customers do not forgive.
A portal is only useful if it is fed automatically. If someone in the office has to update it, it becomes a second system to keep current and it goes stale within a month — so we build it as a view onto the operational records that already move, not as a place anyone has to maintain.
The other half of the work is deciding what customers should not see. Internal notes, margin, crew scheduling and supplier pricing all live next to the data a portal exposes, and drawing that line explicitly is part of scope rather than something to discover after launch.
What It Looks Like When It Works.
The status calls drop because the answer is a link. The approval trail is shared rather than contested. And the customers who expect a portal stop treating you as the less professional option on the shortlist.
- We do not build a portal onto an operation that has no reliable internal record yet. If job status is not trustworthy internally, publishing it to customers makes the problem public.
- We do not expose internal data by default. What customers can see is decided explicitly, written into scope and enforced at the data layer.
- We do not build a customer community or a marketplace. This is a portal onto your own work for your own customers.
Five systems → one
Kilt Contracting · live in production
A general contractor across Edmonton and Calgary moved onto one operations platform where approvals are captured in writing and documents are attached to the job that produced them — the internal record a customer-facing portal has to be built on. Client-reported.
Client & Customer Portals, Answered.
Do Our Customers Have to Log In?
Usually, but not always. Repeat commercial customers get accounts; for one-off residential work a secure per-job link is often better than asking someone to create a password for a driveway replacement. Which model fits is a scope decision, and it can be both.
How Do We Keep Internal Information Out of It?
By deciding what is visible before it is built, and enforcing it in the data layer rather than by hiding fields on a screen. Margin, internal notes and supplier pricing sit alongside the data a portal exposes, so the boundary gets written into scope explicitly.
Will It Stay Up to Date?
Only if nobody has to update it, which is why we build it as a view onto records the operation already maintains. A portal that needs its own data entry is a portal that will be wrong by next month.
Start with the operation, not the software
Book a 30-Minute Call.
30 minutes. We map how work moves through your business today, show you where it leaks, and hand you a costed plan — whether you build it with us or not.
Edmonton, Alberta · No commitment · 587-937-6948
Where To Go Next.
Up a level
Operational Software
Jobs, customers, approvals and documents in one system you own.
More In This Series
Legacy System Modernization
Retiring the Access database and the spreadsheet stack, without stopping work.
Internal Tools & Admin Portals
The one internal screen that replaces a spreadsheet and three logins.
Custom Web Applications
Multi-user operational web apps on a current stack, integrated and owned by you.
Mobile Apps for Field Crews
Capture on site, work without signal, sync when it comes back.
Job Costing & Margin Tracking
Know which jobs make money while they are still running.
Also Worth A Look