A project board runs a simple sales pipeline well, and keeps running it long after it should. The failure is quiet, however: shared history, follow-up, forecasting, and reporting all degrade before anyone calls a meeting about it. This guide marks the point where a board stops saving time and starts costing deals.
Takeaway: Run sales on a board while the pipeline fits in a few people's heads. Move to a CRM the moment revenue depends on records those people don't own.
For a founder running ten deals, a board with four columns beats any real CRM. It's fast, it's visual, and there's nothing to learn.
The strain shows up later. Quietly. A rep inherits an account and can't tell what was promised, or a forecast turns into a spreadsheet nobody believes.
Knowing where that shift happens saves you both a premature migration and a deal lost to a dropped thread.
Running sales on a board solves the first visible problem: getting deals out of scattered notes and into one shared pipeline.
You add columns for New, Qualified, Proposal, and Closed, assign each card an owner, and you're done. For a small team, that already looks like sales infrastructure.
You get stage visibility without a setup project. Reps and founders drag cards along as deals move, and managers scan the board in a weekly review. There's almost no process overhead: nobody defines thirty fields or rethinks how the team works. A company already using task management will spin up a sales board on instinct, because the team already thinks in owners, deadlines, stages, and cards.
A board shows work moving through stages, which looks a lot like pipeline management. A CRM stores something else: the connections between people, companies, opportunities, communications, and activities over time. The visual pipeline is one view onto that record structure.
That difference stays invisible while one or two people know every account. It gets loud the first time someone picks up another rep's deal and has to work out what already happened.
Pro Tip: open a few older deal cards and ask whether a new rep could rebuild the account history without digging through email or pinging colleagues. If the answer keeps coming back no, you've found the board's ceiling.
[BANNER type="lead_banner_1" title="CRM Readiness Scorecard: Spot Gaps in Card-Based Pipelines" description="Enter your email address to get a comprehensive, step-by-step guide" picture-src="/upload/medialibrary/c0f/04zrwoo0jpzvirn15czqu595pynw0yl9.webp" file-path="/upload/medialibrary/4c9/9u7g1hqsf0gvw5r3ipl193sv1omsh3lp.pdf"]A Kanban setup holds up when the sales motion is straightforward: low deal volume, short cycles, few handoffs, and a narrow set of stages most deals move through in order.
It works best when only a few people touch the pipeline. If one founder or a tight sales team owns nearly every conversation, the customer context already lives with the people doing the deals.
A board also does a few things well:
The model is strongest when a deal revolves around one main contact, with little going on around stakeholder mapping, account structure, renewals, or repeat buying. Teams that like working this way can run Kanban boards without signing up for a full CRM process.
The board hits its limit when these questions start coming up on repeat:
Those answers live in relationship history, not stage position. A founder who remembers every buyer fields them from memory. Add a few reps, longer cycles, and more stakeholders, and memory becomes a bad place to keep sales context.
The board holds up fine. What gives way is the assumption that customer memory can live in people's heads.
Boards organize work around items moving through a workflow. CRMs organize customer information around records that persist: contacts, companies, deals, activities. That structural gap decides what happens when a relationship gets complicated.
A deal card starts out holding everything about a prospect:
That's fine while the card is the whole relationship. It breaks when the same buyer comes back, a second opportunity opens, or a new stakeholder from the same company starts talking to a different rep. The usual move is to make another card and hand-copy whatever context looks relevant. Now two or three places all claim to be current.
Example-in-action: a mid-market buyer signs for one product, then months later a different rep opens a renewal-and-expansion conversation. That rep starts a fresh card and copies over what they can find, while the original objection notes, the pricing history, and the procurement contact stay stranded on the first card. Two cards describe one account, and neither is complete.
In a CRM, a contact links to a company, to one or more deals, and to a history of activities. Opening a second opportunity doesn't mean rebuilding the relationship from scratch. In the example above, the renewal attaches to the same company record, so the earlier contacts, activities, and notes are already sitting there instead of buried on an old card.
Picture an account with a department head, a finance approver, and a procurement contact, each entering at a different stage. On a board, those names and threads scatter across comments, checklists, and separate cards. With structured records, each person stays attached to the account and its activity.
In Bitrix24, CRM records connect contacts, companies, deals, and communication history, so whoever inherits the deal sees the sequence of what already happened.
Pro Tip: pick one repeat customer with several contacts and count how many places you have to check before you understand the relationship. That count tells you more than any CRM feature list.
[BANNER type="lead_banner_2" blockquote="\"Bitrix24 has allowed us to efficiently track client interactions, schedule therapy sessions, and manage outreach programs in one place.\"" user-picture-src='/upload/optimizer/converted/upload/iblock/e02/28mm3s6sqw92rqwei5evqcq1c9r20gzs.png.webp?1742830688447' user-name="Founder & CEO, Mpadi Makgalo" user-description="Heal SA Together NPC"]The first cracks show up in ordinary rep work, not executive reporting.
Sales runs on knowing what already happened: who was contacted, what they said, which objections came up, what got promised next. Boards don't build an account-wide timeline on their own. When a company has several stakeholders, one rep's notes sit on one card while another rep logs an update somewhere else. Each entry is correct. Nobody holds the whole sequence. The next account owner rebuilds it by hand, from card comments, email, meeting notes, and whoever's still around to ask.
The tell comes a week later, when they email the buyer a question the buyer already answered in a call back in spring, and the buyer notices.
Most boards hold due dates and reminders. Sales follow-up needs more than that. A rep has to know when the buyer was last contacted, whether it was a call or an email or a meeting, what the agreed next step was, whether a reply is overdue, and who owns the next decision.
Say a deal sits in Proposal. The card looks healthy because it's parked in an active stage. The buyer hasn't replied in two weeks and no one has booked the next activity. Stage position hides that completely.
Example-in-action: two reps each hold a card for the same account. One promises a revised quote by Friday. The other, not knowing, sends the same contact a generic check-in the next morning. The quote never goes out, because each assumed the other had the thread, and the buyer reads the mixed signals as a team that isn't talking to itself. No one was careless. There was just no shared record holding the commitment.
A CRM with activity tracking ties the next action to the deal itself. In Bitrix24, sales pipeline management combines deal stages with activities, ownership, and follow-up, instead of leaning on where a card happens to sit.
Duplicates creep in. The same company gets entered under two spellings. A contact gets recreated when a fresh inquiry lands. Two reps start separate cards for one account without knowing it.
CRMs catch this too when data-entry rules are loose. In Validity's 2024 survey of 600+ CRM admins, 24% said less than half of their CRM data was accurate and complete. Structure doesn't erase the data-quality work. It gives you a system where ownership, standards, deduplication, and cleanup can actually be run.
The pattern underneath all three: once the system stops preserving history, reps rebuild context by hand, follow-up slips, and duplicates make every later report a little less believable.
More deals change what management needs from the system. Leadership starts asking questions a board was never built to answer twice the same way: what's likely to close, where deals stall, which sources produce real opportunities, and who should see which revenue numbers.
Two deals in the same column can be worlds apart. One has a named decision-maker, a real budget, a credible close date, and a buyer who replied yesterday. The other has been untouched for weeks. Drop both in Proposal and a board-level view treats them as roughly equal, unless someone maintains extra fields and activity data by hand.
Example-in-action: Deal A is worth $40,000, has a decision-maker engaged, and a buyer reply from yesterday. Deal B is worth $12,000, has seen no activity for five weeks, and its close date already passed. A stage-only view counts both as Proposal and can weight them the same, so the forecast reads $52,000 of near-term pipeline when only Deal A is realistically live. The number looks precise and is mostly wrong.
Stack a few of those together and the board-level forecast becomes a number you present with a straight face and privately discount.
Custom fields help, but only if every rep fills them the same way every time, and a busy pipeline erodes that discipline first. When amounts, close dates, probabilities, or next steps go missing or mean different things to different reps, the forecast becomes a cleanup job.
You've seen the pattern: a manager exports the board before the forecast meeting, chases missing values rep by rep, and keeps a side spreadsheet for the real numbers. The board still looks useful. The forecast now lives somewhere else.
Counting cards by stage is easy. Reading what happened over time is the hard part. Sooner or later sales leaders want to see:
Every one of those needs structured, consistently maintained data, and unreliable data carries a price. In the same Validity survey, 31% of CRM admins said poor-quality data costs them at least 20% of annual revenue.
Software supplies the fields and the reports. Teams still have to agree on definitions and own what goes in. In Bitrix24, CRM analytics and reporting work off structured deal and customer data, and it pays off once reps log information consistently enough that managers read the reports instead of rebuilding them.
Boards are built for open collaboration, which suits delivery work. Sales data needs tighter edges. Different people need different access:
Revenue figures, customer notes, territory data, and management reports shouldn't be visible to everyone who can open the board. The freelancer you added to tidy up onboarding tasks has no business scrolling past the discount you gave your biggest customer. Role-based access becomes part of daily sales ops, and a CRM separates who views, edits, or manages each record and report.
Line up the features and boards and CRMs look almost identical: Kanban views, custom fields, owners, comments, automation, dashboards, due dates. The jobs underneath are different.
|
Model |
Primary job |
Best fit |
Main weakness |
|---|---|---|---|
|
Project board |
Track work through stages |
Simple, low-volume sales motion |
Weak shared customer history |
|
CRM |
Manage relationships and revenue data |
Multi-touch, growing sales operation |
Requires more structure and upkeep |
A solo founder tracking a handful of live deals does fine on a board. They know every buyer, and they mostly need a visible nudge about what happens next. Change the shape of the team, though, and the math changes. Several reps working related accounts, specialists joining discovery calls, managers reviewing forecasts, deals with four or five stakeholders: now the system has to hold account context while a crowd contributes to the same revenue. That's the point where CRM structure earns the upkeep it costs.
There's no magic deal count or headcount where a board suddenly stops working. The real threshold is operational: how much does your sales process depend on information staying reliable inside the system?
A board stays the right call when:
Adding a CRM too early carries its own tax. You end up maintaining fields and processes the team doesn't need yet.
The threshold has shifted when:
Rule of thumb: once three or more of these are already true, plan the move inside the next quarter rather than waiting for the board to fail in front of a customer. The board still shows every deal. The real question is whether someone who didn't create the card can trust what's behind it.
Before you move anything, take a sample of active and recently closed deals and pin down what the team actually needs to keep:
Then decide who owns each field and when it gets updated. Dumping messy cards into a CRM just relocates the mess.
Yes, while it stays simple. Low deal volume, short cycles, few handoffs, and one or two people who know every account: a board covers that without setup overhead.
Customer history, follow-up, and duplicate records. History scatters across cards, follow-up depends on whoever remembers, and the same company gets entered twice. The forecasting and reporting problems come later.
When coordination starts depending on the system: several people on the same accounts, context lost in handoffs, forecasting that needs side spreadsheets, or knowledge that walks out when a rep leaves. Once three or more of those are true, plan the move.
No. Bitrix24 keeps the Kanban card view on top of real CRM records, so reps work the way they already do while the account history lives underneath.
Bitrix24 adds contacts, activities, reporting, and permissions beneath familiar Kanban pipelines so teams never lose deal context.
Get Started NowA board never announces the day it stops being enough. It keeps showing tidy columns while the history thins out, the follow-ups slip, and the forecast becomes guesswork dressed as a number. By the time a rep quits and takes three accounts' worth of context with them, the cost is already paid.
It's measurable, too: a Journal of Marketing study of a Fortune 500 firm found that rep transitions cut annual sales from the affected customers by 13.2% to 17.6%.
Strip away the tooling debate and one question is left: can your revenue still afford to live in someone's memory, and what does it cost you the day it can't?
When the answer turns, the fix is a system that keeps the customer record intact as more hands touch it. Bitrix24 does that without taking away the board your team likes: Kanban cards on top, contacts, companies, activities, and reporting underneath, at a flat price per organization rather than per seat.
Keep the view. Add the memory.
Takeaway: Deal count won't tell you when to switch. Ask whether someone who didn't create a card could act on it tomorrow without calling the person who did. Once the honest answer is no for more than a handful of deals, the board is costing you more than a CRM would.