From Outline to Upload: A 4-Week SBIR Submission Plan

Written By Sofia Lazaro

Week 1: Lock Your Technical Objectives + SOW (So the Rest Writes Itself)

If you’re aiming for the upcoming June 3 SBIR or STTR deadline, this is the week that determines whether the rest of your proposal process feels controlled or chaotic.

If you’ve submitted before, you already know the trap: you start writing pages, partners start “adding thoughts,” and suddenly you’re rewriting core sections in the final week or surprised by an unusual Volume 5 requirement.

Over the next 29 days, we’re going to walk you through the exact sequence our small business uses week by week to get from “we should bid this” to “submitted” without the last-minute scramble.

One important note: we’re going to work from inside the technical volume out. That means Week 1 is not “project management.” It’s locking your technical objectives and a workable SOW outline early so your drafting, budget, and uploads all have a stable backbone.

This Week’s Goal

Finalize your Technical Objectives and a rough-but-complete SOW outline, aligned with all key personnel, before you draft the full narrative.

When your objectives and SOW are locked early, you:

  • Reduce late-stage rewrites (the most expensive kind)

  • Make your budget and schedule defensible later

  • Keep the proposal in “one voice,” even with multiple contributors

  • Avoid compliance and formatting mistakes caused by last-minute scrambling

Your Week-1 Focus

1) Draft your Technical Objectives (then sharpen them)

Start with 3–5 objectives that are:

  • Specific (not “improve” or “enhance”)

  • Testable (you can prove success)

  • Traceable (each objective clearly ties to the topic)

Practical tip: for each objective, add a short note that answers: “What evidence will we point to that shows we achieved this?” That one line will make Weeks 2–4 dramatically easier.

2) Build your SOW outline from the objectives (technical volume first)

Now work outward from the technical volume. Create a SOW outline that supports your objectives with:

  • Tasks and subtasks

  • Deliverables

  • Schedule logic (what happens first, what depends on what)

  • Clear ownership (who is doing what—especially partners/subcontractors)

You are not trying to write the final SOW this week. You are trying to create a SOW that is complete enough to draft the rest of the technical volume from.

3) Socialize it with key personnel, assign owners, and lock alignment

This is the “save yourself later” step. Schedule a short alignment review (even 30 minutes) with your:

  • PI / technical lead

  • Key contributors

  • Subcontractors / teaming partner(s)

Your goal is to confirm:

  • The objectives are the right objectives

  • The SOW is feasible and coherent

  • Everyone agrees on ownership and inputs

Don’t leave this meeting without assigning a responsible owner for each section.

  • Assign internal owners for each major section of the technical volume

  • Assign owners for the other volumes (be clear about if they are producing content or if it’s just “who is coordinating inputs and final formatting”)

Finally, freeze a v1 so you can draft without moving targets.

Pro tip: check the Volume 5 requirements in the BAA early. Some BAAs include extra items that are time-consuming to create (and they’re the kind of thing that can derail your final week if you discover them late).

Done by Friday (Your Week-1 Checklist)

By the end of this week, you should have:

  • Finalized Technical Objectives (v1 frozen)

  • A rough-but-complete SOW outline that supports the objectives

  • An annotated technical volume outline (section headings + what goes where)

  • Alignment completed with all key personnel (notes captured)

  • Owners assigned for technical volume sections and the other volumes

  • A writing + review calendar that runs through June 2

  • An upload-ready folder structure and version naming convention

Helpful Reads 

Two quick resources that pair well with this Week-1 work:

Use a Proven Example (So You’re Not Guessing)

If you want to move faster this week, don’t start from a blank page. A winning technical volume can help you model:

  • How objectives connect to the work plan

  • The level of detail reviewers expect

  • How to keep the narrative structured and easy to score

In Week 2, we’ll use your finalized objectives + SOW outline to draft quickly—without rewriting the foundation.

FAQ

  • DescriptionSBIR (Small Business Innovation Research) and STTR (Small Business Technology Transfer) are U.S. government programs that fund small businesses to research and develop innovative technologies through competitive solicitations.

    SBIR (Small Business Innovation Research) and STTR (Small Business Technology Transfer) are U.S. government programs that fund small businesses to research and develop innovative technologies through competitive solicitations.

    The key difference is that STTR requires a formal collaboration with a U.S. research institution (such as a university or federally funded R&D center), while SBIR does not (though SBIR can still include subcontractors and research partners).

  • Technical objectives are the specific, measurable outcomes your Phase I or Phase II work must achieve. Strong SBIR technical objectives are testable, traceable to the solicitation, and directly supported by your work plan and SOW.

  • Start by making each objective specific and verifiable (what will be demonstrated, measured, or delivered). Then confirm each objective has a clear method, a realistic timeline, and a corresponding task in your SOW—so reviewers can see feasibility without guessing.

  • An SBIR SOW explains the work you will perform to meet your technical objectives. In Week 1, your SOW outline should include major tasks, subtasks, deliverables, and dependencies—enough structure to draft quickly, even if the language is not final yet.

  • Check Volume 5 requirements in Week 1. Many “administrative” items take longer than expected (data rights assertions, resumes in required formats, letters of support, org charts, facilities, subcontractor documentation). Identifying them early protects your schedule.

  • The biggest Week 1 mistakes are vague objectives, a SOW that does not clearly support the objectives, unclear section ownership, and discovering Volume 5 or compliance requirements late. These issues often force major rewrites in the final week.

  • Yes—AI can help with outlining, researching, rewriting for clarity, and consistency checks, but it must be guided by your objectives, solicitation requirements, and your actual technical approach. Always review for accuracy, compliance, and technical credibility.
    Related: https://intrepidgovproposals.com/free-sbir-resources/how-to-use-ai-for-sbir-proposal

  • We published a detailed list of common mistakes (including formatting and commercialization pitfalls) that frequently cause proposals to be rejected.
    https://intrepidgovproposals.com/free-sbir-resources/common-mistakes-to-avoid-when-submitting-your-sbirsttr

Sofia Lazaro
Next

Strategic Hibernation: A Survival Guide for SBIR Small Businesses During The Government Shutdown