Spreadsheets vs. Kanban: How Swiss SMEs Are Rethinking Their Sales Pipeline
A shared spreadsheet was fine when you had five leads. Here's an honest look at when spreadsheets and email chains stop working — and what an integrated CRM pipeline offers instead.
Almost every Swiss SME starts the same way: a shared spreadsheet with columns for lead name, status, and "next step." It works. Until it doesn't.
Before making the case for an integrated CRM, it's worth being honest about why spreadsheets and email chains got so popular in the first place — and where they genuinely start to break down.
The Old Way: Spreadsheets, Inboxes, and Sticky Notes
For a one- or two-person sales effort, a spreadsheet has real advantages. It's free, everyone already knows how to use it, and there's no onboarding curve. You can colour-code rows, sort by deal size, and it feels flexible because you built it yourself.
The trouble starts when the pipeline grows past a handful of active deals, or when more than one person needs to touch it. A few familiar problems show up:
- Status goes stale. Someone updates the deal stage in the sheet, forgets to log the call that happened yesterday, and now the "current" status is really last week's status.
- Context lives in email, not in the pipeline. The actual conversation history — quotes sent, questions asked, promises made — sits buried in someone's inbox, disconnected from the row that says "Proposal Sent."
- Handovers are painful. When a colleague is away or a lead moves from sales to account management, whoever picks it up has to reconstruct the story from scattered emails and half-remembered calls.
- No real metrics. Pipeline value and close rates technically can be calculated in a spreadsheet, but usually aren't, because it means manually tallying columns that are already slightly out of date.
- Point tools multiply. To compensate, teams bolt on a separate CRM trial, a task app, maybe a shared calendar — and now the lead's story is split across four disconnected systems.
None of this makes spreadsheets a bad choice for a very small, very early pipeline. The trade-off is simple: low setup cost now, in exchange for manual upkeep and fragmented context later.
The Integrated Approach: One Pipeline, Every Touchpoint Attached
A lean Kanban-style CRM addresses the fragmentation directly, rather than adding another disconnected tool to the pile. In Flitz, the CRM sales pipeline is built around three ideas: visibility, context, and continuity.
Visibility: Drag-and-Drop Stages
Leads move through a Kanban board — new, contacted, proposal, won, lost, or whatever stages suit your process. Moving a deal forward is a drag-and-drop action, not a manual field edit. At a glance, everyone on the team sees exactly where every deal stands, without opening a single spreadsheet tab.
Context: Nothing Gets Lost
This is where the spreadsheet approach struggles most. In Flitz, every call, meeting, and note logged against a lead builds an activities timeline attached directly to that lead. Even better, emails sent to and from a lead are auto-linked to their record, so the conversation history travels with the deal automatically — no copy-pasting, no separate inbox to check.
When someone picks up a lead they didn't originally work — because of a holiday, a handover, or simply a second opinion — the full picture is already there.
Metrics That Update Themselves
Because the pipeline is the single source of truth, pipeline value and close-rate metrics are calculated automatically rather than tallied by hand. That means an honest, current view of what's actually in the pipeline, not a snapshot from whenever someone last updated the sheet.
The Trade-Off Worth Taking
Consolidating into one connected system does mean a small adjustment: your team needs to actually log activity in one place instead of scattering it across email and personal notes. That's a real cost, and it's fair to weigh it.
But the payoff is proportional to how much the old way was costing you in lost context, awkward handovers, and manual reporting. For a business with more than a couple of active deals at any time, that trade-off tends to be worth it quickly.
From Won Lead to Customer, in One Click
One detail that spreadsheets simply can't replicate: when a lead is marked won, Flitz converts it into a full Customer record in one click. Name, email, phone, and currency carry over automatically — no re-typing, no risk of typos creeping into your customer master data.
Customer records are deliberately kept separate from the sales pipeline. They hold the things a closed deal actually needs going forward — logo, address, VAT details, and files — rather than cluttering the pipeline view with information that's only relevant post-sale.
Not Every Business Needs This — And That's Fine
Not every tenant on Flitz runs an active sales pipeline. That's why the CRM module is gated: businesses that don't need it can simply hide it, keeping their workspace focused on the modules — accounting, invoicing, HR, banking — that they actually use day to day.
Choosing What Fits
Spreadsheets aren't wrong. They're a reasonable starting point. But as your pipeline grows past what one person can track from memory, the cost of fragmented context — deals stuck in email threads, metrics nobody has time to calculate, handovers that lose information — starts to outweigh the simplicity that made spreadsheets appealing in the first place.
An integrated pipeline connected to email and work doesn't just replace the spreadsheet. It replaces the whole patchwork of tools that grew up around it.