Most SBIR teams are full of brilliant engineers. That's why they won Phase I. But the skills that make great research don't always make a great commercialization plan.
The engineer wants to explain how it works. The reviewer wants to know who will buy it and why. Here's how we close that gap.
Write for two audiences
A good plan tells two stories at once.
The government story covers the mission need, the path through prime contractors, and other agencies that might use the technology. The commercial story covers market segments, your value proposition, your business model, and how you'll enter the market.
We outline these as two separate tracks before we write. Then we weave them together. That way, neither one gets lost.
Ask the reviewer's questions out loud
Reviewers are smart, but they aren't specialists in your field. If something confuses a smart outsider, it will confuse them too.
So during drafting, we play the outsider. What's the real difference between these two pricing options? Why would a customer switch? Who signs the purchase order? If the writer can't answer, neither can the reviewer. Ask the question in the draft, get the answer from the team, and put it in the plan.
Cut what doesn't help the score
This one is hard for technical teams. Hardware specs, test data, and side figures may all be true and impressive. But if they don't support commercialization, they cost the reader attention.
The technical volume is where that detail belongs. In the commercialization plan, every paragraph should help a reviewer score you higher. If it doesn't, cut it or move it.
Write for the template
Agencies have required formats. Some are web forms with character limits. Some have fixed section headings.
We deliver sections in plain text, already mapped to the agency's structure. That way the team can drop them straight into the form without reformatting the night before the deadline.
Run a review cycle that actually closes
Every first draft needs a pass from the technical team. The trick is keeping that review focused, especially when everyone is also racing to finish the technical volume.
A few habits help:
• Tie each comment to one passage. Short and specific, so nothing gets lost.
• Say where the current number lives. "Contracts team has the latest award count" gets answered faster than "update this."
• Ask for names. "Which customers?" is the most valuable comment in any review. Named customers with letters beat any market description.
• Assign one reader for consistency. Someone who only checks that the text, tables, and captions agree will catch what subject experts miss.
• Close every comment with what changed. A short note like "cut by half" shows the issue is done and keeps the round moving.
The payoff
A plan written for the reviewer is usually shorter, clearer, and more specific than one written for the lab. It doesn't change your strategy. It makes your strategy easier to believe and easier to score.