The Slack-versus-Gmail debate inside small agencies is the wrong debate. Both tools are fine. The agencies that win are not the ones that picked the right one. They are the ones that figured out what to do about the seam between them.
This is a piece about that seam. Where it lives, what slips through it, and what an actual coordination layer above both looks like in practice.
"The agencies that win are not the ones that picked the right channel. They are the ones that figured out what to do about the seam between them."
Where the work actually lives
In a 5-to-25 person creative or marketing agency, here is roughly how the channels split out in practice.
Internal team work lives in Slack. The designer pings the strategist. The strategist asks the lead a question. The lead remembers the thing the client said yesterday. The agency has a channel per client and a few all-hands channels. The volume is high. The half-life of any individual message is about two hours.
Client-facing work lives in Gmail. The brief comes by email. The contract goes by email. The weekly update goes by email. The escalation when something is wrong goes by email. Anything the client wants on the record, they put in email, because that is where their own team can find it again later.
The agency knows this implicitly. They Slack each other to figure out what to put in the email, then they email the client. They get the client's email reply, then they Slack about what to do about it. Everyone has lived inside this rhythm so long that it feels like just how the work happens.
The seam
The break point is not Slack. The break point is not Gmail. The break point is the act of moving information across the seam between them. Every transition is a place where context can drop.
Three specific failure modes show up over and over.
All three of these are coordination failures. None of them are Slack failures. None of them are Gmail failures. They are seam failures.
What does not fix the seam
Most agencies, when they recognize this problem, reach for one of three solutions. None of them work.
Forwarding every client email into Slack. Now the Slack channel for the account is a mix of high-noise team chatter and low-frequency client signal, and nobody knows which is which. People stop reading the channel. The signal gets buried in the noise.
CC-ing everyone on every client email. The inbox load on every account person doubles. People start filtering. The important emails get filtered with the noise. The team starts pretending they read everything.
Picking a project management tool as the source of truth. ClickUp, Asana, Notion. These tools are good. They are not the source of truth. The actual decisions still happen in Slack DMs and Gmail threads, and then a junior person is supposed to back-fill the PM tool, which they do for two weeks and then stop.
What all three solutions share is that they try to fix the seam by moving work between channels. The seam is not the channel. The seam is the human translation step in between.
What an actual coordination layer does
A coordination layer that works does three things.
First, it reads both sides. Slack and Gmail, continuously, with permission, as a single context. Not as two feeds to be forwarded between, but as one signal that knows the client said X by email at 2 p.m. and the lead replied with Y on Slack at 4 p.m. and that the two are about the same thing.
Second, it acts on the seam, not at the edges. When the client moves the launch date by email, the layer drafts the DM to the designer, drafts the update to the PM tool, and drafts the internal heads-up. The lead approves with one tap. The seam closes in one move instead of three.
Third, it follows up on its own. If the founder said "we will get you something by Friday" and nothing has gone out by Thursday morning, the layer is the one that reminds the founder. Not a calendar alert. Not a sticky note. A human-quality DM saying "you owe Acme a response by tomorrow on the brand guidelines question, want me to draft something?"
This is what we built into Orbis for creative agencies and Orbis for marketing agencies. It is not a Slack app. It is not a Gmail extension. It is a layer above both, owned by the agency, scoped to their accounts.
What the team feels
The part that took the longest to get right was not the technical wiring. It was the texture. The layer has to feel like a quietly competent coworker, not like an enforcement system. It DMs the right person at the right time. It does not post in shared channels unless invited. It never DMs the client.
When the agency runs this for a few weeks, the qualitative shift is that people stop carrying the running list of seam-spanning work in their heads. The lead used to remember that the client moved the date, that the designer needs to know, that the PM tool needs updating, that the founder is CC'd, and that the Friday update needs to reflect all of it. Now the lead remembers that the layer is on it.
That is what a coordination layer is for. Not to replace the team. To carry the list the team should never have been carrying.
If your agency is on Slack and Gmail
If your agency does most of its work on Slack and Gmail, and you recognize at least one of the three scenes above as something that has happened to you in the last month, this is the gap Orbis exists to close. The Launch Sprint wires the layer into your specific accounts and workflows in two weeks for a fixed price. Or you can get started on your own.