Most India-based outbound teams fail because they're hired as headcount, not built as a system. Here's the pod model and the week-by-week build.
Aditya Dubey
August 14, 2026
8 min read
We have run this motion for US SaaS companies selling into healthcare, financial services, and data infrastructure. This is what it actually takes, including the parts that go wrong.
The failure pattern- A founder hires two BDRs in India, buys Sales Navigator seats, hands over a deck and a list, and asks for meetings in 30 days. Nobody has written down who the buyer is. Nobody has decided what a qualified meeting means. There is no call review, no objection library, no manager who has personally booked a meeting with a US VP.
Six weeks later the dials are happening, the meetings are not, and the conclusion is "India outbound does not work." The conclusion is wrong. What did not work was hiring headcount and calling it a strategy.
What we run instead - We do not place a BDR. We run a pod: a GTM strategist who owns the ICP and messaging, callers who own the dials and sequences, a coach who reviews recorded calls weekly, and an analyst who owns list quality and reporting.
The pod matters because the four jobs fail differently. A caller who is missing meetings because the list is wrong needs a better list, not more motivation. When one person owns all four jobs, nobody can tell which one broke.
Strategist
Owns the ICP and messaging
Callers
Own the dials and sequences
Coach
Reviews recorded calls
Analyst
Owns list quality
Weeks 1 and 2: discovery, which is mostly disqualification -
Discovery is not a product walkthrough. It is deciding who we are not going to call.
With Conversive, the original brief was US healthcare, broadly. Broadly is not an ICP. We spent the first two weeks narrowing to specific segments where the buyer had an active reason to take a call this quarter, then split the motion into a US healthcare track and a financial services and mortgage track because the buyers, the trigger events, and the objections were completely different. Same product, two playbooks.
What we pin down before anyone dials:
- The buying title, and the title that blocks them - The trigger event that makes this quarter different from last quarter - What a qualified meeting means, in writing, agreed by the client - The three competitors the buyer is already using or evaluating - The two segments we are deliberately excluding
That last one is the one founders resist and the one that moves numbers most.
1
1.
Weeks 1-2: Discovery
Deciding who we are not going to call. Buying title, trigger event, qualified-meeting definition, competitors, and the segments we deliberately exclude - all pinned down before anyone dials.
2
2.
Weeks 2-3: Build
Not a script - a call flowchart with the opener and the four most likely responses mapped out. Plus an email sequence, an enriched prospect list, and a synced CRM/sequencer/enrichment stack.
3
3.
Weeks 3-4: Train
Product training, objection handling, mock calls scored against a written rubric. Then live call reviews on tldv - the coach pulls the three worst moments and the one best moment each week.
Now after all these training steps, we start ramping:
Week 4 onward: Ramp: The messy middle. Connect rate is low, the pitch is stiff, the client starts asking questions. That’s expected - it’s part of learning, adapting, and getting comfortable on real calls.
The build output is not a script. It is a call flowchart: opener, the four most likely responses, and where each one goes. A script collapses the moment a prospect says something unscripted. A flowchart survives it, because the BDR has already seen the branch.
If those four tools do not sync, the reporting is fiction and you will not know which segment is working. This is the single highest-leverage hour of the week and it is the first thing that gets skipped when things get busy.
120
Discovery calls delivered - E6Data
51
Meetings booked across US healthcare and financial services tracks - Conversive
35
Meetings from zero prior outbound - Kaara
At E6Data the first 4 weeks produced 2 meetings. What changed the curve was A/B testing openers and moving to persona-specific problem framing. After that the pod completed 120 discovery calls over the engagement.
At Conversive the pod booked 51 meetings across the US healthcare and financial services tracks.
At Kaara, which had never run outbound at all, the pod went from zero to 35 meetings.
Run and optimise:
Weekly: pipeline review with the client, call recording audit, message iteration, list refresh. Monthly: segment-level analysis of which slice of the ICP is converting and reallocation of effort toward it. The messaging that works in month three is rarely the messaging we launched with. The system is not the playbook. The system is the loop that rewrites the playbook.
✅ Strong fit
- Sales motion exists but has never been systematised
- Willing to commit past the 4–6 week ramp period
- Wants a repeatable system, not just a headcount add
⚠️ Not a fit yet
- The product is highly local with non-English-speaking buyers
- The buyer is undefined and just start calling
- Sales has been entirely founder-led with nothing written down
The last one is the most common reason engagements fail, and it fails on the buyer's side, not the pod's.
On cost:Yes, the economics are better. One US SDR's fully loaded cost builds a four-person pod. But cost is the consequence, not the pitch. If cost were the advantage, every company that offshored outbound would be winning, and most of them are not. The advantage is that the same budget buys a system instead of a seat.
Frequently Asked Questions
India's evening shift maps onto US business hours across Eastern, Central, Mountain, and Pacific. It is a planned, permanent shift schedule with the pod working set hours, not overtime bolted onto a day shift. Teams that treat it as overtime burn out in two months and the attrition destroys whatever ramp they had built.
Buyers do not hang up on accents. They hang up on people who clearly do not understand their business. We train for clarity, pace, and buyer knowledge. A BDR who can name the prospect's compliance deadline holds the call. A BDR with a neutral accent and nothing to say does not.
First meetings typically land in weeks 4 to 6. A stable, predictable rate takes 2 months. Anyone promising faster is either quoting a fluke or counting meetings you would not accept.
A CRM (usually HubSpot or Salesforce), a dialer, an email sequencer, an enrichment layer, and call recording. The specific stack follows the client. The requirement is that they integrate, because disconnected tools mean you cannot attribute anything.
Under the Intern Model, yes. We build and run it, then hand it over. Under SDR-as-a-Service we run it as a managed pod inside your business.
Want to see whether your motion is systematisable?
Send over your ICP and current outbound numbers and we will tell you honestly whether this works for you.
Aditya Dubey