How agencies keep client deals out of a messy inbox
An agency inbox is not a pipeline. It is pitches, production, vendors, and “quick tweaks.” The deals need their own columns or they drown.
Agency Gmail is a special kind of chaos. The same address that receives a new-business RFP also receives asset comments, media invoices, freelancer contracts, and a client asking if the banner can be 3px taller. Stars do not survive that mix. Neither do labels named after clients: they file the work, they do not show you which conversations are still sales.
The mistake is treating the whole mailbox as the CRM. A CRM for an agency is a short list of commercial threads: new logos, expansions, renewals, and the odd inbound that might become a retainer. Production mail can stay messy. The pipeline cannot.
Why client labels still leave money on the floor
You already have Clients/Acme. That is correct for finding last quarter’s brand guidelines. It is useless for answering “is Acme a live upsell or a closed project we are milking for tweaks?” The thread looks the same in search either way.
Unread is worse. New-business mail and production mail both arrive unread. The RFP that needed a Monday reply loses to the louder Slack-via-email from an existing account. Volume is not a stage.
A second tab called HubSpot does not fix this if nobody logs the RFP because they are already writing the deck in Google Docs and the conversation is in Gmail. The commercial object has to sit on the mail, or the account lead will keep the forecast in a private note.
Split the jobs: delivery vs deals
Agencies already have project tools. Use them for delivery. Do not drag every “please send the latest cut” onto a sales board. Those cards will bury the three proposals that pay next month.
A practical split:
- On the sales board: new business, scope expansions, renewals, anything with a new number attached.
- Not on the sales board: production comments, vendor mail, recruiting, and support-shaped client chatter.
- Maybe a second board later: if you truly want an ops Kanban of briefs. Do not mix it with Won/Lost.
If a current client emails “can we add a landing page,” that is a deal. Put it on the board with a value even if the value is a guess. If they email “the hex is wrong,” that is delivery. The inbox can hold both. The pipeline should not.
Columns that match how agencies actually sell
Defaults work: Lead, Contacted, Negotiation, Won, Lost. Agencies often need one extra column because legal and procurement sit on retainers:
- Proposal sent — if you regularly wait two weeks after a deck goes out. Otherwise Negotiation hides a graveyard of PDFs.
- Waiting on procurement — if the yes already happened and you are not really selling anymore.
- On hold — they asked for next quarter. Leaving them in Negotiation makes the month look richer than it is.
Do not add a column per service line (SEO, paid, brand). That is a filter you wish you had, not a stage. The stage is about commitment, not the menu. Put the service in the card name or in notes.
Rename freely. Brief → Pitch → Verbal yes → Paperwork is a valid agency board. The rule still holds: a card moves when a fact in the thread changes, not when someone feels optimistic.
Rules for a messy shared reality
Many agencies still sell from personal Gmail, not a shared box. That is fine. Each person can run a board of their commercial threads. The Monday pipeline meeting is then “open your Negotiation column,” not “update the Sheet before the call.”
If you do use a shared inbox, a heavier Gmail CRM with shared boxes may be the right tool. A personal Kanban will not magically become a team inbox. Pick the product that matches who owns the address. KanbanMail is the personal-board-in-Gmail version: you choose emails, you drag cards. It does not turn four people into one mailbox.
Either way, write a next step that names a person. “Wait for the client” is how RFPs die. “Ana sends the revised fee table before Thursday’s call” is a next step. Put company, value, and close date on the card so the meeting is about numbers, not archaeology in search.
A weekly 20-minute new-business pass
- Open the board, ignore the unread badge.
- From right to left: is Won actually contracted? Is Negotiation still a live number?
- Anything with a next step older than seven days gets rewritten or killed.
- Scan the inbox only for threads that should be cards and are not. Create those. Do not card the rest.
- Sum values in Negotiation. If the number feels fake, the board is lying — usually because On hold is still in Negotiation.
This is slower than “we’ll remember the pitches.” It is how you stop discovering in week three that nobody answered the only inbound that was real.
Privacy when client mail is confidential
Agencies should be picky about tools that ingest the whole mailbox to “auto-detect deals.” Client mail includes unreleased campaigns, legal, and sometimes personal data. Prefer a model where a human chooses the thread and the vendor stores card fields — not a scan of everything to build a graph.
KanbanMail does not scan the inbox. You pick the email. We do not request gmail.modify, and we do not read the mailbox from our servers. Sign-in is Google profile. Details are on our privacy page.
The Gmail implementation
KanbanMail is a free Chrome extension that injects a Kanban board into Gmail, plus a Gmail add-on for the open message. Cards hold next step, company, value, close date, and notes, with a link back to the thread. You choose what enters the board — production noise can stay in the messy inbox, where it belongs.
It will not replace your project tool, your time tracker, or a shared Streak box if that is already how the studio sells. It will keep new business from drowning in production. For the method behind the columns, read why columns beat folders and how to build a sales pipeline inside Gmail.