SBIR / STTR FAQ

Questions to settle before Raven goes on the workshare.

Review fit, ownership, delivery, and public-information boundaries before proposal commitments are made.

Fit and teaming

When should we bring Raven into an opportunity? Bring Raven in while there is time to define the software boundary, proposal inputs, workshare, interfaces, and milestones.
Can Raven participate as prime or subcontractor? Yes. Raven can lead a software-centered effort or own a defined software package under another prime.
How does Raven work with an STTR research institution? The institution supplies the research method and domain depth; Raven can implement the software, experiment tooling, tests, and transition package.
What makes an opportunity a good fit? A clear research objective, meaningful software work, known or discoverable interfaces, and a decision working software can help the team make.

What software can Raven own? Software architecture, prototype applications, APIs, simulation and experiment tooling, data pipelines, automated evaluation, integration, documentation, and handoff.
What must the partner provide? Topic strategy, domain science, approved data and interfaces, facilities or hardware when needed, program constraints, and acceptance authority.
What changes between Phase I, Phase II, and transition? Phase I answers feasibility, Phase II expands the viable approach, and transition prepares source, deployment, documentation, ownership, and open risks for the next team.

What does the SwarmSim demonstration show? It runs a deterministic synthetic coordination model with bounded controls, a topology, an event trace, and downloadable run artifacts.
Does Raven claim awards or field performance? No current award, government sponsorship, fielded system, operational deployment, or measured field performance is claimed.
What can we submit through the website? Public, unclassified introductory context only; do not submit controlled or sensitive material.