🚀 There is a product: which proof counts in the FounderSeal

Your product working on a public URL that anyone can try. If it is not software: a prototype you can see running.

Proof asked for: Link to the demo, or a video of the prototype running

A device, a machine or a part that exists and works. Not a render or a drawing: something you can switch on in front of somebody.

Proof asked for: Video of the prototype running, dated

A test version in the hands of people outside your team and your family, with their feedback collected.

Proof asked for: Anonymised list of testers and a summary of what they said

Your app approved and downloadable on the App Store or Google Play. Approved, not in review: the store already let it through.

Proof asked for: Link to the store listing

Your service has been running for three months for real users, with measured uptime. Working one day is not the same as working.

Proof asked for: Monitoring dashboard showing those ninety days

Open source with real activity: regular commits and people outside the team using it, filing issues or contributing.

Proof asked for: Link to the repository, with its stars or forks visible

You are listed in another company’s integration catalogue — Shopify, Salesforce, Slack, an ERP… — with their review passed. Somebody big let you in.

Proof asked for: Link to your listing in that platform’s catalogue

Others can build on top of you: published endpoints, documentation, and keys anyone can request.

Proof asked for: Link to the public documentation

A TRL assessed by somebody external — a public body, a research centre, a funding programme — not the one you would claim.

Proof asked for: Report or decision stating the TRL and who assessed it

Your product meets an accessibility standard checked by a third party (WCAG, EN 301 549). In the public sector this is usually mandatory.

Proof asked for: The audit report, naming the standard and the level