v1

Evidence System

The Evidence System is the foundation of the platform’s methodology.
Instead of relying only on business plans or theoretical descriptions, the system evaluates startups using real signals and verifiable evidence generated during the founder’s work.

This approach reflects how modern startup ecosystems operate.
Incubators, investors, and endorsing bodies rarely rely on written plans alone. They look for proof that the founder has interacted with the market, validated assumptions, and demonstrated the ability to execute.

The Evidence System helps founders capture those signals and organize them into structured evidence that supports the startup’s credibility.


Purpose of the Evidence System

The Evidence System exists to transform startup activity into documented proof of progress.

It allows founders to:

  • record real validation signals
  • organize proof of business development
  • demonstrate founder capability
  • support endorsement and immigration requirements
  • build a clear history of startup progress

Rather than writing theoretical plans, founders collect evidence generated by real actions.


Evidence vs. Claims

A key concept of the system is the difference between claims and evidence.

A claim is a statement such as:

  • “Customers need this product”
  • “The market is large”
  • “The product solves a real problem”

These statements are hypotheses until they are supported by proof.

Evidence is the material that confirms those statements.

Examples include:

  • customer interview records
  • product usage metrics
  • signed letters of intent
  • early sales
  • partnership discussions

The platform encourages founders to convert claims into evidence-backed validation.


Evidence Categories

The Evidence System groups evidence into several categories that correspond to the key elements of startup credibility.

Problem Evidence

Evidence showing that a real problem exists and that potential customers experience it.

Examples:

  • customer interviews
  • support forum discussions
  • industry reports
  • customer complaints about existing solutions

Problem evidence demonstrates that the startup is addressing a genuine need.


Solution Evidence

Evidence showing that the proposed product or service addresses the identified problem.

Examples:

  • prototype demonstrations
  • MVP experiments
  • product feedback from early users
  • usability testing results

Solution evidence shows that the founder has begun testing the proposed approach.


Market Evidence

Evidence that the market opportunity exists and can support a viable business.

Examples:

  • market research reports
  • competitor analysis
  • pricing experiments
  • early customer demand

Market evidence demonstrates that the opportunity extends beyond a single user.


Founder Evidence

Evidence demonstrating that the founder has the capability to build the startup.

Examples:

  • professional background
  • previous projects or startups
  • technical demonstrations
  • relevant industry expertise

Founder evidence helps endorsers assess the founder’s ability to execute the business plan.


Traction Evidence

Evidence that the startup is gaining real momentum.

Examples:

  • early customers or pilot users
  • revenue generation
  • partnership agreements
  • investor discussions

Traction evidence is one of the strongest indicators of startup progress.


Evidence Signals

Evidence in the system is often derived from validation signals generated by real activity.

Examples of validation signals include:

  • user sign-ups
  • customer interviews
  • MVP tests
  • product usage analytics
  • partnership conversations

These signals indicate that the startup is interacting with the market and gathering feedback.

The platform captures these signals and converts them into structured evidence entries.


Evidence Scoring

The system evaluates the strength of collected evidence using a structured scoring model.

Evidence may be assessed based on:

  • relevance to the startup concept
  • credibility of the source
  • level of market interaction
  • repeatability of the signal

For example:

  • one customer interview is a weak signal
  • multiple interviews showing the same problem provide stronger validation
  • early paying customers represent high-confidence evidence

The scoring system helps founders understand how strong their evidence base is.


Evidence and the Readiness Engine

Evidence collected throughout the platform feeds into the Readiness Engine, which evaluates how prepared the startup is for endorsement and visa application stages.

The engine analyzes:

  • the quantity of evidence collected
  • the diversity of validation signals
  • the consistency of the startup narrative
  • alignment with visa evaluation criteria

This allows the platform to estimate whether the startup appears early-stage, developing, or endorsement-ready.


Continuous Evidence Building

Evidence collection is not a one-time activity.

Founders should continuously add new evidence as the startup develops.

Examples include:

  • new product releases
  • customer growth
  • partnerships
  • revenue milestones

This evolving evidence base demonstrates long-term progress and supports future immigration and business milestones.


Why the Evidence System Matters

Traditional business plans often focus on predictions.

The Evidence System focuses on real-world validation and proof of execution.

This approach helps founders:

  • build stronger startup proposals
  • demonstrate credibility to endorsing bodies
  • prepare structured documentation for visa applications
  • track real progress during the business journey

By focusing on evidence rather than assumptions, founders can build more resilient and credible startups.