Topics

Rejected EXIST application: your 4-week recovery plan

Most applicants don't know the revision window exists. Here's how to use the four weeks reviewers give you.

EXIST
Rejection
Recovery
Finn Glas
Finn GlasCo-Founder + Engineering
·May 7, 2026·
1 min read

First read the letter twice

There are two letter shapes from PTJ. "Antrag abgelehnt" - flat rejection, no resubmission of this version, you may submit a fundamentally revised application in a future call. "Zur Nachbesserung zurückgegeben" - revision request, you have four weeks (sometimes six) to address the cited points and resubmit. The wording in the first paragraph tells you which it is. Read it twice before reacting.

Week 1: triage the points

PTJ feedback is structured: typically three to seven cited issues, each with a short justification. Sort them into three buckets - structural (Innovationshöhe weak, no academic anchor), evidentiary (citations missing, no customer conversations), formal (numbering, references, layout). Do the formal stuff first; it is small work that bumps the application from "sloppy" to "polished" with two evenings of effort.

Weeks 2-3: do the structural work

If Innovationshöhe was the cited weakness, this is where you bring three to five new citations to the state of the art and rewrite the section to lead with what is technically new. If the academic anchor was missing, this is where you secure the named professor and add their endorsement letter. Two weeks of work; do not rush it because the formal fixes were quick.

Week 4: re-review and resubmit

Two outside reads from people who have submitted EXIST before. The university's Gründungsbüro counts. A senior consultant counts more if you can afford the hourly rate (€300-€800 for two hours). Submit on a Wednesday or Thursday - submitting on a Friday afternoon means the queue does not register your file until Monday and you lose three review days.

FAQ

Frequently asked

Try Grants

Free plan, no credit card. We host in Germany. You can export and delete everything self-serve.

Finn Glas

Written by

Finn Glas

Co-Founder + Engineering

Finn is one of the Co-Founders. He owns the engineering side, the infrastructure, and most of the late-night fixes that ship before anyone notices.

finn.glas at aicuflow dot comLinkedInWebsite