The product led path rewards people who decided what got built and can show the market agreed. Inside the optional criteria for digital technology it sits opposite the technical path, and assessors read them as two different proofs of innovation: one shows judgment about what a product should be and evidence that users followed, the other shows specialist depth in how it was engineered. If your strongest material is roadmaps you owned, launches you led and adoption you grew, this is your lane. To satisfy it you need dated proof of decisions and outcomes, not a job description. This guide explains what qualifies, what does not and how to present it.
What product led means in practice
The published criteria speak of innovation as a founder or senior member of a product-led digital technology company. In plain terms, an assessor wants to see that the product existed because of choices you made: you defined the problem, shaped the solution, drove it to launch and the market responded. Founders fit naturally. Product heads, chief executives of small firms and senior operators with real decision rights fit too, provided the documents tie outcomes to their involvement.
What does not qualify is proximity to success. Working at a company whose product did well is background, not evidence. The link between your decisions and the result has to be traceable through dates, roles and named responsibility.
Product led versus technical evidence
Applicants often blur the two paths and weaken both. The table below shows how assessors separate them.
| Dimension | Product led file | Technical file |
|---|---|---|
| Core claim | Judgment about what to build and why | Depth in how it was built |
| Strongest unit | A launch with adoption data | A system or method in production use |
| Referee voices | Investors, co-founders, commercial partners | CTOs, principal engineers, maintainers |
| Common weak spot | Claims without outcome numbers | Skill claims without deployed artefacts |
Choose one as your headline and let the other support it. A founder who also writes core code can mention it, but the file reads cleanest when each criterion is anchored by its own clearest proof.
Evidence that proves product leadership
Every claim needs a document a stranger can check. Launch records with dates and versions, usage or revenue figures shown against their source, press coverage naming your role, funding announcements listing you as founder, and post-launch iterations where your roadmap decisions are visible all serve well. Screenshots from analytics dashboards work when the date and product name appear on screen.
Letters matter disproportionately here because product judgment is invisible in code. A letter from an investor or co-founder who watched you kill a failing feature, reposition a product and watch retention recover tells the story no spreadsheet can. Our collection of Tech Nation evidence examples shows how these items map onto the criteria, and our guide to optional criteria explains how many you need to satisfy under current guidance.
Numbers deserve special care. An adoption figure without a source is decoration, so attach the origin every time: the dashboard page, the app store listing, the investor update, the press article. Assessors verify, and unverifiable numbers cost more than modest verifiable ones.
Agency and consulting work under this criterion
Agency delivery is where product-led applications most often stumble. Client projects reward the client, and your name rarely appears in public records. If agency work is your base, extract the pieces that show product ownership: a product line you ran end to end, a pivot you proposed that the client adopted, internal tools that became products. Frame engagements around decisions and outcomes rather than tasks performed, and back each frame with contracts, statements of work or client letters that name you.
Internal strategy roles face a similar test. If you advised rather than owned, say so honestly and lean on the second criterion instead; a thin product claim damages the credibility of strong adjacent evidence.
Your direct questions answered
Does my startup need outside funding to count No. Bootstrapped traction counts when documented. Revenue records, user growth with sources and press coverage carry the argument as well as a funding round would.
Can a product manager without engineering depth qualify here Yes, if you owned direction and the record proves it. The criterion is about product leadership, and letters from engineers and executives confirm who made calls.
How far back can my launches reach Anchor on the last five years, where guidance centres recognition, though an earlier landmark can open the narrative before recent items take over.
Should non-technical founders use this criterion Usually yes. It is the natural home for founders whose contribution was vision, positioning and execution rather than code.
Where do I check the exact wording before applying In the current endorsing body guidance and GOV.UK route pages for digital technology. This article provides general information only and does not constitute legal advice. For case specific questions speak to a qualified adviser.