How to Approach a Program Officer Before You Apply

The single highest-return hour in a federal grant application is a conversation that most first-time applicants never have. Before the solicitation closes, before you write anything, you can talk to the government employee who manages the program — and that person will tell you, often bluntly, whether your project belongs in their portfolio.

Applicants skip this for two reasons. They assume contact is prohibited, which is generally false outside a formal contract competition. Or they treat it as a sales call, open with a pitch, and burn the one contact they had. The conversation has rules, and it rewards preparation more than enthusiasm.

Who you are actually talking to

Titles differ by agency and they are not interchangeable:

• Program officer or director (NIH, NSF) — a scientist who owns a portfolio, advises applicants, chooses which panel sees your application, and influences funding decisions near the payline.
• Program manager (DoD, DOE, ARPA-style offices) — defines the technical problem, shapes the topic language, and manages funded teams actively.
• Grants management specialist — handles eligibility, forms, budgets and the award instrument. They cannot discuss technical merit.
• Topic author (SBIR) — wrote the topic you are answering, reachable only during a defined pre-solicitation window.

Ask the right person the right question. Technical fit goes to the program officer. Whether your entity qualifies goes to grants management. Getting this backwards is the fastest way to waste the contact.

The NSF Project Pitch, specifically

NSF's SBIR and STTR program runs a formal front door called the Project Pitch. You submit a short summary — the technical innovation, the technical risk, the product and the market, in a few hundred words each — and NSF responds with an official yes or no on whether the project fits the program, usually within a few weeks. An invitation is required before you can submit a full proposal.

Two things founders misread. First, this is a screen, not a mini-proposal to be padded with everything you know; a crisp pitch reads better than a dense one. Second, a decline is information, not a verdict — it usually means the project belongs at a mission agency instead. NSF funds broadly applicable innovation with real technical risk; if your work solves one agency's operational problem, the answer sits elsewhere. Use a decline to redirect, as described in choosing between NIH, NSF, DoD and DOE.

NIH program officer contact

NIH runs on a different model. Every institute publishes staff contacts by scientific area, and reaching out before you apply is normal and expected. The standard approach is a short email with a one-page specific aims draft attached, asking whether the project fits the institute's priorities and which study section would be appropriate.

That second question matters more than most applicants realize. Your application is assigned to a study section and an institute, and the assignment shapes who reviews you. A program officer can tell you which panel has the right expertise and can advise on your assignment request. They can also tell you whether a device-focused project fits a particular funding opportunity announcement or whether a different mechanism suits it better — the landscape covered in NIH funding paths for medical device startups.

After review, that same officer explains your summary statement and advises whether to resubmit. Build the relationship before you need it.

DoD and DOE: talk during the open window

Defense SBIR topics have a pre-release period during which you may contact the topic author directly with technical questions. Once the solicitation formally opens, that channel closes and questions move to a public written question-and-answer system where everything you ask is visible to competitors. Calendar the pre-release window; it is short and it is the only time you get a private conversation.

DOE and ARPA-style program managers hold teaming meetings, webinars and office hours around a funding opportunity announcement. Attend them. Managers say things in those sessions that never appear in the written call — which approaches they consider played out, and what they think the hard part is.

What to send before the call

One page. Not a deck, not a white paper, not an attachment set. The page should contain:

• The problem, stated in the agency's terms rather than your market's.
• Your technical approach in a few sentences, including what is genuinely new.
• The hardest technical risk and how you would retire it.
• Where the work stands now — what exists, what has been measured.
• What you would ask the program for, roughly, and over what period.

Write it so a technically trained non-specialist can follow it. That constraint is the same one that governs writing an idea brief before contacting a development firm, and the discipline transfers directly.

Questions worth asking

• Does this project fit your program's current priorities, or is there a better fit elsewhere in the agency?
• Which topic or funding opportunity announcement would you point me at?
• What is the typical award size and duration for this program right now?
• What technical maturity do you expect at the start of an award in this program?
• What do unsuccessful proposals in this area usually get wrong?
• Which review panel would likely see this, and what background do those reviewers have?
• Is cost share expected, and does the program allow equipment purchases?
• Would a resubmission be worth it if this one is not funded?

The question about what unsuccessful proposals get wrong is the most valuable on the list; officers answer it directly because they read those proposals all day.

What not to ask, and what not to do

• Do not ask whether you will get funded. They cannot say, and asking marks you as new.
• Do not ask them to review a draft proposal. A one-page concept, yes. Twelve pages, no.
• Do not pitch. The enthusiasm that works in an investor meeting reads as noise here; the mode is closer to technical peer review than to answering investor questions.
• Do not argue with a redirect. Take the referral and ask who to contact.
• Do not ask questions the solicitation already answers. Officers can tell instantly.
• Do not ask about other applicants, panel composition or paylines.
• Do not disclose anything you need to keep confidential. An informal call is not the venue for unprotected trade secrets. If patentable subject matter is involved, get the filing timing right first — see when to file a patent.

How the conversation changes the proposal

A good call produces three changes. The framing shifts to the agency's language — the mission problem, not your product category. The scope adjusts to the real award size. And the technical risk section gets rewritten around whatever the officer called the hard part, because that is what the panel will focus on.

It also tells you when to stop. If the officer says your project is a good product but not a research risk, you have learned something expensive for free: the money should come from customers or investors instead. That is the same decision framework as grants versus equity funding.

After the call

Send a one-paragraph thank-you restating what you understood and what you will do next. If you apply, reference the conversation in your cover letter where the agency permits one. If declined, ask for a debrief — the specifics are far more useful than the written reviews alone. Then expect the full timeline described in how long federal decisions take to run again.

Projects House helps founders get the technical substance in place that makes these conversations productive — a working prototype, measured performance, an honest risk list and a development plan a program officer can evaluate. If you are preparing to approach an agency and need the engineering behind the concept, contact us through our contact form.