Coherent writing and formatting helps. Clearly explaining what your tech is and what advantages it could offer the funding agency for the listed objectives in their particular topic. You'd be surprised how many companies don't actually make any clear objective case with facts and figures, or look at all from the organization's point of view. Also, keep in mind that the reviewers may not all be deep experts in every possible obscure tech. You don't want to force them to do a ton of research just to understand wtf you're talking about.

Even if you do everything right, you might not get selected for obvious reason. At least at NASA, there always seem to be managers with their own opinions that have some kind of mysterious influence in the background. Plenty of good proposals don't get awarded, so it doesn't necessarily mean there was something wrong with it.

Either-hell-yes-or-no is among the useful mental constructs I have read on HN over the years.

Time-to-learn-or-time-to-earn? Is another. To me this smells a more lot like learning than earning which might or might not be fine. It smells that way to me because my experience is landing government contracts is a specialized sub-discipline within the various industries that contract with governments. This is why grant-writing is a job description.

Finally, maybe grants will be a hell-yes for your future self. Time-to-learn can be a little at a time over a long time. Good luck.

For follow-on work you need to find government customers and project champions. The SBIR program isn’t your customer, it’s funding.

There are a lot of SBIR advisors out there, and some of them are predatory. They’ll promise contacts and contracts but you’ll definitely want to interview previous clients before paying anybody.

Here's my advice:

1) Your proposal needs to be completely solid and well-structured:

- Describe the problem. Put it into a Defense/Intel context. Talk about the needs of the warfighter.

- Do a literature review of the field, and explain what the state-of-the-art looks like today.

- Explain what previous approaches to the problem have been attempted in the past.

- Demonstrate why those approaches are flawed.

- Describe your novel approach.

- Explain why your approach will succeed where others have failed.

- Talk about what you'll deliver in your Phase I deliverable, so that you can demonstrate proof-of-concept.

- Talk about how your eventual Phase II will put your proof-of-concept into a real-world scenario, and offer at least a glimpse of how your Phase III+ will commercialize.

- Talk about your team. Why are you uniquely capable of solving this problem?

- Talk about your budget. How will you spend the money toward satisfaction of the deliverables (salaries, subcontractors, equipment and supplies, etc)

2) As soon as you know you're interested in a topic, send an email to the Principal Investigator, telling them you'd like to meet with them to talk about the topic. Before the phone call, research the PI's history with this topic. Also, lookup the archive of SBIR topics, to see if this person has been a PI on similar topics in the past.

When you meet with them, ask clarifying questions that demonstrate you know the domain. Try to get as much specificity as you can... Ask them what their success criteria look like. See if you can get them excited!

Most importantly, by the time you submit, the PI should already know your name and to expect your submission.

3) If you're not already a recognized expert, with published academic papers on the topic, that's okay! But you'll improve your chances of winning a grant if you hire a known researcher as an advisor. For example, I've hired a Computer Science professor to supervise one of their own grad students, while doing paid work on a SBIR project. So the professor's credentials and the grad student's previous publications also became part of the SBIR proposal.

Anyhow, good luck!

You don't really make money on Phase I projects, but that's how you get the ball rolling on future work, which can be very lucrative.