CANONICAL 15 APPSCC.
REPO-CANONICAL · PLANNING ARCHIVE LABELED
Diligence · Standalone company records

PRE-SEED DATA ROOM

Bankabil supplies shared infrastructure and reusable templates, but investors must be able to diligence each startup as a standalone company.

Companies
15
Shared Folders
8
Shared Documents
157
Investor-Ready Gate
0 / 18

Data room readiness by company

Separation doctrine

The result should be independent diligence rooms. An investor entering DiligenceProof’s room should see no ambiguity about whether they are investing in OperatorProof, Bankabil or any other cohort company. The common infrastructure strengthens the technical case, while legal rights, market, economics, customer evidence, risks and financing remain specific to the company.

Bankabil Technology License and Services Agreement

  • ›Bankabil owns or controls the shared Rails/Rust infrastructure.
  • ›The startup receives a defined license to use it.
  • ›The startup owns its customer relationships and domain-specific workflow.
  • ›Domain-specific product improvements are clearly allocated.
  • ›Shared-kernel improvements are clearly allocated.
  • ›Hosting, security, maintenance, service levels and fees are defined.
  • ›No startup automatically owns another startup’s product data or intellectual property.
  • ›Investor rights in one startup do not create rights in the others.
Bankabil architecture-use scheduleIntercompany data-isolation policyShared-services pricing scheduleOpen-source dependency scheduleFounder/company intellectual-property boundary memo

01 · Company formation and ownership

Each independent legal entity needs its own EIN and corporate records. The IRS issues EINs directly and charges no application fee.

  • Certificate of incorporationPENDING
  • BylawsPENDING
  • Initial board consentPENDING
  • Founder stock purchase agreementPENDING
  • Founder vesting schedulePENDING
  • Intellectual-property assignment agreementPENDING
  • Proprietary information and inventions agreementPENDING
  • Founder roles and responsibilities memoPENDING
  • Current capitalization tablePENDING
  • Fully diluted capitalization tablePENDING
  • Stock ledgerPENDING
  • Option-pool plan or proposed option-pool memoPENDING
  • EIN confirmationPENDING
  • Business bank account confirmationPENDING
  • State registrations and foreign qualifications, where applicablePENDING
  • Beneficial ownership and corporate-record checklistPENDING
  • Conflict-of-interest disclosurePENDING
  • Related-party transaction disclosurePENDING

02 · Fundraising materials

For a SAFE financing, use a recognized form adapted by company counsel. A Regulation D offering generally requires a Form D notice filed through EDGAR after the first sale; counsel determines the correct federal and state process.

  • 10–12 slide investor deckPENDING
  • One-page company overviewPENDING
  • Two-page investment memoPENDING
  • Founder-market-fit narrativePENDING
  • “Why now?” memoPENDING
  • Market mapPENDING
  • Competitive landscapePENDING
  • Business-model summaryPENDING
  • Go-to-market planPENDING
  • Initial customer pipelinePENDING
  • Fundraising target and use-of-funds planPENDING
  • Milestone-based financing planPENDING
  • Investor FAQPENDING
  • Risk-factor memoPENDING
  • Current fundraising-status trackerPENDING
  • Investor outreach listPENDING
  • Warm-introduction mapPENDING
  • Follow-up and diligence trackerPENDING
  • Financing instrument summaryPENDING
  • Draft SAFE or other financing instrument reviewed by counselPENDING
  • Pro forma post-financing cap tablePENDING

03 · Product definition

Every company answers the same eleven questions: company name, product name, founder-market fit, primary buyer, primary reviewer, repeatable workflow, first receipt primitive, Evidence Room contents, pricing wedge, MVP boundary, claims limitation.

  • Product requirements documentPENDING
  • Product thesisPENDING
  • Target-customer profilePENDING
  • Buyer-versus-reviewer mapPENDING
  • Workflow specificationPENDING
  • Receipt schema specificationPENDING
  • Evidence Room specificationPENDING
  • MVP scope documentPENDING
  • Explicit non-goals documentPENDING
  • Claims-limitation documentPENDING
  • User-permission matrixPENDING
  • Data-source inventoryPENDING
  • Integration roadmapPENDING
  • Product roadmap for the next 12 monthsPENDING
  • Demo scriptPENDING
  • Demo acceptance criteriaPENDING

04 · Customer discovery and commercial proof

A letter of intent should identify intended workflow, expected users, demo or pilot period, evidence to be generated, success criteria, proposed commercial price, data-access limitations, and a statement that the letter is nonbinding unless counsel specifies otherwise.

  • Minimum of 15 documented customer interviewsPENDING
  • Interview notesPENDING
  • Interview consent and attribution statusPENDING
  • Pain-point frequency matrixPENDING
  • Current-workflow diagramPENDING
  • Current-tool and substitute analysisPENDING
  • Willingness-to-pay findingsPENDING
  • Buyer-budget-owner analysisPENDING
  • Procurement-path memoPENDING
  • Reviewer-requirements summaryPENDING
  • Design-partner target listPENDING
  • At least three design-partner lettersPENDING
  • At least one pilot letter of intentPENDING
  • Customer pipeline spreadsheetPENDING
  • Objection logPENDING
  • Lost-customer or declined-pilot logPENDING
  • Pricing-interview summaryPENDING
  • Initial channel-partner listPENDING

05 · Demo dataset and Evidence Room

Each company needs a synthetic but realistic first demo company. Never copy private data from a real person or organization without authorization.

  • Demo-company profilePENDING
  • Demo user personasPENDING
  • Demo workflow timelinePENDING
  • Synthetic source documentsPENDING
  • Data dictionaryPENDING
  • Ground-truth answer keyPENDING
  • Expected receipt hashesPENDING
  • Expected signature outputsPENDING
  • Invalid or tampered-document examplesPENDING
  • Demo verification test casesPENDING
  • Reviewer walkthroughPENDING
  • Claims-limits filePENDING
  • Demo READMEPENDING
  • Sample ProofMail messagePENDING
  • One-click or scripted verification instructionsPENDING

06 · Technical architecture and security

Boundary stays fixed — Rails: human workflow, state, permissions, intake and presentation. Rust: canonicalization, hashing, signing and deterministic receipt generation. Evidence Room: reviewable artifacts and source manifest. ProofMail: controlled external handoff.

  • System architecture diagramPENDING
  • Rails workflow architecturePENDING
  • Rust trust-kernel architecturePENDING
  • Rails-to-Rust API contractPENDING
  • Canonicalization specificationPENDING
  • SHA-256 hashing specificationPENDING
  • Ed25519 signing specificationPENDING
  • TLV schema specificationPENDING
  • JSON receipt specificationPENDING
  • Key-generation procedurePENDING
  • Key-storage and rotation policyPENDING
  • Signing-authority policyPENDING
  • Verification procedurePENDING
  • Evidence-retention policyPENDING
  • Tenant-isolation architecturePENDING
  • Role-based access-control matrixPENDING
  • Audit-log specificationPENDING
  • Incident-response planPENDING
  • Data-backup and recovery planPENDING
  • Threat modelPENDING
  • Abuse-case analysisPENDING
  • Software bill of materialsPENDING
  • Open-source license inventoryPENDING
  • Penetration-test roadmapPENDING
  • Security and privacy FAQPENDING

07 · Financial model

The model must separate customer revenue, Bankabil license or service expense, cloud and verification costs, implementation labor, customer support, sales costs and company-specific legal/compliance costs.

  • 24-month monthly operating modelPENDING
  • Five-year annual summaryPENDING
  • Headcount planPENDING
  • Product-development budgetPENDING
  • Hosting and infrastructure assumptionsPENDING
  • Bankabil licensing or shared-services expensePENDING
  • Sales and marketing budgetPENDING
  • Legal and compliance budgetPENDING
  • Insurance budgetPENDING
  • Gross-margin modelPENDING
  • Customer-acquisition-cost assumptionsPENDING
  • Contract-value assumptionsPENDING
  • Sales-cycle assumptionsPENDING
  • Churn and renewal assumptionsPENDING
  • Cash-burn schedulePENDING
  • Runway calculationPENDING
  • Financing requirementPENDING
  • Base, downside, and upside scenariosPENDING
  • Use-of-funds schedulePENDING
  • Milestones unlocked by the roundPENDING
  • Founder salary assumptionsPENDING
  • Capitalization model before and after financingPENDING

08 · Legal, claims, privacy, and compliance

Conduct federal and common-law trademark clearance before committing to a company or product name. The USPTO recommends searching its trademark database before applying for registration.

  • Master claims-limitation policyPENDING
  • Product-specific claims matrixPENDING
  • Approved product languagePENDING
  • Prohibited product languagePENDING
  • Terms of servicePENDING
  • Privacy policyPENDING
  • Data-processing addendumPENDING
  • Customer agreementPENDING
  • Pilot agreementPENDING
  • Design-partner agreementPENDING
  • Confidentiality agreementPENDING
  • Subprocessor listPENDING
  • Data-retention schedulePENDING
  • Data-deletion policyPENDING
  • Security addendumPENDING
  • Customer-content ownership clausePENDING
  • AI-use disclosurePENDING
  • Synthetic-data disclosurePENDING
  • No-professional-advice disclaimerPENDING
  • Insurance requirements memoPENDING
  • Trademark clearance reportPENDING
  • Patent/trade-secret strategy memoPENDING

Demo Evidence Room — file manifest

Canonical

  • README.md
  • claims_limits.md
  • receipt.json
  • receipt.tlv
  • verification_result.txt
  • source_evidence_manifest.csv
  • reviewer_packet.pdf
  • developer_quickstart.md

Required additions

  • demo_data_license.md
  • synthetic_data_disclosure.md
  • expected_results.json
  • tamper_test_results.txt
  • receipt_schema.json
  • public_key.pem (or documented public-key format)

Minimum investor-ready set

  • 01Incorporated entityPENDING
  • 02EINPENDING
  • 03Founder stock and vesting documentationPENDING
  • 04Complete IP assignmentPENDING
  • 05Clean cap tablePENDING
  • 06Bankabil license agreementPENDING
  • 07Investor deckPENDING
  • 08One-page overviewPENDING
  • 09Two-page investment memoPENDING
  • 1024-month financial modelPENDING
  • 11Use-of-funds planPENDING
  • 12Product requirements documentPENDING
  • 13Workflow diagramPENDING
  • 14First receipt schemaPENDING
  • 15Demo Evidence RoomPENDING
  • 16At least 15 customer interviewsPENDING
  • 17At least three design-partner lettersPENDING
  • 18Product-specific claims-limitation documentPENDING

Recommended creation order

Weeks 1–2

Legal and thesis

  • ·Incorporate each entity.
  • ·Execute founder and IP documents.
  • ·Finalize the Bankabil license structure.
  • ·Write the one-page thesis for each startup.
  • ·Confirm buyer, reviewer, workflow, receipt, MVP and claims boundary.

Weeks 3–4

Customer evidence

  • ·Conduct 15–20 interviews per company.
  • ·Obtain three design-partner letters.
  • ·Validate pricing.
  • ·Record reviewer requirements.
  • ·Refine the workflow and MVP.

Weeks 5–6

Demo Evidence Rooms

  • ·Build each synthetic demo dataset.
  • ·Generate first receipts.
  • ·Create tamper-test cases.
  • ·Produce reviewer packets.
  • ·Record concise product demos.

Weeks 7–8

Fundraise room

  • ·Finish decks and investment memos.
  • ·Complete financial models.
  • ·Prepare use-of-funds schedules.
  • ·Finalize draft financing documents with counsel.
  • ·Open separate investor data rooms.
  • ·Begin targeted introductions.