Week 4 SBIR/STTR Submission Sprint: Finalize & Submit To Win Non-Dilutive Funding
Week 4 is the final countdown. This week assumes you’ve already done the heavy drafting work in prior weeks (your Volume 2/technical volume with a strong work plan and your cost volume). Here, you’ll finalize what’s left, improve clarity, and get everything into the submission portal. Let’s turn your mostly-finished draft into a submission-ready package to win your small business R&D funding.
Your three priorities this week
Write Volume 1 (your cover summary/abstract) after Volume 2/your technical volume is complete
Finalize and upload your cost volume in DSIP (or whatever submission portal your agency requires)
Upgrade your technical volume with memorable graphics that still work when printed in black and white
If you need to backfill earlier steps in the sprint, start here:
Week 2 (work plan + commercialization): How to Write an SBIR Work Plan & Commercialization Plan
Week 3 (cost volume + remaining technical sections): SBIR/STTR Submission Sprint Week 3
Step 1 — Finish Volume 2 First (If It’s Not Done Yet)
Volume 1 is easiest when Volume 2 is complete, because Volume 1 is essentially the abstract/summary of the technical volume.
If your Volume 2/technical volume is still in progress, your Week 4 rule is simple: Complete Volume 2 first (even if it’s “good enough”), then write Volume 1 from that finished draft.
This prevents the most common Week 4 mistake: writing a polished summary of a proposal that later changes.
Step 2 — Write Volume 1 as a Thesis Summary (Draft Outside the Portal)
For many agencies, Volume 1 functions like a cover summary or abstract. Requirements vary, so always follow the solicitation prompts and word/character limits.
Even when Volume 1 is ultimately pasted into DSIP (or another portal), draft it outside the portal first so:
Your team can review and align on the story
You can keep version control
You reduce the risk of portal timeouts or formatting surprises
Use this as a starting framework for structuring your Volume 1, then tailor to the agency’s prompts:
Problem / Mission Need (1–2 sentences): State the real-world problem and why it matters now. This should be direct from the solicitation, but your understanding of it.
Your Innovation (1–2 sentences): What are you building, and what makes it meaningfully different from the other proposals evaluators will read for this topic?
Technical Approach (2–4 sentences): Summarize what you will do in Phase I (or the proposed period), at a high level.
Expected Results + Success Metrics (1–3 sentences): What will you prove, demonstrate, or deliver—and how will success be measured?
Why Your Team (1–2 sentences): A credibility line: why you can execute better than any other team proposing against this topic (domain expertise, prior work, facilities, partners).
Impact + Commercialization Direction (1–2 sentences): A brief “so what”: who benefits, and what’s the plausible path to adoption.
Quick quality checks for Volume 1
Every claim is supported somewhere in Volume 2 (no new promises)
Terminology matches Volume 2 (same product name, same objective labels)
The scope described matches your work plan and period of performance
Step 3 — Finalize the Cost Volume and Get It Into DSIP
Adjust for any feedback or inputs received when you drafted your cost volume last week. Export the one-pager to add to your Volume 5 and upload the remaining details to DSIP.
If you want a clean walkthrough to sanity-check your numbers and avoid rework, use:
If you want a fillable template that speeds up the build (and reduces math/formatting errors), use:
Step 4 — Upgrade Your Technical Volume With Graphics (Make It Memorable)
Evaluators read a high volume of proposals. Graphics help them understand and remember your idea faster.
After you complete your final narrative pass through the technical volume, look for any place where a figure would communicate the concept more clearly than text.
Graphics we almost always include:
Competitor comparison graphic (simple, defensible, easy to scan)
Milestone timeline (often a Gantt-style visual)
Architecture diagram (how the proposed system fits together)
Many proposals are printed in black and white. Design accordingly:
Use high contrast and clear labels
Avoid relying on color alone to convey meaning
Use patterns, shapes, or direct annotations instead of subtle color differences
Make sure text is readable at print size
Want to see what “winning” looks like on the page (including how strong proposals use figures and formatting)?
And if you want a fast reality check on why a proposal can still lose (even when the team worked hard), this postmortem might be worth your while: Why This STTR Proposal Didn’t Win
Step 5 — Do a Compliance + Consistency Sweep (Fast, Strict)
This is the “catch what disqualifies you” pass. You’re looking for mismatches created during edits. Check for consistency across Volume 1, Volume 2/technical volume, and the cost volume:
Product/technology name is identical everywhere
Objective and task labels match your work plan
Period of performance and dates are consistent
Key personnel names/roles are consistent
Numbers don’t contradict (hours, totals, quantities)
If you want a quick “run your proposal through this before you submit” filter, use:
And do not leave data rights until the last minute, protect your IP! How to Fill Out an SBIR Data Rights Assertion Table
Step 6 — Upload Everything, and Check the BAA Twice
Did you miss any Volume 5 requirements? Is your font size compliant? This is your time to double or triple check the BAA to ensure you have everything you need. You don’t want to have come this far to get disqualified. With the volume of proposals that some of these topics get, evaluators will take any reason to throw out a proposal.
One last Week 4 non-negotiable: submit early. Portal issues are not a reason for extensions. Aim to have everything uploaded 48 hours before close. Your absolute minimum should be 24 hours before close. If you need to make revisions after uploading, you can typically upload updated files and re-certify. Ask us how we know :)
Week 4 To-Do (Copy/Paste Checklist)
Volume 2/technical volume is done and edits locked
Volume 1 drafted outside the portal, tailored to prompts and limits
Volume 1 matches Volume 2 (no new claims, consistent terminology)
Cost volume finalized and ready to upload
Cost volume uploaded to DSIP (or agency portal) 48 hours early (24 hours minimum)
Graphics added where they improve clarity (competitors, timeline, architecture)
All graphics pass black-and-white readability check
Compliance + consistency sweep completed across all volumes and attachments
Evaluator skim test completed and clarity edits made
Onward, and best of luck! We hope you win against a giant useless SBIR mill.
FAQ
-
The final week is when you turn a mostly complete SBIR proposal or STTR proposal into a submission-ready package. The focus is tightening clarity, completing a final proposal checklist, running a strict proposal compliance review, and submitting early enough to fix issues.
-
A strong SBIR proposal checklist (or STTR proposal checklist) typically includes: all required sections completed, formatting and page/word limits verified, attachments included, budget/cost documents finalized, and a final proposal compliance checklist pass to confirm nothing is missing or contradictory.
-
Proposal compliance means following the solicitation instructions exactly—required components, formatting rules, limits, forms, and submission requirements. A great technical idea can still be rejected if the SBIR proposal or STTR proposal is noncompliant.
-
Common last-minute mistakes include missing required attachments, formatting violations, inconsistent names/dates/numbers across files, and making late changes that introduce contradictions. A final proposal checklist and proposal compliance checklist helps catch these before submission.
