AI Automation

Ditch the Spreadsheet: The 5-Column Kanban Every Pipeline Needs

Most founders think their sales problem is a volume problem, so they reach for a bigger spreadsheet. Another tab, more rows, a new column for "status." The spreadsheet grows, the founder feels organized, and deals keep going quiet anyway. The question being answered is "how do I keep track of my deals?" That is the wrong question, because tracking is not the job. A record of your deals is a record of the past. It does not move anything forward. The real question is "what is the single next action on every live deal, and when does it happen?" A spreadsheet cannot answer that. It has no opinion. A row that says "Proposal sent, following up" has been lying to you for three weeks and the spreadsheet will never flag it, because a spreadsheet stores state, it does not enforce motion. That is the difference between a ledger and a pipeline, and it is the difference between a founder who is busy and a founder whose deals actually close. Replace the sales spreadsheet with a 5-column Kanban where every card must carry a dated next action to remain on the board, because the failure mode that kills founder-led pipelines is not too few deals, it is deals that stall silently with no scheduled next step, and the same dysfunction sinks CRMs: average CRM adoption sits around 26 percent and roughly half of implementations fail to meet their goals precisely because reps treat them as records to fill in rather than systems that tell them what to do next .

Joshua Agonya Pi'Rwot

By Joshua Agonya Pi'Rwot

Founder, Business Growth Accelerator

Executive summary

A sales spreadsheet records history, it does not run a pipeline. A 5-column Kanban forces a next action on every deal and stops silent stalls. Here it is.

Section 1

Why the spreadsheet quietly fails you

A spreadsheet is a beautiful tool for a job sales does not have. It excels at static data you look up. Sales is dynamic data you act on, and the two need opposite designs. The spreadsheet is passive by nature: it shows you everything at once, weighted equally, with no sense of what is urgent, what is rotting, or what you promised to do on Tuesday. The information is all there. The judgment is entirely on you, every time you open it, which means it gets skipped the moment you are busy. This is the exact reason expensive CRMs fail too, and it is worth learning from their failure before you assume the answer is more software. Average CRM adoption across organizations sits around 26 percent , and industry estimates put CRM project failure somewhere between 18 and 69 percent depending on the study . The cause is consistent: the tool was built for management visibility, not for the rep's next move, so reps enter the minimum and the real pipeline migrates to a private spreadsheet . A more powerful passive record does not solve a passivity problem. Whether it is Excel or a six-figure CRM, if the system does not force a next action, deals stall in it just the same. There is a second, quieter cost. When you log a meeting "later," the detail decays. Reps who delay entry lose the specifics that make the follow-up land, because later becomes much later and the useful nuance fades from memory . A pipeline that captures the next action while the call is warm preserves the one thing that actually converts: specificity.

Section 2

The five columns, and why exactly five

The board has one rule that does all the work: no card sits in a column without a dated next action attached. If you cannot name the next step and when it happens, the deal is not "in progress," it is stalled, and the board makes that visible instead of letting it hide inside a green "active" cell. Five columns is deliberate. Fewer and the board cannot tell a live conversation apart from a real opportunity, which is where founders overcount their pipeline. More and you are doing pipeline administration instead of sales, and every extra stage is another place to move cards instead of moving deals. Five is the smallest number that distinguishes "we are talking" from "this is qualified," which is the single most over-optimistic error in founder-led selling: a warm conversation is not a qualified opportunity, and a board that blurs them will always look healthier than it converts.

Section 3

The rule that makes it a pipeline: a dated next action on every card

A Kanban board without this rule is just a prettier spreadsheet. The rule is what converts a record into an engine. Every card, in every column except Won/Lost, must carry two things: what happens next, and when. The moment a card cannot answer both, it is flagged, and a flagged card is the most valuable object on your board, because it is a deal that was quietly dying and just became visible while there is still time to act. This is why the board beats the spreadsheet on the exact metric that matters. A spreadsheet lets "following up" sit unchallenged indefinitely. The board does not permit a next-action-less card to look healthy. It surfaces the stall. And stalls, not shortages, are what starve a founder-led pipeline: the deal you forgot to follow up on was more winnable than the cold name you spent Saturday finding. Persistence is the differentiator, top prospectors convert their opportunities with disciplined sequenced follow-up rather than more sends , and the dated-next-action rule is simply persistence made structural so it does not depend on you remembering.

Section 4

How to run the board in ten minutes a day

The board earns its keep only if you touch it daily, briefly. The ritual: 1. Open on the flagged cards first. Any card without a next action gets one now, or gets moved to Lost with a reason. No card hides. 2. Work today's dated actions. The board has already told you your sales to-do list. You do not decide what to do, you execute what the cards scheduled. 3. After every interaction, set the next action before you close the card. This is the non-negotiable. You never leave a live card without its next step, because the next step set while the conversation is warm is the specific one that converts . 4. Move the card, then write the reason if it is Won or Lost. Closed deals feed the only learning loop you have. Ten minutes. The board replaces the anxious open-the-spreadsheet-and-scan ritual with a decided one, because the work of deciding what matters was done when you set each next action, not when you opened the board under pressure.

Section 5

What the board teaches you over time

After a month, the columns become a diagnostic. If cards pile up in Conversation and never reach Qualified, your problem is qualification, not lead flow, and no amount of new prospecting will fix it. If Qualified cards die in Proposal, your problem is the proposal-and-decision process, not the top of funnel. The board localizes the leak. A spreadsheet, showing everything equally, hides exactly where the pipeline actually breaks, which is why founders working from spreadsheets so often solve the wrong problem: they pour leads into a funnel that is leaking at the bottom.

Section 6

Key takeaways

• A spreadsheet stores state, a pipeline enforces motion. The distinguishing feature is a dated next action on every card, not the number of rows. • More powerful passive records do not fix a passivity problem: CRM adoption averages around 26 percent and a large share of implementations fail because the tool records rather than directs . • Five columns is the minimum that separates a live conversation from a qualified opportunity, which is the most over-optimistic error in founder-led pipelines. • Silent stalls, not lead shortages, starve founder-led sales. The board's job is to make a stall visible while there is still time to act. • Set the next action while the interaction is warm, because delayed logging loses the specifics that make follow-up convert .

FAQ

Direct answers for operators.

Do I need software, or can this be a physical board?

Either works, because the leverage is in the rule, not the tool. A whiteboard with sticky notes enforces the dated-next-action discipline as well as any app, and often better, because it is in your eyeline. Adopt software only once the manual board is a habit, so you are digitizing a working system instead of hoping the software creates one, the mistake behind the roughly 26 percent CRM adoption rate .

How is this different from the deal stages my CRM already has?

Most CRMs let a deal sit in a stage indefinitely with no forced next action, which is exactly why real pipeline data leaks out of them into private spreadsheets . The Kanban rule, no card without a dated next step, is the discipline CRMs allow you to skip. You can run this inside a CRM. You just have to enforce the rule the CRM will not enforce for you.

Won't five columns oversimplify a complex sale?

Five columns track where a deal is, not how complex it is. The nuance of a complex engagement lives in the card's notes and next actions, not in more columns. Adding stages feels rigorous and mostly creates more places to move cards instead of moving deals. Start at five and only split a column when a real, repeated decision point demands it.

What do I do with the deals that stall anyway?

Move them to Lost with an honest reason, and let the reason codes teach you. A deal with no next action you are willing to schedule is not a live deal, it is a hope, and hopes inflate your pipeline and your stress in equal measure. Closing a stalled card is not losing the deal. It is refusing to keep paying attention rent on a deal that already left.

Joshua Agonya Pi'Rwot

Written by

Joshua Agonya Pi'Rwot

Founder, Business Growth Accelerator · Country Director, AVODA Group Uganda · EMBA

Joshua helps service-business operators turn scattered marketing into a clear path from first attention to booked call. He is Founder of Business Growth Accelerator and Country Director of AVODA Group Uganda.