The client walkthrough is the agency's weekly ritual: screen-share the work, talk through progress, collect feedback. And the workspace around the work — the browser tabs, the project titles, the notifications — carries the rest of your professional life: other clients' names, internal Slack channels, the deal you were just negotiating. The client came to see their deliverable. The share shows them your desk.
The Standard Setup (And Why It Fails)
"I share one window and that's all they see."
Why it fails:
- "Let me pull up the analytics" — and the pull-up passes through a switcher or a new tab that names another client.
- Slack and email notifications render mid-call: your internal channel names, a subject line from a different client's thread.
- The window title names the project: "Figma — [Client A] — Homepage v3" — and next on the calendar is Client B.
- A quick "screenshot for the recap" after the call captures the whole desktop — and lands in the recap email to the client.
Clients talk to each other. One walkthrough frame naming another client is a referral you didn't make — and a confidentiality breach you did.
The NoCapture Setup for Walkthroughs
Cloak the rest of the book. Everything not belonging to this client — other clients' projects, internal tools, personal surfaces — protected list, fired by routine when the call starts. The share receives their deliverable and their analytics, and the capture stream has no concept of the rest of your week.
Mask the titles. Project names, file names, tab titles — sanitized in the window manager so switcher frames and enumeration read generic labels. The frame wanders; the labels don't confess.
Shield the call. Slack, email, and tool notifications held for the meeting's duration — the internal thread about a different client never renders in front of this one.
A routine per client. Calendar-integrated: Client A's walkthrough fires Client A's configuration. The protection matches the invite, not your memory of it.
Live preview while they join. As the client connects, the preview pane confirms what's visible. The first thirty seconds of the call are when the audience is looking hardest — make them the cleanest.
The Honest Limitation
The screen layer can't fix content you choose to share. If you open another client's file "just to reference the layout," that's a business decision, not a capture accident — and no cloak replaces the professional judgment of keeping client work in its lane. Build a clean workspace per client for walkthroughs, and let the architecture make the accidents impossible while your process makes the choices disciplined.
The Bottom Line
Every walkthrough is a tour of your desk by someone who pays you for discretion. Give them the deliverable and nothing else: rest of the book cloaked, titles masked, banners held, preview checked while they join. The client should leave the call knowing their project is in good hands — not knowing who else's hands are on your desk.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
