By Luiz Otávio Gonçalves Published 2026-09-26

Kommo CRM in 2026: how to design governance (SLA, fields, and audit) so the CRM doesn’t become a mess

If you want to know how to make Kommo CRM truly deliver ROI in 2026, the answer is simple and not very glamorous: governance. It’s not “more automation,” not “more funnel,” not “more integration.” It is defining SLA, standardizing fields, creating audit and operating the CRM as a system — not as a salesperson’s agenda.

I have implemented Kommo in small, medium, and large operations, and the pattern repeats: when the CRM becomes a no-man’s land, the team might use it… but the manager can’t forecast revenue, marketing can’t close the quality loop, and the owner feels like they “paid a lot just to get another spreadsheet.” When governance exists, Kommo becomes an engine: organizes chaos, reduces downtime, increases conversion, and cuts rework.

What CRM governance is (in practice, no theatrics)

CRM governance is the set of rules and mechanisms that ensure 3 things:

• Data consistency (what enters the CRM enters standardized).
• Operational discipline (no one “skips a stage” without reason and without record).
• traceability (you see who did what, when, and why).

This is what makes Kommo stop being “just a tool” and become commercial infrastructure.

Who this is for (and who it’s NOT for)

Serves for operations that:

• have at least 2 people in sales (or 1 salesperson + 1 manager/owner) and need predictability;
• sell with lead volume (inbound, WhatsApp, SDR, paid traffic, referral) and suffer from inconsistent follow-up;
• want to scale without inflating the team (governance multiplies capacity).

DOES NOT serve (still) if you:

• don’t have a minimum process and want the CRM to “create a process magically”;
• aren’t willing to enforce usage and standards (CRM without enforcement becomes decoration);
• have a sales cycle so simple that a well-made spreadsheet solves it (for now).

If you’re in that last group, I’d start with the basics: routine and process. Then the tool. If you want an objective criterion, I detailed this in 5 signs your company needs to change software.

The biggest ROI killer in Kommo: a “pretty funnel” without rules

Kommo is quick to set up, and that’s good. But it also makes the classic mistake easy: building a “pretty” funnel with 12 stages, and not defining:

• what each stage means;
• What is the SLA movement criteria;
• which fields are mandatory;
• what the win/loss criteria are;
• how you audit usage.

Result: the funnel becomes opinion. Each salesperson interprets it differently. And when everything is interpretation, the data stops being data.

If you want guidance on structure by niche (without falling into generic templates), I also recommend reading CRM by niche: the number 1 mistake that destroys ROI — here I will specifically deepen governance within Kommo.

The 4 pillars I implement in governance in Kommo

When I join an operation, I don’t start by “installing Kommo.” I start by activating governance. These are the 4 pillars:

• Pillar 1 — Operational SLA: maximum time per stage and maximum first response time.
• Pillar 2 — Mandatory data and standardization: fields, lists, and filling rules.
• Pillar 3 — Audit and internal compliance: logs, responsible parties, and review routines.
• Pillar 4 — Data-driven management routine: weekly rituals and metrics the team can’t “dress up.”

Pillar 1: SLA that stops “leads quietly dying”

SLA is not bureaucracy. SLA is control of invisible losses. In Kommo, I define SLA at 3 levels:

• First response time (especially WhatsApp): e.g., 5 minutes during business hours.
• Maximum time stopped in the stage: e.g., “New lead” doesn’t stay more than 30 minutes without action.
• Maximum time without next task: lead without task = abandoned lead.

This ties directly to follow-up. If you still think follow-up is just “sending a message,” you’ll unlock a lot in Automatic sales follow-up: what it is and how to build it.

Pillar 2: mandatory fields (Kommo only becomes BI if you feed it properly)

Practical rule I use: if the data is necessary to decide or charge, it can’t be optional.

Examples of fields that almost always become mandatory (adapted by niche):

• Lead source (UTM/Channel/Partner): without this, marketing and sales fight in the dark.
• Reason for loss (closed list, no unlimited “others”): without this, you can’t optimize proposal or approach.
• Profile/segment (B2B: size, CNAE/segment; B2C: interest, unit, procedure).
• Next step (meeting, proposal, document sending) and date.

Here comes a discipline that changes the game: closed list for everything you want to measure. Open fields become creative text. Creative text doesn’t become metrics.

Pillar 3: audit (no witch hunt, with traceability)

The word “audit” scares people because many think it means punishment. For me, audit is what allows correcting the process and protecting results.

What I audit in practice:

• Leads without tasks (main indicator of abandonment).
• Stages with exceeded time (broken SLA).
• Reasons for loss (weekly and monthly trend).
• Activities per salesperson (volume and quality: call, meeting, proposal).
• Conversion by source (to stop scaling a bad channel).

Without this, the operation goes into “feeling” mode. And I don’t operate by feeling.

Pillar 4: data-driven management routine (no useless meetings)

CRM with governance requires a light and objective ritual. I like a routine like this:

• Daily (10 min): check SLA and leads without tasks.
• Weekly (30–45 min): pipeline review + bottlenecks + reasons for loss.
• Monthly (60 min): performance by channel + forecast + process adjustments.

This is not “another meeting”. It is less improvisation. And yes: when the routine is right, you reduce meetings because you stop putting out fires.

The playbook I use: from modeling to “CRM running without me”

I will show you the path I apply (and that works) to implement governance in Kommo without paralyzing the team.

Step 1 — Define the “real unit”: Lead, Contact, Company, and Deal

It seems basic, but this is where a lot of mess starts. The team needs to know:

• What is lead (input),
• What is Contact (person),
• What is Company (B2B),
• What is deal (negotiated opportunity).

If you duplicate deals, you lose history. If you duplicate contacts, you lose context. Governance starts with modeling.

Step 2 — Design the funnel with “stage definition” + entry/exit criteria

I don’t accept a stage without a written definition. Simple example:

It doesn’t need to be complex. It needs to be clear.

Step 3 — Implement “minimum fields” and anti-mess locks

My standard is to start with few fields and expand. What kills adoption is asking for 30 fields on day one. What kills ROI is asking for zero.

The balance is: minimum + mandatory fields where it matters. Example:

• Source (list)
• Reason for loss (list)
• Product/service of interest (list)
• Estimated value (number)
• Next step + date (task)

Step 4 — Automate what is rule (not what is exception)

Good automation is rule automation. Automated exception becomes an expensive bug.

Where I see the fastest ROI in Kommo:

• Automatic task creation upon entering a stage (no task = no owner).
• SLA alerts (internal) and escalation (manager).
• Distribution by queue/round-robin with capacity rule.
• Scheduled follow-up based on status (without becoming spam).

If you want to deepen tool choice and when to automate, I wrote this very straightforwardly in How to choose the ideal automation tool.

Step 5 — Create dashboards that demand behavior (not vanity)

Vanity dashboard is: “how many leads entered”. Dashboard that generates ROI is: “how many leads were left without action”.

I build dashboards focused on:

• SLA: % on time / late
• Contact rate: managed to talk to the lead?
• Conversion by stage: where it’s leaking
• Cycle time: how long to close
• Reason for loss: trend and root cause

How much Kommo costs (real data) and why this matters in governance

Price matters because governance has to respect reality: license, team, and volume.

Kommo charges with US$ per user/month (subscription). Prices change over time and may vary due to promotions and payment methods, so I keep a page always updated with numbers and account traps: How much does Kommo CRM cost? Prices and plans in 2026.

Why did I bring this up? Because if you have 10 users and the team doesn’t use it properly, you don’t have “a CRM problem”. You have a problem of Management costing in dollars.

Governance checklist (for you to apply tomorrow)

• 1) Each funnel stage has a written definition and entry/exit criteria.
• 2) Every opportunity has an owner and a future task (always).
• 3) First response SLA defined and monitored.
• 4) Minimum mandatory fields: source, reason for loss, product/service.
• 5) Reason for loss is a closed list (no freestyle).
• 6) Weekly audit: leads without task + SLA breached + losses by reason.
• 7) Monthly ritual: performance by channel + process adjustments.

When governance “takes hold”, what improves first?

In my experience, gains appear in this order:

• 1st Less lead lost due to forgetfulness (consistent follow-up).
• 2nd More predictability (more reliable pipeline).
• 3rd Better lead quality (marketing adjusts channel based on data).
• 4th Scale with fewer people (team capacity rises).

It’s not a miracle. It’s method + accountability + data.

In conclusion: Kommo doesn’t fail — operation without governance fails

I like Kommo because it’s fast, flexible, and very strong for operations that sell on WhatsApp. But flexibility without governance becomes chaos. If you want CRM that delivers ROI, the question isn’t “which tool”. It is: what execution standard you will sustain.

If you want me to design (and implement) this governance in your operation — SLA, fields, audit, automations, and management routine — the next step is simple: request a project.

FAQ — real questions about governance in Kommo CRM

The questions below are the ones I answer most in implementation and consulting.