If you want to use the Kommo CRM to traditional B2B outbound and stop depending on seller's WhatsApp to close, the answer is: you need to design a funnel by commitment stages, with SLA, cadence and control points (tasks + automations) — and not a generic pipeline “New lead > Proposal > Closed.” This is what I implement when the company wants predictability, governance, and measurable ROI.
I am a mechanical engineer by training and became a digital engineering implementer in commercial operations. Method > improvisation. DATA > guesswork. And the truth is simple: outbound with “loose” WhatsApp still works when small, but breaks down when you need to scale, replace people, train quickly, and have forecast management.
The real problem: your “outbound” has become a collection of WhatsApp conversations
In Brazilian B2B, almost every outbound operation starts like this:
- Cold/semi-cold list (LinkedIn, purchased database, referral, event, old inbound).
- SDR sends message on “personal” WhatsApp and does follow-up “from memory.”
- When it heats up, it passes to the closer… via audio and screenshot.
- The company owner asks for numbers and gets “it's fine, we're talking to quite a few people.”
This is not a process. This is survival. And the hidden cost is high: lost lead, delayed follow-up, false forecast, and dependence on specific people.
My goal when I implement Kommo in B2B outbound is to turn conversations into a manageable pipeline. It's not just “putting in CRM” — it's building a commercial system.
Who this is for (and who it’s NOT for)
Serves If you:
- Sells B2B with an average ticket that justifies a process (recurring service, consulting, software, industry, engineering, distribution).
- Has or wants to have SDR/BDR + closer (even if it's one person in each role).
- Wants predictability and goal control with conversion data, not feeling.
- Needs to centralize history (calls, emails, WhatsApp, meetings) to reduce seller dependence.
DOES NOT serve (or it will be overkill) if you:
- Close sales in 1 touch, no follow-up, and your cycle is minutes (e.g., cheap fast-moving product).
- Not willing to standardize stages and enforce SLA. CRM without enforcement becomes just a nice database.
- Wants “a robot that sells alone” without a team or routine. That's hype.
The new angle that almost no one applies: pipeline by “commitments” (not by “internal phases”)
The number 1 mistake in B2B outbound is designing the funnel with names that only make sense internally (“In contact,” “In negotiation”). This becomes subjective and impossible to measure.
I design the funnel by verifiable commitments. Practical example of structure (you can adapt):
- 1) Lead qualified for prospecting (has minimum ICP and valid contact).
- 2) 1st touch executed (WhatsApp/email/call recorded).
- 3) Responded / opened conversation (there was interaction).
- 4) Diagnosis scheduled (date/time set).
- 5) Diagnosis done (checklist filled in CRM).
- 6) Proposal sent (document attached + value + next action).
- 7) Negotiation in progress (objections mapped).
- 8) Closed won / Closed lost (mandatory reason).
Notice: each stage has “proof.” This is what turns Kommo into a machine, not a showcase.
SLA in outbound: what I implement to stop missing timing
Outbound is a timing game. The difference between winning and losing is often responding fast and following the cadence.
I like to handle SLA in 3 layers:
- 1st touch SLA: how long after the lead enters they receive the first contact.
- Follow-up SLA: maximum interval without next action (automatic tasks).
- Handoff SLA (SDR → closer): clear rule of when and how to pass.
In Kommo, this becomes practice with:
- Mandatory tasks by stage (without task, the lead “dies”).
- Task creation automation when moving stage.
- Mandatory fields (e.g.: loss reason, origin, ICP, company size).
- Routing rules (e.g.: by region, by segment, by portfolio).
If you want a more advanced design of WhatsApp operation within Kommo, I recommend you read my guide on queues and routing: Kommo CRM with WhatsApp: how to design SLA, queues, and routing. There I go into operational detail.
Outbound cadence: it's not “sending more messages,” it's controlling events
A good cadence has 2 things: multichannel and attempt control. If you only use WhatsApp, you become hostage to “didn't see” and “I'll reply later.”
What I structure in Kommo:
- Sequence of events (e.g.: D0 WhatsApp, D1 call, D3 email, D5 WhatsApp, D7 LinkedIn).
- Stop rule (e.g.: responded → goes to “Responded” stage and changes cadence).
- Attempt tag (e.g.: Attempt 1/2/3…) to measure effort vs return.
- Standardized reasons (no fit, already has supplier, timing, no budget, not decision maker).
This is what allows you to measure response rate by channel and adjust quickly. If you want a basis to design follow-up the right way, this post helps: Automatic sales follow-up: what it is and how to build it.
What changes when you stop depending on the seller's WhatsApp
When the company moves from the “personal WhatsApp decides everything” model to “CRM decides the process,” you unlock:
- training: onboarding becomes checklist + clear stages (not “João's shadow”).
- Management: the manager sees bottleneck by stage, not “conversation volume.”
- Predictability: forecast based on conversion rate, not hope.
- scale: you add people without causing operational chaos.
- Governance: history stays in the company. If the salesperson leaves, the pipeline doesn’t disappear.
Kommo price (real data) and what you need to account for
I won’t make up a price here because it changes by region, promotion, currency, and commercial policy. The real and updated data I maintain is in this post: How much does Kommo CRM cost? Prices and plans in 2026.
Now, editorial honesty: Kommo’s cost is not just the license. In outbound B2B, it usually also includes:
- WhatsApp integration (ideally official/API, depending on strategy and volume).
- Lead source (database, enrichment, LinkedIn, traffic, etc.).
- Operational discipline (task routine and auditing).
- Implementation (funnel design + fields + automations + training).
If you want to learn how to measure automation ROI and stop buying tools blindly, read: How to measure the ROI of business automations. That’s the game: putting numbers on what today is subjective.
Blueprint: how I implement Kommo for outbound B2B in 10 steps (execution)
- 1) I define ICP and qualification criteria (3 to 7 objective criteria, no fluff).
- 2) I design the funnel by commitments (proofs per stage, as I showed above).
- 3) I create fields that become data (segment, size, pain, decision maker, competitor, reason for loss).
- 4) I standardize source and campaign (without this, ROI becomes a guess).
- 5) I implement cadence with automatic tasks (scheduled follow-up, with SLA).
- 6) I implement routing (who takes what and why).
- 7) I create SDR → closer handoff rules (when it passes, what needs to be filled, and what the minimum “delivery” is).
- 8) I implement checklists at critical stages (e.g.: Diagnosis done: require filling 5 questions).
- 9) I train the team with real simulation (it’s not a tutorial; it’s a real scenario with a real lead).
- 10) I activate metrics dashboard and weekly routine (response rate, show rate, conversion per stage, average cycle).
How I prove ROI in outbound (without guessing)
ROI in outbound is not “more conversations.” It is improving conversion rate and reducing cost per opportunity/client.
I like to use a simple and executive model:
- Input: leads prospected per week + attempts per lead.
- efficiency: response rate + scheduling rate + show rate.
- Conversion: diagnoses done → proposals → closings.
- time: average cycle (days) and follow-up SLA.
- Savings: hours saved with automation and rework.
When the funnel is well designed, you quickly see where to attack: if the problem is in list/ICP, in messaging, in follow-up discipline, or in the proposal.
Traps that make the project stall (and I cut them early)
- Generic pipeline without verifiable commitment (becomes subjective).
- Too many fields (the team doesn’t fill them; data becomes garbage).
- Automation without rules (robot pushes wrong lead and annoys client).
- No process owner (CRM needs a responsible person, not “everyone takes care”).
- No management routine (if there’s no meeting and audit, the CRM dies in 30 days).
I’ve seen dozens of operations “buying Kommo” and failing because they tried to improvise the process. I don’t do that. I implement digital engineering: rules, metrics, routine, and continuous improvement.
Table: signs that your outbound is ready for Kommo (or not yet)
| Sign | If you are here… | What I would do |
|---|---|---|
| You have a clear ICP | Can say “for whom yes and for whom no” | Implement funnel by commitments and start measuring conversions |
| Your team does disciplined follow-up | There is a routine, even if manual | Automate tasks and SLA to gain speed without losing control |
| You don’t know why you lose | Loss is “disappeared” | Mandatory loss reason + diagnostic checklist |
| Pipeline depends on 1 salesperson | Without them, no one understands the status | Centralize history and standardize handoff |
| You want scale | You will hire SDR/closer | Routing + objective stages + weekly dashboard |
Practical conclusion
Kommo in outbound B2B works very well when you use it the right way: funnel by commitments, SLA, cadence and data. The goal is not to “organize conversation.” It is to build an operation that closes with predictability and doesn’t collapse when you change people or try to double volume.
If you want me to design and implement this in your operation (with funnel, automations, metrics, and training), the next step is simple: request a project.
FAQ
The questions below are the ones I answer most when the topic is Kommo + outbound B2B.