Sales behaviour, end to end

Why this matters for Indian B2B specifically

Indian SMB sales runs on volume and speed in a way that breaks a pure record-keeping approach. Leads pour in from IndiaMART, JustDial, TradeIndia, Sulekha, website forms, Google Ads, and property portals — hundreds a month for a mid-sized team — and the serious buyers reach out after hours, on WhatsApp, on their own time. WhatsApp is now the default business channel here: it has more than 500 million users in India, and a Kantar study cited by Meta found 91% of online Indian adults message a business at least weekly. A workflow that assumes reps sit inside a CRM typing structured updates simply doesn't survive contact with that reality.

The research on where deals leak is blunt. A Harvard Business Review audit of 2,241 companies found the average firm took about 42 hours to respond to a web lead, and 23% never responded at all — while contacting a lead within an hour made it roughly 7 times more likely to qualify. Separately, InsideSales research reported that only about 27% of inbound web leads are ever contacted by a rep, meaning the majority of demand a business pays to generate is never even worked. And Salesforce's State of Sales report found reps spend just 28% of their week actually selling; the rest goes to admin, data entry, and figuring out who to call next.

Add it up and the Indian SMB problem isn't a missing database — most teams already have a CRM or a spreadsheet. It's that judgement doesn't scale. At ten leads a day a good rep holds priority in their head; at a hundred, spread across five portals and a WhatsApp inbox, they can't, and the ₹40 lakh buyer gets the same treatment as the tyre-kicker. That is exactly the gap a Sales Behaviour OS is built to close — and a gap another dashboard doesn't touch.

How to instil sales-behaviour discipline

The mechanics of doing this well follow a simple chain: grade, then prioritise, then surface the money at risk, then wrap it in daily rituals. Grading comes first because it is the objective input everything else depends on. Score each lead on Fit (does it match your ideal customer — industry, geography, role, budget), Intent (how engaged it is right now, based on real signals like a pricing question or a WhatsApp reply), and Quality (is the data even usable). Keep the weights fixed and transparent so a rep can always see why a lead is Grade A rather than trusting a black box — you configure your ideal-customer profile, not the scoring maths.

Prioritisation is where behaviour actually changes. A Priority Queue takes the graded leads and ranks them so the highest-intent, highest-value lead a rep hasn't yet contacted is always on top. The rep stops deciding who to call — a decision they get wrong under load — and starts working a list that is already right. Then surface the cost of inaction in rupees: instead of '12 overdue tasks', show 'this much revenue is sitting in Grade A leads that have gone past their follow-up window.' A number in rupees is a number a sales head acts on; a task count is noise.

Rituals are what make it stick. A role-specific morning brief tells each rep the handful of leads that matter today and tells the manager where the team is leaking. A weekly review looks at leading indicators — response time to Grade A, follow-up completion, whether the right lead was worked next — not just the lagging closed count, which arrives too late to coach on. And logging has to be near-frictionless: if recording a call or a WhatsApp outcome takes a form nobody fills, the data rots and the whole chain breaks. The discipline is only as real as the data is complete.

Common mistakes teams make

The first and most common is confusing activity with behaviour. A dashboard that celebrates 200 calls a week rewards busyness, not judgement. A rep can hit every activity target by dialling the easy, low-value leads and still miss the two enquiries that would have made the month. Activity is volume; behaviour is which lead, how fast, followed up how well — and only the second predicts revenue.

The second is treating the CRM's stored fields as if they were a plan. A record answers 'what happened to this lead?' It does not answer 'who should I call in the next hour?' Teams that expect their system of record to also drive the day end up with reps who dutifully update stages after the fact and still work the wrong leads in real time.

The third is over-automating outreach and calling it behaviour change: bolting a sequence tool onto a messy pipeline just sends more messages to badly-graded leads and scales the mistake. The fourth is coaching on effort instead of signal — 'try harder', 'be more disciplined', with nothing measurable to point at. Without a slow-Grade-A-response number or a dropped-follow-up rate, a review becomes a vibe check, and it slides into micromanaging because the manager has nothing concrete to reference.

How Leadkaun approaches it

Leadkaun is a Sales Behaviour OS built for Indian SMB B2B teams, and it is deliberately the layer your CRM is missing rather than a replacement for it. Your CRM keeps doing what it is good at — contracts, records, reporting. Leadkaun sits in front of it and drives the behaviour: it grades every lead A–F across Fit, Intent, and Quality, and because those weights are fixed and transparent, a rep can always audit why a lead landed where it did. Intent decays when a lead goes silent, so a Grade A from two weeks ago doesn't block genuinely hot leads underneath it.

From those grades it builds each rep a Priority Queue — the one screen they open every morning, re-ranked live so the most valuable un-contacted lead is on top. The Missed Opportunity Engine flags leads that have gone stale past their grade's window and rolls up the ₹ at risk, so the leak shows as money, not a task backlog. A role-specific morning brief goes to reps and managers, follow-up cadences keep the next touch scheduled, and Rep Tracking turns leading indicators — response time, follow-up completion, missed-lead recovery — into a scorecard managers can coach on without hovering.

The register throughout is honest about what the product is. WhatsApp logging is manual and fast — three taps to open your own WhatsApp and record the outcome as a signal — not an automated messaging integration. The numbers a team sees are its own: where we describe rupees at risk, that is your pipeline valued by your data, not a promised result. That honesty is the point of the category. A behaviour layer earns trust by showing reps exactly why the queue is ordered the way it is, which is what makes them actually work it.

Getting started and what to measure

You don't rip anything out to start. Point your ideal-customer profile — the industries, geographies, decision-maker roles, and budget bands that define your best customers — set your SQL thresholds, and import your leads by CSV (Indian amount formats like ₹1,50,000, 2.5L, and 1Cr parse natively). The moment leads land, they are graded and the queue is ranked; your CRM stays exactly where it is.

Then measure the leading indicators, not just the closed count: first-response time to Grade A leads, follow-up completion rate, how much of the week goes to selling versus admin, and the rupee value recovered from leads that were about to slip. These move before revenue does, which is what makes them coachable. When a weekly review points at a specific slow Grade A response instead of a rep's general effort, accountability stops feeling like surveillance and starts feeling like the job getting easier.