You made the first sales hire in India that your young company has ever made. The offer letter is signed, they start Monday, and now there's a quieter question sitting on your desk: what do you actually hand this person on day one? Most founders answer it badly. They buy a CRM the week before — the one a friend at a 200-person company swears by — set up nothing, and watch their new rep spend the first fortnight fighting software instead of calling leads.
The first sales hire in India usually walks into a startup with no playbook, no pipeline that lives anywhere except the founder's head, and a list of leads scattered across three WhatsApp chats, a Google Sheet, and a few business cards. The tools you give them either fix that on day one or quietly make it worse. This is the short list of what helps, and the longer list of what to skip.
TL;DR
- Give your first rep three things on day one: a single source of truth, fast logging, and a priority queue that says who to call next. Skip everything else.
- A heavy CRM hurts a one-rep team — it's built for an ops person to configure and a manager to report on, neither of which you have yet.
- Set targets in ₹, not in activity counts. "Close ₹8L this quarter" beats "make 50 calls a day" — the second one games easily.
- The right setup takes about 60 minutes, imports your existing CSV or Google Sheet, and lets the rep start calling the same afternoon.
- Hire the second rep when the data shows Grade A leads slipping uncontacted every week — a measured bottleneck, not a hunch.
Start with one source of truth, or you've already lost
Before tooling, a confession most early-stage founders will recognise. Right now, your leads live in your head, a spreadsheet, your inbox, and a couple of WhatsApp threads. That was survivable when you were the only one selling. The moment a second person needs to act on those leads, the scatter becomes the bottleneck.
So the first thing the rep needs is not a feature — it's a single place where every lead lives. One list. When a lead comes in from a form, a referral, or a cold reply, it goes there. When the rep calls someone, the outcome goes there. No parallel notebook, no "I'll update it later." Later never comes, and three weeks in you have two versions of reality.
This is also where founders over-buy. The instinct is: single source of truth means CRM, and CRM means the big names. But a one-rep team doesn't need objects, pipelines, custom fields, and workflow automation. It needs a clean list the rep trusts and updates. Weight you don't use isn't neutral — it's friction the rep pays for every single day.
Logging has to take ten seconds, not ten clicks
Here's the failure that kills most first-hire setups, and it's worth being precise about whose fault it is. It's not the rep's. When logging a call takes six clicks, a drop-down, and a mandatory "next step" field, the rep doesn't log the call — not because they're lazy, but because they're between meetings with a phone in one hand and a customer waiting on the other line. The situation makes the data impossible. Then you, the founder, look at the system, see nothing, and conclude the rep isn't working. Both of you are now wrong about each other.
The fix is making logging faster than not logging. For an India-based rep, that means the phone and it means WhatsApp. A huge share of B2B selling here happens over WhatsApp — quotes, follow-ups, "sir, did you get a chance to look at it?" — and pretending otherwise just pushes that activity off the books. A rep should be able to log a WhatsApp conversation in three taps without switching apps or opening a laptop. Leadkaun's 3-tap WhatsApp logging exists for exactly this reason: capture the interaction where it actually happens, in the time the rep actually has.
When logging is genuinely fast, adoption isn't a fight. The rep logs because it's quicker than trying to remember. And once the data is real, every other decision you make gets better.
A priority queue beats a longer to-do list
Drop a fresh rep in front of 300 leads and the honest reaction is paralysis. Which one first? They'll do what anyone does — call the names they recognise, the easy ones, the ones who replied last. That feels productive and quietly wastes the best leads, because the hottest lead is rarely the most familiar one.
What a first rep needs is a ranked answer to one question: who do I call next? That's a priority queue. Leadkaun grades every lead A through F in under 500ms based on fit and behaviour, then orders the day around it. The rep opens the queue, sees the Grade A leads at the top, and works down. No deciding, no second-guessing, no opening the spreadsheet and staring.
This matters most precisely when you have one rep, because one rep has the least slack. Every hour spent on a Grade D lead while a Grade A goes cold is ₹ leaving the building, and a solo rep has no colleague to catch the miss. The Missed Opportunity Engine surfaces exactly that — the high-grade leads nobody contacted in time — so a slip shows up as a number instead of a regret three weeks later. Pair it with a Morning Brief that lands before the day starts, and your rep walks in already knowing the plan. For a one-person desk, that structure is worth more than any reporting dashboard.
If you want the mechanics of how grading works, the lead scoring breakdown walks through the A–F logic and what feeds it.
Set the target in rupees, not in activity
Founders love activity targets because they're easy to count. "50 calls a day, 100 WhatsApp messages a week." The problem is that activity targets are trivially gamed and they teach the wrong instinct. A rep optimising for call count will burn through the easy, low-value leads to hit the number, and ignore the ₹5L deal that needs three patient touches.
Set the target in money. "Close ₹8L this quarter" or "build ₹40L of qualified pipeline by August." Then let the priority queue and the grading do the work of pointing the rep at the leads that actually move that number. The rep's daily question shifts from "have I made enough calls?" to "am I working the leads that get me to ₹8L?" — which is the question you actually want them asking.
This also keeps the conversation between you and your first hire honest. When the target is ₹ and the system shows which graded leads are open and which slipped, a weekly check-in becomes a five-minute look at real numbers, not a debate about effort. You blame the gap in the process — a window missed, a follow-up that slipped past its hour — not the person.
Why a heavy CRM hurts before it helps
It's worth saying plainly, because the pressure to buy one is real. A full CRM is a fine tool — for the company it's built for. That company has a sales ops person to configure it, a manager who lives in the reports, and enough reps that standardised workflows pay off. You have none of those yet. You have one rep who needs to call people.
Drop that CRM on a solo rep and three things happen. Setup eats weeks you don't have. The interface, built for ops and reporting, slows down the one job that matters — logging and calling. And adoption craters, because every minute in admin is a minute not selling, and the rep knows it. You end up paying enterprise money for a tool that's 70% unused and actively making your one rep slower. Buy the weight when the team and the workflows justify it. On day one, lighter wins. (For the deeper teardown of why this misfit is so common in India, see why Indian companies leave Salesforce.)
The 60-minute setup, and when to add the second hire
None of this needs a quarter-long implementation. A right-sized setup for a first hire looks like: import your existing leads from a CSV or Google Sheet, let the grading rank them, point the rep at the priority queue, and set a ₹ target. That's roughly a 60-minute job — the rep can be making calls the same afternoon. If your tooling needs a consultant before anyone can dial, it's the wrong tooling for this stage. There's a fuller walkthrough in our guide to sales operations setup for Indian startups.
So when do you add the second rep? Not when it "feels like time." Add capacity when the data shows your first rep is consistently leaving Grade A leads uncontacted because the hours aren't there. When the Missed Opportunity Engine flags high-grade leads slipping past their window week after week, that's ₹ walking out the door that one more pair of hands could catch. That's a measured signal — a bottleneck you can point at — not a vibe. Hire to that number, and the second rep pays for themselves fast.
Your first sales hire is the moment your company stops being a founder who sells and becomes a company with a sales function. Give that person a clean list, fast logging, a queue that tells them who's next, and a target in rupees. Skip the rest until you've earned the need for it.
Want to see what a first-rep setup looks like end to end? Take a look at the product, or book a 15-minute demo and we'll walk through the 60-minute setup with your own leads.