What was broken
An AI healthcare startup had previously applied for a national startup recognition programme but received objections due to inadequate documentation and an unclear articulation of innovation. Without recognition, the founders faced delays in accessing government benefits and investor incentives.
What we did
CapEasy reassessed the business model, rebuilt the innovation documentation, strengthened the technology narrative, aligned supporting evidence with the programme's requirements, and prepared a fresh application that addressed every concern raised during the earlier review.
Where it landed
The startup received recognition on its subsequent application, unlocking access to startup-specific benefits, improved investor confidence, and eligibility for future government incentives.
A decline letter is a punch list, not a verdict
Founders who get turned down for a federal award tend to read the outcome as a judgment on the company. Read it as a document instead. SBIR.gov describes the programme's own proposal review as deliberately built this way: it "provides critical feedback that can help refine your concept" — the review exists to generate a specific, actionable response, not just a yes or no.
The habit that separates a resubmission that lands from one that repeats the mistake is simple: go through the reviewer language line by line and turn every objection into a named fix — a missing technical milestone, an unsupported market claim, a budget category that does not tie to the work plan. A rewritten cover narrative that does not touch the specific gaps a reviewer flagged reads, on the second pass, exactly like the first submission.
US federal grant programmes are built for more than one attempt
SBIR/STTR runs across 11 participating federal agencies, each publishing its own solicitations and running its own review cycle, with the same three-phase structure everywhere: Phase I feasibility awards in the roughly $50,000–$275,000 range over 6–12 months, Phase II development awards from roughly $400,000 up to $1.8 million over about 24 months (current programme figures, per SBIR.gov). A concept declined by one agency's solicitation is not disqualified from the next cycle, or from a different agency's solicitation for the same underlying technology — the programme is structured as a recurring competition, not a single gate.
That structure only pays off if the resubmission is treated as a new, complete proposal against the specific solicitation's evaluation criteria — not a resend of the declined one with a new cover page. The fix has to live in the technical narrative, the budget justification and the supporting evidence, in the same places the reviewer looked the first time.
The rebuild method that transfers
The method in this engagement generalises directly: reassess the underlying case (what is actually being claimed as innovative or eligible), rebuild the supporting documentation to match, and align every piece of evidence to what the specific programme asks for — before touching the narrative again. Only once the file supports the claim does the pitch get rewritten around it.
In a US context, that documentation work — reconciling the numbers a technical narrative leans on, organising the cost and budget schedules a reviewer or programme officer will check against your books, keeping the paper trail consistent across a first submission and a resubmission — is bookkeeping and reporting work a team can hand off. Eligibility judgment calls, the technical write-up itself, and anything filed with an agency stay with the founders, their technical team and the partner CPA firms we work with across 15 US states; CapEasy's part is making sure the numbers behind the file are correct, current and ready before the reviewer opens it.
What to take from it
- A decline is written to be actionable — treat every objection as a named line item, not a mood to overcome with better prose.
- Federal grant programmes like SBIR/STTR are recurring competitions across many agencies and cycles; one decline does not close the door on the underlying technology.
- Fix the file before you touch the pitch: a resubmission that only rewrites the narrative repeats the objections a reviewer already raised.
- Resubmissions get reviewed against the same criteria as first submissions — the evidence and budget have to hold up on their own, not ride on the story.
- Keep the documentation current between attempts. A file that is only assembled when a deadline hits is the reason the first submission read as thin.