Kanban board

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Columns you define, for the things no purpose-built board fits.

Card age surfaces the item that has quietly stalled, which is usually the expensive one.

Right when the stages are yours and wrong when a specific module already matches them.

How it works

1
Columns are defined for the process at hand rather than chosen from a template.
2
Cards move as conversations report movement.
3
Age accumulates in place, so a card that stopped is visible without anyone auditing.
4
Right when the stages are yours and wrong when a purpose-built module already matches them.

Best for

Anything that moves through stages: leads, orders, applications.

Not the right choice for

Data with no natural stages — you get one very long column.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

Field	Type	Filled from
Cardrequired	text	The item moving through stages, whatever it is.
Columnrequired	text	The stage it is at. The columns are yours and inventing them badly is the usual failure.
Age	text	How long it has been where it is. Surfaces the item that quietly stalled.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

General-purpose, which means it knows nothing about what it is holding.
No automation between stages.
No assignee, due date or priority unless you add them as columns of the card text.
Being able to model anything means it models nothing well.

Before it works

What you have to provide, if anything.

Define the columns from the real process. Copying somebody else stages is how a board stops matching reality.
Check whether Task board, Prospects or Research board already fits before using this.

In practice

A shop hiring a weekend assistant and a driver at once.

“Where is everyone up to on the hiring?”

What was said to the agent

What the agent built

A board with applied, interviewed, offer out and rejected, and four candidates placed.

What changed

An offer had been out for nine days with no chase. The candidate had taken another job four days earlier.

Better with

These do a different job on the same data. An agent can have all of them.

Task boardLive

Several pieces of work are in flight at once and the useful question is what stage each is at rather than when it is due.

ContactsLive

Almost any agent that talks to more than one person and needs to remember who they were. The default people module when nothing more specific fits.

Intake formLive

New enquiries need the same information every time and chasing it afterwards costs days.

Who uses this page

Recruiting team

Answers candidates properly, screens the basics, and keeps every pipeline visible.

Creator or influencer

Answers your audience and filters brand enquiries, so the DMs stop being a job.

Job seeker

Keeps every application, contact and follow-up straight — and answers recruiters for you.

Podcaster

Answers listeners from your back catalogue, and filters the guest and sponsor pitches.

Questions

What data does the Kanban board page use?

It reads card records the agent has collected. Any board of cards. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a kanban board the wrong choice?

Data with no natural stages — you get one very long column. It is best for: anything that moves through stages: leads, orders, applications.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.