WebKing / Capability 08 / Client Portal Development
If your team spends part of every day answering "where are we on this", that's a portal-shaped problem. We build the branded place your clients log in to see status, files, invoices and history, so the update is already there when they wonder.
Your brand, your domain, real logins, real permissions. Built on React and TypeScript with a PostgreSQL back end, so the data is yours and the access rules are enforced on the server, not hidden in the interface.
FEWER
Status emails your team has to write by hand
1
Login, on your own domain, carrying your brand
ANYTIME
Your client can check at 11pm without calling anybody
How this work gets scored
WebKing has worked with Houston businesses for 27 years. The scores that decide whether this work pays off still come from outside: these are the rules that grade it, what each one requires, and where each one is published.
WCAG 2.2
The accessibility standard plaintiffs and courts cite in ADA website lawsuits. Among its rules, body text needs a 4.5:1 contrast ratio against its background, and anything a finger taps needs at least 24 by 24 pixels of room.
The W3C standardCore Web Vitals
Google's speed standard, read from real visits over the previous 28 days rather than a lab test. A page passes when at least 75% of visits see the main content within 2.5 seconds, get a response to a tap within 200 milliseconds, and keep layout shift at 0.1 or less.
Google's thresholdsWhat you actually get
01
That email isn't impatience, it's a visibility gap. When the client can see the current status themselves, they have less reason to ask, and your team spends less time writing the same three-line reply.
02
Drawings, permits, photos, signed change orders. In a thread they're findable only by whoever was on it. In a portal they're attached to the job, so the person who joined last month can find them too.
03
A client comparing you to a bigger competitor is looking for a reason to feel safe. A real portal on your own domain answers that before anybody says a word about it.
04
When what's owed is visible next to the work it paid for, the conversation about money is less of a chase. It's just there, alongside the thing it bought.
05
Client A does not see client B. A subcontractor sees only their scope. Your own team sees everything. The access rules are enforced on the server, not hidden in the interface.
How we work
We look at the questions your clients email today. Those questions are the screens. A portal built from what we imagine they want is a portal nobody opens.
Which roles exist, what each one can see and do, and what it costs. The phases are laid out in order.
We ship authentication and the single most-asked-for view early, on a real URL. You put one friendly client on it and listen.
Documents, invoices, messaging, history. Releases to a staging site so you steer it while it is cheap to steer.
Access rules tested per role, a check that one client cannot reach another by editing a URL, and a review of what the server actually returns.
Production deploy on your domain, a short guide your clients can follow, and the finished code handed over to you once the engagement is paid in full.
Common questions
Every answer ends with how to take the next step. Tap any question, get the answer + a way to start.
They use it when it answers the thing they were going to email about, and when logging in is easy. That is why we build the most-asked-for screen first and test it with a real client before building the rest. If the answer is no for your business, we will tell you during scoping instead of taking the work. Free 30-minute scoping call at (832) 830-6474, Houston, Texas.
Ready when you are
No slides. No pitch deck. We pull your account, your competitors, and your traffic, and tell you exactly what is leaking money and what to do about it.
Free audit
We read your real client portals numbers and come back with what is leaking and what to fix first. No slides, no pitch deck.
