Startup application evidence pack: the documents that make claims testable

Why this matters

Most weak applications do not fail because they lack pages; they fail because important claims cannot be checked. A business plan says “large market,” while the evidence folder contains no customer interviews, pricing test or source for the number.

A usable framework

• Founder evidence: CV, ownership, roles, relevant achievements and time commitment
• Problem evidence: interview notes, observed workflows, complaints and cost of the problem
• Solution evidence: product scope, prototype, technical feasibility and data responsibility
• Market evidence: segment size, competitors, willingness to pay and acquisition channels
• Finance evidence: assumptions, runway, source of funds and milestone budget
• Route evidence: required endorsement, incubator, facilitator or authority documents

How to apply it

1. Create an evidence index before writing the final narrative.
2. Give each key claim an ID and link it to a file or calculation.
3. Use one source-of-truth table for dates, ownership, budgets and team roles.
4. Remove unsupported superlatives and replace them with observable facts.
5. Run a consistency check across forms, plan, pitch deck and translations.

Common mistakes

• Uploading many documents with no index
• Using screenshots without dates or context
• Changing revenue assumptions between documents
• Letting translations alter names, figures or legal meanings

The output you should have

A reviewer should be able to move from claim to evidence in one step. The final deliverable is an indexed, versioned folder plus a one-page consistency sheet.

Immigration, residence, company and tax rules can change without notice. Treat this guide as structured orientation, not legal advice; verify the current official requirements before paying fees or submitting an application.