Skip to the page

Get in touch

Inside the client portal.

One private place for your website, after launch. Sign in and you see how your site did this month, what we finished and what it did, and where each of your requests stands. What you won’t find is a progress bar, or a number dressed up to look better than it is.

Journal · 7 minute read · Updated 17 November 2026

The short answer

Our client portal is a private site each client signs in to. It answers the three questions owners ask after launch: is my site working, what is the studio doing, and how do I ask for something? So it shows the site’s visitors, where they came from and how fast it loads; every finished job, with a line on what it did; and each request, with where it stands.

Every screen on this page belongs to Brightwater Plumbing & Heating, our sample client. The business is made up and so are its numbers, which lets us show every screen without showing a real client’s.

A portal home page greeting Dana, with a tune-up page waiting for approval, and a photo of the business’s van behind cards for visitors, inquiries and four Lighthouse scores.
Home, as the owner sees it.

What do I see when I sign in?

A greeting, one line on what’s ready for you, and your own site’s photo with the month on it. Anything ready for you to look at sits in the middle as one card: Approve, or Ask for changes. Under it, three quiet buttons start a request, open your messages or open your site.

On the photo: visitors and inquiries for the last 30 days, each with its change, and the four Lighthouse scores (Google’s free test of a page) named in plain words: Speed, Easy for everyone, Built well, Ready for Google. You shouldn’t have to read a paragraph to know how the month went.

Home, from the greeting down to Done for you.

Under the photo is Done for you: the last three things we finished, each with its picture and what it did. Once a site is live, this takes the place of a progress bar, because a full bar tells you nothing and finished work tells you plenty.

A card titled Done for you with three finished jobs, each a page screenshot above a line and a date: a one-line result for two of them, the job’s name for the newest.
Done for you: the last three finished jobs.

On a phone, the same portal puts its places in a bar at the bottom, within reach of your thumb, with a + for a new request.

Two phone screens side by side: the portal’s home with its greeting and approval card, and the Site tab with inquiries, visitors, a chart and who is on the site now.
Home and the Site tab on a phone.

Is my site working?

The Site tab answers that in one screen. First visitors and inquiries for 30 days, then the month as one chart: the line is visitors, the small marks along the bottom are inquiries, and each ring on the line is a day we finished something. Below it: who’s on the site now (each with a made-up name for the day), how people found you, which AI tools read your pages, where visitors are, the scores and what we did this month.

The Site tab: inquiries and visitors with their changes, a 30-day chart, a list of people on the site now, sources led by Google, and reads by ChatGPT, Claude and Perplexity.
The top of the Site tab.

Small numbers swing, so the portal doesn’t dress them up. Say inquiries went from 2 to 4: that’s up 100%, which is true and tells you nothing. So when the count before was under 20, a change shows as a plain difference (“+24”). That’s why inquiries above read +24 and visitors read 51%. For more on what those AI readers are, see which AI crawlers visit your website.

Extra services each get a card on Home and a block here, seen only by a client who has that service: no greyed-out upsells. A client with a chat assistant on their site would see the block below: chats, those that ended in an inquiry, and visitors who reached out before and after it went live. Brightwater has every service so we can show them all; a real client sees only the ones they have.

A block titled Chats on your site with counts for chats, inquiries and after-hours chats, a bar chart split into form and chat inquiries with the day the assistant went live, and the share of visitors who reached out before and since.
The site assistant’s block on the Site tab.

How do I ask for something?

Press New request, on any page. Say what you need and pick when: no rush, a day, or urgent. Each request gets its own page with what you asked, a status, and a thread for the back and forth. Behind the small “i” it says: “We get an email when you send a request, and we write back within a business day.”

Opening a request from the list.

A request moves through five plain states: New, In progress, Waiting on you, Done and Cancelled. Each move adds a line to its thread, so the request carries its own history. You can edit or withdraw it until we start, and if one is waiting on you, your reply moves it back to In progress by itself.

A request titled Add our new financing option, marked In progress, with the owner’s question, three replies and a reply box.
One request: what was asked, its status and the thread.

Everything else goes in Messages: one conversation with the whole team, with photos and files if you like. When either side writes, the other gets an email, so nobody has to keep checking.

A message thread with three notes from the studio about a busy week, a moved phone number and a page ready to approve, above a box that reads Message Olive Branch.
Messages with the studio.

Under Your brand there’s a board, an open canvas for notes, pictures, links and quick drawings that both sides add to, and your files beside it. It beats a photo buried in a text from last month.

A board with screenshots of the business’s web pages, a photo of its van, a link card and three colored notes about the phone number, colors and photos still needed.
The board under Your brand.

Every finished job says what it did

Updates is the whole project on one page. First, anything ready for you to look at, with a picture: Approve finishes it, and Ask for changes opens a request with its own thread. Then what’s up next, then everything done.

The Updates page: a tune-up page ready for review with Approve and Ask for changes buttons, two jobs up next, and five finished jobs with dates, four of them with a one-line result.
Updates: ready to look at, up next and done.

Each finished job carries one line on what it did, at most 140 characters. The line says what the numbers show, never why, because we can’t prove a cause from a chart and won’t pretend to. A person writes or checks every line, and the newest job here has none yet on purpose: under a week of numbers says nothing.

The numbers behind it

These are counts from the portal’s own code, taken on 17 November 2026. They describe the product, not anyone’s results.

WhatNumberDetail
Places in a client’s portal5Home, Updates, Messages, Your brand and Site
States a request moves through5New, In progress, Waiting on you, Done, Cancelled
Lighthouse scores shown4Checked weekly, phone and computer; each check runs three times and keeps the middle one
AI crawlers our counter knows by name40Of 69 crawlers on its list; matched by the name they announce, so a trend, not proof
Finished jobs on Home3The newest; the rest are on Updates
Where a percentage stopsUnder 20Below 20 in the period before, a change shows as a plain difference
Languages2English and Spanish; each person picks theirs

And seven things a client can do there without writing a single email:

  • Approve a piece of work, or ask for changes to it.
  • Send a request, and say when it’s needed.
  • Reply in a request’s thread.
  • Edit or withdraw a request until we start on it.
  • Message us, with photos or files.
  • Add notes, pictures, links and drawings to the board.
  • Add files.

What this means for your business

Every client gets a portal like this, whatever we build for them. We look after what we make for as long as you like, and this is where that work happens in the open: what we did, what it did and what’s next, without you having to ask. For how that compares with hiring an agency, see Olive Branch or an agency.

Under the hood

  • Each client’s records are walled off in the database itself: on every read, it checks who’s asking (row-level security). Notes the team keeps on a request never reach a client’s browser.
  • Sign-in is by invitation only, with a link or code sent to your email.
  • Visits come from our own counter script, under 2 KB, rather than a third-party analytics tag.
  • Each kind of record lists its states once in the code, and our pre-release check fails if a list is retyped elsewhere.
  • The sample client sends no email and stays out of the team’s views across clients. The team works from the same portal, on its own side.

What we’d do differently. We built the service cards before the jobs that fill them, so for now they run on sample numbers only. The Site tab counts inquiries and AI readers only on sites under our own domain so far; a client’s site needs one more piece we haven’t built. And messages refresh every 20 to 30 seconds instead of arriving instantly. That’s the first thing we’d change.

Questions

Who can see my portal?

You, the people you ask us to invite, and our team. Sign-in is by invitation only, and the database hands a portal’s records only to people who belong to it.

What if I’d rather just email you?

That works. When we write to you in the portal or reply on a request, you get an email about it. If you email or call with a request, we can add it to your portal ourselves, so it still gets its page and its status.

Can my staff have their own logins?

Yes. We invite each person by email, and each signs in with their own address. Everyone we invite to your portal sees the same portal you do.

What happens to it if we stop working together?

Your website is yours from the first day, and if you’d rather take it from there yourself, we hand it over cleanly; who owns your website covers what to check.