Every Lead Became an Opportunity. Their Close Rate Was a Guess.

The Setup

The same real estate coaching company. After we fixed the duplicate lead problem, we started looking at the downstream: what happened to those leads once they entered the pipeline. What we found was worse.

The Problem

Every lead in the CRM auto-converted to an opportunity on capture. That meant "opportunity count" was functionally identical to "lead count," which made close rate — calculated as deals closed divided by opportunities — a meaningless number.

It got worse. The CRM had no standardized status set. Setters and closers had been creating their own statuses over time. One of them read "Call Booked with Adam." Adam left, and every lead sitting in that status was stranded — nobody worked them, because working them would have meant being Adam.

The same lead often appeared across multiple opportunity records. The setter would create one. The closer would create another. A follow-up sequence would create a third. The CEO looked at his pipeline dashboard and saw a healthy number of active opportunities. He was counting the same people more than once.

What We Found

The opportunity count was not a count of opportunities. Every lead auto-converted on capture, and a single lead could sit across several opportunity records at once, so the pipeline number and the close rate underneath it were both fiction.

The person-specific statuses had created a graveyard of orphaned deals. The pipeline looked active because nothing ever cleaned itself up.

What We Built

Seven standardized lead statuses. Twelve setter-specific fields. Fifteen closer-specific fields. Every status maps to a lifecycle stage; every field maps to a metric the CEO actually needs for a decision.

We built the status transitions as a state machine — a lead can only move between statuses that make sense. The CRM enforces it. You can't put a lead in "Contract Sent" without "Proposal Discussed." You can't create a second opportunity for the same lead without explicitly orphaning the first one.

The person-specific statuses were migrated to new owners or archived.

Build time: eight weeks.

The After

For the first time, the CEO could look at his pipeline dashboard and know what the number counted. Every lead had been auto-converting on capture, and the same lead could sit across several opportunity records at once. Both were fixed.

Closing

Once the pipeline logic was honest, every downstream decision got easier.