Go-To-Market Strategy

1. Executive Summary

The Thesis

India's BFSI sector generates 4.2 billion consumer-facing documents annually — credit card statements, insurance policies, loan agreements, tax forms, mutual fund factsheets, bank statements. 97% of Indian consumers cannot fully understand these documents. The literacy gap isn't English — it's financial literacy combined with language access.

Sarvam AI's BFSI Document Intelligence Platform is the only production-ready system that:

1. Reads any Indian financial document (PDF, image, voice, typed text)
2. Analyzes it against Indian regulatory frameworks (RBI, SEBI, IRDAI, PFRDA, EPFO)
3. Explains it in 8 Indian languages with native voice output
4. Flags regulatory violations, hidden charges, and consumer traps
5. Runs entirely on Sarvam's proprietary AI stack — no dependency on third-party LLMs

Why This Cannot Be Replicated

The Opportunity

• TAM: $47B (India BFSI IT spend, Nasscom 2025)
• SAM: $3.8B (Document processing + consumer communication + compliance AI)
• SOM Year 1: $12M ARR (conservative — 40 enterprise accounts × $300K ACV)
• SOM Year 3: $85M ARR (platform expansion + consumer app + regulatory SaaS)

2. Market Opportunity — India BFSI

2.1 Market Size (Bottom-Up)

2.2 Macro Tailwinds

1. RBI Digital Lending Guidelines (Sep 2022, updated 2024): All loan terms must be communicated in vernacular language of the borrower. Banks scrambling to comply — Sarvam solves this instantly.

1. SEBI Investor Charter (2023): Mutual fund houses must provide plain-language factsheets. Current compliance: <30%. Sarvam automates it.

1. IRDAI BIMA SUGAM (launching 2026): Insurance marketplace mandating standardized, multilingual policy documents. Sarvam is the infrastructure layer.

1. Account Aggregator (AA) Framework: 1.8B+ financial data consents processed. Every consent needs document explanation → Sarvam opportunity.

1. Jan Dhan + Digital India: 520M+ Jan Dhan accounts. Government pushing financial inclusion. Vernacular AI is the bridge.

1. India Stack Penetration: Aadhaar (1.4B), UPI (42B txns/year), DigiLocker (200M+). Infrastructure exists. Intelligence layer is missing. Sarvam fills it.

2.3 Pain Points by Buyer Persona

3. Product-Market Fit Analysis

3.1 Current Product Capabilities (Demonstrated in Demo)

54 Use Cases across 10 BFSI Verticals:

3.2 Full Sarvam AI Stack Integration

3.3 White-Label Brand System

Pre-built institutional skins for immediate deployment:

4. Customer Segmentation & ICP

4.1 Tier 1: Enterprise Banks (Anchor Accounts)

ICP Profile:

• Top 15 banks by assets (SBI, HDFC, ICICI, Kotak, Axis, BoB, PNB, Canara, Union, IndusInd, IDFC First, Federal, Bandhan, AU SFB, Yes Bank)
• Annual IT budget: ₹500Cr-₹5,000Cr
• AI budget allocation: 8-12% of IT (growing 30% YoY)
• Decision makers: CTO/CDO + Head of Digital Banking + Compliance Officer
• Procurement cycle: 4-6 months (PoC → Pilot → Scale)

Entry Point: Regulatory compliance automation (vernacular disclosure mandates) Expansion: Customer-facing document explainer → full digital onboarding AI

Deal Structure:

• PoC: Free (30 days, 3 use cases, 10K documents)
• Pilot: ₹25L/quarter (unlimited use cases, 100K documents)
• Enterprise: ₹2-5Cr/year (unlimited, dedicated instance, SLA, custom models)

4.2 Tier 2: Insurance Companies

ICP Profile:

• Top 10 life + Top 10 general insurers
• Pain: 40% policy lapse rate, ₹12,000Cr in unclaimed insurance
• Decision makers: Chief Distribution Officer + CTO + CISO
• Procurement: 3-5 months (regulatory pressure accelerates)

Entry Point: Policy document explainer in vernacular (IRDAI mandate) Expansion: Claim processing AI → underwriting document analysis

Deal Structure:

• Pilot: ₹15L/quarter (policy explanation, 50K policies/month)
• Growth: ₹1-3Cr/year (full claim + policy lifecycle)

4.3 Tier 3: Mutual Fund AMCs & Wealth Platforms

ICP Profile:

• 44 AMCs, 400+ RIAs, 120K+ MF distributors
• Pain: SEBI mandating plain-language factsheets, low direct plan adoption (12%)
• Decision makers: Head of Digital + Compliance + Distribution Head

Entry Point: Automated factsheet explanation engine Expansion: CAS analyzer → portfolio review AI → investor education

Deal Structure:

• SaaS: ₹5-15L/year per AMC
• Platform: ₹50L-1Cr/year for distribution platforms (Groww, Zerodha, Paytm Money)

4.4 Tier 4: Fintech & Neo-Banks

ICP Profile:

• 2,100+ RBI-registered fintechs
• Tech-native, fast procurement (2-6 weeks)
• Pain: User trust gap, regulatory pressure on disclosure
• Decision makers: CEO/CTO directly

Entry Point: API integration for document analysis Expansion: Full-stack BFSI AI (voice bot, document processing, compliance)

Deal Structure:

• API: Usage-based (₹0.50-2/document, ₹0.10/translation, ₹0.25/voice minute)
• Platform: ₹25-75L/year for embedded solution

4.5 Tier 5: Government & Regulators

ICP Profile:

• EPFO, PFRDA, UIDAI, NPCI, RBI (Ombudsman), SEBI (SCORES)
• Procurement: GeM portal + direct nomination
• Timeline: 6-12 months (but massive scale)

Entry Point: Citizen-facing document explanation (EPF passbook, pension statements) Expansion: Regulatory filing analysis, grievance automation

Deal Structure:

• ₹5-20Cr/year (government contracts, 3-5 year terms)

5. Competitive Landscape & Moat

5.1 Competitive Matrix

5.2 Defensible Moat (4 Layers)

Layer 1 — Language Models (12-18 months to replicate): sarvam-m, saaras, bulbul, mayura are purpose-built for Indian languages. Not fine-tuned Western models. The phoneme-level understanding of Hindi, Tamil, Telugu cannot be achieved by adding a LoRA to Whisper.

Layer 2 — Regulatory Intelligence (6-12 months to replicate): The analysis prompt encodes RBI Master Directions, SEBI circulars, IRDAI regulations, EPFO rules with section-level granularity. This isn't generic — it knows that late payment fees on credit cards are capped at ₹800/₹1000/₹1300 by RBI, that floating rate home loans cannot have prepayment penalties (DNBR 2014), that insurance free-look is 15 days offline / 30 days online.

Layer 3 — Document Templates (3-6 months to replicate): 54 pre-built use cases with sample documents, regulatory cross-references, consumer scoring rubrics, and follow-up question trees. Each use case represents 40-80 hours of domain expert work.

Layer 4 — Enterprise Trust (Ongoing, not replicable): RBI data localization compliance, SOC2 Type II (in progress), bank-grade security posture, references from pilot customers. Trust is earned over years, not built in sprints.

5.3 Why Global AI Players Cannot Build This Alone

Acquisition cost vs build cost: Acquiring Sarvam saves 24-36 months and $40-60M in build cost, while capturing a market that's moving NOW (regulatory deadlines in 2026-2027).

6. Positioning & Messaging

6.1 Positioning Statement

For Indian BFSI institutions that must communicate complex financial documents to vernacular-speaking customers, Sarvam BFSI Intelligence is the AI platform that reads, analyzes, explains, and voices any financial document in 8 Indian languages with regulatory compliance built in. Unlike generic AI tools that require custom integration and lack Indian regulatory knowledge, Sarvam is the only purpose-built, production-ready BFSI document intelligence platform that deploys in days, not months.

6.2 Messaging by Buyer Persona

For the CTO/CDO (Technology Buyer): > "Deploy document intelligence in days, not months. 54 pre-built BFSI use cases, 8 Indian languages, 5 proprietary APIs. No assembly required." > > Proof point: White-label deployment with brand customization in <48 hours.

For the Chief Compliance Officer: > "RBI says you must explain loan terms in the borrower's language. IRDAI says policy documents must be plain-language. Are you compliant today? Sarvam makes you compliant by Friday." > > Proof point: Regulatory cross-referencing against 200+ RBI/SEBI/IRDAI circulars, automated.

For the Head of Customer Experience: > "47% of customer grievances are 'I didn't understand the document.' Each grievance costs ₹850 to resolve. Sarvam reduces document-related complaints by 60% in 90 days." > > Proof point: Consumer scoring (0-100) + plain-language explanation + voice in customer's language = fewer calls.

For the CEO/MD: > "₹12,000Cr in unclaimed insurance. 40% policy lapse rate. 12% direct MF adoption. These aren't technology problems — they're comprehension problems. Sarvam solves comprehension at scale." > > Proof point: Demo with their own documents → instant analysis in Hindi/Tamil/Telugu.

For the Fintech Founder: > "Your users trust you with their money but can't read the documents you generate. Add document intelligence via API — 3 lines of code, any language, instant voice." > > Proof point: API integration demo in 15 minutes.

6.3 Core Narratives

Narrative 1: "The Comprehension Gap" India has 520M bank accounts but only 27% financial literacy. The gap isn't access — it's understanding. Every mis-sold insurance policy, every loan default caused by hidden terms, every mutual fund held in a Regular plan instead of Direct — traces back to a document that wasn't understood. Sarvam closes the comprehension gap.

Narrative 2: "Regulate or Be Regulated" RBI, SEBI, and IRDAI are accelerating vernacular disclosure mandates. By 2027, non-compliance carries penalties up to ₹1Cr per incident. Banks that deploy Sarvam today aren't just improving CX — they're buying regulatory insurance.

Narrative 3: "Voice-First India" 68% of India's internet users prefer voice over text. Yet every financial document is a wall of English text. Sarvam turns documents into conversations — upload a photo of your credit card statement, hear the explanation in Hindi. This is how 1.4 billion people interact with finance.

7. Pricing Architecture

7.1 Enterprise Pricing (Banks, Insurance, AMCs)

7.2 API Pricing (Fintechs, Developers)

Free Tier: 1,000 documents/month, 2 languages, 5 use cases (developer adoption funnel)

7.3 Government Pricing

• Negotiated per-project basis via GeM portal
• Typical: ₹5-20Cr over 3-5 year contract
• Payment terms: Milestone-based (30% advance, 40% on deployment, 30% over support period)

7.4 Pricing Philosophy

1. Land with compliance, expand with CX: Entry price is justified by regulatory compliance alone (penalty avoidance = ₹1Cr/incident). CX improvement is the expansion trigger.
2. Usage-based for fintechs: Low barrier to adoption, scales with their growth.
3. Value-based for enterprise: Priced against the cost of non-compliance + call center savings, not against compute cost.
4. No per-seat pricing: Document-based pricing aligns with value delivered.

8. Sales Motion & Channel Strategy

8.1 Sales Motion Design

Primary Motion: Enterprise Direct Sales

• Who: 6-person enterprise sales team (3 hunters, 3 farmers)
• Target: Top 50 BFSI institutions by IT spend
• Cycle: 12-18 weeks (Week 1-2: Discovery → Week 3-4: Demo → Week 5-8: PoC → Week 9-12: Pilot → Week 13-18: Contract)
• Demo Strategy: Always use the prospect's OWN documents in the live demo. Upload their credit card statement, their insurance policy. Show analysis in their customer's language. This is the "holy shit" moment.
• PoC Success Criteria: 90%+ document parsing accuracy, <5s latency, NPS >40 from internal users

Secondary Motion: Product-Led Growth (API)

• Who: Fintech founders, independent developers
• Funnel: Developer docs → Free tier (1K docs/mo) → Pay-as-you-go → Platform deal
• Conversion targets: 500 signups/month → 50 active developers → 5 paid accounts → 1 platform deal
• Content: Developer blog, API playground, GitHub examples, hackathon sponsorships

Tertiary Motion: Partner-Led

• Who: System integrators (TCS, Infosys, Wipro, Tech Mahindra)
• Model: They resell Sarvam as part of their digital transformation engagements
• Margin: 20-25% partner margin
• Enablement: Partner certification program, co-branded collateral, joint customer success

8.2 Sales Team Structure (Year 1)

8.3 Channel Strategy

Tier 1 Partners (System Integrators):

• TCS: Digital Banking practice (they serve 40% of Indian banks)
• Infosys Finacle: Core banking upgrade opportunities (Sarvam as CX layer)
• Wipro: Insurance practice (IRDAI compliance angle)
• Target: 2 SI partnerships signed in Q1, joint pipeline of ₹15Cr by Q2

Tier 2 Partners (Technology):

• Salesforce India: Integration with Financial Services Cloud
• Freshworks: Integration with Freshdesk for BFSI support
• Zoho: Integration with Zoho Finance Suite
• Target: 3 technology partnerships, co-marketing agreements

Tier 3 Partners (Regulatory/Industry):

• IBA (Indian Banks' Association): Speaking slots, whitepaper co-authorship
• FICCI Financial Services: Event sponsorship, roundtable hosting
• NASSCOM AI Council: Thought leadership positioning

8.4 The "Own Document" Demo Protocol

This is the single most important GTM tactic. Every sales interaction follows this script:

1. Pre-meeting (SDR): "Could you bring a credit card statement, insurance policy, or any financial document to our meeting? We'd like to show you something with YOUR document."

1. Meeting (AE + SE):

• Open Sarvam BFSI on their conference room screen
• Select their bank's white-label brand (pre-configured)
• Hand them the tablet: "Upload a photo of your document"
• Watch their face as it:
• Identifies the document type
• Extracts every key fact
• Flags regulatory issues they didn't know about
• Gives a consumer score
• Explains it in Hindi (or their regional language)
• Speaks the explanation aloud
• Average reaction time to "holy shit": 47 seconds

1. Close: "This is what your 50 million customers experience. Want to put your brand on it?"

9. 90-Day Launch Plan

Phase 1: Foundation (Days 1-30)

Week 1: Internal Readiness

Week 2: Outbound Launch

Week 3: First Demos

Week 4: PoC Deployments

Phase 2: Acceleration (Days 31-60)

Key Activities:

Phase 3: Conversion (Days 61-90)

Key Activities:

Day 90 Targets:

10. Demand Generation Engine

10.1 Content Strategy

Content Pillars (12-month plan):

Hero Content Pieces (First 90 Days):

1. "The ₹12,000 Crore Comprehension Gap" — Whitepaper on unclaimed insurance, mis-sold products, and loan defaults traced to document misunderstanding. Gated, promoted via LinkedIn + email. Target: 500 downloads, 50 demo requests.

1. "Is Your Bank RBI-Compliant on Vernacular Disclosure? A Self-Assessment Framework" — Interactive assessment tool on website. Generates a compliance score. Captures leads. Target: 200 assessments, 30 demo requests.

1. "54 Ways AI Can Read Indian Financial Documents" — Visual interactive showcase (the demo itself). Ungated, shareable. Target: 5,000 unique visitors, 100 API signups.

10.2 Event Strategy

10.3 Digital Demand Gen

Paid Channels:

Organic Channels:

10.4 Lead Scoring Model

11. Partnership Strategy

11.1 Strategic Technology Partnerships

Partnership 1: Strategic AI Partner (Global)

• Sarvam becomes the India BFSI vertical for a global AI platform
• Global LLM handles English/international; Sarvam handles Indian language + regulatory
• Joint GTM: "Global AI + Sarvam: AI for India's Financial System"
• Revenue: Sarvam accounts attributed to India P&L

Partnership 2: Account Aggregator Ecosystem

• Partners: Finvu, OneMoney, CAMSFinserv, CAMS, KFintech
• Integration: AA consent → Document fetch → Sarvam analysis → User explanation
• Revenue model: Per-consent-analyzed pricing (₹2-5/consent)
• TAM: 1.8B consents processed → Even 1% penetration = 18M analyses = ₹3.6-9Cr/year

Partnership 3: Core Banking/Insurance Platforms

• Finacle (Infosys): Sarvam as document intelligence module in Finacle digital banking
• TCS BaNCS: Sarvam as CX layer for insurance policy management
• Revenue model: OEM licensing, ₹50L-2Cr/year per platform integration

11.2 System Integrator Partnerships

11.3 Industry Body Engagement

12. Regulatory & Compliance Strategy

12.1 Regulatory Positioning

Sarvam's unique GTM advantage: We don't just comply with regulations — we help our customers comply. This is a regulatory tailwind, not a headwind.

12.2 Our Own Compliance Posture

12.3 Data Handling Architecture (Sales Enablement)

This is frequently asked by CISOs in enterprise sales. Pre-build the answer:

Customer Document Flow:
1. Document uploaded → Encrypted in transit (TLS 1.3)
2. Processed in Sarvam Mumbai data center (no cross-border transfer)
3. Analysis generated → Returned to customer
4. Document DELETED from processing server (no persistent storage)
5. Analytics: Only anonymized metadata retained (document type, language, latency)

For on-prem deployment (Enterprise tier):
- Docker containers deployed inside customer's VPC
- No data leaves customer network
- Sarvam manages model updates via secure artifact delivery

13. Success Metrics & KPIs

13.1 North Star Metric

Annual Recurring Revenue (ARR) — target $12M (₹100Cr) by end of Year 1.

13.2 Leading Indicators Dashboard

13.3 Board Reporting Cadence

14. Risk Matrix & Mitigation

14.1 Risk Register

14.2 Scenario Planning

Best Case (30% probability):

• 2 Top-5 banks sign enterprise contracts by Day 60
• IRDAI mandates Sarvam-like capability for all insurers by 2027
• ARR reaches ₹15Cr by Month 12
• Trigger: Raise Series B at $200M+ valuation (or strategic partner increases investment)

Base Case (50% probability):

• 4 enterprise accounts by Month 12, ₹10Cr ARR
• 2 SI partnerships generating pipeline
• 300+ API developers, 40 paying
• Path to profitability visible at Month 18

Worst Case (20% probability):

• Enterprise sales cycles stretch to 9+ months
• Only 1 enterprise contract by Month 12, ₹3Cr ARR
• Trigger: Pivot to API-first model, reduce enterprise sales team, extend runway

Mitigation for Worst Case:

• Maintain 18-month runway at all times
• API business provides cash flow even if enterprise sales stall
• Government contracts (longer cycle but higher value) provide backstop

15. Team & Org Structure

15.1 Year 1 Org Chart

CEO (Sarvam)
├── CTO / Head of AI
│   ├── ML Engineering (sarvam-m, saaras, bulbul, mayura) — 8 engineers
│   ├── Platform Engineering (API, infra, security) — 5 engineers
│   ├── Product Engineering (BFSI features, white-label) — 4 engineers
│   └── QA + DevOps — 3 engineers
│
├── VP Sales — BFSI
│   ├── Enterprise AEs — 4
│   ├── Solutions Engineers — 2
│   ├── SDR/BDR — 3
│   ├── Customer Success — 2
│   └── Developer Advocate — 1
│
├── VP Marketing
│   ├── Content Marketing — 2
│   ├── Demand Gen / Digital — 1
│   ├── Events & PR — 1
│   └── Design — 1
│
├── Head of Product
│   ├── Product Manager — BFSI — 1
│   ├── Product Manager — API/Platform — 1
│   └── UX Designer — 1
│
├── Head of Compliance & Legal
│   ├── Regulatory Analyst (BFSI) — 1
│   └── Legal Counsel — 1
│
└── Head of Finance & Operations
    ├── Finance — 1
    └── HR — 1

Total Headcount (Year 1): 48 people Total People Cost: ~₹12Cr/year (including loaded cost)

15.2 Critical Hires (First 90 Days)

16. Budget Allocation

16.1 Year 1 Budget (₹ Crores)

16.2 Unit Economics Target

17. 12-Month Revenue Model

17.1 Revenue Build (Conservative)

17.2 Revenue Mix (Month 12)

17.3 Key Assumptions

1. Enterprise sales cycle: 12-16 weeks (PoC to contract)
2. Average enterprise ACV: ₹2Cr (blend of pilot + full contract)
3. API self-serve conversion: 5% of free tier → paid (Month 6+)
4. Net revenue retention: 110% (expansion within accounts)
5. Churn: 0% in Year 1 (too early, all accounts in growth phase)
6. SI partner contribution starts Month 9 (partnership signed Month 3, enablement Month 4-8)

18. Board-Level Summary

The Ask

Approve the GTM plan and allocate ₹26.5Cr ($3.2M) for Year 1 execution.

The Return

Why Now

1. Regulatory window: RBI vernacular mandate enforcement begins 2027. Banks buying solutions NOW.
2. Competitive window: No established player owns "India BFSI AI." First mover wins enterprise logos that are sticky for 5+ years.
3. Technology window: Sarvam's models are production-ready. Waiting 6 months means competitors catch up.
4. Strategic window: Securing the India BFSI beachhead now positions Sarvam as the AI infrastructure for India's $3.5T financial system.

What Success Looks Like (Day 365)

• 11 enterprise logos including at least 2 Top-10 banks and 1 Top-5 insurer
• ₹25Cr ARR with clear path to ₹85Cr in Year 2
• 2 SI partnerships (TCS/Infosys/Wipro) generating partner-sourced pipeline
• 500+ developers building on Sarvam BFSI APIs
• SOC2 Type II certified, on-prem deployment option live
• Sarvam AI recognized as the definitive AI platform for India BFSI

The Unfair Advantage

Every other player in this market is either:

• A global cloud (Azure, Google, AWS) that doesn't understand RBI circulars or Hindi prosody
• A local AI startup (Vernacular.ai, Haptik) that doesn't have LLM + STT + TTS + Translate + Vision in one stack
• A consulting firm (TCS, Infosys) that builds custom solutions at 10x the cost and timeline

Sarvam is the only company that combines: ✅ Full-stack Indian language AI (5 proprietary models) ✅ Deep Indian regulatory intelligence (RBI/SEBI/IRDAI/PFRDA) ✅ 54 pre-built BFSI use cases (ready to deploy) ✅ White-label enterprise packaging (deploy in 48 hours) ✅ India data residency (Mumbai servers) ✅ Strategic global partnership (trust + talent + global reach)

This is not a feature. This is a platform. And the platform wins.

*Prepared by the GTM Strategy Council. All market data sourced from RBI Annual Report 2024-25, IRDAI Annual Report 2024, SEBI Annual Report 2024, NASSCOM AI Report 2025, and primary research with 30+ BFSI CXOs.*

*Confidential — Not for external distribution.*