Streams: turning a CRM into a Kanban board your team will actually use
Why most CRMs feel like data entry, why Kanban works, and how Streams in ClientPulse blends the two.
Most CRMs feel like data entry because they are. You log a call, you update a stage, you add a note. The reward for doing all that work is a report you do not read.
The reason a Kanban board works — and the reason most teams adopt them eagerly — is that the board is the work. You do not log what you did. You move the card. The board's state is the state of the work.
Streams in ClientPulse are CRMs in Kanban shape.
What a Stream is
A Stream is a vertical lane of cards, each card representing a piece of work for a specific client. Each card moves through stages defined by you: New, In Progress, Awaiting Client, Pending Completion, Done.
You can run multiple Streams in parallel — a "Quotes" stream, a "Service Visits" stream, a "Onboarding" stream. Each Stream has its own stages, owners, and overdue thresholds.
Why this matters
In a traditional CRM, the question "what is happening with this client right now?" requires you to open the client record, read 12 notes, and infer the current state.
In a Stream, the question answers itself: their card is in the "Awaiting Client" stage, parked there since Tuesday, owner is Sipho, overdue threshold is 7 days.
The state is visible. The state is the work.
What teams actually do with it
The teams we work with use Streams in three patterns:
- Sales pipeline. New lead → Discovery → Quote sent → Closed. Cards move left to right as the deal progresses. Overdue alerts fire when a card sits in one stage too long.
- Service operations. New job → Scheduled → On site → Pending sign-off → Signed off. Streams here often have a deeper pipeline because the work has more checkpoints.
- Client lifecycle. New client → Onboarded → Active → At risk → Churned. This is the long view — months, not days. Useful for businesses with retainer-style relationships.
What makes it different from a generic Kanban tool
The cards are clients, not abstract tasks. So each card carries:
- The client's contact details and message history
- Open quotes, invoices, and job cards
- The "Last contact" date — when MJ or you last interacted
- The overdue alert if the card has not moved in N days
- Any pending Approval Inbox items linked to that client
When you click into a card, you are not just opening a task — you are opening the entire client picture, which is what you actually need to act on the card.
The team-assignment angle
In April we added per-card team-member assignment. Each card has an assignee, the assignee sees their work-in-progress on the dashboard, and overdue alerts route to them rather than to the org admin.
This was the missing piece for two-to-five-person teams. Before assignment, the boss was a bottleneck for every overdue alert. After assignment, the right person is nudged directly.
A small honest admission
Streams are not for businesses with one person and ten clients. If you can hold the whole pipeline in your head, you do not need this view.
Streams pay off when you have 50+ active clients, multiple parallel workstreams, or a team. That is when the cognitive offload becomes real and the data entry stops feeling like a tax.
If that is you, give it 7 days. If it is not, stay with the inbox. Use the tool that fits the size you actually are.