How to turn a Gmail thread into a deal in one click
The thread is already the history. The click is for the fields Gmail will not show: stage, value, close date, next step.
Most “Gmail CRMs” ask you to become a clerk. Copy the sender. Create a contact. Create an opportunity. Paste a note. Link the email if the tool remembers how. By the time you are done, you could have answered the customer. So you skip the CRM, and the deal stays a starred thread.
The right gesture is the opposite: you are already looking at the conversation that matters. One action sends that conversation onto a board as a card. You type only what the inbox cannot display. Then you go back to selling.
This walkthrough is that gesture — in the Chrome extension that injects a Kanban board into Gmail, and in the Gmail add-on that sits beside the open message. Same pipeline. You pick the thread. Nothing vacuums the mailbox.
What “one click” is allowed to mean
One click cannot mean “we invented a deal from every sender.” That is how boards fill with dentists and newsletters. One click means: this thread, this column, this card, with a link back so you never paste the history into notes.
After the click you still owe yourself thirty seconds: a value if you have one, an expected close if you are honest, a next step in a verb. Skip those and you have only labelled the mail with extra software. The click is the capture. The fields are the CRM.
From the inbox: the Chrome extension
Install KanbanMail from the Chrome Web Store. Open Gmail in that browser. The board is injected into the Gmail UI (InboxSDK): columns you can drag, cards you can open, sitting where you already work.
- Open the thread that is actually a deal. Not the newsletter. Not the invoice for a deal you already won unless you are tracking collections as a separate board.
- Send it to the board. The contact, subject, snippet and thread link travel with it. You are not retyping the email address into a spreadsheet.
- Drop it in the honest column: Lead if you have not really spoken, Contacted if the ball has moved, Negotiation if a number or scope is on the table.
- Fill company if the sender name is useless. Value and currency when you know them. Close date as a tripwire. Next step in one line. A note only if there is a trap (“invoice the parent”).
- Tomorrow, open the card from the board when you need the mail. Do not search. The thread is one click from the card.
That is the desktop habit. It is the one you will use if you live in mail.google.com all day.
From the open message: the Gmail add-on
The add-on is the side panel on the conversation you have open. Use it when you want to see which column this person is in without hunting the board, or when you are in a Gmail surface where a full injected Kanban is not the right UI (including mobile Gmail, where the visual board of the extension does not follow you).
Same rule: you send this thread, not your entire mailbox. Move the deal between Lead, Contacted, Negotiation, Won and Lost — or your renamed columns — without leaving the message. The extension still owns the visual board on the desktop; the add-on is the companion for the email in front of you.
If you install only one thing today, install the extension. Add the add-on when you want the panel on the thread. They share the pipeline.
What gets stored (and what does not)
On the card: sender, subject, snippet, thread id and link, plus the fields you type — company, value, close, next step, notes. That is enough to drag a deal and reopen the mail.
What does not happen: a server-side Gmail API crawl of your inbox. No “sync all mail.” No auto-contacts from every domain. Privacy here is not a slogan; it is the product constraint. If a tool must read everything to be useful, it is a different product. Some people want that (full Streak-style participation in the mailbox, or a HubSpot logger). Fair. If you do not, pick a board that only receives what you send it.
When not to click
Do not create a card for FYI threads, recruiting mail you will never sell, or a client’s seventh “quick question” on a project you already won unless you are tracking that work as its own pipeline. Won sales cards can stay Won; delivery can be another board with other column names.
Do not create a second card because the subject changed from “Intro” to “Proposal.” Update the existing card. Two cards for one conversation is how you follow up twice or not at all.
Do not click five years of archive on a Sunday. Last 30 days of live pain, then forward only. Import theatre is how people quit before Tuesday.
After the click: make the card argue with you
A card with no next step is a label. A card with no close date in Negotiation is a wish. A card with €0 because you felt you had to type a number is a lie; leave value empty until the quote exists.
When the customer replies, you do not “log an activity.” You open Gmail. If the stage changed, drag the card. Rewrite the next step. That is the whole loop. For the surrounding habit, use Inbox Zero for sales — archive the thread if you want; keep the deal on the board. For column rules, sales pipeline stages that work in Gmail. The wider picture is Gmail as a CRM.
KanbanMail is free. The first card takes about forty seconds. The click is cheap on purpose. If capture is expensive, you will not capture, and you will be back to stars.
FAQ
How do I add a Gmail email to a sales pipeline?
Open the thread, send it to the board with one click from the Chrome extension (the board is injected into Gmail via InboxSDK) or from the Gmail add-on side panel. Fill value, close date and next step. You choose the thread; nothing scans the mailbox.
Does KanbanMail read my entire Gmail?
No. You pick the emails that become cards. There is no mailbox scan and no Gmail API on the server reading your inbox. The card stores contact metadata, the thread link and the fields you type.
What is the difference between the Chrome extension and the Gmail add-on?
The extension draws the Kanban board inside Gmail in the desktop browser. The add-on is the side panel on the message you have open, including where a full injected board is not available. Both send a thread you choose onto the same pipeline.