Revenue engines on repeat.

This is one of the most important timing decisions in a startup's growth journey. The answer has two parts — when you can hire, and when you should hire:

• You can hire when: You have closed at least 10–15 deals yourself, you can articulate exactly why customers buy and why they don't, and you have a repeatable sales process documented — not just in your head.
• You should hire when: You are personally spending more than 40% of your time on sales activities and it is preventing you from product strategy, fundraising, or hiring. Or when you have strong inbound demand but lack bandwidth to follow up.

The most common mistake: Hiring a sales rep too early — before the founder has a proven, repeatable sales motion. A rep cannot invent a sales process; they can only execute one. If the founder hasn't cracked the sale personally, a rep will fail and waste 6–9 months of runway.

Hiring sequence recommendation: Your first sales hire should be an SDR or BDR to handle prospecting and qualification — not an AE. This frees the founder to continue closing while the pipeline grows. Hire your first AE once the SDR is generating 3–4 qualified meetings per week consistently.

A well-designed commission plan does three things: rewards the right outcomes, is simple enough to calculate mentally, and doesn't incentivise short-term behaviour that hurts long-term growth. Key principles:

• Pay on ARR, not TCV: Commission on Total Contract Value (multi-year deals) incentivises over-discounting for big upfront numbers. Commission on ARR (first-year value) is cleaner and aligns with company economics.
• Accelerators above quota: Reps should earn more per rupee closed above 100% quota than below. Standard: 100% attainment = 100% commission rate; 125% attainment = 150% commission rate; 150%+ = 200%. This motivates reps to push hard in the second half of the quarter.
• Clawback provision: If a customer churns within 90 days of signing, the commission on that deal is clawed back. This prevents reps from closing bad-fit deals just to hit quota.
• Minimum activity thresholds: Commission is only paid if the rep meets minimum activity standards (logged in CRM, handoff to CS completed). This prevents "close and forget" behaviour.
• Quota setting: Quota should be set at 3–5× the rep's OTE variable. A rep earning ₹12L variable should have a ₹36–60L ARR quota. Stretch quotas (above 5×) cause reps to give up mid-year.

Always have a signed Sales Incentive Plan (SIP) document — verbal commission promises are unenforceable and create legal and HR risk when reps leave.

MEDDPICC is an enterprise sales qualification framework that helps reps understand every dimension of a complex deal before investing time and resources. The letters stand for:

• M — Metrics: Quantifiable business impact of your solution (e.g., "saves 12 hours/week per finance team member")
• E — Economic Buyer: The person with budget authority who can say yes without approval from above
• D — Decision Criteria: What factors the buyer uses to evaluate solutions (security, price, integration, references)
• D — Decision Process: The steps, approvals, and stakeholders involved in making the purchase decision
• P — Paper Process: Procurement, legal, and PO processes — how long does contracting actually take?
• I — Identify Pain: The explicit business problem or opportunity with a measurable cost of not solving it
• C — Champion: Your internal advocate — someone who wants you to win and has influence over the decision
• C — Competition: Who else is in the deal, including the option of "do nothing" or building in-house

Should your startup use it? MEDDPICC is overkill for SMB transactional sales (sub-₹2L ACV, 30-day sales cycle). It becomes essential when: your sales cycle is longer than 60 days, multiple stakeholders are involved, and deals above ₹10L ACV are common. Start with BANT for early deals, introduce MEDDPICC frameworks at the deal review level once you have an AE team and are selling to mid-market or enterprise accounts.

Price objections in India are almost never purely about price — they are usually about one of three things: unclear value, wrong champion, or wrong timing. Here's how to diagnose and handle each:

• If it's unclear value: You haven't connected your product to a measurable business outcome. Go back to discovery: "Help me understand — what does this problem cost you today?" Build a business case together. If solving the problem is worth ₹50L in recovered time or lost revenue, ₹5L for your software is a 10× ROI and not expensive at all.
• If it's the wrong champion: Your contact doesn't have budget authority or doesn't feel the pain personally. Ask: "Is this a budget concern or a priority concern?" Budgets are created for things that matter. Find the economic buyer who owns the pain and the budget.
• If it's timing / cash flow: Offer flexible payment terms — quarterly billing instead of annual, or a 2-month pilot at reduced fee before full subscription. Indian buyers, especially SMBs, often have genuine cash flow constraints rather than objections to value.

The scripted response that works: "I understand price is a consideration. Can I ask — is it that ₹X is more than you expected, or is it that you're not yet sure the value justifies ₹X? Those are two different conversations and I want to make sure I address the right one." This separates price shock from genuine value uncertainty and tells you exactly where to go next.

What not to do: Never discount immediately when you hear "it's too expensive." The first mention of price is rarely the final position. Reps who discount at first resistance leave 20–30% margin on the table across their entire book of business.

A sales playbook is a documented guide that captures everything a new sales rep needs to go from onboarding to quota-carrying in the shortest possible time. It is the codification of everything the founder learned during the founder-led sales phase. A complete playbook contains:

• ICP (Ideal Customer Profile): Company size, industry, geography, tech stack, budget range, and 5–7 qualifying questions to identify a true ICP
• Buyer personas: Who within the ICP company buys your product — their title, day-to-day challenges, what they care about, what they fear, how they measure success
• Discovery call framework: 10–15 questions that uncover pain, quantify impact, identify the economic buyer, and establish next steps — with example answers that signal a strong vs. weak opportunity
• Demo structure: Standard demo flow — not a feature tour, but a problem-led narrative that connects each product capability to a buyer pain point
• Objection handling guide: Top 10 objections with recommended responses, based on what actually worked in past deals
• Competitive battlecards: One page per competitor — their strengths, weaknesses, how to position against them, and what to say when the buyer says "we're also looking at X"
• Email and call templates: High-converting outreach sequences, follow-up emails after demo, and "proposal sent — no response" re-engagement
• Closing mechanics: How to ask for the business, what the contract and signing process looks like, and how to manage multi-stakeholder approval chains

The playbook is never finished — it should be a living document updated monthly based on what's working and what's failing in the field.

Channel sales — selling through partners, resellers, system integrators, or consultants — can 3–5× your market reach without proportionally scaling headcount. India has a large ecosystem of regional IT distributors, CA firms, consultants, and VARs (Value-Added Resellers) who already have trust relationships with your buyers.

When to build a partner channel:

• Your product requires implementation or customisation — implementation partners can deliver this faster than you can hire
• Your target buyers trust a specific category of advisor (e.g., CA firms for accounting software, IT distributors for hardware-adjacent tools)
• You want to reach Tier 2/3 cities without opening field offices

Partner programme structure:

• Referral partners: Earn 10–15% commission on first-year ARR for introductions that convert. Low commitment, low margin impact. Good starting point.
• Resellers / VARs: Buy your product at 25–40% discount and sell at full price, adding their own implementation margin. They own the customer relationship. Higher scale potential but you lose visibility into the end customer.
• System Integrators (SIs): Large SIs (TCS, Infosys, Wipro) or boutique SIs who bundle your product into larger implementations. Deal sizes are larger but sales cycles are 6–18 months. Relevant from Series A onwards.

Critical requirement: Assign a dedicated Partner Success Manager before launching the programme — partners go cold within 90 days if they don't close their first deal and receive enablement. TDS at 5% under Section 194H applies to commissions paid to partner firms.

Revenue Operations (RevOps) is the function that aligns sales, marketing, and customer success operations under a single accountability umbrella — with shared data, shared definitions, and shared revenue goals. Rather than each function having its own ops, tools, and reporting, RevOps creates a unified infrastructure.

What RevOps owns:

• CRM architecture, data quality, and system administration
• Funnel definitions and handoff SLAs between marketing, sales, and CS
• Sales forecasting models and pipeline review processes
• Quota setting, territory planning, and compensation modelling
• Revenue reporting and board-level dashboards
• Tool evaluation, procurement, and integration across the GTM stack

When to invest: You don't need a dedicated RevOps hire until you have 5+ people in GTM roles (sales + marketing combined) and are spending more than 2 days per month reconciling conflicting data across systems. Before that, the founder or VP Sales should own this directly. The first RevOps hire is typically a Sales Operations Analyst at ₹8–14L CTC who lives in the CRM and builds reports and automations. A full RevOps leader (VP or Director) is a Series A+ hire once you have a 10+ person revenue team.

Enterprise and government sales in India operate by fundamentally different rules than SMB transactions. The key differences:

Key strategies for enterprise sales in India:

• Find and develop a champion: In every large Indian organisation, someone is politically motivated to solve the problem you address. Find them, help them build the internal business case, and give them the ammunition to sell internally on your behalf.
• Pilot-first strategy: Large Indian enterprises rarely do "evaluation then buy" — they almost always require a paid or unpaid pilot. Structure pilots with clear success metrics and a defined convert-or-exit timeline.
• Government sales: Register on the GeM (Government e-Marketplace) portal at gem.gov.in — mandatory for selling to central government departments. Obtain MEITY empanelment for IT products. Government payments are typically on 30–90 day credit; build this into pricing.

The average ramp time for an AE in Indian B2B SaaS is 6–9 months — but a structured onboarding programme can compress this to 60–90 days for a strong hire. The 90-day plan:

• Week 1 — Product immersion: Full product training, complete the onboarding flow as if they were a customer, shadow 5 customer calls, read every case study and win/loss review. Goal: can demo the product unassisted by end of week.
• Week 2 — Process and tools: CRM setup, pipeline hygiene standards, email cadence setup, call recording tool, proposal templates. Learn the sales playbook inside out. Shadow 5 discovery calls.
• Week 3–4 — ICP and market: Deep-dive into the 3 top customer personas; review all competitive battlecards; attend 2 customer success calls to understand post-sale; do first 10 cold outreach attempts with manager review.
• Month 2 — Supported selling: Run full sales cycles with manager co-piloting. Do 8–10 discovery calls independently; complete first demo with manager feedback; aim to get first proposal out by week 6.
• Month 3 — Independent ramping: Own pipeline independently; weekly 1:1 with manager on deal reviews; close first deal by end of month 3. Quota is typically 50% of full quota in month 3, ramping to 100% in month 4–5.

The single biggest predictor of ramp success is call volume in weeks 2–4. Reps who make fewer than 30 calls in their first two weeks of selling consistently underperform vs. those who make 50+. Build this into the onboarding schedule explicitly.

India-to-global SaaS is the defining opportunity of the current decade — proven by Zoho, Freshworks, Chargebee, and dozens of others. The playbook for going global from India:

• Product-market fit in India first (optional but useful): Some founders go global from Day 1 — especially if the problem is inherently global or the Indian market is too small. Others validate in India and then expand. Both paths work; the key is knowing which one you're on.
• Currency and payment setup: Accept payments in USD/EUR via Stripe or Razorpay International. Ensure your Indian entity has an AD Bank account set up for forex receipts. File FC-GPR if payment is investment, or simply receive as export income.
• Legal entity decision: For US sales above $500K ARR, consider incorporating a Delaware C-Corp as the contracting and invoicing entity — US buyers strongly prefer US-incorporated counterparties. Indian entity remains the operating subsidiary.
• US sales without a US office: Digital-first outreach works well for SMB and mid-market US deals from India. LinkedIn outreach, G2 reviews, and ProductHunt launches generate inbound leads without physical presence. Hire a US-based SDR or AE as a contractor at $60–90K/year once you have 5+ US customers.
• FEMA and RBI compliance: Export of software services is zero-rated for GST — file LUT annually. Receive payment through banking channel within 9 months of invoice date. Annual FLA return to RBI if outstanding export receivables exceed threshold.
• Trust signals for global buyers: SOC 2 Type II certification, US-based customer references, and a .com domain hosted on a US CDN dramatically increase conversion rates from US and European prospects who are risk-averse about India-based vendors.

Revenue forecasting is an art and a science. A credible forecast requires disciplined pipeline management — garbage in, garbage out. There are two primary approaches that work well together:

• Probability-weighted forecast (bottoms-up): Assign each open deal a close probability based on sales stage (using the stage probability table in this guide). Sum probability × deal value across all open deals. Add committed deals (stage 6–7) at full value. This gives your "base case" forecast.
• Conversion rate model (top-down): Look at your historical stage-by-stage conversion rates. If you know that 40% of proposals convert and you have ₹50L in proposals, forecast ₹20L from that stage. Multiply across each stage for total expected revenue.

Three forecast categories boards expect:

Non-negotiable forecasting hygiene: Every deal in the CRM must have a close date, a stage, a next step, and an assigned owner. Deals with no activity logged in 14+ days are automatically flagged in the weekly pipeline review. Sandbagging (reps understating pipeline to sandbag easy quotas) and hockey-stick forecasts (80% of quarterly revenue in week 12 of 13) are managed by reviewing stage age and requiring documented exit criteria before stage progression.