A composite case study of a successful Exceptional Promise application — what evidence was submitted, how the mandatory criterion was argued, and what made it work.
This is a composite case study based on real application patterns, with all identifying details changed. It illustrates how a well-structured Exceptional Promise application works in practice.
Background: Software engineer turned founder, four years post-graduation. Had worked at a mid-sized UK SaaS company for two years before leaving to build a developer tooling startup. Company was 18 months old at time of application, pre-revenue but with a small active user base (approximately 800 monthly active users) and £150k in pre-seed funding from a recognisable angel.
Initial self-assessment: "I think I need more experience before I can apply."
After Meridian readiness diagnostic score: Innovation Signal: 42/100. External Recognition: 28/100. Recommendation Network: 35/100. Narrative Coherence: 31/100. Total: 136/400.
The profile was weaker than the applicant thought in some dimensions and had hidden strengths in others.
After a two-month building phase and a focused application preparation, here is what was submitted:
Mandatory criterion:
The innovation claim was specific: the applicant had developed a novel approach to local development environment synchronisation that solved a problem every distributed development team faces. The approach was technically non-obvious (it used a specific combination of techniques that other tools hadn't combined in this way) and had been validated by users who switched from existing tools.
Evidence:
Optional criterion 1: Contributions beyond employment
A 450-star open source library the applicant had built alongside the startup, solving an adjacent problem. Independently verifiable adoption via npm download stats.
Optional criterion 2: External recognition
A talk at a London developer meetup (600+ members) about the technical approach — recorded, publicly available. Plus a feature in a developer-focused newsletter with 8,000 subscribers.
Recommendation letters:
The mandatory criterion claim was specific. "I built a tool that solves developer environment synchronisation in a non-obvious way" is assessable. The assessors could evaluate whether the approach was genuinely innovative by reading the technical blog post and testing the product.
The evidence was externally verifiable. Every piece of evidence had an independent source: the product was live, the open source was on GitHub, the talk was recorded, the newsletter feature was online, the investor and CTO letters were from real external parties.
The recommendation letters addressed the right questions. The investor letter explained the investment thesis and technical insight. The CTO letter described the specific problem it solved and why existing tools hadn't. The engineer letter spoke to the technical quality of the open source contribution.
The narrative coherence was high. Every piece of evidence supported the same claim: this person builds developer tools in a technically innovative way, the community finds the work valuable, and expert validators have recognised it.
The forward trajectory was specific. The personal statement articulated a clear, grounded plan: with UK presence, the applicant planned to build out the enterprise version of the tool, engage with the UK developer community, and develop the open source ecosystem around the approach. These plans were connected to existing UK customer relationships and specific technical roadmap.
The applicant had several items they considered including that were ultimately excluded:
Excluding these made the application tighter and stronger.
Want a read on whether your profile could be built into a viable application? The free readiness assessment takes four minutes and gives you a scored breakdown similar to the one in this case study.
Ready to find out where you stand?
See your Founder Credibility Index score and exactly which dimensions to fix first.