If you sell through WhatsApp, Kommo CRM is only truly “worth it” when it shortens the path between the conversation and the paid proposal. The angle that almost no one explores is: catalog + proposal + automation inside the funnel. When this is well implemented, you reduce response time, standardize the offer, decrease pricing errors, and increase closing rates without inflating the team.
I am Luiz Otávio Gonçalves (a mechanical engineer who became a Digital Engineer). I don’t buy CRM for a “nice dashboard.” I implement what becomes process, data, and ROI. In this article, I get straight to the point: how I design this structure in Kommo for operations that sell on WhatsApp and need execution.
Who this is for (and who it’s NOT for)
It’s for you if:
- Your team sells through WhatsApp and wastes time assembling proposals “by hand” (PDF, spreadsheet, loose text, screenshot).
- You have price variations by package, plan, size, region, deadline, modality, etc., and this causes errors and rework.
- You want standardize the offer without becoming rigid (proposal with options and rules).
- You want to measure: time until proposal, acceptance rate and reasons for loss with data — not guesswork.
It’s NOT for you if:
- You still don’t have a minimally defined offer (each salesperson “invents” the proposal).
- Your volume is low and you close everything by referral with 5 messages (implementation becomes overkill).
- You want to “automate” to not sell. Automation speeds up a good process; a bad process just gets worse faster.
The real problem: the bottleneck isn’t the CRM. It’s the proposal.
In practice, most operations have funnels, tags, basic automations… but get stuck here:
- The lead asks for price.
- The salesperson leaves WhatsApp, looks for the table, asks in the group, opens Drive, copies and pastes…
- When they return, the lead has cooled off. Or they send the wrong price. Or they send a confusing long text.
This is time, it is Margin, it is Conversion. And it can be tackled methodically.
The playbook I implement: Catalog → Minimum qualification → Proposal in 1 click
I like to think of 3 layers within Kommo:
- Layer 1 — Essential data: few fields, but the right ones.
- Layer 2 — Offer rules: catalog, packages, conditions, and limits.
- Layer 3 — Execution automation: tasks, SLA, routing, and follow-up.
If you try to start with “nice” automation (automatic message, bot, AI), without having data and a tied offer, you create a noisy funnel and not a funnel that sells.
1) Define the minimum fields that unlock the proposal (without bureaucracy)
I see many people creating 30 fields and no one fills them. I prefer few fields with clear rules. Examples of fields that usually unlock a quick proposal:
- product/service (closed list)
- Model/Plan/Package (closed list)
- Quantity (number)
- Deadline/urgency (closed list)
- City/State (if price/logistics change)
- Lead source (to measure CAC and performance by channel)
Practical rule: if a field does not change the proposal or does not change the service priority, it is not a mandatory field at the start.
Want guidance on funnels by niche and where most go wrong? I explain in more depth here: CRM by niche: the number 1 mistake that destroys ROI.
2) Build a “sellable” catalog (not a dead PDF)
When I talk about catalog, it’s not a static “price list.” It’s a structure for the salesperson to select the right offer and generate a consistent proposal.
What I put in the catalog (regardless of niche):
- Commercial name of the item (what the client understands)
- Short description in 1 line (no institutional text)
- Price range or base price (when applicable)
- Conditions (deadline, warranty, scope, what is not included)
- Natural upsell (the next best package)
The goal is to reduce improvisation. If each salesperson “explains their own way,” you lose conversion and create operational noise in post-sale.
3) Turn WhatsApp into an execution track: SLA + task + next action
A catalog without execution becomes decoration. I tie this into 3 mechanisms:
- Response SLA by funnel stage (e.g., a new lead needs action within 5 minutes during business hours).
- Mandatory task at critical stages (e.g., “Send proposal” cannot exist without a task).
- Explicit next action (if the salesperson doesn’t define the next step, the lead disappears).
If you want to design governance so CRM doesn’t become a mess (fields, audit, standards), I’ve already written this very directly here: Kommo CRM in 2026: how to design governance (SLA, fields, and audit).
4) Quick proposal: what I automate and what I DO NOT automate
Now the central point: proposal.
What I automate (safely):
- Creation of the task “assemble proposal” when the lead enters the “Qualified” stage.
- Confirmation message of receipt + estimated time (e.g., “Within 20 minutes I’ll send you the options”).
- Automatic follow-up if the lead received the proposal and didn’t respond (with window and limit).
What I DO NOT automate in the pilot (to avoid destroying conversion):
- Sending a “blind” proposal without minimum qualification.
- Aggressive message sequence (this becomes spam and reduces responses).
- Sensitive negotiation (discount, exception, special deadline) without human validation.
If you want to do automatic follow-up the right way (without annoying the lead and without burning the number), I recommend reading: Automatic sales follow-up: what it is and how to build it.
How much does it really cost to put this live?
Let’s work with real numbers, no fantasy.
Kommo licenses: Kommo sells plans in US$ per user/month. The price varies by plan (and can change over time), so I prefer to point you to the updated analysis I maintain here: How much does Kommo CRM cost? Prices and plans in 2026 and also How much does the real Kommo cost per month?.
WhatsApp: if you are going to use official WhatsApp (API), there is a conversation cost charged by Meta (varies by country/category). This cost is not “from Kommo.” It is included in the account and, when you scale, it can become the largest budget item. I break down the calculation and where ROI gets stuck here: Kommo CRM with WhatsApp: how to calculate the real cost per conversation.
Implementation: it depends on your starting point (spreadsheet vs old CRM), volume of integrations, and process maturity. I don’t guess numbers without diagnosis. But I explain the real ranges and what goes into the project here: How much it costs to implement Kommo (implementation service).
How I design the funnel (practical example of stages that shorten the cycle)
A simple and extremely effective funnel for selling via WhatsApp with a quick proposal:
- New lead (Short SLA + screening)
- Contact in progress (minimum qualification)
- Qualified (define package/plan + generate proposal)
- Proposal sent (schedule follow-up date)
- Negotiation (exceptions with control)
- Closed — Won (handoff to onboarding/post-sale)
- Closed — Lost (mandatory reason + remarketing)
The “trick” is: the lead only moves to “Proposal sent” if the minimum fields are filled. Without this, the proposal becomes a lottery and the team “outsources” errors to sales.
Implementation checklist (executable in 7 to 14 days in small/medium operations)
- Day 1-2: map the offer (packages, variations, exceptions) and define minimum fields.
- Day 3-4: configure funnel + stages + loss reasons + basic SLA.
- Day 5-7: structure catalog (at least the 20% of items that generate 80% of revenue).
- Day 8-10: task and follow-up automations (simple, without overengineering).
- Day 11-14: team training + adjustments based on data (time to proposal, response rate, closing rate).
How to measure ROI of this setup (without self-deception)
I measure ROI with 3 metrics that don’t lie:
- Average time to proposal (decreased? you gained cash flow speed).
- Proposal acceptance rate (increased? your offer became clearer/standardized).
- Lead to sale conversion rate (increased? the funnel is performing end to end).
If you want to calculate automation ROI the right way (including hidden costs, maintenance, and hours saved), I left the method here: How to measure the ROI of business automations.
The 5 mistakes I see most (and that destroy ROI)
- 1) Catalog without rules: becomes a “menu” and the seller keeps improvising.
- 2) Too many fields: no one fills them, the CRM looks nice but useless.
- 3) Proposal without next action: send and wait for a miracle. Sales don’t work like that.
- 4) Aggressive follow-up: burns the number, irritates the lead, and lowers response.
- 5) Not measuring time to proposal: you think the bottleneck is the lead, but it’s the process.
Conclusion: Kommo is not a “WhatsApp CRM.” It is an execution track.
When I implement Kommo with catalog and quick proposal, the game changes because the team stops “fighting with the tool” and starts to execute a process: minimum data → consistent offer → quick proposal → smart follow-up → closing.
Do you want me to evaluate your scenario and tell you, without romanticizing, if it’s possible to shorten your sales cycle and unlock ROI with Kommo (or if it doesn’t make sense for you now)? Then the next step is simple: request a project.
FAQ
The questions below are the ones I hear most when I design this type of implementation.