FeedWise (originally "a niche data-feed API")
Idea status: Idea stage · Target: MRR ladder by month 24 (recommended: $3k at ~15 hrs/week, $5k full-time) · Verdict: No as described. Go small, as an India business-day API for lenders, fintechs and brokers, with a day-45 kill test. · Last updated: 30 Sept 2026
Start here → WHAT-TO-DO-AND-AVOID.md for the final call: the MRR ladder, customer math, what to do, what to avoid, and the checkpoints.
Where the idea came from: row D9 ("Niche data-feed API") of the 30 Sept 2026 micro-SaaS idea catalog. The catalog's evidence is IPinfo (bootstrapped, ~$1M ARR by 2017), OpenCorporates (UK filing) and apilayer (bought by Idera in 2021). "FeedWise" is a working name. Check trademark and domain before using it publicly.
The one-line concept
An API that tells Indian lenders, fintechs, brokers and payroll platforms whether a date is a business day for a given RBI centre, payment rail or exchange, and what the next one is. Every date is sourced to RBI, an exchange or a state gazette. A webhook fires within hours when any date changes.
Why this dataset (short version)
Seven candidate datasets were scored on six tests: hard for a customer to assemble, changes at short notice, businesses pay, gap in free sources, a solo founder can keep it accurate, and no licence risk. India bank and market business days scored 24/30. The next best scored 19. The detail is in analysis/01-verdict.md.
Folder layout
feedwise/
├── WHAT-TO-DO-AND-AVOID.md ← final analysis and decision (read first)
├── README.md ← this index
├── analysis/ ← the investor-style assessment
│ ├── 00-one-page-brief.md
│ ├── 01-verdict.md
│ ├── 02-market-reality-check.md
│ ├── 03-feature-scrutiny.md
│ ├── 04-expanded-feature-catalog.md
│ ├── 05-pre-mortem.md
│ ├── 06-fundability.md
│ ├── 07-gaps.md
│ └── 09-assumptions-and-open-inputs.md
├── plans/ ← execution plans
│ ├── 08-90-day-plan.md
│ └── 11-24-month-gated-roadmap.md
└── research/ ← verified, cited evidence
└── 10-verified-research.md
File numbers match every other idea in the portfolio, so cross-references like "doc 08" work the same way.
Documents
| # | Document | What it answers |
|---|---|---|
| — | WHAT-TO-DO-AND-AVOID.md | Final decision: MRR ladder odds, customer math, 12 do's, 14 avoids, checkpoints |
| 00 | analysis/00-one-page-brief.md | The whole verdict on one page |
| 01 | analysis/01-verdict.md | Which dataset and why, odds by MRR level, Tier A and B, fundable yes/no |
| 02 | analysis/02-market-reality-check.md | Buyer, pain score, competitors, vitamin vs painkiller, market size |
| 03 | analysis/03-feature-scrutiny.md | Every candidate dataset and implied feature sorted into Table stakes, Differentiator, Distraction or Liability |
| 04 | analysis/04-expanded-feature-catalog.md | Features business-day API buyers ask for, each classified |
| 05 | analysis/05-pre-mortem.md | Three most likely causes of death, warning signs, whether each is fixable |
| 06 | analysis/06-fundability.md | Would I invest, the skeptic's first 5 minutes, metrics that flip the answer, bootstrap vs raise |
| 07 | analysis/07-gaps.md | Gaps to paid, renewed and referred customers |
| 08 | plans/08-90-day-plan.md | First 90 days, week by week, with the day-45 kill test |
| 09 | analysis/09-assumptions-and-open-inputs.md | Assumptions made, and the inputs that would change the verdict |
| 10 | research/10-verified-research.md | Cited research (30 Sept 2026) and what it changed |
| 11 | plans/11-24-month-gated-roadmap.md | Month 0–24 phases, gates, revenue path, budget guardrails |
Caveat
Hours per week, location, team and buyer access were never provided. The assumptions are in analysis/09. Still unverified: the number of Indian firms that would buy this (NBFC, broker and fintech counts), whether they'll pay against a free RBI page and a free library, and how often RBI and exchange holiday dates change mid-year. See research/10.