How to run client projects in one workspace without exposing your internal chat

Most client projects run across four or five places at once. The team talks in its own chat tool. The client gets email, plus a group chat someone created in a hurry, plus a weekly call on whatever link was handy. Files travel as attachments. Every time something moves from one of those places to another, a detail falls out: the approval that was given on a call but never written down, the revised scope that lives in one inbox, the file that is "final" in two different versions.

The fix is not another tool. It is one workspace for the whole project with a hard wall inside it: a room where your team thinks out loud, and a room where the client sees what you have committed to. This guide is the setup we recommend to agencies, accounting firms, consultancies and anyone else whose work is done for clients.

The two-room model

Every client project gets two rooms in the same workspace.

• The internal room is for the team only. This is where estimates are argued over, drafts are torn up, risks are named honestly and someone asks the question they would never ask in front of the client.
• The client room is where the company speaks with one voice. Updates, approvals, deliverables, decisions. The client is in it, and so are at least two people from your side.

The rule that makes this work is simple: nothing moves from the internal room to the client room on its own. A person decides to post it, which means a person has read it. That single step catches most of what goes wrong in client communication.

Because both rooms live in one workspace, the person posting the update has the internal context one click away, and the history of what the client has been told sits next to the history of why.

Set up a client room in ten minutes

1. Create a room named after the client and the project, so it is findable a year from now.
2. Add the account owner and at least one more person from your team. No client relationship should rest on one person.
3. Invite the client contacts as client accounts, not as team members. They should reach this room and nothing else.
4. Pin the scope, the timeline and the names of who approves what. When a question comes up in month three, the answer is at the top of the room.
5. Agree the rhythm in the first message: when updates land, how approvals are given, and what counts as urgent.
6. Share the first files as links, not attachments, so you can replace or revoke them later.
7. Book the kickoff call from the same room, with a guest link the client can join by entering their name.

What the client should never see

The wall only works if it is enforced by the tool, not by everyone remembering to be careful. Before you bring a client in, check that the workspace itself keeps them away from:

• Your team directory, and the ability to message anyone on it.
• Other clients, and any hint that other clients exist.
• Internal estimates, costs and margins.
• Drafts, half-finished work and the discussion that produced the final version.
• The ability to start new conversations or create new rooms.

In SphereOne, client accounts are built this way. Clients don't appear in your directory, can't start conversations, and reach only the rooms you add them to. There is nothing for your team to remember.

A rhythm that keeps clients calm

Clients rarely become difficult because of bad news. They become difficult because of silence, and because they cannot tell what is happening. A predictable rhythm fixes most of that before it starts.

• One update, same day, same shape. A short post every week with four headings: Done, Next, Need from you, Risks. Clients learn where to look and stop asking.
• Approvals in writing, in the room. If a decision is made on a call, the next message in the room records it and asks the client to confirm. The call is where you talk; the room is where it counts.
• Decisions in threads. When a question is settled, it is settled in a thread under the message that raised it, so the reasoning is attached to the outcome.
• One voice. Disagreement among your team happens in the internal room. The client room gets the conclusion.

Writing the weekly update is where SphereOne Assist saves the most time: ask it to summarize the week in the internal room, then edit the result into the client update in your own words. Assist only reads what you can open, so it never pulls anything from a room the client could not see anyway, and you remain the one who decides what crosses the wall.

Files, approvals and the "final" problem

Every client project eventually has a file called final, a file called final-v2 and an email that says "use the one I sent on Tuesday". Three habits end this for good.

• Share links, not copies. When the file lives in one place and the client has a link to it, there is one final. Update the file and the link stays the same.
• Keep the history. With version history, the version that was approved is always recoverable, even after a dozen revisions.
• Let links expire. Set client links to expire when the project closes, or revoke them when a contact changes. What you shared stays shared only for as long as you intend.

Calls without friction

Clients should never need to install anything or create an account to talk to you. Send a guest link and they join by entering their name. Schedule the call from the client room so the invite, the agenda and the follow-up all live in one place, and if a client prefers their own meeting tool, attach that link to the meeting instead.

After the call, the first thing that goes into the client room is a short written note of what was decided. Calls are where misunderstandings begin; the room is where they end.

Handovers and endings

Two moments test whether a project is really business-owned: when a person on your team changes, and when the project ends.

• When a team member changes, add the new person to both rooms a week before the old one leaves. Introduce them in the client room, let them read the history, and let Assist summarize the internal room so they start informed. On the last day, the departing person loses access and nothing else changes.
• When the project ends, keep both rooms. They are the record of what was agreed and delivered. Expire the file links, post a closing note in the client room with where the final deliverables live, and leave it there. The next project with the same client starts with everything in view.

If client conversations have already drifted onto personal phones, our guide to keeping client relationships when an employee leaves covers how to bring them back without alarming anyone.

Why one workspace beats five tools

Separate tools feel safer because the wall between inside and outside is physical: different apps, different logins. But that wall has to be crossed constantly, by hand, and every crossing is a chance to lose something. One workspace with a wall built into it gives you the same separation with none of the copying, and it gives you something the five-tool setup never can: a single history of what you did for a client and why, owned by the business, ready for whoever picks it up next.

SphereOne was designed for exactly this shape of work. Client rooms, guest calls, controlled file links and an assistant that respects who can see what are all part of the same workspace. Pricing lists what each plan includes, and the client communication page covers the details.