What a grant reviewer actually checks before approving non-dilutive money

What was broken

An agritech robotics startup building affordable automation for small and marginal farmers needed non-dilutive capital to advance prototype development and field testing.

What we did

CapEasy prepared the grant proposal — a grant-permitted budget covering product development and prototyping, a phased milestone plan, and the financial projections behind the ask. The application was aligned to the scheme’s eligibility and permitted-activity rules so it stood up to committee review.

Where it landed

Seed grant approved through an incubator-backed program; funds are milestone-released. The committee approval is a sanction, not a disbursement — actual release follows due-diligence and compliance milestones and is not guaranteed.

The federal program built for this exact sector

For field robotics and precision-agriculture technology, the sector-matched non-dilutive program is USDA’s Small Business Innovation Research (SBIR) grant, administered by the National Institute of Food and Agriculture (NIFA). NIFA releases one SBIR Request for Applications a year across ten numbered topic areas, and two map directly onto agtech robotics: 8.13, Plant Production and Protection — Engineering, which funds engineering technologies that improve system efficiency and profitability in crop protection, and 8.12, Small and Mid-size Farms, aimed at farms with annual sales under roughly $1 million.

Phase I is capped at $175,000 for most topics, but 8.6 and 8.12 are capped lower, at $125,000 — a reviewer checking topic fit will also check that your requested budget matches the ceiling for the topic you applied under, not the general one. Phase I runs 8 months for SBIR (12 for STTR). Phase II, open only to prior Phase I awardees, is capped at $600,000 over 24 months. Applicants can layer Technical and Business Assistance (TABA) funding on top — up to $6,500 at Phase I, up to $50,000 at Phase II — for commercialization activities like market validation and IP strategy, but TABA explicitly cannot pay for R&D already covered by the grant, indirect costs, or accounting services.

What the budget justification has to survive

NIFA SBIR does not accept the NIH-style modular budget. Applicants file the SF424 Research and Related (R&R) Budget component, itemized and justified line by line, and a sub-award (a university field-trial partner, a fabrication shop) needs its own separate budget justification attached. A reviewer reading that justification is checking the same thing an Indian incubator committee checks in a grant-permitted budget: does every line map to a permitted activity for the topic, does the ask match the phase ceiling, and does the cost story hold together across categories — personnel, equipment, materials, travel for field testing — rather than arriving as one lump "R&D" figure.

Indirect costs get their own scrutiny. An applicant with an existing negotiated indirect cost rate agreement (NICRA) from another federal agency can carry it over if current and non-expired; without one, the applicant can still claim the 10% de minimis rate. Either way, the rate has to be stated and defensible on the file — reviewers do not accept an indirect number that shows up without the agreement or the de minimis election behind it.

The file that separates funded from rejected

A phased milestone plan is not a nice-to-have narrative device — it is the artefact a program officer uses to release money and later to check progress against. That is exactly the discipline the engagement produced: a milestone plan a committee could hold the applicant to, tied to the budget behind it. On a NIFA award, that discipline continues after the check clears: grantees file periodic SF-425 Federal Financial Reports on the schedule NIFA sets in the award’s terms and conditions, plus a final SF-425 at closeout, with no unliquidated obligations left open on that final report. A separate narrative — the Research Performance Progress Report (RPPR) — covers accomplishments and outputs; it does not substitute for the financial report, and NIFA expects both, each on its own schedule.

The pattern that gets applications rejected before a reviewer even reaches the science is the same pattern that stalls diligence everywhere: a budget built after the narrative instead of reconciled against it, cost categories that do not tie to the milestone plan, and no clean answer for the indirect-cost rate. A file built the other way round — milestones first, budget lines tied to each one, cost tracking that can produce an SF-425 on schedule without a scramble — is what a reviewer, and later a program officer, is actually reading for. CapEasy prepares that file: the itemized budget, the milestone-to-cost mapping, the cost-tracking structure ready to feed a financial report on NIFA’s schedule. The award decision, the eligibility determination, and anything filed on the SF424 or SF-425 forms themselves run through your grant administrator and the partner CPA firms we work with across 15 US states.