In a page-limited proposal, every figure is bought with text you could have written instead. One clear system diagram usually outperforms three decorative renders, because the diagram answers a question the reviewer has and the renders answer one nobody asked. Before a figure goes in, name the specific thing it explains faster than a paragraph would. If you cannot, cut it.

The one figure most proposals need

For a hardware or device project, the highest-value figure is almost always a system diagram: the blocks, what flows between them, where the innovation sits, and which blocks are off-the-shelf. It settles in seconds what would otherwise take two pages of prose, and it tells the reviewer exactly how much of the system you are actually inventing.

A close second is a figure that carries evidence rather than architecture: preliminary data, a measured curve against a benchmark, or a labeled photograph of a working bench setup. A photo of a real breadboard says the team has hands, which is a different claim from a rendering and a stronger one. Photorealistic renders have a role in an investor deck, and a good product rendering costs real money, but a review panel scoring technical feasibility gains nothing from studio lighting.

Legibility beats beauty

Assume your figure will be read in grayscale, at print size, by someone whose eyes are tired. That has concrete consequences:

  • Do not encode meaning in color alone. Use line style, fill pattern, or direct labels so the figure survives a black-and-white printout.
  • Set type sizes against the printed page, not the screen. Axis labels smaller than the body text are unreadable, and a screenshot of a CAD window is usually unreadable twice over.
  • Label directly on the figure instead of using a legend the reader has to map back and forth.
  • Keep one figure to one idea. Four subpanels crammed into a half-page column is four figures nobody can see.

Captions that state the takeaway

A caption that reads System block diagram is a label. A caption that reads Sensor output is fed to the custom front end, the only block not commercially available, is an argument. Write captions as complete sentences that state the conclusion the reader should draw, because captions are read on the fast pass even when the surrounding paragraph is not. The same reasoning that governs how reviewers score what they find applies here: a claim they cannot locate is a claim they did not read.

Spend the page budget deliberately

Figures consume the space your technical approach needs, so treat the page limit as a budget with two competing demands. A useful discipline is to draft the text first, at length, and only then decide which paragraphs a figure can replace outright. If adding a figure does not let you delete something, it is probably decoration.

Watch the formatting rules too. Solicitations set minimum font sizes and often say whether text inside figures is exempt, and shrinking a caption to reclaim a line is the kind of thing that gets a proposal returned unreviewed. Check the current solicitation and the general SBIR application requirements before you lay anything out, and keep figures consistent with the numbers in your commercialization plan so the two halves of the proposal do not contradict each other.

Projects House produces the system diagrams, bench data, and technical drawings that go into SBIR proposals for physical products. Send us your project through the contact form.