A Progressive-Disclosure Platform for Startup–Investor Synergy

Founders need visibility to raise capital. Investors need enough substance to screen a deal. Between those two needs sits proprietary information - unfiled IP, technical architecture, unit economics, customer lists - which loses its legal protection the moment it is shared carelessly.

Indian law gives founders two thin twigs to stand on: a contractual NDA, enforceable under the Indian Contract Act, 1872, but only where breach and resulting damage can be proven; and the general law of confidence, an equitable remedy with an even heavier evidentiary burden. Neither survives a broad, undocumented, low-friction pitch process of the kind most deal-flow platforms currently encourage.

Existing platforms solve discovery and syndication well. None of them solves the disclosure-gating problem structurally. Confidentiality is left to a static NDA template rather than being built into how information is released.

The design principle: progressive disclosure

Rather than one dualistic choice - share the full deck or share nothing - information is released in layers, each gated behind a proportionate legal and technical control. Nothing at Layer 1 should ever be sensitive enough to need protecting. By Layer 3, the parties are committed enough that a bilateral, logged NDA is a reasonable ask on both sides.

Layer 1 - public teaser. Problem statement, market sizing, stage, traction headline, ask amount. No algorithms, source code, pricing formulas, customer names or unfiled IP. Open to browse and filter by sector, stage and ticket size. This layer is designed to exclude anything the founder reasonably treats as confidential, patent-sensitive, personally identifying or commercially material. No NDA needed or expected.

Layer 2 - gated data room. Financials, cap table, technical architecture, product roadmap, redacted key contracts. The investor requests access; the platform auto-generates and e-signs a bilateral NDA before unlocking, and every view and download is timestamped and logged. The legal basis is section 10A of the IT Act, 2000 on the validity of electronic contracts, read with the Indian Contract Act, 1872.

Layer 3 - deal room. Term sheet drafts, SHA and SSA drafts, IP assignment records, full customer and vendor contracts. Opened only on mutual written interest, with watermarking, screenshot restriction and time-boxed access, and a deal-specific confidentiality addendum layered onto the base NDA - with section 38 of the Specific Relief Act, 1963 on injunctive relief as a backstop.

A pre-Layer-2 IP hygiene prompt should be built into the flow. Before any technical detail unlocks, the founder is nudged to confirm whether the underlying innovation is patentable and, if so, whether a provisional application has been filed. Trade secret protection may be fragile once shared even under NDA; registered IP may not be. NDA protection depends on confidentiality controls and contractual proof, while registered IP provides stronger, legally defined rights without eliminating ownership, validity, infringement or enforcement risk. The platform's role here is procedural nudging, not legal advice.

What the platform is, and deliberately is not

It is a matching, discovery and controlled-disclosure layer between founders and investors, with an audit trail that makes a future confidentiality claim provable rather than merely arguable.

It is not a securities exchange, a crowdfunding portal, or a party to any investment. No allotment, subscription or consideration ever moves through the platform.

Section 42 of the Companies Act, 2013 caps a private placement at 200 persons per financial year and prohibits anything resembling a public offer or advertisement of securities. On crowdfunding specifically, SEBI has issued no regulation or circular as of 2026. The platform should therefore not host subscription, allotment, escrow, payment, binding investment commitments or execution of securities transactions.

This structure may reduce certain regulatory risks, but does not by itself determine whether the platform sits outside the scope of the Companies Act, the SEBI Act, securities regulations, investment-advisory rules or other applicable law. The analysis must be revisited if the platform solicits investors, recommends opportunities, negotiates terms, verifies issuer claims or charges transaction-linked remuneration. An open, algorithmically matched pitch feed leading straight into a subscription flow risks being read as exactly that. Keeping share allotment, SHA execution and fund transfer off-platform - routed through counsel, a registered RTA and normal banking channels - keeps the platform on the discovery side of that line.

The legal risk matrix

• Securities law. Matching plus in-platform subscription reads as an unregistered private placement under section 42, or as unauthorised crowdfunding. Mitigation: no subscription or allotment functionality on-platform; cap the visible investor pool per listing where relevant; route issuance through counsel and an RTA. Residual exposure: low, if the boundary is maintained and documented in the terms.
• Merchant banking and investment advice. A success fee tied to a completed raise can look like unregistered merchant banking or investment advisory activity. Mitigation: flat subscription fees on the investor side and platform or data-room usage fees on the founder side, not success fees contingent on capital raised. Residual exposure: medium - the fee structure needs periodic legal review as the model evolves.
• Confidentiality and trade secrets. India has no standalone trade secrets statute; protection depends entirely on maintained confidentiality plus provable breach. Mitigation: auto-executed, logged NDAs at Layers 2 and 3, audit trails of access and download, and an arbitration clause to keep the leak itself out of public litigation. Residual exposure: medium, inherent to any disclosure-based model but materially reduced by logging.
• Data protection. Founder, team and cap-table data is personal data under the DPDP Act, 2023, and cross-border investor access raises transfer questions. Mitigation: consent-based processing, purpose limitation in the data room, and a documented basis for cross-border access, with notice, withdrawal, retention, processor terms, grievance handling and breach response in place. Residual exposure: low to medium.
• Intermediary liability. The platform could be held liable for user-uploaded content - misrepresented figures, infringing material - without safe harbour. Mitigation: section 79 of the IT Act, 2000, supported by a compliant grievance and takedown mechanism and no editorial curation of listings beyond basic screening. Residual exposure: low.
• KYC and AML. On-boarding investors without verification exposes the platform to being a conduit for illicit funds once deals reach Layer 3. Mitigation: accreditation and KYC checks at signup, consistent with PMLA obligations. Residual exposure: low.
• Foreign-investor onboarding. FEMA pricing, instrument, eligibility or reporting non-compliance, and cross-border flow concerns. Mitigation: residency and route self-declaration, issuer FEMA and NDI checklists, no on-platform subscription or payment, and issuance and filings through counsel, the AD bank and the RTA. Residual exposure: medium.
• Sectoral restrictions and conditional FDI. Foreign investment in prohibited or approval-route sectors without the required caps, conditions or approvals. Mitigation: capture the issuer's sector, carry an FDI-policy disclaimer, and require approval confirmation for sensitive sectors. Residual exposure: medium.
• Consumer protection. Misleading claims on deal quality, success rates or regulatory safety. Mitigation: conservative, verifiable claims, a clear distinction between discovery and regulated activity, transparent fees, a grievance mechanism, and marketing consistent with the terms. Residual exposure: low to medium.
• Investor accreditation on the Angel Fund route. SEBI's September 2025 reform restricts Angel Funds to accredited investors, with existing funds required to comply by 8 September 2026, sharply narrowing the pool of Angel-Fund-routed capital. Mitigation: capture accreditation status at onboarding and segment listings by accredited versus self-certified or direct-angel status, since direct individual angel investment is not subject to the same mandate. Residual exposure: medium.

Positioning, for the terms of use

The platform should describe itself consistently across its terms, marketing and founder and investor agreements in language that reinforces the boundary: it facilitates discovery and controlled information exchange between founders and investors; it does not solicit investment, recommend securities, arrange financing for a fee contingent on a raise, or hold or transmit investor funds; and all investment decisions, terms and documentation are the responsibility of the parties and their respective counsel.

That framing should be drafted and cross-checked by counsel before launch, and revisited if the fee model or feature set changes - a founder-side success fee or an in-app subscription flow would each independently require re-testing.

Why this is the solution

The founder-side trust problem is not hypothetical. Publicised disputes over investors allegedly building on pitched ideas continue to shape founder wariness toward informal disclosure. At the same time, investors resist blanket NDA requests at the first-meeting stage, citing deal volume. That asymmetry is precisely what progressive disclosure is designed to resolve: no ask at the teaser stage, and a provable, logged NDA only once an investor is serious enough to request deeper access.

::