Tech Nation Exceptional Promise Rejection: Appeal or Strengthen My Reapplication?
I recently received a rejection for my Tech Nation Global Talent application under the Exceptional Promise pathway
The panel confirmed that I was eligible for Exceptional Promise and that my recommendation letters were adequate. However, the Mandatory Criterion, OC1 and OC4 were not awarded.
Mandatory Criterion
My evidence included:
- Winner of the Best AI Feature award at a competitive UK hackathon involving more than 96 teams.
- Invited talk in a webinar on AI in healthcare.
- Digital technology and AI workshop delivered at a leading university to an audience of more than 100 people.
- Jury panel role for a startup innovation challenge.
- External recognition award and media coverage.
- Strategic collaboration MoU.
- Leadership in developing and launching Product X.
- Engagement through the NHS Innovation Service, including meetings with NIHR and Health Innovation Network South London regarding clinical validation, NHS adoption, real-world evidence and deployment.
The panel accepted that some activities were eligible but considered them too early-stage, with insufficient scale and wider-sector recognition.
OC1 – Innovation
I submitted Product X, a live AI-powered preventive healthcare application developed and deployed under Company A.
My evidence included:
- End-to-end technical and product ownership.
- Deployment on both the App Store and Play Store.
- More than 700 early users, with users increasing daily.
- Subscription revenue of over ÂŁ600 in the first two months.
- Public frontend and backend repositories demonstrating technical ownership and open-source contribution.
- A market survey of over 100 respondents showing strong demand and willingness to pay for subscription.
- NHS Innovation Service engagement.
- An innovation-collaboration meeting with the NIHR-funded D4D programme, which reviewed the product and showed interest in its potential adoption within the UK healthcare environment.
- Independent market and investment interest from a technology company director who recognised the product’s scalability and commercial potential.
- Reference letter from tech leader.
The panel recognised Product X as a genuine live product but considered the adoption, revenue and measurable impact too limited.
OC4 – Research Contribution
I submitted three first-authored, peer-reviewed AI healthcare papers, published and presented at IEEE and ACM conferences.
My supporting evidence included:
- Research covering all three papers.
- Public code repositories and open-source research implementations.
- Translation of the research into features within the live Product X platform.
- Independent academic recommendations and feedback.
- Further research collaboration discussions with lecturers and PhD researchers.
- Evidence that another researcher requested access to my implementation to build upon the work.
- Continued academic engagement and knowledge sharing.
The panel accepted that first authorship was a genuine contribution but stated that the publications were recent and had limited adoption, reach and GitHub engagement.
Question:
I understand that the panel does not have to comment on every item. For a future reapplication, which improvements would have the greatest impact across MC, OC1 and OC4, for example stronger recognition from established technology organisations, greater user and revenue growth, formal UK healthcare pilots or partnerships, more research citations and independent adoption, and stronger GitHub engagement? Based on my current evidence, would you recommend requesting an endorsement review now or strengthening these areas and reapplying later?
The feedback did not specifically address several submitted items, including the NIHR-funded D4D meeting, HIN South London engagement, ongoing revenue, market and investment interest, open-source contribution, and independent interest in using my research.
I would be grateful for advice from anyone who has successfully appealed or reapplied after similar feedback.
@Raphael @Akash_Joshi @Francisca_Chiedu @Noddy
