2. Market Reality Check
Competitor prices were checked on 30 Sept 2026 where a source is linked in research/10. Buyer counts in India are estimates, not verified. Re-check both before using them externally.
2.1 Who exactly is the buyer?
"Developers who need data" is not a buyer. For an India business-day API, split the market by who loses money when a date is wrong:
| Segment | Rough count in India (estimate, not verified) | What a wrong business day costs them | Willingness to pay | Pain score (1–10) | Verdict |
|---|---|---|---|---|---|
| NBFCs and banks with in-house lending tech | Hundreds with their own engineering teams (thousands of NBFCs are registered, most tiny) | Wrong due-date messages, interest accrual on the wrong day, collections calls on a holiday, audit questions. NACH itself shifts the debit automatically. | ₹2k–15k/mo. Enterprise buyers want an invoice, an SLA and a contract. | 6 | Best first buyer. Regulated, audited, doesn't vanish. |
| Lending platforms, payment aggregators, payout and collections fintechs | Several hundred | Payout and settlement ETAs, reconciliation breaks, SLA timers, customer support load | ₹2k–5k/mo | 6 | Good buyer, but startups die. Churn by company death is real. |
| Brokers, wealth apps, MF distributors | A few hundred with their own tech (estimate) | Wrong settlement date (T+1), wrong order cut-off, MCX session errors | ₹5k–15k/mo | 6–7 | Second segment. Settlement calendars are where exchanges publish in circulars, not data. |
| Payroll, HR and attendance SaaS | ~100–300 | Wrong holiday on a payslip or attendance record | ₹2k–5k/mo | 4–5 | Weak. They need state public holidays, which python-holidays covers free. |
| Logistics and delivery ETA engines | ~100–300 | Wrong delivery promise in a state closed for a festival | ₹2k–5k/mo | 4 | Weak. Low stakes per mistake. |
| Global firms with Indian operations (treasury, payroll, EOR) | Thousands, but hard to reach | Payment runs to India on a bank holiday | $49–499/mo | 5 | USD upside, but they buy Copp Clark or build it. Second phase. |
Assumption: you haven't chosen a dataset or a buyer. The catalog row reads as "any niche data developers need". That's the problem: a developer who needs the data can usually get it free. The buyers above pay only for what free sources don't give: centre-level bank holidays, settlement days, change alerts and audit history.
Overall pain score for the idea as described: 3/10. FX, IP location and global holidays are solved problems with free tiers. For the India wedge: 5–6/10. Real, but most teams tolerate a yearly copy-paste.
2.2 Competitors and substitutes
Free sources (your biggest threat)
| Source | What it covers | Why a buyer would or wouldn't switch to you |
|---|---|---|
| RBI holiday matrix (rbi.org.in) | NI Act holidays for 34 office centres, by month. HTML only. Notes that banks close on 2nd and 4th Saturdays. | It's the source of truth, and it's free. It has no API, no change feed and no history. You win on "machine-readable, alerting, versioned". |
| python-holidays (MIT licence) | 250 countries with subdivisions, including India's 36 states and UTs, and 24 financial markets including NSE | Excellent and free. It has no RBI bank-holiday category for India, its India static dates are hardcoded by year, and it's a library, so changes arrive only when a release ships and the customer upgrades. |
| Nager.Date | 210 countries, open source, free API | No Indian regional or bank detail worth building on (not checked in depth). Fine for national holidays. |
| NSE, BSE, MCX holiday pages and circulars | Trading and clearing holidays by segment | Free, but in PDFs and circulars, with changes announced by circular. |
| Consumer pages (BankBazaar, Bajaj Finserv, bank blogs) | State-wise bank holiday lists for readers | Not for machines, not sourced per date, and legally risky to copy. |
| An intern and a config file | Whatever the team re-keys each January | The real competitor. It costs nothing until the year a date moves. |
Paid holiday and calendar APIs
| Product | Price (checked 30 Sept 2026) | What it lacks for this buyer |
|---|---|---|
| Calendarific | Free 500 calls; $12/mo or $100/yr Starter; $500/yr Business (weekly updates); $4,000/yr Enterprise (daily updates) | General public holidays. No evidence of RBI centre-level bank holidays or settlement calendars (not checked in depth). |
| Holiday API (holidayapi.com) | $249/yr countries; $399/yr with 3,680 states and provinces | General public holidays by state. Not bank or settlement calendars. |
| TradingHours.com | Market Status API $50 / $100 / $150 a month (24 / 148 / 900+ markets, via EODHD); enterprise pricing on request | Global breadth for trading and settlement. India depth and RBI bank holidays by centre unverified. A real threat if a buyer wants 20 countries. |
| Copp Clark | Subscription, price on request. Publishing since 1841. Bank, currency, exchange trading and settlement holidays, T+ settlement calendars. | The enterprise gold standard for banks. Too expensive and too broad for an Indian fintech's engineering team. |
Other candidate datasets (rejected, summarized)
| Dataset | Incumbents and substitutes | Why not |
|---|---|---|
| IP geolocation | IPinfo, MaxMind (free GeoLite), ipdata, ipapi, ip2location, db-ip | Accuracy needs infrastructure and years of data. IPinfo charges $26 / $163 (per the catalog) and has a free tier. |
| Exchange rates | ECB and RBI (free), Open Exchange Rates $12 / $47 / $97, ExchangeRate-API $10 / $30 (per the catalog), fixer | Identical data everywhere. Price is the only lever, and it's pinned near free. |
| Indian company and GST data | Tofler (₹15,000/yr for 40 credits), Probe42, Signzy, Surepass, Perfios/Karza, Apify wrappers from $2.50 per 1,000 records, data.gov.in master data | Crowded, funded, cheap per call, and built on portal access with terms-of-service risk. |
2.3 Vitamin or painkiller?
A vitamin for most buyers, a painkiller for a few.
- Vitamin: "we'd like the holiday list in JSON." They'll copy it once a year and move on.
- Painkiller: "a state declared a holiday on Thursday for Monday, our collections dialler called 4,000 borrowers on a bank holiday, and our due-date SMS was wrong." Or: "our settlement engine credited a day early because the exchange closed and we didn't know." That costs money, trust and an audit finding.
- Test: if the API disappeared tomorrow, what would the buyer lose? For the list, nothing: they'd copy the page. For the change alerts and history, they'd lose a person-hour a week and their audit trail. Only the second retains.
The honest problem: NPCI shifts NACH debits off holidays automatically, and UPI runs every day. The most expensive failure in Indian lending is already handled by the rails. What's left is real, but it's operational friction, not a fire.
2.4 Market size: venture-scale, lifestyle, or a feature?
Bottom-up SAM (rough, not verified):
- Indian firms with engineering teams whose code depends on bank or exchange business days: ~2,000–5,000.
- Realistic spend with one vendor for this: ~$300–1,200 a year.
- SAM ≈ $0.6–6M a year. Capturing 5–10% is $30k–600k ARR, and the upper end needs Enterprise contracts.
- Adding global firms with Indian operations (USD) might double that, but they're harder to reach and more likely to buy Copp Clark.
Answer, by dataset:
- IP location, FX, global holidays: features that are already free or owned. Not a company for a new entrant.
- Indian company data: a venture-funded KYC category. Not yours to win alone.
- India business days: a small lifestyle business. Durable, cheap to run, and capped in the low tens of thousands of dollars of MRR at best.
2.5 Geography and legal points
- Location matters for the checking routine. Being in India, reading Hindi, and ideally one more regional language helps read state gazettes. English covers RBI and the exchanges.
- Facts aren't copyrightable, and India has no separate database right like the EU's (reasoned, not verified by a lawyer). But copying another compiler's formatted list is still the weakest ground. Build from primary sources only.
- Selling to firms abroad from India: register for GST, file a Letter of Undertaking to export services without IGST, and use Stripe or Paddle for USD (standard practice, not verified for this case).
- No personal data is processed, so DPDP obligations are minimal. Log API keys and usage only.