NASA funds SBIR and STTR work through contracts, against a topic structure that traces back to the agency's own technology needs. The question behind every NASA evaluation is whether the technology could end up on a mission, in a ground system, or in an aeronautics program. That word — infusion — is the one that decides awards, and it is why NASA proposals fail for reasons that would not matter at NSF.
How the topics are organized
NASA publishes topics grouped under its mission directorates: space technology, exploration systems, science, aeronautics research and space operations. Each topic is divided into subtopics written by technologists at specific NASA centers, and each subtopic states the need, the state of the art and what a successful Phase I would demonstrate. The subtopic also usually identifies the lead center, which tells you where the interested engineers sit.
The subtopics are derived from NASA's technology taxonomy and roadmaps — the agency's structured statement of what capabilities it needs over the coming decades. Reading the relevant roadmap section before you write tells you what problem the subtopic is a piece of, and lets you position your work as part of a capability NASA already committed to pursuing. Directorate names, taxonomy structure and subtopic lists all change between solicitations; work from the current one.
Technology readiness and infusion
NASA thinks in technology readiness levels, and proposals are expected to state where the technology starts and where Phase I or Phase II would move it. Be honest about the starting point. Overstating readiness is easy to detect and hard to recover from, and understating it makes the work look premature.
Infusion means naming the destination: a specific mission class, instrument, vehicle system or ground capability that would adopt this. Proposals that describe a generally useful technology with no identified NASA user score poorly, even when the engineering is good. If the subtopic names a center, the technologists there are the audience you are writing for. The same customer-first logic runs through the commercialization plan, with the twist that NASA is often the first customer rather than the last.
What being a contract changes
Because NASA awards contracts, expect a statement of work, deliverable schedules, invoicing and a contracting officer distinct from the technical monitor. Cost proposals follow acquisition rules rather than grant cost principles, and the paperwork burden is closer to DoD than to the civilian grant agencies. Register in the federal contracting systems early; that step derails more first-time applicants than the technical writing does. Ongoing obligations are covered in reporting and milestones.
Who NASA suits
NASA fits companies working on propulsion, power, avionics, sensors and instruments, robotics and autonomy, structures and materials, thermal systems, communications, life support, in-space manufacturing, entry and landing, and the software behind all of it. It also fits aeronautics work, which founders often forget is in scope. Commercial spinout markets strengthen a proposal, but they do not substitute for a NASA use case. Award values, phase structures and the follow-on mechanisms beyond Phase II are set in the current solicitation — check them there, not in summaries like this one.
Projects House designs and builds the hardware behind space and aeronautics proposals, from concept through tested prototype. Start through the contact form.