Request for Review: UK Global Talent (Digital Technology – Exceptional Promise, YC Founder)

Stage 1
1

Applying for Global Talent Visa (Exceptional Promise)

Hey guys, I would love your help in reviewing my application. Below is a summary of the evidence I will be submitting. I have the following questions:

  • Does the evidence and supplemental documents for each criteria match what’s required?
  • Do you spot any gaps in my application that would need further evidence or don’t make sense?
  • For each evidence document, does each new image or screenshot count as 1 page? Or just whatever I can fit on 3 A4 pages counts? E.g. I can have 2 images on 1 page to back up my explanation?
  • Any other suggestions are more than welcome.

Tagging a few people @Akash_Joshi @Raphael

Thanks in advance!

My Profile

CEO & Co-founder of an AI startup in insurance, company headquartered in the US, backed by YC. Raised $X. Have background in fintech, product, engineering. Company has revenue with enterprise customers.

Letters of Recommendation

  1. Co-founder and Chief Executive of a Fintech SaaS company
  2. Co-founder of two billion-dollar Finance companies
  3. Vice President of IT & Technology at Insurance company (customer)

Mandatory Criteria

MC Evidence 1 — International recognition through Y Combinator

  • YC acceptance letter
  • Letter from YC president which mentions 1–2% acceptance rate + Unicorn companies from YC, my company’s acceptance into the program and the funding we have received (>$500K)
  • I also refer to my LOR2 here as he mentored me during YC (but I am not submitting it as separate evidence)

MC Evidence 2 — Leading growth and customer adoption

  • Customer contract from a top 50 insurer & Fortune 500 publicly listed entity
  • Email negotiations which I led to secure this contract between me and the VP of technology
  • I refer to my LOR here but not submitting it as separate evidence

MC Evidence 3 — Panel participation evidence

  • Confirmation of judging letter from the President of YC
  • Consulting agreement between myself and YC
  • Evidence of panel participation (redacted emails which show an application being assigned to my email address to be judged)

Optional Criteria 1 — Innovation

OC1 Evidence 1 — Innovation

Company profit/loss statement and balance sheet for year ending Dec 2025 and more recent Stripe payments from customers. Trying to show commercialization of innovative product in market.

OC1 Evidence 2 — Innovation

Product architecture (guidance on what to show here would be appreciated). Currently, I have screenshots of architecture diagrams of product, git commit history. What else can I show here?

OC1 Evidence 3 — Innovation

Customer reference letter outlining how our product is innovative and has made an impact (saving costs + time).

Optional Criteria 3 — Significant Contributions/Impact

OC3 Evidence 1 — My role + technical contribution

  • Co-founder reference letter outlining my contributions regarding the initial vision and conceptualization of the company, securing contracts with multiple companies, & spearheading fundraising

OC3 Evidence 2 — Entrepreneurial

  • 2x Funding/SAFE Agreement from a venture capital fund
  • Email screenshots between myself and investors showing my involvement in the negotiation

OC3 Evidence 3 — Commercial growth

  • Customer contracts
  • Sales pipeline and CRM screenshots of current active leads
2

The MC section holds together. YC acceptance as an international-recognition anchor works with the president’s letter contextualising acceptance rate and outcomes. The customer contract with negotiation trail is solid commercial-leadership evidence. The YC judging role is legitimate panel participation and the redacted assignment emails are the first-party proof assessors want.

OC1 needs the most work. Innovation evidence has to show novelty of the product or technology. The P&L and Stripe payments demonstrate revenue, which is OC3 territory. Move that piece. Architecture diagrams and git commits are self-documented and carry very little weight; assessors flag this pattern frequently. Stronger OC1 evidence looks like technical press coverage, a patent filing, a talk at a recognised technical venue, or a benchmark against existing tools. If none of those exist, reframe the customer reference letter around what your product does that existing tools cannot, rather than cost savings.

Watch the overlap between MC2 and OC3.3. Both draw on customer contracts. Pick the strongest contract for MC2 and use different pieces for OC3.3, such as the sales pipeline or a second customer. Same rule for the co-founder LOR referenced in OC3.1: if you are submitting it as one of the three recommendation letters, do not also count it as an evidence document.

On the page cap: each evidence document is limited to 3 A4 pages total. Multiple screenshots on the same page are fine. The physical page count of the compiled PDF is what counts, not the image count.

3

Hi @Akash_Joshi, thanks so much for your response. Super helpful!

For OC1:
I can reframe the customer letter around innovation and difference with existing tools. However, I dont have technical press, patent filing, etc. What else can I show here if I can’t show the architecture diagrams and git commits?

Would it make sense to switch the P&L to OC3 and cofounder letter to OC1?

Open to any other suggestions!

Thank you!

4

Hi @909,

Being the CEO of a YC‑backed company is a strong validation that you’ve built something useful. However, if it’s not positioned strategically, it can still be dismissed. I worked with a YC company whose co‑founder’s TN application was rejected, so it’s not about YC alone.

As a CEO/Co‑Founder, the first thing you need to establish is how you led the growth of a product‑led digital technology company, product, or team. After that, the YC acceptance and the amount you raised serve as validation that your work was valuable and recognised by leading VCs.

For MC2: if the contract and the growth you led are from the same company, then it’s weak. Those should be part of MC1. Your panel participation to assess the work of others is good, but you need to be clear about what was assessed and show that it falls within your area of specialisation, not as a consultant.

For OC1:

Profit/loss statements are validating evidence that what you built was innovative enough to generate sales, but they do not show that the product itself is innovative. You need to demonstrate the innovation first, then use sales to validate it. Product architecture alone is not an innovation, it can support contribution, but only if you are a technical co‑founder. If you are, then for coherence, in MC you need to show at least some technical leadership to make the overall narrative strong. Customer letters mentioning your innovation are weak if you don’t clearly demonstrate the innovation through the concept itself or through validating evidence such as a patent.

A letter from your co‑founder may be considered self‑authored. Also, starting a criterion’s evidence lineup with a letter, when the guidance clearly states that a letter alone is not sufficient is not strategic. A funding agreement is good, but you need to clearly show what you did that led to the funding. Those are the contributions, things like pitching, collaborations, strategic session documents, correspondence, agreements signing with your names etc.

I think you have good validating evidence, but you are not clearly demonstrating what you did or innovated that led to these outcomes. Also, it appears you are reusing evidence across evidence sets and criteria. The guidance is clear about each evidence set being unique

You need to clearly show and demostrate what you did. The application is about you, not your company and its achievements.

All the best.

1 Like
5

On the OC1 gap: without technical press, patents, or a talk at a recognised venue, the strongest lever left is external technical validation. Independent benchmarks from a customer’s engineering team, a third-party technical evaluation, or coverage of your product on a specialist AI/insurance publication like InsurTech Insights or Insurance Journal Tech would all land. If a partner or design partner has a public technical write-up mentioning your approach, that’s OC1 material. Reframing the customer letter around technical novelty rather than cost is worth doing, but pair it with something the assessor can verify independently.

Yes, swap the P&L to OC3 and lift the co-founder LOR into OC1 only if the letter concretely describes the technical novelty of the product rather than your role. If it’s the latter, it stays in OC3.

One more thing worth flagging: your OC3 lineup leans heavily on funding and customer contracts, which risks reading as company achievements rather than personal contribution. The Guide is explicit that the assessment is about you, not your company. Whichever pieces you keep in OC3, make sure the narrative in each evidence document says what you personally did, not what the company achieved.

6

Hi @Raphael I have a question on this. What if you show all of the below:

  1. In depth discussion of your innovation and how it is different from existing solutions (evidenced by architecture diagrams with your contribution)
  2. Customer reference letter (describes how traditional software or other automation tools did not solve their problem and how my product provided a fundamentally different approach + my role leading this innovation)
  3. Audited accounts showing commercial proof of product in the market (P&L + Balance sheet)

Also wondering if there’s anything else external to strengthen this apart from patent or AI publication etc.? I have:

  • An article in Walturn focusing on top YC companies from my batch with innovative uses of AI across various industries which mentions my company
  • YC launch
  • National media article about being accepted into YC (but doesn’t describe my innovation)

@Akash_Joshi would also love your thoughts!

7

The Walturn article is your strongest OC1 piece in that list. Independent editorial coverage that describes your company as an innovative use of AI is exactly what an OC1 anchor looks like, since the recognition comes from outside your own materials. Lead with it.

Audited accounts belong in OC3, not OC1. They validate commercial success but say nothing about whether the product is novel. YC launch is a self-authored artefact and won’t carry weight on its own. The national media article about YC acceptance sits closer to MC than OC1 since it recognises the acceptance itself, not the innovation.

Architecture diagrams remain thin as OC1 evidence even paired with narrative. If the customer reference letter can point to a specific technical approach that traditional tools lack, and the customer’s engineering team can name it, the combination lands. If the letter is mostly ROI framing, it stays as OC3 support.

One external validating piece plus a customer letter that names the novelty gives you a defensible OC1. The accounts and diagrams sit as supporting artefacts underneath, not as the primary evidence.