Most Indian startup founders build their sales operations setup twice. The first time is by accident — a Google Sheet, a WhatsApp group, and the founder's memory. The second time is in a panic, after a ₹6 lakh enquiry sat unanswered for three days because nobody owned it and nobody noticed.
This is a plan to skip the panic. Ninety days, three phases, ₹-first the whole way — built for a founder running an early sales motion in India, not for an enterprise with a RevOps team. The goal is a sales operations setup in India that catches money before it goes cold, without the enterprise bloat you'll spend six months ripping out later.
TL;DR
- Days 0–30 — foundation. Five fields, one source of truth, one owner per lead. A spreadsheet is genuinely fine here. Track ₹ deal size and last-contacted date above all else.
- Days 30–60 — systems. When the sheet becomes a graveyard, graduate. Add prioritisation (which lead first?), follow-up discipline, and WhatsApp logging that takes 3 taps, not 3 minutes.
- Days 60–90 — scale. First sales hire, lead grading so a junior rep knows what to chase, and ₹-at-risk reporting the founder reads in 5 minutes a morning.
- Track money, not activity. "47 calls made" tells you nothing. "₹12 lakh in Grade A leads untouched for 48 hours" tells you everything.
- The whole stack costs under ₹10k/month for 3 reps. One saved deal pays for the year.
Days 0–30: Foundation — track five things, own every lead
A sales operations setup in India doesn't start with software. It starts with a decision: every lead has exactly one owner, and there is exactly one place the team looks. Two places is zero places.
In the first 30 days, a Google Sheet is the right tool. Don't apologise for it. With your first 50–100 leads and one or two people selling, a spreadsheet beats any CRM on speed and beats any process on simplicity. The mistake founders make isn't using a sheet — it's putting 22 columns in it.
Track five fields. That's the whole schema:
| Field | Why it earns its place |
|---|---|
| Lead source | Tells you where ₹ comes from. Kill the channels that don't pay. |
| ₹ deal size | The single most important number. Everything sorts by this. |
| Stage | Three values max: New, In Conversation, Closing. Not fourteen. |
| Last-contacted | The cold-lead detector. Anything past 48 hours is bleeding. |
| Owner | One name. No "team." No blank cells. |
Notice what's missing: lead score, custom fields, probability percentages, activity logs. You don't need them yet. With 60 leads, the founder's head still holds the context. The job of these 30 days is to externalise just enough that the context survives the founder's next bad week.
The ₹-first habit starts now. When you review the sheet, you don't ask "how many leads do we have?" You ask "how much money is in In Conversation, and which of it hasn't been touched in two days?" A founder who sorts by ₹ deal size descending and scans last-contacted dates is doing real sales ops with a free tool.
Days 30–60: Systems — graduate when the spreadsheet becomes a graveyard
There's a precise moment the spreadsheet stops working, and most founders feel it before they can name it. It's when you open the sheet on a Monday, see 40 open leads, and have no idea which three to call first. The sheet records reality. It doesn't act on it.
That's the graduation trigger — not headcount, not revenue, not a funding round. Three failures show up together around day 45:
- Prioritisation breaks. Forty open leads, no signal on which ₹8 lakh deal is hot and which ₹40k tyre-kicker is wasting the morning. The rep calls in the order they scroll, which is the worst possible order.
- Visibility lags. You find out a lead went cold on Friday's review, four days after it actually went cold. The ₹5 lakh was already gone by Tuesday.
- Follow-up depends on memory. "I'll call them tomorrow" is the most expensive sentence in early sales, because tomorrow there are new leads and the old ones quietly rot.
This is where a behaviour layer earns its keep — not a heavyweight CRM, a tool that does the three things above and nothing it doesn't need to. Leadkaun grades each lead A–F in under 500ms the moment it lands, so a rep opening their morning sees a Priority Queue, not a flat list. The Missed Opportunity Engine puts a rupee figure on what's going cold — ₹12 lakh in Grade A leads untouched for 48 hours is a sentence that changes behaviour, where "you have pending follow-ups" never did.
And the logging has to survive the field. The reason reps abandon CRMs is that logging a call takes six clicks between two meetings, so they don't, and your data becomes 30% of reality. Leadkaun's 3-tap WhatsApp logging treats WhatsApp as the first-class sales channel it actually is in India — the rep finishes the chat, logs it in three taps, and the founder's visibility stays honest. Importing your existing sheet takes one CSV upload, and setup runs about 60 minutes start to finish.
Don't build a 14-stage pipeline because the tool allows one. Keep the three stages from your sheet. The system's job in days 30–60 is prioritisation and discipline, not process theatre.
Days 60–90: Scale — the first sales hire and ₹-at-risk reporting
By day 60 the founder is the bottleneck, and that's the good problem. Now you scale, and scaling early sales ops means two things: the first dedicated sales hire, and reporting that runs in money.
The first sales hire is rarely a senior closer — at ₹50k–₹90k/month, an early-career rep who'll do volume is the realistic hire for most Indian startups. The problem with a junior rep is judgement: they don't yet know that the ₹9 lakh manufacturing enquiry from IndiaMART is worth ten of the ₹30k ones. So you don't rely on their judgement. You hand them a Priority Queue.
This is exactly what lead scoring buys you at this stage. When every lead arrives pre-graded A–F, a new rep on day one knows what to chase without a quarter of pattern-matching they don't have. The grade does the seniority. The rep does the calling. A junior hire with a graded queue often outperforms a senior hire working a flat list, because they're spending their hours on the right ₹.
The reporting also changes shape at scale. The founder can't read 200 leads a day, so the system reads them. The Morning Brief lands at 8:30 AM IST — before the day's first call — and it leads with money: what closed, what's at risk this week in rupees, which Grade A leads slipped past the follow-up window overnight. Five minutes of reading replaces an hour of opening the sheet and squinting.
Sales Rep Tracking matters here too, and the framing matters more. When a rep's numbers dip, the question is never "why is this rep lazy." It's "what in the situation made the follow-up slip?" Maybe 60 leads landed in one day and the queue overflowed. Maybe the ₹ deal sizes were all small and the rep deprioritised correctly. Blame the situation, find the gap, fix the workflow. The data is there to coach the system, not to indict the person.
The lightweight stack and what it costs
Here's the entire sales operations setup for a 3-rep Indian startup at the end of 90 days:
- Storage / source of truth — a behaviour layer that holds leads, grades, and history. Replaces the sheet once you graduate.
- The selling channel — WhatsApp, logged in 3 taps, not bolted on as an afterthought.
- Prioritisation + reporting — Grade A–F scoring, Priority Queue, Missed Opportunity Engine, Morning Brief.
On Leadkaun's pricing, that's ₹999 per rep/month on Starter, ₹1,999 on Growth, or ₹2,999 on Scale. Three reps on Growth is ₹5,997/month — see the full pricing for what each tier includes. Put that next to one missed ₹6 lakh deal and the maths isn't close. The stack pays for itself the first time it catches a Grade A lead before it goes cold.
What's deliberately not in this stack: a marketing automation suite, a 14-stage pipeline, custom dashboards, a RevOps hire. Those are real tools for real problems you don't have at 3 reps. Adding them now is how startups end up with software that's 80% unused and a setup they'll rip out at 30 reps.
The 90-day arc, in one line
Days 0–30, externalise just enough — five fields, one owner, a sheet. Days 30–60, graduate when the sheet turns into a graveyard, and add prioritisation, discipline, and honest logging. Days 60–90, hire your first rep into a graded queue and run your reporting in rupees. The founder who follows this arc isn't building enterprise sales ops. They're building the smallest system that stops money going cold — which is the only sales operations setup an early-stage Indian startup actually needs.
See it on your own leads — book a 15-minute demo and we'll show you a Priority Queue and a ₹-at-risk number built from a sample of your data.