What a non-dilutive grant reviewer actually reads in your financial file

What was broken

A robotics startup developing semi-autonomous solutions needed capital to run pilot programmes and advance its technology roadmap.

What we did

CapEasy structured a public seed-fund application around a staged market-entry and technology plan with a defensible budget and projections, and prepared the eligibility and compliance framing for committee review.

Where it landed

The startup secured a public seed-fund approval. A seed-fund approval is the incubator committee’s sanction; actual disbursement follows the scheme’s due-diligence and compliance milestones and is not guaranteed.

The programs built for dual-use autonomy

US autonomous-systems and robotics founders have a specific set of non-dilutive doors, and they are not generic "startup grants." AFWERX, the Department of the Air Force’s innovation arm, runs SBIR/STTR solicitations through the DoD SBIR/STTR portal that explicitly target dual-use technology — solutions with both a defense end user and a commercial market, which is exactly the profile of a company selling autonomy into pilots today and defense or transportation customers later. The Department of Transportation runs its own SBIR program out of the Volpe National Transportation Systems Center, with recurring solicitation cycles that name automated vehicles and unmanned aircraft systems (UAS) as priority technology areas because AI-driven automation is treated as a direct accelerant of DOT’s safety and mobility mission.

The sequencing matters as much as the agency. A DoD SBIR Phase I is a short feasibility award; a Phase II moves to prototype-scale funding tied to a specific government customer and, for AFWERX-run topics, often requires a signed Customer Memorandum of interest before the company can compete. Read the current cycle’s topic list and award ceilings directly on the DoD SBIR/STTR portal before you write anything — they are set per solicitation, not fixed year to year.

What a reviewer opens first: the budget justification

A technical narrative gets you read. A budget justification gets you funded. SBIR.gov’s own guidance is explicit: proposed costs must be reasonable, allocable, and allowable under federal cost principles (2 CFR Part 200 Subpart E for most agencies, FAR Part 31 where it applies), and every labor rate has to be defensible — reviewers routinely ask a company to explain how it derived a rate in its cost proposal and why that rate is "reasonable," in both Phase I and Phase II negotiations. A principal investigator’s time commitment is checked against agency minimums, not just claimed. An indirect cost rate has to be the company’s own, built from its own rent, utilities and overhead — not borrowed from a comparable firm because building one from scratch is slower.

For a hardware and autonomy company this is where applications fail quietly: prototype builds mix R&D labor, purchased components, test-flight or test-rig costs, and subcontracted work, and a budget that cannot separate those lines from each other reads as a company that does not know its own cost structure yet — which is precisely what a reviewer is trying to price the risk of.

The accounting system that survives a DCAA look

DoD SBIR/STTR awards are backstopped by Defense Contract Audit Agency oversight, and SBIR.gov’s own accounting tutorials lay out what an approved system needs before or shortly after award: direct costs segregated from indirect costs, direct costs accumulated by contract or project, a consistent method for allocating indirect costs, cost accumulation under general ledger control, and — the requirement that generates the most audit findings — a formal timekeeping system where every person on the project, including the founder, logs hours daily against the specific contract, not as an end-of-month percentage estimate.

For a company running parallel prototype builds — one iteration for a DoD pilot, one for a commercial customer, one funded by the award itself — that segregation is the whole game. Costs have to trace to a specific line item and a specific contract, not to "engineering" as a bucket. Post-award, cost-reimbursable Phase II work adds an Incurred Cost audit, where the company reports its actual year-end costs against what it billed — which only reconciles cleanly if the books were built to that standard from the Phase I proposal onward, not retrofitted once a program manager asks.

The discipline the engagement already proved

The mechanism was different — a seed-fund committee weighing a seed-stage grant against registered eligibility criteria — but the underlying test was the same one a US SBIR reviewer runs: does this company’s budget, its projections and its cost structure hold together as a document a committee can underwrite, not just a pitch a founder can narrate. The reconciled, staged plan is what a review board — anywhere, or at AFWERX — is trained to look for before it will put non-dilutive money behind a technology roadmap.

CapEasy prepares that file: the cost segregation, the labor and indirect-rate documentation, the budget built line by line against the milestones a reviewer will hold you to. Filing the SBIR/STTR proposal itself, any DCAA-facing representations, and returns or attest work run through partner CPA firms across 15 US states — the eligibility and program decisions belong to the agency and your counsel.