# Making sure the team calls the right people first.

> Bhavin built a lead-ranking A/B playground at a US consumer app. The reported revenue improvement was 5–8%. Experiment details that remain unconfirmed are left out.

Canonical page: https://developerlabs.in/work/lead-ranking/

Attribution: Work delivered by Bhavin at an anonymized US consumer app. The 5–8% revenue figure is reported. Experiment duration, sample size, significance, ranking method, and technical stack are not available to publish.

Reported outcome: +5–8% — Reported revenue improvement.

## A new ranking only matters if the business result improves.

At a US consumer app, the team needed a way to tell whether a change in lead order actually helped. Calling people in a different sequence is not useful on its own. It has to show up in the outcome that matters.

## A playground for comparing rankings.

Bhavin built a lead-ranking playground so alternatives could be compared through A/B experimentation. That made ranking behavior something the business could examine and test, rather than a one-off change.

The ranking method, experiment allocation, and technical stack are not published here. Those details remain unconfirmed.

## The reported outcome

The reported revenue improvement was 5–8%. That figure is reported. Experiment duration, sample size, and significance are not available to publish, and a result like this does not automatically transfer to another audience, ranking approach, or business.

When Developer Labs takes on similar work, the same standard applies: test the change against a business outcome, and be explicit about what the evidence does and does not support.

Bhavin wrote a longer account on his personal site: [Making sure the team calls the right people first](https://bhavinkamani.com/work/lead-ranking/).

