Visual pipelines: run your LinkedIn conversations on a kanban board
A kanban pipeline built around LinkedIn conversations: the columns, what a card needs, when to move it, and the daily and weekly passes that keep deals moving.
By Swimlane Updated September 14, 2026 6 min read
Designing your stages is a quarterly job; the guide to sales pipeline stages covers it. This article is about the other days: a kanban sales pipeline you open every morning to decide who gets a message today. On LinkedIn, the unit of work is a conversation, so the board should be built around conversations, not around likes or a vague idea of “warmth”.
Why a kanban sales pipeline beats the inbox and the spreadsheet
The LinkedIn inbox is sorted by recency. It tells you who wrote last, not where each relationship stands. A promising thread from nine days ago sinks below this morning’s recruiter pitch.
A spreadsheet is worse: it records where things were when someone last updated it, and it hides the shape of your prospecting. On a board, the shape is the first thing you see:
- which column is piling up
- which column is empty
- which cards have not moved since you last looked
Those three observations are most of pipeline management.
Columns built around the LinkedIn conversation
A board that works for most LinkedIn prospecting has eight columns. Each has a clear way in and a clear way out, and every move is triggered by something in the thread or on the invitation, never by a like.
- To invite. Good fits you want to talk to, not connected yet. Out: you send the request.
- Invited. Request sent, waiting. Out: accepted, or given up on after a few weeks.
- Connected. They accepted; nobody has written yet. Out: you send the first message.
- Conversation open. You wrote; the ball is in their court. Out: they reply, or stay silent after your follow-up.
- Replied. They answered; the ball is in yours. Out: you book a call, or the exchange ends.
- Meeting booked. A date is in both calendars. Out: the meeting happens and you decide.
- Done. A deal handed to your CRM, a client, a partner.
- Abandoned. A clear no, or silence after your last follow-up.
Why split “Conversation open” and “Replied”? Because they need opposite actions. In the first you wait or follow up once; in the second you are the bottleneck. Merging them hides the conversations where you are the one making people wait.
What a card needs to show
A card should let you recognise the person and judge the fit without opening anything. In Swimlane, a pipeline card shows:
- the photo and name
- the headline and company
- the tags on the contact
- the ICP level, one of five from very low to excellent
That is enough. Who they are, whether they fit, and your own labels. Everything else is one click away: the card opens the contact, with the conversation, notes, reminders and the AI analysis.
Use tags for the one extra dimension you sort by in your head, such as “event-lead”, “referral” or “came-from-campaign”. A campaign’s “Add tag” step shows up on the card too, so you can see at a glance which conversations an automation started.
Moving cards: by hand, on purpose
Swimlane never moves a card on its own, and no campaign step does. That is the right design for a conversation board: a stage is a judgment about what the person said, and a rule that guesses will be wrong in exactly the conversations that matter.
What makes manual moves cheap:
- Drag and drop on the board.
- The stage selector on the contact page, beside the thread, and in the inbox’s conversation list, so you can move someone the moment you read their reply.
- The suggested stage. The AI analysis reads the conversation and can propose one of your stages; a Move button accepts it.
The habit that keeps the board true: move the card while the message is on your screen, not in a Friday clean-up.
The daily pass, right to left
Work the board from the stage closest to revenue back to the newest contacts.
- Meeting booked. Anything today or tomorrow? Prepare, confirm the time.
- Replied. Answer every card here today. It is the only column where the delay is entirely yours.
- Conversation open. Anyone silent for more than a week gets one follow-up, a reminder for later, or a move to Abandoned.
- Connected. Open conversations. Write one by one when each person deserves a specific opener. When one short opener genuinely fits everyone in the column, the column menu can send it to all of them, with
{firstName}and the other variables filled in. - To invite. The same column menu sends a connection request to every contact in it.
Column sends are queued, spaced out and capped to what is left of your daily invitation and message limits. When a column holds more contacts than your remaining limit, Swimlane tells you how many will go out before it queues anything.
The weekly pass: read the shape
Once a week, look at the counts per column; the dashboard’s pipeline widget shows them for any pipeline. Then read the patterns:
- To invite and Invited pile up. Requests are not being accepted. Look at who you invite and whether your note gives them a reason.
- Connected piles up. You connect and never write. That is the cheapest column to fix.
- Conversation open piles up. Your openers do not earn replies. Rewrite the first message before sending more.
- Replied piles up. You are the bottleneck. Block time for it.
- Replies but no meetings. You are not asking. Propose a specific next step in your second or third message.
Then close honestly. Mark your closing columns with the Done and Abandoned column types. Contacts there stop being suggested in the dashboard’s “People to interact with”, so a closed conversation does not come back to haunt your morning.
One board or several
- One pipeline per motion. Outbound prospects, inbound people who commented on your posts, partners. Their columns differ, and mixing them muddles the patterns above.
- Clients elsewhere. Once someone buys, move them to Done here and manage the account in the CRM or on its own board.
- One stage per pipeline. A contact can sit on several boards, but holds a single stage on each.
- Pipelines live in the inbox too. Each pipeline has a page in the inbox sidebar, so you can work its conversations as a list when the board view is not what you need.
- Personal boards. A pipeline created in the app is yours: each rep runs their own board on the contacts and lists the team shares.
The LinkedIn CRM page shows the boards and the contact record, and the LinkedIn inbox page shows where the conversations themselves are handled.
Getting started this week
- Create one pipeline with the eight columns above. Set Done and Abandoned as their column types.
- Put your twenty most active LinkedIn conversations on it, honestly placed.
- Do the daily pass for five days without adding anything new.
- On day five, read the shape and fix the column that piles up.
After a week the board stops being a picture of your prospecting and becomes the place you decide what to do next.