SB StartupBasket
All ideas
76 /100 GO Low complexity

EDFiler — monthly export filer for Indian service exporters

Files the new monthly export declaration for Indian agencies and SaaS firms who never had to file one before.

Compliance SaaS India SMBSolo-builderCompliance-drivenAI-agentServices-exportFEMA
— views
Evaluation Scores
76/100

GO

Overall Score

15
Problem
12
Demand
13
Build
12
Distrib.
11
Revenue
8
Time
5
Defense

EDFiler

1. One-liner

Files the new monthly export declaration for Indian agencies and SaaS firms who never had to file one before.

2. Trend signal — why now?

On 1 October 2026, the RBI’s Foreign Exchange Management (Export and Import of Goods and Services) Regulations, 2026 come into force. They replace the FEMA 2015 export regulations plus the stack of Master Directions and circulars layered on top. The piece that matters here: SOFTEX dies, and a unified Export Declaration Form (EDF) replaces it for all exports — goods, services, and software alike.

Three things changed at once, and each one on its own would be a minor compliance footnote. Together they create a customer segment that did not exist in August 2026 and will exist in October.

One — the P0802 escape hatch closes. For years, a large number of Indian freelancers, agencies and small SaaS firms took foreign payments under purpose code P0802 (“software consultancy/implementation other than those covered in SOFTEX form”) and reasonably concluded they were outside the SOFTEX net. Under the 2026 regime, all service exports require EDF filing. Winvesta’s write-up is blunt about it: the system “eliminates the P0802 workaround that allowed some consultants to bypass declarations.” The population that thought it was exempt now isn’t.

Two — banks become the certifying authority, and nobody has told the customer. Previously STPI held the monopoly on certifying software exports. From 1 October, DTA units can get EDF certified by their AD bank or STPI — STPI certification is no longer mandatory. iSPIRT, which follows this policy area closely, flagged that the upside is real but the operational picture isn’t: “bank implementation processes remain undefined, leaving operational uncertainty,” the software definition is “very ambiguous, and it seems to include everything intangible,” and purpose codes “lack clarity and aren’t mapped to HSN or Service Accounting Code standards.” A new obligation with an undefined process is exactly the moment a tool gets bought.

Three — the filing shape flipped from per-invoice to monthly consolidated, on a 30-day clock. Filing is due within 30 days of the end of the invoice month. March invoices → file by 30 April. That’s a recurring monthly operational task with a hard deadline, which is the shape that sustains a subscription. It is also a genuine simplification for anyone at volume — one write-up describes a SaaS company processing 500 invoices monthly across 30 countries that previously managed hundreds of SOFTEX entries and now files a single monthly EDF. Simpler in principle; still nobody’s software does it.

The stakes are not theoretical. FEMA §13(1) penalties run up to three times the sum involved, or ₹2,00,000 where the amount isn’t quantifiable, plus ₹5,000 per day for a continuing contravention. Procedural lapses were capped at ₹2 lakh after the April 2025 reforms — but a two-year backlog of unfiled declarations against realised foreign remittance is not obviously a procedural lapse.

And the segment is demonstrably ignorant of the obligation today, before the rules even tighten. A Bangalore CA firm that sells this service writes: “Most of the Small and Medium software exporting companies are not having an idea about Non STPI registration. And, most importantly, for all the software companies (IT and ITES), however small or big they are, Non STPI registration is mandatory!” Another practitioner note calls it out directly: “A common misconception is that freelancers, small agencies, or early-stage SaaS firms are exempt, but that is incorrect.”

Sizing the gap: only 2,125 STP units were registered across all of India in FY 2025-26. That is the entire population currently inside the formal software-export filing system. India has roughly 15 million freelancers (world’s second-largest freelance workforce) and tens of thousands of small IT/SaaS firms and agencies billing foreign clients. The delta between 2,125 and that number is the addressable market, and on 1 October it stops being optional.

Provenance:

3. The opportunity

There are three groups adjacent to this problem and none of them are actually solving it for the customer I care about.

The cross-border payment rails (Skydo, xFlow, Karbon, Winvesta, PayGlocal). These are well-funded and competent, and xFlow auto-issues eFIRA within 24 hours covering GST/EDPMS/RBI compliance. But their compliance coverage is structurally limited to money that flows through their own rail. If you’ve been taking payment via Wise for two years, or direct wire to your ICICI current account, or Stripe→Payoneer, the rail can’t file for what it never saw. Compliance is their retention feature, not their product — which is exactly why it stops at the edge of their ledger. The customer’s obligation covers all their foreign revenue, not the slice that happens to route through one vendor.

The CA firms. They’ll do it, manually, per-filing, and they’ll do it correctly. They’re also the reason the pain is currently tolerable and the reason pricing has a ceiling. But a CA doing monthly consolidated EDF filings across a client book is doing rote data assembly — pull invoices, map remittances to invoices, get purpose codes right, produce the declaration, chase the bank. That’s the work AI collapses.

NIRYAT (“compliance OS for Indian SME exporters”) is the closest real competitor and worth taking seriously: cross-portal reconciliation across DGFT/ICEGATE/EDPMS/bank, eBRC self-certification, refund radar, EPCG tracker. But read its targeting — ₹5 crore to ₹500 crore export turnover, textiles/engineering/chemicals/pharma, filing 5+ shipping bills monthly, onboarding design partners in Tirupur, ₹60,000–₹24,00,000/year. That is a goods exporter product for a Tirupur garment unit. A 12-person Pune dev shop billing $40K/month to three US clients has no shipping bills, no ICEGATE, no RoDTEP scrip, no drawback scroll, and cannot justify a ₹60K/year floor for a product whose modules are 80% irrelevant to it.

The gap is specific: services and software exporters, sub-₹5 crore, who have zero shipping bills, who were outside the filing net until 1 October 2026, and who need one recurring monthly artifact produced correctly. Nobody is building for them because until this quarter they weren’t a compliance customer at all.

4. Target market

Primary customer: The founder or finance lead at an Indian software services business billing foreign clients — dev shops and digital agencies (5–50 people), bootstrapped SaaS companies, design studios, and IT consultancies. Annual foreign revenue ₹40 lakh to ₹5 crore. Non-STPI or unregistered. Located anywhere, but concentrated in Bengaluru, Pune, Hyderabad, NCR, Chennai, Indore, Jaipur, Kochi. Typically no in-house CFO; a part-time CA handles GST and ITR, and nobody owns FEMA.

A secondary segment worth serving on a cheap tier: high-earning solo freelancers and consultants billing $5K–$25K/month to overseas clients. Bigger population, thinner wallet, better viral loop.

Why they buy — in their words. From the practitioner literature and CA case files:

“Most of the Small and Medium software exporting companies are not having an idea about Non STPI registration.” — Balakrishna & Co, Chartered Accountants, Bangalore

“A common misconception is that freelancers, small agencies, or early-stage SaaS firms are exempt, but that is incorrect.” — practitioner guidance on Non-STP registration

“They were due for merger with another company but the process was put on hold till STPI regulation was complied with!” — Balakrishna & Co, on a client engagement

“A State run bank, refused to operate the account, till such time, SOFTEX forms were submitted.” — same source

“India Company / Captive center in India do not comply with the aforementioned regulation” — Lalit Valecha, on widespread P0802 misuse in place of P0807

“Errors in shipping bill data… banks delaying updates of remittance details” — EximPe, on why entries stay open

“Freelancers and small SaaS firms are not exempt if they receive foreign remittance, and there is no value threshold since an old USD 25,000 floor was removed in 2013.”

“Bank implementation processes remain undefined, leaving operational uncertainty.” — iSPIRT, on the October 2026 EDF transition

The buying trigger is not civic virtue. It is one of four moments: (a) the bank sends a letter asking for declarations against unmatched inward remittance; (b) a GST refund or LUT renewal gets held up; (c) due diligence for a fundraise, acquisition, or bank loan surfaces the gap; (d) their CA reads the October circular and forwards it with “we need to discuss this.”

Rough TAM reasoning: Only 2,125 STP units file today. India’s services exports target for FY26 is US$450 billion, and MSMEs in IT are explicitly named as a key contributor. Conservatively, 40,000–80,000 Indian entities export software/IT services with enough regularity and volume to feel a monthly filing obligation, plus a long tail of several hundred thousand serious freelancers. Capturing 1,500 paying entities at ₹1,500/mo average is ₹2.7 crore ARR (~$320K). Capturing 5,000 is ~$1.1M. This is a real business well before it needs the whole market.

Why now for them: Before 1 October they had a defensible “I didn’t think it applied to me.” After, the obligation is unambiguous, monthly, and dated — and the first bank letters will land in the November–January window as AD banks operationalise the new regime against their existing inward-remittance data.

5. Product sketch (MVP)

  • Connect your money, wherever it lands. Import foreign inward remittances from bank statements (PDF/CSV upload for ICICI, HDFC, Axis, SBI, Kotak to start) and from Wise, Payoneer, Stripe, PayPal, Skydo and xFlow exports. One place, regardless of rail.
  • Auto-match remittances to invoices. Pull invoices from Zoho Books, QuickBooks, Xero, or plain CSV, then match each inward remittance to the invoice(s) it settles — handling the classic breakers: platform fees deducted at source, FX rounding, timezone date gaps, payer name ≠ client name, and part-payments across invoices.
  • Purpose code check. Flags remittances booked under the wrong code (the P0802-where-it-should-be-P0807 problem) before it becomes a mismatch the bank rejects, with the reasoning shown.
  • Monthly EDF pack, generated on the 1st. A consolidated declaration for the prior month’s service/software exports, formatted for the AD-bank route, ready to submit within the 30-day window — with a per-bank cover note because implementation practice will differ by bank.
  • Backlog mode. Point it at the last 24 months of statements and it produces the catch-up filing set plus a written exposure summary: what’s unmatched, how old, and what the realistic remediation path is. This is the wedge feature — it’s what someone buys the day the bank letter arrives.
  • Deadline tracking. Countdown to the 30-day filing deadline, realisation-window tracking against the new 15-month clock, and alerts on anything ageing toward a problem.
  • Auditor’s binder. One-click export of matched invoices, remittance evidence, declarations and filing acknowledgements — the artifact you hand a CA, a due-diligence team, or a bank.

6. AI angle — what’s load-bearing

Strip the AI out and this becomes a spreadsheet template that nobody finishes. The AI carries two jobs that are genuinely hard and genuinely repetitive.

Reconciliation across dirty, heterogeneous inputs. Bank statement PDFs from five Indian banks in five layouts, Wise and Stripe CSVs with their own schemas, invoices in whatever format the agency uses. Matching “USD 4,850 credited 14 Mar, remitter STRIPE TECHNOLOGY INC” to “Invoice #2026-041, $5,000, Acme Corp, 28 Feb” requires reasoning about platform fees, FX rate, settlement lag, and the fact that the payer is a processor rather than the client. Deterministic rules solve the easy 60%; the tail is where filings die, and that tail is exactly what an LLM with good tool scaffolding handles well. The industry’s own guidance confirms these are the standard failure modes: amount differences from platform fees, timezone date gaps, payer name mismatches, wrong purpose codes.

Classification and declaration drafting. Deciding whether a given line of revenue is software export, professional services, or something else — against a definition iSPIRT itself calls “very ambiguous, and it seems to include everything intangible” — and then producing a defensible declaration with the reasoning attached. That judgment work is what the CA currently bills for.

The AI is not a chat box on the dashboard. It is the thing that turns 24 months of mess into a filing.

7. Localization angle

This is the localization play — it’s an India-only regulatory product and that’s the entire point. The specificity is the moat against generic global tools: FEMA, EDPMS, purpose codes, AD-bank practice, STPI-vs-bank routing, GST LUT interaction, the 30-day monthly clock.

Pricing must be Indian. A ₹999–₹2,999/month tier works where $49/mo does not; the freelancer tier has to sit near ₹499. UPI autopay and GST-compliant invoicing are table stakes. Distribution is WhatsApp- and CA-mediated, not email-drip. And the language is English — this buyer sells software to Americans — which keeps the build lean.

8. Business model — path to $1M–$5M ARR

Pricing:

  • Solo — ₹499/mo. One entity, up to 15 inward remittances/month. Freelancers and consultants.
  • Studio — ₹1,999/mo. Up to 100 remittances/month, multi-currency, accounting integrations, auditor’s binder. The core agency/SaaS tier.
  • Firm — ₹4,999/mo. Multi-entity, higher volume, priority support, CA seat access.
  • Backlog cleanup — ₹15,000–₹60,000 one-time, scaled by months and volume. High-margin, and it’s the entry point for most customers.
  • CA partner plan — ₹9,999/mo for a practice managing up to 25 client entities from one console.

ACV: ₹24,000 ($285) blended, before backlog revenue. Backlog fees realistically add ₹8,000–₹12,000 of first-year revenue per customer, pushing effective year-one ACV toward ₹34,000 (~$400).

Rough math to $1M ARR: ₹8.7 crore. Roughly 3,000 Studio-tier customers at ₹1,999/mo (₹7.2cr) plus ~₹1.5cr from Solo tier and backlog work. Alternatively ~1,200 Studio + 150 CA partner practices gets most of the way there with far fewer logos to acquire — which is why the CA channel matters disproportionately.

Rough math to $5M ARR: ₹43 crore requires either ~15,000 paying entities, or a materially higher ACV via expansion. The honest path is the latter: add GST refund/LUT tracking for exporters, FIRA/eBRC handling, and an entity-compliance calendar, moving Studio ACV from ₹24K toward ₹60K, then needing ~6,000 customers. $5M is a stretch and I’d rather underwrite this as a strong $1–2M ARR business that a small team keeps.

Expansion path: Backlog cleanup → monthly subscription → multi-entity → CA-practice seats → adjacent FEMA/GST filings for the same entity. Every one of those is the same data, already ingested.

9. Go-to-market wedge — first 100 customers

1. The CA channel — the highest-conviction motion. There are practitioners actively selling Non-STPI/SOFTEX filing as a service line today; they’re findable because they publish on it (Balakrishna & Co, Swati K & Co, IndiaFilings, KMGC, and dozens of similar firms rank for these keywords). Build a list of 300 such firms from search results, ICAI directories, and LinkedIn “FEMA/STPI consultant” titles. The pitch is not “we replace you” — it’s “the EDF obligation just expanded your addressable client base tenfold and you cannot service it manually; take our CA plan and bill your clients for the outcome.” Offer revenue share. A single mid-size practice brings 15–25 entities. 20 practices = 300+ entities.

2. The October deadline content ambush. Every payments company is writing generic “SOFTEX is dead” explainers to farm keywords. None of them ship a free tool. Build a free EDF exposure checker — upload 12 months of bank statements, get a report of unmatched foreign remittance and estimated filing gap, no signup required to see the number. Push it into the exact queries these firms are ranking for, plus r/india_startups, r/developersIndia, r/IndianStreetBets-adjacent founder communities, IndieHackers India, and the SaaSBoomi / iSPIRT / Headstart founder circles. The free report is the sales pitch: it produces a specific, alarming, personal number. Convert to backlog cleanup.

3. Direct outreach to identifiable software exporters. Indian companies with foreign clients are discoverable: Clutch.co and DesignRush directories of Indian dev agencies (thousands, with revenue bands and client geographies listed), GitHub org pages, and companies with an active GST LUT. Scrape 2,000, send a personalised note referencing the 1 October change and their specific profile, offer the free exposure check. At a 6% reply and 15% close on replies, that’s ~18 customers per 2,000 sends — modest, but the list is renewable and the message is date-driven and therefore urgent.

4. Ride the bank letters. When AD banks start writing to customers about unmatched inward remittance (expect a wave November 2026–February 2027), the search volume for “bank asking for export declaration” spikes. Have the answer page and the tool already ranking. This is reactive demand capture at the exact moment of maximum willingness to pay.

5. Partner with the payment rails’ blind spot. Wise, Payoneer and PayPal have large Indian freelancer/agency bases and offer them no FEMA filing support — unlike Skydo and xFlow, they aren’t Indian AD-adjacent and won’t build it. Community and affiliate placement where those users congregate is uncontested.

10. Build complexity — justification

Low. No novel technology. The work is document ingestion (bank statement PDFs, payment platform CSVs), a matching engine with an LLM handling the messy tail, a rules layer for purpose codes and deadlines, and document generation. Accounting integrations (Zoho Books, QuickBooks, Xero) are well-documented public APIs. There’s no government API dependency for the MVP — the filing goes to the AD bank, so v1 generates the pack and the customer submits it, which sidesteps the biggest integration risk entirely.

The genuine work is domain encoding, not engineering: getting purpose codes, thresholds, deadlines and per-bank practice right, and keeping them right. Budget 8–10 weeks to a usable v1 for a technical founder plus a FEMA-literate CA on retainer. The CA is non-optional — this product is wrong and worthless if the domain logic is wrong.

11. Gating checklist

GatePass?Note
Legal in target market✅Compliance-assistance software. Generates declarations the customer files; doesn’t impersonate an AD bank or STPI, and doesn’t require a licence. Must avoid holding out as a CA.
Ethical — no harm / dark patterns✅Helps small firms meet a real legal obligation cheaply. The one discipline required: the free exposure checker must report the honest number, not a manufactured scare.
Market exists (evidence above)✅Obligation dated 1 Oct 2026; CAs already bill for the manual version; funded payment companies content-market the keyword; only 2,125 units currently in the formal net.
1–5 person team can build this✅Technical founder + FEMA-literate CA. Two people to v1.
Launchable with <$50K / ₹40L✅₹6–10 lakh realistically: CA retainer, LLM inference, hosting, outreach tooling.

All five pass.

12. Feasibility score

AxisWeightScoreNotes
Problem intensity2015/20Real and legally hard-edged — FEMA §13(1) is 3× the sum involved plus ₹5,000/day continuing, and there are documented cases of a frozen merger and a bank refusing to operate an account. Docked because it’s latent pain: most of this segment doesn’t know it’s exposed yet, so it’s a problem I have to make them feel rather than one they wake up feeling. That’s a real GTM tax.
Demand evidence1512/15Strong indirect evidence — CAs actively sell the manual service, funded fintechs content-market the exact keywords, a dated regulation forces the behaviour, and practitioners state on the record that the segment is ignorant and non-compliant. Docked 3 because I have practitioner testimony and regulatory certainty rather than customers already paying for this specific product.
Build feasibility1513/15Off-the-shelf stack, no government API in the critical path for v1, 8–10 weeks with two people. Docked for the messy-input reconciliation tail and the need for a domain expert on retainer.
Distribution clarity1512/15The CA channel is named, enumerable, and economically motivated; the free exposure checker converts on a specific number; a dated deadline creates urgency; the bank-letter wave is predictable demand capture. Docked because CA partnerships take longer to close than the model assumes and no channel here is yet proven.
Revenue mechanics1511/15Pricing is benchmarked against real alternatives (CA fees, $19–29/invoice payment rails, NIRYAT’s ₹60K floor) and the $1M path needs ~3,000 customers — achievable but not trivial at ₹1,999. Docked because Indian SMB price sensitivity is real, churn after backlog cleanup is a genuine risk, and $5M requires a product expansion I can’t yet underwrite.
Time to first revenue108/10Backlog cleanup is a one-time fee that can be sold and delivered semi-manually before the product is finished — revenue in 4–6 weeks is plausible. Not a 9–10 because the buying trigger is externally timed and the first real wave lands with the bank letters.
Defensibility105/10Execution-and-domain moat: accumulated per-bank filing practice, purpose-code edge cases, and CA-channel relationships compound. But a funded payment rail could bolt this on as a retention feature, and NIRYAT could move down-market. A 12-month head start plus channel ownership is the realistic defence, not a moat.
Total10076/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · content-heavy

Technical because reconciliation across dirty multi-source financial data is the product. Content because the CA channel and the deadline-driven search demand are both won with authoritative writing — and because in a category this confusing, being the clearest published explanation of the new rules is itself the distribution. A FEMA-literate CA co-founder or retained advisor is mandatory, not optional.

Key assumptions to validate (3–5)

  1. Assumption: Small services exporters will pay to fix a problem they don’t yet know they have. How to test: Run the free exposure checker against 50 real firms’ statements (recruited via CA partners and founder communities) and measure what fraction converts to a paid backlog cleanup within 14 days of seeing their number. Below 15% and the latent-pain problem is fatal.
  2. Assumption: AD banks will accept a third-party-generated EDF pack, and the format is stable enough to productise. How to test: Before writing significant code, take a hand-assembled pack to the trade desks of four banks (ICICI, HDFC, Axis, one PSU) and get their actual acceptance criteria. Divergent or hostile answers mean a per-bank build, which changes the cost model.
  3. Assumption: CA practices will resell rather than treat this as a threat to billable hours. How to test: Pitch 25 firms that publicly market Non-STPI/SOFTEX services. Measure how many take a revenue-share pilot. Fewer than 5 and the primary channel is gone.
  4. Assumption: Retention survives backlog cleanup — customers keep paying monthly once the scare is resolved. How to test: Can’t be tested pre-launch; instrument from day one and treat month-4 retention as the leading indicator. Below 70% and this is a services business wearing SaaS clothes.
  5. Assumption: The October regime lands roughly as written, without a deferral or a de-minimis carve-out for small service exporters. How to test: Track RBI circulars, FIEO/NASSCOM/iSPIRT representations, and AD-bank operational guidance weekly through Q4 2026.

Risk flags

  1. Regulatory risk (the big one, and it cuts both ways): The regulation is the market. A deferral of the 1 October date, or a de-minimis threshold exempting small service exporters, would substantially deflate the urgency. Note there is precedent for relief in this area — RBI discontinued automatic caution-listing after FIEO pressure, and the 2026 rules already introduce a ₹10 lakh self-declaration route for small-value entries. A similar carve-out for services is plausible. Watch for it.
  2. Platform dependency (bank-side): v1 depends on AD banks accepting a generated pack. Banks are not obliged to make this easy, and iSPIRT has already flagged that implementation processes are undefined. If banks insist on proprietary portals or their own formats, the product fragments into per-bank work.
  3. Incumbent absorption: Skydo, xFlow and Karbon are funded, already own the customer relationship for anyone using their rail, and already market compliance. Any of them could ship an EDF module. The defence is serving all rails including their competitors’ — a position they structurally cannot copy without undermining their own business — plus owning the CA channel.
  4. Latent-pain GTM tax: Selling insurance against a risk the buyer doesn’t perceive is a harder, slower, more expensive sale than solving a felt pain. This is the single biggest reason the score is 76 and not 85. The entire GTM depends on manufacturing awareness efficiently — which is why the free exposure checker is load-bearing, not a nice-to-have.
  5. Down-market competition from NIRYAT: It already does cross-portal reconciliation and eBRC self-certification. Its pricing floor and goods-exporter focus protect this niche today, but a services SKU is an obvious move for them.

14. Structured verdict

Score:                  76/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder who can handle messy financial-document
                        reconciliation, paired with a FEMA-literate CA (co-founder
                        or retained). Must be willing to write authoritative content —
                        the CA channel and search demand are both won on credibility.
Time to revenue:        4–8 weeks (backlog cleanup sold semi-manually before v1 ships)
Capital to launch:      ₹6–10 lakh ($7–12K)
Top 3 assumptions to validate first:
  1. Latent pain converts — run the free exposure checker on 50 real firms;
     require >15% conversion to paid backlog cleanup within 14 days.
  2. Banks accept a third-party-generated EDF pack — take a hand-assembled pack
     to 4 AD banks' trade desks and get written acceptance criteria BEFORE building.
  3. CAs resell rather than resist — pitch 25 firms already selling Non-STPI/SOFTEX
     services; require ≥5 revenue-share pilots.
Kill criteria:
  - Abandon if RBI defers 1 October 2026 or introduces a de-minimis services
    exemption that covers firms under ₹5 crore export turnover.
  - Abandon if fewer than 5 of 25 targeted CA practices take a revenue-share pilot
    AND direct outreach converts below 3% — that removes both primary channels.
  - Abandon if 2+ of 4 major AD banks require a proprietary submission format that
    can't be generated externally.
  - Abandon if month-4 subscription retention after backlog cleanup falls below 60% —
    that's a services business, not SaaS, and should be priced and run as one.

15. Next step — 1-week validation sprint

Day 1–2 — Kill the bank risk before anything else. Hand-assemble one complete monthly EDF pack from a real (consenting) exporter’s data. Walk it into the trade finance desks of ICICI, HDFC, Axis and one PSU bank. The question is narrow: “If my client submits this, do you accept it — and what exactly do you need that’s missing?” Written or emailed criteria from at least 3 of 4. If banks are hostile or each demands a different proprietary format, stop here — the product is a consulting business, not software.

Day 3–4 — Test whether latent pain converts. Recruit 20 Indian software exporters (₹40L–₹5cr foreign revenue) through founder communities, Clutch listings and two CA contacts. Manually run their last 12 months of statements and produce a real exposure report — unmatched remittance, filing gap, estimated FEMA exposure. Deliver it, then quote ₹25,000 for backlog cleanup. The measurable outcome: how many say yes on the call, not “interesting, send details.”

Day 5 — Test the channel and decide. Pitch 25 CA practices that already sell Non-STPI/SOFTEX filing on a revenue-share partner plan. Count signed pilot agreements, not expressions of interest.

Go / no-go, falsifiable: Proceed only if ≥3 of 4 banks give workable acceptance criteria, ≥4 of 20 exporters commit money for backlog cleanup, and ≥5 of 25 CA practices sign a pilot. Miss any one of the three and the corresponding risk — bank format, latent pain, or channel — is the thing to fix before writing code, not after.

Interested in a detailed proposal?

Get a deep-dive with market research, competitive analysis, and implementation roadmap.

Contact us

info@startupbasket.ai