On paper, Optional Criterion 3 (OC3) appears straightforward: demonstrate that you have made a significant technical, commercial, or entrepreneurial contribution as a founder, senior executive, or employee of a product-led digital technology company.

In practice, however, many otherwise strong applications are refused—not because the applicant lacks experience, but because the evidence focuses on what the company achieved rather than what the applicant personally contributed.

This is one of the most common reasons OC3 applications fail. Understanding how Tech Nation evaluates individual contribution can make the difference between a compelling application and a refusal.

Where Applicants Commonly Misread OC3

OC3 is not asking whether you performed well at a successful company.

Instead, assessors want to see a significant contribution that can clearly be attributed to you, within a company whose core business is building and selling digital technology products—not simply using technology to deliver another service.

Two issues frequently appear together:

• The company is not recognised as a product-led digital technology business.
• The applicant's individual contribution cannot be separated from the work of the wider team.

Either issue can weaken an application. Together, they often prove fatal.

Product-Led Companies Matter

One of the first questions reviewers ask is whether the employer actually qualifies as a product-led digital technology company.

This is often overlooked.

For example, banks frequently invest billions in technology and employ exceptional engineers and product teams. However, their primary business remains financial services rather than selling proprietary digital technology products.

As a result, banking employers tend to satisfy OC3 only in a relatively small percentage of applications, and usually only where every other aspect of the evidence is exceptionally strong.

Applicants should not assume that simply working for a technology-heavy organisation automatically satisfies the product-led requirement.

Common Evidence Mistakes

Confusing Digital Transformation with Product Creation

Many applicants present evidence describing:

• Modernising internal systems
• Digitising business operations
• Improving customer portals
• Implementing enterprise software
• Leading internal transformation projects

These may represent substantial achievements.

However, Tech Nation often views them as operational improvements, rather than evidence of building the digital product the company sells.

The distinction is important.

Assessors look for evidence that contributed directly to the company's core technology product—not simply improvements in how the business operates internally.

Presenting Team Success as Individual Achievement

Applications frequently rely on impressive business metrics, including:

• Revenue growth
• User acquisition
• Product adoption
• Customer retention
• Market expansion

These outcomes are valuable—but they rarely demonstrate individual contribution on their own.

Product success typically reflects collaboration across engineering, product, design, marketing, sales, operations, and leadership teams.

Unless the evidence clearly identifies your specific decisions, ownership, and measurable impact, assessors generally attribute those results to the company rather than the individual.

Similarly, statements such as:

• "I led the project."
• "I managed the team."
• "I was responsible for delivery."

are rarely sufficient without independent evidence explaining exactly what you personally changed and how that influenced the outcome.

Working for a Company That Doesn't Meet the Criterion

Some applicants genuinely demonstrate senior leadership and significant commercial impact—but within organisations whose business model is consultancy, professional services, outsourcing, or advisory work.

Examples commonly include:

• Strategy consultancies
• Digital agencies
• Systems integrators
• Professional services firms
• IT consulting businesses

Even where the work itself is highly technical and commercially significant, OC3 requires contribution within a product-led digital technology company.

If the company does not meet that definition, the criterion may simply not apply.

Using Company Metrics as Personal Evidence

Another common mistake is presenting organisation-wide achievements as proof of individual impact.

Examples include:

• Annual company revenue
• Overall user growth
• Funding rounds
• Valuation increases
• Global expansion

These figures demonstrate business performance—not individual contribution.

Without evidence directly linking those outcomes to decisions, products, or initiatives you personally owned, reviewers cannot reasonably conclude that company success represents your own contribution.

What Tech Nation Is Really Looking For

At its core, OC3 asks one simple question:

Can the reviewer draw a clear line between a specific contribution and the applicant who made it?

The strongest applications make that connection easy.

Rather than relying on broad descriptions of company success, they present evidence showing:

• A clearly defined problem
• The applicant's specific role
• Decisions made by the applicant
• Tangible outcomes resulting from those decisions
• Independent evidence supporting those claims

When the evidence allows reviewers to verify this without relying solely on the applicant's own narrative, applications become significantly stronger.

Strong Evidence Is Usually More Specific

Many applicants assume broader achievements create stronger evidence.

In reality, the opposite is often true.

A narrowly defined contribution supported by documentation, metrics, product releases, technical artefacts, stakeholder testimony, or other independent evidence is usually more persuasive than broad claims about leading major initiatives.

Specificity builds credibility.

Practical Takeaways for OC3

When preparing evidence for Optional Criterion 3, continually ask yourself:

• What specific contribution was uniquely mine?
• Could someone else reasonably claim this achievement?
• Can I demonstrate ownership with objective evidence?
• Does my employer clearly qualify as a product-led digital technology company?

These questions help shift the focus from company success to individual impact—the distinction reviewers care about most.

It is also worth confirming early that your employer satisfies the product-led requirement. Even an exceptional career may struggle under OC3 if the company itself does not fall within Tech Nation's definition.

Need Help Assessing Your Evidence?

Many applicants only discover weaknesses in their OC3 evidence after receiving a refusal.

A structured review before submission can identify whether your career history aligns with the criterion, determine which achievements are most persuasive, and highlight where additional evidence may be needed.

If you're unsure how your experience maps to Optional Criterion 3, consider speaking with an experienced advisor before investing time in preparing your application. A consultation can help ensure your evidence reflects what Tech Nation assessors are actually looking for.