Zoho CRM: leads, deals, and stage design

Leads and deals usually sit in separate modules, and the conversion point is the most consequential decision in the account. It determines what a lead count means, what a pipeline total contains, and which reports people trust. Three approaches are common:

• Convert on first substantive contact. Deals accumulate early, the pipeline looks larger, and forecast accuracy depends on stage discipline later.
• Convert at a qualification threshold. The definition has to be written in observable terms, or two people qualify differently and the pipeline becomes an opinion.
• Convert manually, by the owner of the record. Workable where volume is manageable, but the criterion still needs stating, because the conversion rate otherwise measures enthusiasm.

Whichever is chosen, record what has to be true at conversion. That single sentence prevents most of the argument that later appears in a pipeline review.

1. List the moments where the buyer's situation genuinely changes, not your team's activity.
2. Give each stage one exit criterion that can be checked from the record.
3. Name an owner for each stage, even where the same person owns several.
4. Decide what the stage requires to be recorded — the fields the review will read.
5. Stop. Where two stages would share an exit criterion, they are one stage.

Stages that reflect internal effort ("proposal drafted") tend to grow in number and lose meaning. Stages that reflect verification ("scope agreed with the person who signs") stay few and stay readable.

Ownership answers who is accountable for a record now; sharing answers who can see it. Both are process decisions with configuration consequences. Decide the intent first — who must see a deal to do their job, who must not — and then express it in roles and sharing. Where sharing is widened to solve one person's access problem, the account ends up with visibility nobody chose.

On rules: keep the set small enough to describe. Each rule should have a stated purpose, one trigger, and an owner. Rules whose purpose cannot be stated are candidates for disabling and observing rather than immediate deletion, because the effect of removing them is not always obvious.

The example below is hypothetical and describes a pattern rather than a client account.

This work is scoped as Zoho CRM consulting, part of the Operations & Systems capability and the wider CRM consulting scope. Edition and permission checks happen before a scope is written, so the configuration matches what the account actually supports.