How to get client communication into one place

You are looking for a logo. You know it exists, because the client emailed it in March, or maybe they dropped it in a shared Drive folder, or maybe their office manager sent it over chat with the message "here you go!!" and no file extension you recognize. Fifteen minutes later you have found three versions and you still cannot tell which one is current. Meanwhile a contract is sitting at two of three signatures and nobody on your team knows, because the e-sign tool emailed the person who sent it, and that person is on vacation.

This is not a discipline problem. It is a structural one, and it is fixable in about a week if you attack it in the right order.

Why client work scatters across email, drive, chat, and e-sign

Client work scatters because each tool solves one step of the job perfectly and has no idea the other steps exist. Email is excellent at reaching a person who has never heard of your process. Drive is excellent at holding a 400MB video. Chat is excellent at "can you look at this today." E-sign is excellent at producing a legally defensible signature. None of them knows that the logo in the email, the video in the folder, the question in chat, and the signature on the contract all belong to the same client and the same decision.

So the connective tissue lives in your head. You are the index. That holds up while you are the only person who ever needs the index, and it breaks the first time you hire someone, take a real vacation, or need a second person to pick up an account cold.

What each handoff actually costs you

Every time work moves between tools, you pay four separate costs, and only the first one is obvious.

• Search time. The visible cost. Minutes per lookup, several lookups a day.
• The version question. Worse than search, because you cannot resolve it by looking harder. You have to go ask the client which file is current, which makes you look disorganized to the person paying you.
• The accountability gap. When approval happens in a reply to a forwarded thread, you cannot prove later who approved what and when. That is the conversation you least want to have during a scope dispute.
• The handoff tax. Every scattered client is a client only you can service. A new project manager cannot take over an account whose history lives across your inbox, your chat DMs, and a Drive folder named "Client Stuff Final v2."

The fourth one is the expensive one. It is the difference between an agency and a job you gave yourself.

How do you decide what your system of record should be?

Your system of record is wherever a decision becomes binding. Not where the most messages happen, not where the most files sit. Where approvals, scope changes, deliverable handoffs, and signatures land. Chatter can live anywhere. Decisions cannot.

Use this rule to test any candidate tool. If a new employee opened it on their first day, could they answer these five questions about a client without asking anyone?

1. What was the last thing we delivered, and did they approve it?
2. What are we waiting on from them right now?
3. What did we agree the scope was, and when did it change?
4. Where is the current version of every asset they gave us?
5. What is signed, and what is still out?

If a tool cannot answer all five, it is not your system of record. It is a channel. That distinction is the whole article.

A one-week consolidation sequence you can actually run

Do not attempt a migration. Migrations fail because they front-load all the pain and deliver value at the end. Do this instead, one step per day, none of it longer than ninety minutes.

Day 1: Audit three clients, not all of them. Pick your three most active accounts. For each one, list the last ten things that happened and write down where each one lives. Ten items, three clients, thirty rows. You will see the pattern immediately, and you will not need the rest of your roster to confirm it.

Day 2: Pick the system of record and write the rule in one sentence. Something like: "Anything a client needs to see, approve, or sign happens in the workspace." Put that sentence somewhere your team will see it. A rule you cannot state in one sentence is a rule nobody will follow.

Day 3: Move one client forward, not backward. Choose a healthy client mid-project, not your messiest account. Set a cut line: everything from today forward happens in the new place. Do not migrate the archive. Copy over exactly three things: the current scope document, the active file set, and the open items list. If you cannot say what the active file set even is, settle where client files should live first, because that decision sits upstream of this one. History stays where it is and you link to it if you ever need it. Try to move two years of email and you will not get through day 3.

Day 4: Change your own behavior first. For that one client, stop replying from your inbox. When they email you, answer in the workspace and let the notification go out. This feels rude for about two days. It is the only step that actually makes the system stick, because clients follow the reply, not the announcement.

Day 5: Handle the stragglers. More on those below.

Days 6 and 7: Roll it to two more clients and stop. Three clients running cleanly beats a whole roster half-moved. Add the rest at a pace of two per week during their next natural project start.

None of this depends on every client cooperating. Some of them will never log into anything, and the answer is to make their email replies land in the right place rather than to convert them, which the honest email versus portal comparison argues out in full and the onboarding sequence sets up on day one.

What does not need to move

Consolidation gets a bad name because people take it too far and end up with a worse version of what they had. Leave these alone.

• Internal team chat. Your team needs a place to say "this client is driving me insane." Keep it separate and keep it out of anything the client can see.
• Design and dev tools. Figma, your repo, your staging environment. Link to them; do not try to mirror them.
• Huge media. Raw video and photo libraries belong in storage built for storage. Put the deliverable in the workspace and the working files wherever they already are.
• Billing. Invoicing and accounting have their own compliance requirements. Leave that stack intact.
• Executed contracts. Already signed and filed is already done. Move the process, not the archive.

Email also stays, and this trips people up. Email is a fine delivery channel. It is a terrible storage system. The goal is not to stop using email. The goal is to stop email from being the only place something exists.

Before you evaluate a single tool, ask about the exit

Ask any vendor exactly how you get your data out, then make them show you. Not "we support export." Ask what format the message history comes out in, whether files come with a manifest mapping them back to the conversation, whether signed documents come with their audit certificates, and what is missing from the export. Every product has gaps in what it exports. The ones worth trusting will tell you what theirs are.

This matters more than features, because the thing you are consolidating is the record of your client relationships. If that record is only readable inside one company's software, you have not consolidated. You have posted collateral.

If you buy nothing, do these three things this week

You can capture most of the value with tools you already pay for.

1. Write the one-sentence rule anyway. "Approvals and scope changes happen in writing in [place]." Even if that place is a specific email thread per project, having one named place beats having none.
2. Keep a waiting-on list per client and read it every Monday. Three columns: what we need, who owes it, how long it has been sitting. A stalled project is often not stalled on your work. It is stalled on something nobody re-asked for. A quiet item older than 48 hours needs a nudge, and it is worth automating that nudge whenever your tools allow.
3. Run the five-question test on your worst client this Friday. Open whatever you currently use and try to answer all five. Where you cannot, you have found your actual problem, and it is probably narrower than "everything is scattered."

Consolidation is not about having fewer tools. It is about having one place where a stranger could pick up your client relationship and not drop it. Get that, and you can use as many tools as you like.