5 common mistakes in the EXIST application – and how to avoid them

If your vision sounds vague, reviewers can't tell which concrete problem you want to solve. A diffuse outlook on 'digital revolution' or 'sustainable future' is not enough to show market relevance. In a few clear sentences describe which pain point you're addressing, how large the market is, and why your specific team can deliver the solution.

EXIST doesn't fund castles in the air – it funds data-driven concepts. Validation means proving that real people or companies are willing to pay for your solution. Early surveys, structured interviews, and non-binding letters of intent are invaluable. B2B models are validated through company conversations on LinkedIn; B2C through surveys. Link validation to your business model: does the problem occur once (one-time payment) or repeatedly (subscription)?

A patchy plan looks unprofessional. Help reviewers assess it with clear financial diagrams and key metrics. More importantly, link every expense to a milestone: what do you want to achieve and which resources – team, materials, coaching – do you need for it? Detail the first 12 months, then a rough 5-year forecast. The further into the future, the more uncertainty – don't over-engineer the outer years.

Reviewers place great value on a competent and complementary founding team. How you met shows whether you can work together through the EXIST phase and beyond. Use the space: two years as flatmates, friends since kindergarten, four years studying together, same sports club. Did you build a podcast together? How did the idea come about? Does it drive you emotionally as well as commercially? Include all of that – and don't be too modest.

The university connection is your USP in the EXIST application. Show that your idea is grounded in academic research and that you benefit from your university's infrastructure. Describe which labs, equipment, or test facilities you use – but don't imply the IP belongs to the university. Name your EXIST mentor, their field, and how they support you. Reference papers, studies, or theses that underpin your concept. Google Scholar, Arxiv, Elsevier, and PubMed are your starting point.

EXIST Ideenpapiere are scored on three axes - team, innovation, and market - and market typically weighs as heavily as the innovation itself. Applicants who pour ~90% of the text into technical detail starve the two sections that decide borderline cases. Below a clear point threshold the panel usually invites a single round of Nachbesserung (revision) rather than an outright rejection - but a sub-threshold score can block a fresh attempt, so the first submission has to land. Exact thresholds and the page limit shift between handbook versions, so confirm them against the current exist.de Handbuch before you plan around them.

Content is only half the battle. Fill the official PDF forms in Adobe Acrobat Reader specifically - other PDF tools can corrupt the file at the agency. Respect the page limit (often around 20-25 pages); first drafts routinely balloon past 50 and read as unfocused. And plan the calendar: the whole route from first Gründungsbüro contact to submission runs 4-5 months, with university signatures and holiday periods as the usual bottlenecks. The full end-to-end timeline lives in our EXIST Gründerstipendium guide - engage the Gründungsbüro and your mentor early, because they file the formal application, not you.

Writing 'there is no competition' signals you didn't do market research - name competitors' strengths and the customer's current workarounds, then win a specific niche. Leaving out a go-to-market path - which first customer segment, which channel - reads as a concept without a plan; your exploitation story is what turns funded work into revenue. And beware the service trap: EXIST explicitly excludes Unternehmensberatung, and service-heavy models raise scalability doubts. If your model leans on billable hours, reframe it around a productised, scalable core before you submit.