The problem statement
This is where most applications lose. "Improving healthcare in India" is not a problem. It is a category. A real problem names who suffers and how much.
Compare these two. Weak: "Healthcare access is poor in rural India." Strong: "Rural health centres in tier-3 districts have no way to track vaccine stock, so doses expire and outbreaks happen during immunisation drives." The second one a reviewer can picture. Write that.
The solution
Say what you built or are building, in plain words, and why it beats the alternative. Reviewers do not need jargon. They need to understand it in one read. If you cannot explain it without buzzwords, you have not made it simple enough yet.
Market size, the honest version
Do not paste a ₹10,000 crore TAM you found in a report. Reviewers see fabricated numbers all day. Build it bottom up: how many customers, what they pay, how often. A defensible ₹40 crore beats a made-up ₹10,000 crore every time, because you can answer the follow-up question.
The team
Schemes back people as much as ideas. Show why this team can build this thing. One common red flag: three engineers and nobody who can sell. Most startups fail on go-to-market, not on product, and reviewers know it. If you have a gap, name how you will fill it.
Traction, even a little
Anything real helps. Ten users who paid ₹100 beats a thousand signups who paid nothing. A letter of intent from one customer beats a slide of projections. If you have early numbers, put them up front. They do more than any adjective.
Use of funds, be specific
"Marketing" is not a use of funds. "Three months of runway for two engineers to finish the matching algorithm and run a 50-user pilot" is. Tie every rupee to a milestone. Vague asks read as you not knowing what you need.
Financial projections
Three-year projections are expected. Everyone knows they are guesses. The point is to show you have thought about unit economics. Conservative and defensible wins. Projecting ₹100 crore in year two from zero tells the reviewer you are not serious.
What gets applications rejected
- Missing a required registration like DPIIT recognition.
- A vague problem statement.
- No traction and no plan to get any.
- Applying to the wrong programme for your sector or stage.
- Unrealistic financials nobody can defend.
- "We will figure out monetisation later."
A short pre-submit checklist
- You meet every stated eligibility criterion.
- The problem names a specific person and pain.
- Market size is built bottom up.
- Every line of the budget maps to a milestone.
- One person who is not you has read it and understood it.
Common questions
What is the single biggest reason grant applications get rejected?
A vague problem statement. Name who has the problem and how much it costs them, with a concrete example. Reviewers fund problems they can picture.
How big should my market size claim be?
As big as you can defend. Build it bottom up from real customer counts and prices. A believable smaller number beats an inflated one you cannot back up under questioning.
Do I need traction to apply?
Not always, but any real traction helps a lot. Even ten paying users or one signed letter of intent moves you ahead of applicants with only projections.
How detailed should the use of funds be?
Very. Tie every amount to a specific milestone and timeframe. 'Marketing' is too vague; 'three months of runway to run a 50-user pilot' is the level reviewers want.
Find your match
See every grant you actually qualify for.
Incubateer scores your startup against 10,000+ programs and tells you honestly which ones fit, so you only apply where you have a real shot.
Find your grant