7. What's Missing: The Gap Between Built and Paid, Renewed, Referred
Assumption: nothing is built yet. So these are gaps between the idea and a business.
7.1 Gaps to pay
| Gap | Why it blocks payment | Fix |
|---|---|---|
| No chosen dataset | "A niche data feed" can't be priced, sold or marketed | Pick India bank, payment-rail and exchange business days (01). |
| The data itself is free | RBI, exchanges and python-holidays give most of it away | Sell what's not free: change alerts within 4 hours, source and status per date, "as known on" history, business-day arithmetic, SLA. |
| No pricing model | The catalog's $10–160 range starts where Calendarific and Open Exchange Rates already sit | Free (current year, national + 3 centres, 1k calls) → Developer ₹1,999 → Business ₹4,999 (all data, webhooks, history) → Enterprise ₹14,999 (SFTP, audit export, SLA, contract) → Global $149. Annual = 2 months free. |
| No quantified value promise | "Accurate holiday data" is what every free source claims | "When RBI or a state moves a date, you'll know within 4 hours, with the notice attached." Publish the changelog with found-at and published-at times as proof. |
| Procurement friction at regulated buyers | Banks and NBFCs need a GST invoice, a vendor form, sometimes an information-security questionnaire | GST registration from day 1. A one-page security note (no personal data, keys only, hosting region, uptime). A standard contract with a liability cap. |
| No trust signals | Nobody automates debits or settlements on data from an unknown source | Source link on every date, a public changelog, a named founder, a status page, and 3 named design partners (with permission) by month 6. |
7.2 Gaps to renew
| Gap | Fix |
|---|---|
| A yearly job, not a weekly one. The list changes in January, so customers are tempted to copy it and cancel. | Put the value in the changes during the year: webhooks, status, history. Send a monthly "what changed" email even when nothing did ("0 changes across 34 centres this month, verified daily"). |
| No switching cost | Versioned history and webhooks wired into the customer's systems. Leaving means losing the audit trail and rebuilding the alerting. |
| Startup customers die | Sell to RBI- and SEBI-regulated firms first. Target ≥60% of MRR from them by month 12. |
| Annual price shock | Push annual plans from the start (2 months free). They cut churn and match how Indian finance teams budget. |
| One wrong date ends trust | Two-person cover, source-silence alerts, public post-mortems for any miss, and a service credit. |
7.3 Gaps to refer
| Gap | Fix |
|---|---|
| Nothing visibly shareable | The public changelog ("RBI added a holiday for Kolkata centre, 3 days' notice, published 42 minutes after the notice") is shareable by design in fintech engineering groups. |
| No free hook | The open-source package with the confirmed current year. It's what developers find when they search GitHub, PyPI or npm. |
| No community presence | Answer questions about Indian bank holidays and business-day logic where Indian fintech developers ask them (Stack Overflow, Reddit, fintech Slack and Discord groups, LinkedIn). That's the modern version of how IPinfo grew. |
| No referral economics | One month free per referred paying customer, for both sides. |
7.4 Non-product gaps
Distribution
- Missing from the description: "developer search, free tiers, docs" is necessary but slow. Search volume for "bank holiday API India" is probably tiny (not measured).
- Channels that fit: (a) direct outreach to engineering and ops leads at NBFCs, lending platforms, payment firms and brokers, (b) the open-source package, (c) the public changelog and a monthly "Indian business-day changes" post, (d) listings on API marketplaces (RapidAPI, EODHD-style marketplaces) and an MCP server directory, (e) partnerships with loan-management and core-lending software vendors who could embed it.
- Channels that burn time: paid ads to "developers", Product Hunt launches, global holiday SEO.
Positioning
- Current: "a niche data-feed API". Generic, and it invites comparison with free sources.
- Better: "India's bank and market business days as an API. Every RBI centre, NSE, BSE and MCX. Sourced, versioned, and updated within hours when a date moves."
- One sentence, one buyer, one outcome.
Sales motion
- Developer and Business plans: self-serve, with a 20-minute onboarding call for the first 30 customers.
- Enterprise: founder-led. Expect 1–3 months to close, a vendor form and a security questionnaire. Start after 10 self-serve customers.
Compliance and legal
| Area | Requirement |
|---|---|
| Data sources | Primary sources only: RBI, NSE, BSE, MCX, state gazettes. Don't copy compiled lists. Respect robots.txt and rate limits on government sites. |
| Liability | Terms: informational data, verify with the official notice, liability capped at 12 months' fees, no guarantee of accuracy. Professional indemnity insurance before the first Enterprise contract. |
| Tax and invoicing | GST registration. A Letter of Undertaking for exporting services to foreign customers. Stripe or Paddle for USD. (Standard practice, not verified for this case.) |
| Privacy | No personal data processed. API keys and usage logs only. A short privacy policy and data-processing note for enterprise buyers. |
Team
- You, plus one paid backup for weekends and festival days once revenue allows (₹15–25k a month, estimated).
- Useful advisor: someone from lending operations, treasury or a broker's back office who knows which dates break which processes. Unpaid or small equity.
Metrics and instrumentation
Minimum set from day 1:
- Median notice-to-publish time, and missed changes (target zero).
- Paying customers, MRR, and the share from regulated firms.
- Monthly revenue churn, and the reason for every cancellation.
- Free keys → paid conversion.
- Webhook adoption among paying customers (target ≥60%: it predicts retention).