From the day we accept the engagement, every milestone, every line item, every estimate change, every reply you send — they all live in a private portal that updates the moment we touch it. No status calls. No PDFs at the end of a phase. No surprises in the final invoice. Credibility is structural here, not promised.
The first time we lost a client’s trust, it wasn’t because the code shipped late. It was because the cost moved and we hadn’t shown them why. By the time we put the reason in front of them, it sounded like a defense. The trust never came back.
So we built the room first. Before we wrote a single feature of the marketing site, we built the portal — the surface where every change to scope, every estimate revision, every file you upload, every reply you send threads back into a live, audit-grade timeline. The agency-side admin and the client-side portal share one database; what we see is what you see, on the same heartbeat.
Transparency isn’t a value we picked. It’s a control we engineered.
The discipline behind the portal — and the only commitments we make to every client we take on, regardless of scope.
The portal updates the moment we touch it — milestones, files, comments, estimate changes, replies. The moment we save, your phone lights up. There is no Friday status call, because there is no Friday silence.
The headline price cannot move without a written reason — logged, surfaced to you alongside our name, and emailed to you with a clear before-and-after. By default, you see it the moment we write it.
When we reply from inside the portal, the email lands in your inbox like any other. When you hit reply, your message threads back into the same live conversation we’re reading. No new app to learn. No lost replies.
Every panel below is rendered exactly as it appears in the portal — minus your project name. The layout, the typography, the cyan accent: what you see here is what you sign into.
A single horizontal bar shows what’s been paid, what’s outstanding, and what’s remaining — at a glance. The Phase Board breaks the engagement into named line items, each with its own status and (when it’s billed) a Stripe link to pay or download the receipt.
Every adjustment to the headline price — up or down — opens a dialog that requires a written reason of at least twenty characters. The reason is logged immutably, surfaced in the portal alongside the operator’s name, and emailed to you with a before/after diff. There is no silent path.
Scope expanded to include an admin role and multi-tenant Stripe wiring; we'd rather price the new surface honestly than carry it as a hidden cost.
Pinned at the top of every project: a live timeline of milestones, files, decisions, questions, and replies. When something changes, the row fades in with a one-second cyan pulse and settles. The connection state is shown by the ‘Live’ pip in the header.
Thursday at ten works on my end…
Marked as in progress
Uploaded by client · 1.4 MB
Logged on the project record
When we reply from the operator console, the email lands in your inbox like any other. When you hit Reply, your response threads back into the portal automatically — via plus-addressed routing, with an In-Reply-To header fallback for gateways that strip the address. You never lose a reply.
Sending a quick check-in — the foundation phase is wrapped. Let me know when you're free for a fifteen-minute walk-through.
Thursday at ten works on my end. The portal makes it easy to keep up between calls — appreciated.
Five sections, around seventeen questions. Autosaves on every blur — you can leave the tab and come back without losing a field. When you submit, the form locks read-only. The version is captured so future intake updates don’t silently overwrite what you said.
Three toggles: email, web push, and estimate updates specifically. Each one is a sub-gate, not a kill switch — so even when push is off, the in-portal bell still updates. Web push is delivered to every device you install the PWA on, including iPhone home-screen installs.
The portal is the receipt. The reason column is the trust. The audit log is the contract. You don’t have to take our word for any of it.
Within twenty-four business hours of accepting the engagement, you’ll have a private portal URL, a password, and a discovery intake waiting for you. The first row in your activity feed will be the one that says “kickoff.”