What was broken
A tech-enabled mobility startup addressing rural roadside assistance needed early capital to scale after launch.
What we did
CapEasy built the seed-funding application — a utilisation plan, market framing, and financial projections — and aligned the proposal to the program’s eligibility and compliance requirements.
Where it landed
The startup secured approval from a public seed fund. A seed fund approval is the reviewing committee’s sanction; actual disbursement follows the program’s due-diligence and compliance milestones and is not guaranteed.
The federal program built for this exact sector
For mobility, logistics and transportation technology, the sector-matched non-dilutive program is DOT’s own Small Business Innovation Research contract, administered by the Volpe National Transportation Systems Center on behalf of DOT’s operating administrations. Which ones sponsor topics varies by year — Federal Highway, Federal Motor Carrier Safety, Federal Railroad, Federal Transit, NHTSA and PHMSA have all sponsored topics in recent solicitations. DOT publishes one Phase I solicitation a year with a handful of numbered topics spanning each participating administration’s priorities, and a roadside-assistance, fleet-routing or connected-vehicle platform sits squarely inside that scope — check the current solicitation on SBIR.gov for the specific topics open in a given year rather than assuming a prior year’s list repeats.
Per SBIR.gov’s DOT program page, Phase I contracts go up to $150,000 (individual topic ceilings can be lower — check the ceiling stated for the topic you apply under, not the program maximum), and Phase II runs $350,000 to $1 million, with a sequential Phase IIB available for up to 24 months. A critical distinction from most other agencies: DOT administers SBIR as contracts, not grants — the accounting posture that follows from that is different from an NSF or NIH award, and it is the first thing a reviewer with contracting experience will check your budget against.
What the accounting system has to prove before a dollar moves
Every cost on a federal proposal is judged against three tests SBIR.gov states plainly: allowability, reasonableness, and allocability — a cost has to be permitted, has to be what a prudent business would spend in competitive conditions, and has to tie to the specific contract, not sit as an unassigned overhead figure. For a logistics-tech applicant that means the budget can’t bundle "engineering" and "field-test operations" into one line; a reviewer wants development labor, sensor or telematics hardware, and route-testing costs itemized and justified separately, the same way a utilisation plan has to show each rupee against a stated use rather than a lump sum.
SBIR.gov’s accounting-system tutorial lists ten attributes DCAA checks before a Phase II award clears a pre-award survey, on Standard Form 1408: segregating direct from indirect costs, accumulating direct costs by contract, a consistent method for allocating indirect costs, general-ledger cost control, and — the one every applicant underestimates — timekeeping. Entries have to be made daily, by every employee including founders, in actual hours rather than percentages. A logistics startup running lean with engineers splitting time between the funded prototype and commercial product work cannot reconstruct that split from memory in month eleven; it has to be logged from day one.
Payment is milestone-tied, not lump-sum — and the discipline outlives the check
DOT structures Phase I as a fixed-price contract paid against three deliverables: two progress reports submitted roughly bi-monthly and a final report at close, with a partial payment released on the government’s acceptance of each one. That is a materially different cash-flow shape than a single up-front check — a mobility startup budgeting against a DOT award needs a runway model that assumes payment on report acceptance, not on contract signature, the same way a milestone-released seed grant pays out against verified progress rather than on approval alone.
The pattern that separates a funded application from a rejected one is the pattern this engagement produced in a different jurisdiction: a utilisation plan and financial projections built to survive scrutiny, not to impress on a first read. CapEasy prepares that file — the itemized cost buildout, the timekeeping structure ready to substantiate direct labor, the runway model that matches the report-and-payment cadence. Eligibility determinations, the contract itself, and anything filed on the SBIR proposal forms run through your grant or contracts administrator and the partner CPA firms we work with across 15 US states.
What to take from it
- Federal research-funding programs vary in structure — some run as contracts with fixed-price, deliverable-triggered payment, others as grants; check which regime you are actually budgeting against.
- The relevant agency’s annual solicitation reliably includes mobility- and logistics-relevant topics — check the current-year list rather than assuming a prior year’s topics repeat; a routing, telematics or roadside-assistance platform is a genuine sector fit for the program, not a stretch.
- Every line has to clear allowability, reasonableness and allocability; a bundled "engineering" cost line fails the same review a lump-sum utilisation ask fails.
- Timekeeping is not optional paperwork — daily, actual-hours entries from every employee, founders included, are what an accounting system audit checks first.
- Awards often pay in instalments tied to report acceptance, not on contract signature — build the runway model around that cadence before you assume the award amount lands as one lump sum.
Primary sources
- SBIR.gov — DOT individual agency requirements (award ceilings, contracts not grants)
- SBIR.gov — Accounting system requirements for SBIR awardees (10 core attributes, timekeeping)
- SBIR.gov — SBIR/STTR audits (SF1408, allowability/reasonableness/allocability)
- Volpe Center — U.S. DOT SBIR payment timing (Phase I reports and partial payments)