If you want to use the Kommo CRM to structure SDR/BDR and do outbound that closes (and not just “filling the funnel”), the correct way is to design a funnel with operational stages, activity cadence and Passing rules — and not copying a generic pipeline like “New lead > Contact > Proposal > Closed”. When I implement Kommo for outbound, I start with what delivers ROI: response speed, follow-up consistency, and connection rate per channel, all measured inside the CRM.
This article is about Kommo applied to active prospecting (SDR/BDR), with an angle that almost no one executes well: activity-oriented funnel (what the SDR does) and not just status-oriented (what the lead “is”).
Who this is for (and who it’s NOT for)
It's for:
- Operations with SDR/BDR (1 to 30 people) doing outbound via WhatsApp/call/email/LinkedIn.
- B2B businesses and mid-ticket services that need cadence: industry, software, consultancies, energy, premium clinics, real estate with internal team.
- Companies that accept the basics: process > improvisation and data > guesswork.
Does NOT work for:
- Those who want “a CRM that prospects itself”. Kommo is not a miracle, it’s leverage.
- Operation without validated offer (when you don’t even know who buys, for how much, and why).
- Team that doesn’t follow minimum routine (logging contact, completing tasks, recording loss reason). Without this, it becomes an expensive spreadsheet.
The number 1 mistake in outbound CRM: status pipeline without cadence
Outbound doesn’t fail due to lack of leads. Outbound fails due to lack of sequence. Most build the funnel in Kommo as if it were inbound: “lead arrived, conversation, proposal”. But in outbound you need a pipeline that “pulls” the SDR to execute the next action, with deadlines, and a clear reason to move the card.
If you haven’t designed your cadence yet, I also recommend reading: Automatic sales follow-up: what it is, why almost everyone does it wrong, and how to set it up. Here I will show how I turn this into a funnel inside Kommo.
The funnel design I implement in Kommo for SDR/BDR (practical model)
I separate into 2 pipelines when it makes sense:
- Pipeline 1: Prospecting (SDR/BDR) — goal: generate qualified meeting / opportunity.
- Pipeline 2: Sales (Closer/AE) — goal: proposal, negotiation, contract.
If your operation is small (1 to 3 people) you can start with 1 pipeline and evolve later. But when there is an SDR → Closer handoff, separating avoids mess and protects metrics.
Prospecting Pipeline (SDR): stages that work in real life
Example of stages (adjust to your cycle):
- List / Imported Lead (still no contact)
- 1st attempt (D0) (WhatsApp or call)
- Cadence in progress (D1 to D12, for example)
- Connected (answered / picked up)
- Qualification (pain, timing, authority, budget — whatever your business uses)
- Meeting scheduled
- Passed to sales (handoff)
- Lost (reason)
The trick is here: “Cadence in progress” is not a generic stage. It needs to be tied to mandatory tasks and execution SLA. If the lead stays “stuck” in this stage, the system has to alert loudly.
Cadence: what I set as standard (no fluff)
Cadence is a script of attempts by channel and time. A simple and executable example:
- D0: WhatsApp 1 + call 1
- D1: email 1 (short) + WhatsApp 2
- D3: call 2
- D5: WhatsApp 3 (with proof/social)
- D8: email 2 (breakup/“closing here?”)
- D12: last attempt + loss reason
This is not a “recipe”. It’s a starting point. What matters is data: response rate per channel, connection rate by time slot, conversion by segment.
How I translate this into Kommo (to turn it into execution, not theory)
Kommo is powerful when you use: tasks, automation and pipeline rules to lock the right process. In practice:
- Mandatory tasks per stage: entered “1st attempt”, creates automatic WhatsApp + call task due the same day.
- Gatekeeper: doesn’t allow moving to “Qualification” without filling key fields (e.g., segment, size, main pain).
- Visible SLA: lead without future task = dead lead. I configure it so it’s impossible to ignore.
If you want to understand Kommo from lead to closing before setting anything up, this speeds it up: How Kommo CRM works in practice: from lead to closing.
The 5 fields I consider “non-negotiable” in outbound
Without fields, you have no metrics. Without metrics, you don’t optimize. I practically always implement:
- ICP / Segment (e.g., metallurgical industry, clinic, real estate)
- List source (old database, referral, event, scraping, LinkedIn etc.)
- Contact status (responded, viewed, answered, invalid number)
- Loss reason (SDR) (no fit, no timing, no response, competitor, etc.)
- Next step (meeting, send material, follow up in X days)
What to truly measure to prove Kommo’s ROI in outbound
If you only measure “how many opportunities came in”, you’re blind. I first look at activity metrics (leading indicators), then at result metrics (lagging indicators).
| Metric | Why it matters | Where it hurts when it's bad |
|---|---|---|
| SLA 1st attempt (time until 1st contact) | Speed increases response rate | Lead cools down, team improvises |
| Overdue tasks by SDR | Shows cadence discipline | Pipeline turns into a “graveyard” |
| Connection rate (response/attendance) | Validates list and channels | You waste energy on the wrong lead |
| Show rate (meeting scheduled vs held) | Shows scheduling quality | Full schedule and empty cash register |
| SQL rate (meeting held → real opportunity) | Shows qualification | Closer becomes an “order taker” |
If you want a guide to put ROI on paper (and stop “thinking it improved”), read: How to measure the ROI of business automations. I use this logic for CRM + automation too.
Price (real data) and what you need to include beyond the license
Kommo works with license per user (recurring charge). I won’t guess the value here because price varies by plan, currency, payment method and promotions, and changes over time. The reliable (and updated) data is in this post of mine: How much does Kommo CRM cost? Prices and plans in 2026.
Now, what almost everyone gets wrong in the calculation is thinking “CRM = monthly fee.” For outbound, you should add:
- Implementation time (process, fields, automations, reports, training)
- Integrations (lead capture, enrichment, telephony, official WhatsApp if applicable)
- Governance: someone needs to maintain data standards and routine
Want a project range and what goes into a real implementation? I break it down here: How much it costs to implement Kommo (implementation service): real price ranges and what’s included in the project.
Kommo + WhatsApp in outbound: where it works and where it fails
Outbound via WhatsApp works when you have:
- Short copy and contextual (no long text)
- List with minimum fit (decent ICP)
- Cadence (not mass blasting)
- Daily ritual of the SDR to clear tasks and qualify
It goes wrong when you try aggressive automation, mix unofficial channels and then get surprised by blocking/banning. If WhatsApp is the heart of your flow, you need to understand the basics of integration and risk: Kommo and WhatsApp: official integration (API) vs unofficial and why this decides if you get banned.
The 4 biggest mistakes blocking Kommo ROI in SDR teams
- 1) Not having a definition of “good lead”: SDR becomes a curious person's attendant.
- 2) Pipeline without rules: everyone moves cards their own way, report becomes a joke.
- 3) Too many fields: team stops filling, you lose tracking. Start with the minimum that drives decisions.
- 4) No weekly review routine: outbound needs fine tuning. If you don’t review loss reasons, ICP and message, you just repeat the mistake faster.
10-day implementation checklist (minimum viable to start selling)
I like to execute fast and improve with data. A practical path:
- Day 1-2: define ICP, offer, qualification criteria and loss reasons
- Day 3: design SDR pipeline and Sales pipeline (separate or not)
- Day 4: create mandatory fields and simple layouts
- Day 5-6: set up task automations by stage + SLA
- Day 7: import pilot list and run first cadence
- Day 8: adjust copy and objections based on real responses
- Day 9: minimum report (SLA, overdue tasks, connection, meetings)
- Day 10: training and daily SDR “ritual” (execution and CRM hygiene)
This checklist is not a “nice setup.” It is to activate operation and produce quick ROI signals (better contact rate, more meetings, fewer forgotten leads).
Conclusion: Kommo is not the secret — the secret is the method
Kommo is a strong tool for outbound because it allows you to build process, implement cadence, optimize follow-up and scale with predictability. But it only pays off when you treat CRM as an operation: rules, routine and data.
If you want me to design and implement this in your company (pipeline, automations, dashboards, SDR playbook and training), the next step is simple: request a project.
FAQ — Kommo for SDR/BDR and outbound
The questions below are the ones I get most when the topic is Kommo for active prospecting.