← Blueprint for proposal responses
What Phase I reviewers expect, generated from your brief.
SBIR Phase I scoring rubrics consistently flag four SE artifacts that small-team responses underdeliver on: operational concept, system requirements with verification methods, risk register, and a credible Phase II transition plan tied to PDR-ready artifacts. Blueprint generates the full set from your proposal brief in 10–15 minutes.
What an SBIR Phase I SE pack looks like.
Phase I is the feasibility phase. The SE artifacts reviewers score against:
- Operational Concept (ConOps). Nominal + off-nominal scenarios with timing, actors, and environment assumptions.
- System Requirements Document (SRD). Functional / Performance / Interface / Constraint requirements with verification method per shall.
- Logical decomposition. Functional architecture, component breakdown, derived technical requirements (DTRs), and the Allocated Baseline trace.
- Risk register. Per-risk likelihood × impact + mitigation plan, tied to the components or interfaces the risk applies to.
- V&V plan. Verification activities per shall + validation activities per MOE / ConOps scenario.
- Phase II transition readiness. Gate-readiness assessment showing PDR criteria status with traceable evidence per finding.
Blueprint emits 35 artifacts in a Phase 1.4 run — every item above + the rest of the Handbook §6.7 surface. The Phase-D PDR readiness assessment maps directly to the scoring rubric’s transition criteria.
The math on a 6-week Phase I cycle.
Every Phase I SE deliverable + the Phase II transition assessment.
Iterate as your technical narrative evolves; the per-run cost is trivial.
500 runs covers the Phase I cycle + your other in-flight proposals.
One agile day = ~30 iterations. Catch up to a 2-week SE delay in one afternoon.
Why this passes Phase I review.
SBIR Phase I reviewers — particularly DoD components running on quick-turn evaluation panels — score against:
- Technical merit + feasibility. The ConOps + SRD demonstrate the team understood the problem.
- Innovation. Comes from the technical narrative; Blueprint covers the SE structure around it.
- Commercial / mission relevance. The Stakeholder register + ConOps tie the work to the sponsoring component’s mission.
- Team capability. A complete, citable SE pack with the right structure + traceability signals the team works at Phase II maturity — which directly impacts scoring.
Blueprint addresses 1, 3, and 4 by structure — your team owns 2.
Phase I proposal questions.
What about the topic-specific deliverables in the BAA?
Blueprint generates the SE structure around your topic narrative. Topic-specific deliverables (MTBF estimates, specific test protocols, technology readiness assessments) need your engineering team's input. Drop them into the right artifact section post-generation; Blueprint's structure makes the slot clear.
Does Blueprint know about SBIR / STTR-specific formatting requirements?
No. Output is plain markdown — apply BAA-specific formatting (page limits, font, headers) post-generation. The content is structured to map to common BAA sections (Technical Volume, Commercial Volume); formatting is final-mile editor work.
What's the security story for an unclassified proposal that's part of a controlled program?
Your brief is private to your account. Blueprint is hosted SaaS; don't upload classified material. For CUI / ITAR-controlled programs, controlled-tier deployment is roadmapped (months 6-9). For pre-award unclassified work on a CUI-bound program, Blueprint is fine.
Related.
- AFWERX response SE artifact template →
AFWERX-specific framing — how Blueprint output maps to the USAF rubric.
- PDR-ready artifacts in a day →
The PDR-readiness assessment that lands in your Phase II transition section.
- ← Back to: Blueprint for proposal responses
See the SE pack Blueprint writes for your proposal brief.
Free tier · no card · 3 runs / month.
Start free →