Free resources

Guides for Indian sales teams

Short, practical playbooks — no fluff, no 50-page ebooks. Written for managers and reps who are moving off spreadsheets and want a pipeline they can actually trust.

Getting started

Moving your sales pipeline out of spreadsheets

Most sales teams in India start in Excel or Google Sheets. It works — until it doesn't. Here's a practical, low-pain path to move your pipeline into a real CRM without losing a week of selling time.

6 min read ↓

Management

A sales manager's weekly pipeline review that actually takes 30 minutes

Pipeline reviews die of two causes: they take too long, and reps spend the meeting preparing a story instead of selling. Here's the ritual we've seen work for small Indian sales teams.

5 min read ↓

Forecasting

Forecasting basics: from gut feel to numbers you can defend

Ask most founders for this month's forecast and you'll get a number that's either wishful or padded. Here's how to build a forecast your investors — and you — can actually trust.

7 min read ↓

Field sales

Field sales follow-ups that never slip

In India, a lot of selling happens on WhatsApp and in person. The deal knowledge ends up in the rep's phone, not the CRM. Here's how to close that gap without forcing reps to do double data entry.

5 min read ↓

Getting started · 6 min read

Moving your sales pipeline out of spreadsheets

Why spreadsheets break first

Spreadsheets are great for a founder selling alone. The moment you have 3+ reps, three problems appear: nobody knows which version is current, deals go stale because updating feels like extra work, and forecasting turns into a guessing game every month-end.

The hidden cost isn't the sheet itself — it's the follow-ups that slip because nothing reminds a rep when a deal has been quiet for 10 days.

The 7-day migration plan

Day 1–2: Export your current sheet. Keep only active deals — archive closed or dead ones, don't carry clutter.
Day 3: Define your stages in plain language your reps already use (e.g. New lead → Contacted → Demo → Negotiation → Won/Lost).
Day 4: Import deals, assign owners, set deal values in ₹. Sanity-check the total against your sheet.
Day 5–6: Reps update their own deals. Run your first pipeline review from the CRM, not the sheet.
Day 7: Freeze the spreadsheet — read-only. If it's still being edited, something in the CRM isn't working; fix that instead of maintaining both.

What to do in the first month

Resist importing every field from your old sheet. A CRM works when it's lighter than the spreadsheet, not heavier. Keep: company, contact, value, stage, next step, next step date. Everything else can wait.

Set one rule from day one: every deal must have a next step and a date. That single habit is what turns a CRM from a record-keeping tool into a selling tool.

Management · 5 min read

A sales manager's weekly pipeline review that actually takes 30 minutes

Pipeline reviews die of two causes: they take too long, and reps spend the meeting preparing a story instead of selling. Here's the ritual we've seen work for small Indian sales teams.

The 5 questions, per rep

Which deals moved forward this week — and what evidence do we have (a meeting, a signed PO request, not just a feeling)?
Which deals went quiet for 10+ days? Every one of these needs a next action today.
What's closing this month vs what's slipping? Be honest about slippage — it's data, not failure.
Where is the top of the funnel thin? If no new leads entered this week, next month's close rate suffers.
What's the one blocker I (the manager) should unblock for you this week?

Why this beats a full-day review

A good CRM shows this on one screen: stage-wise value, deals with no activity, and forecast vs target. If your review requires reps to prepare anything, it's already failing — the data should already be there.

Keep it to 30 minutes per team, same day every week. The rhythm matters more than the format.

Forecasting · 7 min read

Forecasting basics: from gut feel to numbers you can defend

Ask most founders for this month's forecast and you'll get a number that's either wishful or padded. Here's how to build a forecast your investors — and you — can actually trust.

Weight your pipeline by stage, not by mood

Every stage has a rough close probability based on your own history. A deal in negotiation is not the same as a deal where the demo went well. Start simple: New lead 10%, Contacted 20%, Demo done 40%, Negotiation 70%, verbal yes 90%.

Multiply each open deal value by its stage probability. That weighted number is your baseline forecast. It will be wrong at first — that's fine. Track how wrong, and adjust the percentages over time.

Watch the gap, not just the total

Compare weighted forecast against your target. If there's a ₹40L gap mid-month, you need to know now — not on the 28th. The question becomes concrete: which deals could realistically pull that gap forward?

Also watch velocity: how long deals spend in each stage. If negotiation suddenly takes twice as long as it used to, something changed in your market or your pricing — before your numbers show it.

One number to rule them all

If you report one number upward, report committed forecast: deals that have a dated next step, an identified decision-maker, and no red flags. Everything else is upside, not plan.

Field sales · 5 min read

Field sales follow-ups that never slip

In India, a lot of selling happens on WhatsApp and in person. The deal knowledge ends up in the rep's phone, not the CRM. Here's how to close that gap without forcing reps to do double data entry.

The two-minute rule after every meeting

Immediately after leaving the meeting, the rep logs one line: who, what was discussed, next step, date.
Voice notes are fine — the point is capture within 5 minutes, before the next meeting wipes the context.
Managers: never ask 'why didn't you update the CRM?' — ask 'what's the next step on this deal?' If the next step isn't in the system, the update is the missing piece, and it will fix itself.

Make WhatsApp an input, not a dead end

Deals genuinely move on WhatsApp in India. Fighting it loses you the data; embracing it means every important WhatsApp commitment — 'sending the proposal by Friday' — should end up as a dated next step in the CRM.

When the CRM reminds you before that Friday, and the rep closes the loop, you've turned chat conversations into pipeline discipline.

Measure follow-up latency, not activity count

Don't count calls made. Measure the time between a lead arriving and the first contact, and between a meeting and the follow-up. Those two numbers predict revenue better than any activity dashboard.

Put the guides into practice

ApexSales gives your team the pipeline visibility, follow-up reminders and honest forecasting these guides describe — free to start.

Book a demo See pricing

Free to start · No credit card required