One client costs 1,000 calls

The chain, as it actually happens

So far, so familiar. Here is the multiplication nobody does: this firm closes one client from every twenty leads. Twenty leads, at two leads per hundred calls, is a thousand calls. Not a thousand conversations -- a thousand dials, six hundred of which nobody even answered.

One client = 1,000 calls = 400 pickups = 60 real conversations = 20 leads.

Every call is worth Rs 50 -- including the unanswered ones

A client is worth roughly Rs 50,000 a year to this firm. Divide by the thousand calls it takes to win one and every single dial is worth about Rs 50 -- the answered and the unanswered alike, because you cannot have the forty pickups without the hundred attempts. The rep who makes 150 calls today did Rs 7,500 of expected work. The rep who made 60 because “nobody was picking up” left Rs 4,500 on the table -- and without the chain, nobody in the room can see that number to say it out loud.

This is also why “call quality over quantity” -- true as far as it goes -- becomes an alibi in teams that never did the arithmetic. Quality decides your ratios. Quantity decides how many times the ratios get to work. You need both, and you can only manage what you have actually multiplied out.

Run it backwards and targets stop being moods

The chain becomes useful the moment you run it in reverse. Say the firm wants five new clients this month. That is not a wish, it is a worksheet: five clients means a hundred leads, which means five thousand calls, which across twenty-six working days means 192 calls a day for the team -- 64 each for three callers. Suddenly the monthly review writes itself: either the calls happened and a ratio underperformed (a coaching problem, and the chain tells you which stage), or the calls did not happen (a different conversation entirely). What it can never be again is a mystery.

Do it for your own business now -- the calculator takes two minutes and runs entirely in your browser. Enter the four numbers the way you would say them aloud, and it hands back what your target actually asks of each caller, per day. If the answer looks impossible, better to meet that fact in a calculator than in a quarterly review.

Three honest caveats

• Your first ratios are guesses. Write them down anyway. A stated guess can be corrected by a month of real outcomes; a vague feeling cannot be corrected by anything.
• Chains are not laws. Referrals, repeat clients and seasonality all bend the numbers. The chain is the baseline that makes the bending visible, not a machine that replaces judgement.
• The number is a pace, not a whip. The purpose of 64-calls-a-day is that everyone agreed to it in daylight -- not that someone stands behind the team counting. Teams that use the chain as surveillance lose the honesty that makes the ratios true.

Where we fit, stated plainly

We make Saahak, a CRM for Indian SMB sales teams, and the reason we care about this arithmetic is simple: once a team knows its daily number, the bottleneck becomes actually making the calls -- and that is a queue problem. Saahak’s calling queue orders the day (never-called first, cooling-off between retries, works offline), official WhatsApp follows up, and the outcome of every call moves the pipeline as a side effect of logging it. The arithmetic above stays yours either way -- the calculator needs no signup and this article works the same if you run your chain on a whiteboard.