TaxOwl
Automate the monthly FX-compliance loop (invoice → match → EDF/pack → CA review → AD close) that the 1 Oct 2026 EDF mandate makes unavoidable.
RBI/FEMA (purpose codes, realisation clock, EEFC). GST (LUT, GSTR-1). Income tax (44ADA, Form 67 / FTC).
FX corridor markup, double taxation, INR round-trip on money that should sit in EEFC.
Speed and accuracy on matching / purpose codes over manual CA work, plus proactive FX and cash-timing calls a once-a-year filer never makes.
Wedge, buyer, price, and market size not yet locked.
Freelancer cite
Not sized
Calls done
Research opens inline on this page (needs http, not file://). Competition is a sibling page — works from disk.
Draft · needs further research
Segment our customers: how many, what they do, and their income — and how stable that income is. Numbers that are not ready stay as 15M or TBD — hover for the caveat.
Segmentation, earnings bands, and the TAM stack are a working cut from the research folder. FX-liable headcount, state/city, and invoice regularity are gaps. Do not quote any row as a published TAM until that pass lands.
Headcount cite · hover
FX exporters · hover
Wedge · hover
Economic Survey gig series (order of ~12M, growing). Mostly domestic, low FX, not our problem.
Industry cites in the low-teens of millions. Mix of domestic gigs and export work. Still the wrong unit for FEMA.
RBI’s unit. Anyone billing a foreign client for services. This is the set that must file . No count exists yet.
People and earnings are what the research folder actually published. Regularity and state are mostly gaps. Hover TBD. Do not add the people column into a TAM without reading the source note — these universes do not nest cleanly.
| Segment | People | Earnings (published) | Regularity | By state | Source |
|---|---|---|---|---|---|
| Software / IT / web | ~2.8M | Web ₹50k–2L / mo potential; enterprise software ₹20–50 LPA | TBD · invoices often large | TBD | |
| AI / data | TBD · 15% of WC-gig roles | AI/ML ₹20–60 LPA; data/ML ₹1.5–4L / mo potential | TBD | TBD | |
| Design / UX / creative | ~1.9M bundled creative | UI/UX ₹40k–1.5L / mo ranges | TBD · more ≤₹10L invoices likely | TBD | |
| Writers / marketing / SEO | TBD · 12% of WC-gig roles | Writing ₹40–80k / mo potential; marketing ₹30k–1L / mo | TBD | TBD | |
| Consulting (finance, strategy) | ~1.1M | Enterprise consulting ₹2–5L / mo potential; Grok ₹8–40L+ band | Retainers common | TBD | |
| Creators (YT / Meta / ads) | TBD | TBD · platform $100 thresholds | Monthly platform payout | TBD |
Income across freelancers (not by skill): ~60% < ₹3 LPA · ~30% ₹5–15 LPA · ~10% ₹15–60 LPA — Dheya 2026 citing Payoneer / KPMG-related. Average ~₹8 LPA is called misleading in the same source.
Each row is an input, not a conclusion. The only number that would be our TAM is “service exporters with foreign invoices.” That row is empty.
| Layer | Working figure | What it is | Feeds TAM? | Source |
|---|---|---|---|---|
| Gig / platform workforce | 12M (FY25) · 7.7M FY21 · 23.5M FY30 proj. | Official series. Includes delivery / ride-hail. | No — too wide | Economic Survey 2025–26 · NITI Aayog Gig and Platform Economy · |
| Freelance / independent cite | 15M · 15–20M platform-registered | Industry headcount. Mixes domestic + export. | Placeholder only | Dheya · Jobbers · Flexable · CII Skills · |
| White-collar gig | ~6.8M | Company-led + consultant models. Adjacent. | No — not exporters | foundit / 2025 · |
| Tech + creative + professional | ~5.8M derived | Sum of three Dheya sector point estimates (~2024). | Working numerator only | Market report Appendix A.1 |
| Service exporters (FX invoices) | TBD | RBI’s unit. Anyone who must file EDF. | This would be TAM | No census. Gap. |
| × regularity (monthly / retainer) | TBD | Who has a repeating invoice, not a one-off. | WTP / SOM filter | No survey. Creators monthly (Grok). Consultants “retainers common” (Grok). |
| × earnings band that can pay | TBD | Top ~10% at ₹15–60 LPA is a share of freelancers, not of exporters. | SOM filter — do not multiply 15M × 10% | Dheya 60/30/10 · |
| × state | TBD | Where they live / bank. Needed for AD-branch GTM. | Geo, not TAM | Not in this research set. Next: PLFS, GSTIN, STPI city, IEC state tables. |
| Gap | What we would need | In folder? |
|---|---|---|
| FX / EDF-liable headcount | Count of residents invoicing foreign clients (IEC, e-FIRC, purpose-code, or GST export) | No |
| State / city split | KA / MH / TS / DL / TN or STPI cities | No |
| Invoice regularity by segment | % monthly vs quarterly vs one-off | Anecdote only (creators monthly, consultants retainers) |
| People × earnings in the same survey | Headcount in each LPA band inside a named skill | No — people tables and LPA tables are different sources |
| Compliance rate | % who already file anything like EDF | No — report says none |
Scales with earnings. A ₹8L writer and a ₹40L engineer do not have the same leakage or the same FEMA pain.
Competition v0.2 floated ₹1.5–9L/yr “given” on a ₹15–60L earner using a 10–15% leakage stack. That is arithmetic on an unpublished band — keep it in the analysis page, not in the pitch as fact.
Scales with stability of those earnings, not the headline rate.
Pick later
A wedge is the first promise we can keep for a named person. Everything else is a later layer. Competition v0.2 has a recommended wedge — it stays an option until interviews agree.
Own the new obligation nobody files automatically. CA on the exception queue. Gateway-agnostic ledger: Payment Received + EDPMS Closed on the same invoice.
Why it might win: Oct 1 is a forcing function; rails stop at FIRA. Why it might lose: Xflow already has a compliance desk and fresh capital.
Volume play for designers, writers, smaller invoices. Bulk declaration, AD closes on exporter word. Simpler product, weaker willingness-to-pay.
Why it might win: most invoices may sit here. Why it might lose: Zolance-priced market, thin surplus.
Lead with FX / Form 67 / EEFC rupees. File EDF because you cannot keep the rupees without a clean ledger.
Why it might win: people pay for money, not forms. Why it might lose: leakage % is unmeasured; looks like a rail.
Priya-shaped product: one console, many freelancer clients, 24-hour queue as the service. Freelancer is the user; CA firm is the buyer.
Why it might win: validation notes going in. Why it might lose: slower land, different GTM, we have not spoken to 5 CAs yet.
Only if IEC or STPI turns out to be the actual bottleneck for tech exporters. Do not build this first on a hunch.
Depends on the IEC question. Priya.
Full wedge write-up and platform-risk note → competition.html
Not 10% ready
There is no channel plan, no offer, no first-100 list. What exists is an instinct and an interview kit. Treat everything below as options to test, not a launch sequence.
| Date | Person | Segment | Signal |
|---|---|---|---|
| 18 Aug | CA Srixxx Jaxxx | Freelancer (int'l tutoring) + practicing CA | Confirmed he'd use it while receiving foreign income. Named the Oct 1 EDF change unprompted, before seeing any of our material. Also a CA — counts toward both buyer tracks, doesn't resolve which one. |
Full notes: Srixxx call transcript.
They feel the bank. They already pay Skydo/Wise. We sit next to that bill. We talk to their CA so we are not “replacing the CA.”
Fails if most say “my CA handles it” and the CA will not adopt us.
Seat licence or per-client. Priya’s console is the product. Freelancer never pays us directly in v1.
Fails if CAs want a junior, not software, or will not change October workflow.
Skydo / Xflow / Karbon attach EDF as a feature. We are the vendor behind their button. Fast distribution, ugly economics, we teach them to replace us.
| Motion | What it is | Why it might work | Why it might not |
|---|---|---|---|
| Warm network | IIM-A / ex-Credain / “ask for 2 intros” | Fastest path to 15 honest calls | Friends are polite; they are not a market |
| Complaint miners | r/IndiaTax, r/IndiaInvestments threads on FIRC / purpose code / stuck remittance | They already have a story and a rupee amount | Small n; selection bias toward disasters |
| Peerlist / LinkedIn / X | Devs and designers billing foreign | Dense, public, low friction | Noisy; easy to look like a pitch |
| CA clubs / Taxguru / ICAI circles | CAs already writing about 2026 export rules | Pre-qualified; one CA is many clients | Different sale; we have not done it |
| October content | Two-page “what changes 1 Oct” as the trade for a call | Costs nothing; doubles as first asset | Not written yet |
Channel copy lives in validation/where-to-find-them.md. Scoreboard in validation/findings.md. Neither is a GTM plan.
Hypothesis · Priya pending
Each process type we might run for a freelancer. Software comes after these are named. Done means a system of record moved, not “the app showed a tick.”
| Process | What it is | Trigger | Steps | Done when | Who | Cadence |
|---|---|---|---|---|---|---|
| File EDF + close EDPMS | Declare the month’s service exports and get the bank to close the monitoring entry. | Invoice raised in a calendar month (software / services). | Capture invoices → draft one EDF → exporter signs → submit to AD (or STPI/SEZ) → AD enters EDPMS in 5 working days → match remittance / FIRC → AD closes. | EDPMS entry closed. Not “EDF uploaded.” | Exporter accountable. AD closes. Platform drafts + watches SLA. | Monthly · due 30 days from month-end |
| ≤₹10L self-declaration | Bulk close of small invoices on the exporter’s word. | Open EDPMS entries ≤ ₹10L per invoice. | Group eligible entries → draft quarterly pack → exporter signs declaration → AD closes without extra docs. | Those entries closed on the declaration. | Exporter declares. AD closes. Platform packs. | Quarterly pack |
| LUT | Letter of Undertaking so GST-registered export of services goes out at 0% instead of charging IGST. | GST registered and exporting. | Confirm GSTIN + export nature → file LUT on GST portal for the FY → keep acknowledgement with the month’s pack. | LUT accepted for the financial year. | Exporter / CA files. Platform reminds + stores. | Once a year |
| GST registration | GSTIN once turnover crosses the threshold (generally ₹20L; ₹10L in special-category states). | Aggregate turnover hits the line, or they opt in to claim ITC / LUT. | Check run-rate → apply → GSTIN live → then LUT + GSTR-1 become monthly work. | GSTIN issued. | Freelancer. CA typically files. Platform flags the threshold. | Once |
| GSTR-1 (export invoices) | Report zero-rated export invoices on the GST return. | GST registered and invoicing foreign clients. | Map month’s invoices to GSTR-1 export table → file → keep in sync with EDF month. | Return filed for that tax period. | Exporter / CA. Platform pre-fills from the same invoice master. | Monthly |
| IEC keep-alive | If they hold an Import-Exporter Code: annual DGFT confirm (incl. “No Change”) 1 Apr–30 Jun. Pure services often need no IEC — do not push one. Goods path is out of scope. | Exporter master says hasIEC, or 1 April arrives. |
Skip if no IEC. Else: DGFT login → confirm/update → store ack. On address/bank/partner change: modify now (₹200). If deactivated: file pending update, then resume EDF. | Ack for this FY on the master, or explicit “no IEC”. | Exporter on DGFT. CA not required. Platform reminds + stores. | Yearly window · plus on change |
| Purpose code + FIRC match | Each inward remittance coded (e.g. P0802 software) and tied to an invoice / EDF line. | Money lands (bank, Skydo, Wise, Payoneer, AdSense, Meta). | Read credit / e-FIRA → suggest purpose code → match name / amount / invoice → flag mismatches before AD genuineness check. | Each credit has a code and a matched invoice. | AD is authority. Platform pre-matches. | Per remittance |
| Realisation clock | Watch 15 months (FCY) / 18 months (INR) from invoice date. After +1 year unpaid: future exports only against advance / LC. | EDPMS entry open. | Start clock on invoice date → age dashboard → chase → extension letter if needed → restriction flag if it blows. | Entry closed before the restriction line, or extension on file. | Exporter owns the receivable. Platform watches. This is the product. | Continuous |
| Extension request | Ask the AD to extend EDF filing or realisation when the month will slip. | Will miss 30-day EDF or the realisation window. | Assemble reason letter + evidence → exporter/CA signs → AD decides. | Written AD grant or rejection. | Exporter + CA. Platform drafts. AD decides. | As needed |
| e-BRC / GST refund | Bank realisation certificate generated from closed EDPMS — needed to claim GST refund on exports. | EDPMS closed. | Confirm close → AD generates e-BRC from EDPMS → attach to refund claim. | e-BRC available. We do not issue it. | AD generates. Platform tracks eligibility. | After each close |
| Form 67 / FTC | Claim Indian credit for tax withheld abroad (US platform/client withholding). | Foreign tax was withheld. ITR season. | Collect withholding evidence → fill Form 67 → file with ITR. | Form 67 on record for that year. | CA files. Platform assembles. Checklist TBD — Priya | Yearly |
| EEFC | Hold export USD in an Exchange Earners’ Foreign Currency current account so they do not convert to INR and back. | Regular FCY receipts and/or FCY costs. | Open EEFC with AD → route receipts there → pay USD costs from it → document for books. | Account live and receipts landing there when it is the right choice. | Freelancer + AD. Platform advises. Checklist TBD — Priya | Ongoing |
| FX / leakage review | Monthly look at corridor markup, double conversion, and withheld tax — the 10–15% stack. | Any foreign credit that month. | Compare rail vs mid-market → flag Form 67 candidates → flag INR round-trips that should have been EEFC. | Review logged — not a guaranteed recovery %. | CA + freelancer act. Platform flags. | Monthly |
Four surfaces a freelancer, a bank, a regulator, and an admin would each touch. Only one is a real workflow today — the rest are ideas, not builds. Do not read this table as "done."
| Interface | Who | Today | Idea on the table |
|---|---|---|---|
| Freelancer | Exporter | None built | WhatsApp bot ("Text") — raise an invoice by chatting, get compliance status back in the same thread. Website stays system of record either way; WhatsApp is a front door, not a replacement. |
| Bank (AD) | AD branch officer | None — no design-partner branch yet | Bicycle phase: file through the freelancer's own bank portal by hand. API/SFTP only after one AD branch proves it will actually close entries from us (see Execution gate). |
| Regulator | RBI | None, by design | We do not file RBI directly, ever. Only the AD writes EDPMS / PRAVAAH. Treat any pitch line that implies a direct RBI interface as wrong. |
| Internal / CA ops | Priya, or the CA firm if D is the wedge | None — described, not built | 24-hour review queue: exceptions, compounding cases, 44ADA halts. This is the one console the product actually needs first. |
24-hour human review queue. Not “100% filing accuracy.” The exporter remains accountable.
We do not move the money. We sit on whatever they already use.
v1.1 · 20 Aug 2026 · CA S.J. chart + FEMA 23(R) · not Priya-signed
Two processes are now specified enough to agent-ise: IEC keep-alive and EDF file + EDPMS close. LUT, GST, Form 67, EEFC stay in the catalog. Software comes after the exceptions below are named. Done means a system of record moved.
Scope: DTA export of services (design, consulting, writing, teaching, coaching, non-STPI freelance). Goods and STPI/SEZ software are out of product scope — classifier rejects and stops. They appear on diagrams only as reject nodes.
If they hold an IEC: DGFT annual update 1 Apr–30 Jun, including “No Change.” Miss 30 Jun → deactivate → banks can refuse remittances. Pure services often need no IEC — do not push one.
Done = DGFT ack for this FY, or “no IEC” on the exporter master.
Monthly declaration of service exports, then the AD closes the monitoring entry. Exporter signs. CA is not required. AD certifies. Rails (Skydo et al.) can draft; they cannot write EDPMS.
Done = EDPMS entry closed, not “PDF generated.”
Invoice-then-pay is only one path. Advance and “money landed, no invoice” are different. Partial (more coming) is not short-and-done (write-off). Agents classify the event pair first.
Invoice raised, or credit landed, or both.
Services? Else reject goods / STPI software.
Advance · uninvoiced credit · invoiced unpaid/partial/paid.
One object per rupee we must declare.
Platform. Full export value, even if unpaid.
Cannot skip. CA not required.
DTA services. How we hand it over is Q11.
AD writes the ledger. We do not.
Credits sum to declared. AD genuineness → close. e-BRC eligible.
Keep open. EDF stays at full value. Clock runs.
AD reduction / write-off, or ≤₹10L declaration if residual qualifies.
AD may extend. After +1 year unpaid: future exports vs advance / LC only.
Diagram footnote: goods (shipping bill) and STPI/SEZ software (SOFTEX) are reject nodes, not product paths.
Rows 2 and 3 look similar in a bank statement. They are not the same object.
| # | What happened | Not the same as | ExportUnit | EDF | Close |
|---|---|---|---|---|---|
| 1 | Invoice, then full pay | — | invoiced · match 1:1 |
Month of invoice, full value | Normal match |
| 2 | Advance — contract exists, invoice later | Uninvoiced credit | advance_held until invoice attaches |
Non-software may file on or before receipt. Pick a rule — Q14. | Advance + balance |
| 3 | Credit, no invoice, no contract (AdSense, YouTube, residual) | Advance | uninvoiced_credit — force an invoice or a declaration. Do not skip EDF. |
Month of credit until Q14 is closed | Same credit |
| 4 | Partial — more is expected | Short-and-done | invoiced_partial |
Full value already filed | Keep open |
| 5 | Short, no more coming | Partial | Reduction pack | Amend / AD reduction | AD write-off or ≤₹10L declaration |
| 6 | Overpay | Partial | Split extra credit into a new unit or an outward (15CA/15CB — other process) | Do not inflate the original line | Split |
| 7 | Pay before EDF | Advance (if invoiced, it is just early money) | Credit sits unmatched | Still due 30 days from invoice-month end | Match after EDPMS exists |
| 8 | EDF in, money never | Short | Chase + realisation extension | Already filed | Cannot close; +1 year → restriction |
| 9 | Late EDF | Late realisation | Extension letter | File with AD grant | Once AD accepts |
| 10 | Many invoices / clients, one month | One form per invoice | Many units, one EDFBatch |
One form, Section 2B | Per EDPMS line |
| 11 | Split rails | Overpay | Many credits, one unit | One line | Sum of credits |
| 12 | ≤₹10L per bill, tired of paper | Skip EDF (wrong) | Still declared | EDF required. This is close, not skip. | Quarterly self-declaration |
| 13 | Goods or STPI software | Services | reject_* |
— | Out of scope |
| Step | Exporter | CA | Platform | AD | Rail (Skydo etc.) |
|---|---|---|---|---|---|
| Draft EDF | Accountable | Not required | Can draft | May one day draft in-app (Q13 risk) | Has invoices if they issued them; still must reach an AD |
| Sign EDF | Signs | No | Cannot skip | — | — |
| Certify / EDPMS | — | — | — | Certifies, writes, closes | Not the ledger |
| Spend the rupees | Once AD has credited | — | — | Genuineness is before credit. Close vs credit = Q12. | Already paid them |
No → skip. Do not push a code on pure services.
DGFT login. Confirm or update. “No Change” still files.
On the exporter master before the next EDF.
Auto-deactivate. File pending update. No late fee. Days you cannot get paid.
Goods exporters must hold an IEC. Out of scope. Master-data change (address, bank, partners) = modify when it happens (₹200), do not wait for June.
Every file is a Document { type, issuer, issuedOn, refs, file{ mime, sha256 }, fields }. No invented EDPMS XML.
| type | Typical mime | Must-have fields | Issuer | Agent use |
|---|---|---|---|---|
invoice | no, date, SAC, currency, amount, buyer, LUT/IGST | Exporter (we may draft) | ExportUnit invoiced | |
contract | pdf / image | parties, fee, advance clause, country | Either party | Advance vs uninvoiced |
credit_advice | pdf / csv / screenshot | date, amount, rail, narrative | Rail or AD | Credit |
efirc | no, date, amount, purpose code | AD / rail’s Indian partner | Proof of inward | |
edf | RBI Annex pdf, filled | month, units[], declaration, exporter sign | Exporter (we draft) | Submit to AD |
edf_ack | pdf / screenshot | AD stamp / ack no | AD | at_ad |
self_decl_10l | entries ≤₹10L, exporter sign | Exporter (we pack) | Close path | |
extension_letter | which clock, reason, evidence | Exporter (we draft) | Late file / late money | |
reduction_request | old value, new value, reason | Exporter | Short-and-done | |
iec_certificate | IEC | DGFT | Run or skip A | |
iec_update_ack | pdf / portal | FY, no-change or delta | DGFT | A done |
lut · gstr1_export · ebrc | pdf / json | FY / period / closed EDPMS | GSTN / AD | Other processes. We never issue e-BRC. |
Document (classifier + fields).ExportUnit using the event matrix. Reject goods / STPI software.EDFBatch → exporter sign.PDF / Excel · SAC · currency · contract
One form, all recipients. Section 2B services.
Digital sign / declaration. Cannot skip.
DTA non-software → AD. Software → AD or STPI. SEZ → DC.
Only when STPI / SEZ was chosen.
Within 5 working days of receipt.
Match remittance / FIRC → AD verifies genuineness → close on credit. e-BRC eligible.
Per invoice, not annual. Quarterly pack allowed. AD closes on exporter word.
15 mo FCY / 18 mo INR from invoice date.
AD decides if filing or realisation will slip.
If unpaid > 1 year past due / extended date.
From closed EDPMS only. We do not issue it.
AD recommends to RBI RO. Residual practice — 2026 text rationalised.
Roles: E exporter · P platform · AD bank · SA STPI / SEZ DC · RBI rare.
| # | Task | Input | Output | Depends on | R | A | C | I | Notes |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Capture & validate invoices | Invoice PDF/Excel, client, SAC, currency, amount, contract | Invoice master + flags | — | E | E | P | AD | Auto-extract SAC / FX; flag gaps |
| 2 | Prepare consolidated monthly EDF | Validated invoices + IEC, GSTIN, PAN, AD code | Draft EDF (Annex fields) | 1 | P | E | AD | One EDF / month. Section 2B services. | |
| 3 | Review & approve EDF | Draft EDF | Approved EDF | 2 | E | E | P | — | Exporter signs. Cannot fully automate. |
| 4 | Submit to specified authority | Approved EDF | Ack / authenticated EDF | 3 | E / P | E | SA / AD | — | DTA non-software → AD; software → AD or STPI; SEZ → DC |
| 5 | SA forwards to AD | Authenticated EDF | EDF at AD | 4 | SA | SA | AD | E, P | Only if SA ≠ AD |
| 6 | AD enters EDPMS | Authenticated EDF | EDPMS entry | 4 or 5 | AD | AD | — | E, P | SLA: 5 working days |
| 7 | Monitor realisation clock | EDPMS + invoice date | Ageing (15 / 18 mo) | 6 | P | E | AD | — | 15 mo FCY · 18 mo INR |
| 8 | Record remittance & match | Credit advice / FIRC / IRM | Matched realisation | 6 | AD | AD | P | E | Genuineness before credit |
| 9 | Close EDPMS (normal) | Matched realisation | Closed entry + e-BRC eligible | 8 | AD | AD | — | E, P | Close on credit |
| 10 | ≤₹10L self-declaration | Open entries ≤ ₹10L + text | Declaration pack | 6 or open | E | E | P | AD | Per invoice. Quarterly OK. Reductions too. |
| 11 | AD closes on declaration | Task 10 pack | Closed entries | 10 | AD | AD | — | E, P | No extra docs for ≤₹10L / bill |
| 12 | Extension request | Reason letter + docs | Grant / reject | 3 or 7 | E | E | AD | P | AD on reasonableness |
| 13 | Advance / LC restriction | Open > 1 yr past due / extended | Restriction flag | 7 | P | AD | E | — | Future exports only vs advance / LC |
| 14 | e-BRC | Closed EDPMS | e-BRC | 9 or 11 | AD | AD | — | E, P | From EDPMS only |
| 15 | Caution-list handling | EDPMS caution feed | Alert + restricted docs | Ongoing | AD | AD | E | P, RBI | TBD — 2026 text rationalised; residual bank practice |
| Document | Link | Status |
|---|---|---|
| FEMA 23(R)/2026-RB | rbi.org.in | In map |
| A.P. (DIR) Circular No. 20 · 16 Jan 2026 | rbi.org.in | In map |
| EDF Annex | In map | |
| RBI press release 16 Jan 2026 | rbi.org.in | In map |
| A.P. (DIR) Circular No. 12 · 1 Oct 2025 (₹10L precursor) | TBD — MD has a placeholder URL. Search RBI as Circular No. 12 of 2025–26. | |
| PRAVAAH (AD → RBI) | pravaah.rbi.org.in | In map |
| Late submission fee schedule for EDF | TBD — none published for 2026 EDF. AD extension is the relief. | |
| Priya-signed monthly checklist | TBD — this tab is the research stub until she replaces it. |
Landscape · 17 Aug scan
Rails move money and stop at FIRA. Software and CAs take the same rupee we want. The pitch’s “we are not a gateway” line is positioning. The comparison a freelancer actually opens is Zolance or Remote Munshi.
Free / ₹199 / ₹499 a month. Invoicing, LUT, GSTR-1. No CA layer, no EDF automation. Same freelancer, undercuts on price. ~3 months in; traction unproven.
₹35,400/yr below ₹75L; ₹3,54,000/yr above. Validates a CA-priced band. Manual. Does not scale the way a queue does.
$16.6M Series A @ $85M (PayPal Ventures, Stripe in the round). Human compliance desk on EDPMS/SOFTEX. Closest analog. Highest platform risk.
Own collection and often e-FIRA. Skydo: $10M Series A, 30k+ MSMEs/freelancers. Partner-shaped unless they ship monthly EDF. PillowTax is adjacent (NRI/founders), not this wedge.
That is a small lift on top of e-FIRA they already generate. Our only durable answers so far: sit across rails (people split volume), and a CA exception layer a payments company will not staff like Priya. Speed still matters more than the pitch admits.
Numbers in this tab were pulled 17 Aug 2026 for the analysis page. Verify before quoting outside this folder.
Toward a plan
The pitch’s bicycle → scale → agencies is a story. An execution plan starts when a gate is passed. Until then we are still choosing.
Without conversations, GTM stays an instinct. Use the existing outreach copy. Update validation/findings.md every third call.
When it arrives, this memo’s Solution tab is rewritten to her flow. Do not keep both. IEC and the leakage checklist are hers to close or park.
Written in the validation scoreboard. That decision is the first line of a real GTM, not a slide.
Not “AI Digital CA.” A named segment, a monthly artefact, a price neighbourhood (Remote Munshi vs Zolance), a definition of done: EDPMS entry closed.
File through the freelancer’s existing bank portal. Do not hire a bank-integration team before ~20 paying betas have submitted packs through one branch that will actually close them.
Parked. The ₹20–60k band is a Remote Munshi neighbour if and only if the CA queue is real in the first ship, not a later promise.
Product, GTM experiments, interviews, platform architecture, fundraising. Owns this memo staying honest.
Process, IEC, leakage checklist, risk guardrails, the 24-hour queue. 10-year CA. Fundraising.
Navdeep is off the external story. He can still run developer/PM interviews. GIFT City is not a team slide.
Source folder
Open a file inline. Claims in this memo should point here. The viewer needs http (this site or a local server). Raw .md also works as a download.
Unanswered
If a row is still open, the matching pitch line is a draft.
Market size — TAM/SAM/SOM are all TBD (row 1). No count of FX-liable exporters exists anywhere in the research folder. Pricing — no measured willingness-to-pay (row 2). ₹20–60k/yr is a Remote Munshi analogy, not our data. Neither goes in front of an investor or a freelancer as fact until closed.
| # | Question | Why it is open | Owner | Gate |
|---|---|---|---|---|
| 1 | How many freelancers, of what kind? High risk | Gig ≠ freelancer ≠ service exporter. No census by skill × FX. TAM placeholder is 15M. SAM/SOM are TBD. | Nirav | Before any published size |
| 2 | Value created vs extracted? High risk | Created scales with earnings (risk + leakage). Extracted scales with stability (retainer vs feast/famine). No measured WTP by segment. | Nirav + Priya | Before a price card |
| 3 | Who is the buyer? | Instinct: freelancer, liaise with their CA. Validation notes also said the CA may pay. Calls done: 1 / 15 + 0 / 5. | Nirav | On or before 5 Sep 2026 |
| 4 | Which wedge first? | Monthly EDF close, ≤₹10L packs, leakage as the sale, CA-batch, or STPI/IEC path. Competition v0.2 recommends A — not locked. | Both | After buyer call |
| 5 | Does a DTA service freelancer need an IEC? | Goods: yes. Pure services: still unconfirmed. 20 Aug: if they hold one, annual update 1 Apr–30 Jun is mandatory (incl. “No Change”). Process A is now “keep-alive or skip,” not “get everyone a code.” | Priya + S.J. | Before Phase 1 scope |
| 6 | Which AD branch will close our packs? | We cannot write EDPMS. Until one branch is a design partner, autopilot is a brochure. | Priya + Nirav | Before bicycle ship |
| 7 | GIFT City — idea or decision? | Incentives / grants / credits. Planning idea. Brand stays TaxOwl either way. | Nirav | Later · fundraising |
| 8 | Can we defend 10–15% leakage? | FX + Form 67 + EEFC are real mechanisms. The % is not a measured cohort. | Priya | Before a public claim |
| 9 | What other benefit areas can we offer? | Compliance + leakage + AI speed/accuracy is the current stack. Unresearched: retirement/investment routing, credit access off a clean filing history, multi-currency invoicing, other FEMA-adjacent filings (ODI, LRS) freelancers hit as they scale. | Nirav | Before roadmap beyond MVP |
| 10 | Who creates and signs the EDF? Part-closed 20 Aug | S.J.: exporter signs; CA is not required; AD certifies. Platform / rail can draft. Still: can an accountant (non-CA) click submit for them with a mandate? | S.J. | Before agent roles |
| 11 | How does a filled EDF actually reach the AD? | No public exporter EDPMS API. Email, branch upload, net-banking, physical? Until this is named, “we file EDF” is a PDF generator. | S.J. + one AD branch | Before bicycle ship |
| 12 | Can the exporter spend the money before EDPMS close? | AD genuineness check is before credit. Whether close is simultaneous with credit was not answered on 20 Aug. Product copy must not say “frozen until we file.” | S.J. | Before any “use your money” line |
| 13 | Will ADs / Skydo / Xflow ship EDF in their own apps? | S.J.: “very simple, bank may introduce extension in their apps.” We remain useful only if we sit across rails and own exceptions (no invoice, advance, partial, reduction). This is a competition question, not a filing one. | Nirav | Wedge lock |
| 14 | When there is no invoice, which month and which clock? | Advance ≠ uninvoiced credit. FEMA 23(R): non-software services may file EDF on or before receipt. Clock in the regs is from invoice date. Credit-only (AdSense etc.) has no invoice date. Do not code a default. | S.J. + Priya | Before ExportUnit schema freeze |
| 15 | Realisation: 9 months or 15 / 18? | S.J. IEC editorial still cites 9 months. FEMA 23(R)/2026 is 15 months FCY / 18 months INR from invoice. Which sentence we print on the year graph. | S.J. | Before compliance-year copy |
| 16 | Can a reduction / write-off and a ≤₹10L declaration apply to the same residual? | Shrikant chart: AD may permit reduction, non-realisation, or write-off with satisfactory reasons; ≤₹10L exception on partial realisation. Overlap not specified. | S.J. | Before close-pack agent |
Shared language
Dotted terms elsewhere open a short definition. Search filters this list. TAM/SAM/SOM entries describe how those words have been used — they are not a published size.