Most SBIR recipients meet their program officer once, treat the call as an administrative formality, and then spend the rest of the award guessing what that person expects. The kickoff is the cheapest hour of the whole project. It is where you find out what success means to the individual who will later be asked whether you delivered.

The person on the other end is not an obstacle

A program officer at NIH or NSF, a technical point of contact at a DoD component, or a contracting officer's representative on a contract award all do a version of the same job: they translate your project to the agency and the agency's expectations back to you. They are also the person who gets asked, often informally, whether your company is worth funding again. Founders who send a short note every month or two and flag problems early tend to fare better than founders who go silent between required reports. That is not favoritism, it is simply that a project someone understands is a project they can defend.

Note that authority and advice are not the same thing. On a contract award the contracting officer, not the technical representative, is usually the only person who can change the terms. Knowing who holds which role from day one saves an argument later, and the general etiquette of dealing with a federal program manager applies here too.

What to settle before the call ends

Come with an agenda and leave with answers, in writing wherever you can get them:

  • Reporting cadence and format. Quarterly, semiannual, or annual varies by agency and by instrument, and the required template matters as much as the schedule; check it against the agency's written reporting and milestone requirements.
  • What each deliverable actually has to contain. A phrase like prototype demonstration can mean a bench rig to you and a field-representative unit to them.
  • Who may approve a change of direction, and who can only offer an opinion about one.
  • How invoices or drawdowns are submitted, and who reviews them.
  • Whether site visits, demos, or program review meetings are expected during the period of performance.

Send a short summary email afterward listing what you understood and inviting corrections. It takes ten minutes and it is the only record you will have when the portfolio changes hands mid-project, which happens more often than founders expect.

Ask the awkward questions now

Ask them while goodwill is high and nothing has gone wrong. What happens if a technical objective turns out to be unachievable, and is a negative result an acceptable outcome? What would make you recommend against a follow-on? Was there anything in our proposal you thought was weak? Program officers answer all of that far more candidly at kickoff than at month nine, when the same question reads as an early warning. If a Phase II proposal is your goal, this is also the moment to ask what evidence would make one competitive.

Projects House works alongside small companies executing federal awards, from build plan to demonstration hardware. Bring us the technical objectives you just agreed to through the contact form.