The series has built its argument one piece at a time, the programs, the agencies, the eligibility, the proposal, the money, the compliance, the strategy, and the analogs each treated in turn. This final article puts the pieces back together by following one company through a whole campaign, because the parts are easier to learn separately than to see working together, and the point of the series was always the working whole. One idea has organized everything and it organizes this capstone, that the programs supply non-dilutive capital in stages against demonstrated risk reduction, a staircase from feasibility to prototype to market, and the company that understands the climb uses each award to buy the next rung rather than to stand still. The company below is a constructed illustration rather than a real firm, and the figures, the timelines, and the program details remain the time-sensitive and agency-specific matters the series has flagged throughout, so nothing here is advice for a particular campaign and the current solicitations and rules are the authority.
The company is the small firm that has run through the whole series, the one building a fixed-wing unmanned aircraft from lightweight printed structures and fiberglass. Its technology is an unmanned aerial vehicle airframe with an unusual endurance-to-cost ratio, and it is deliberately a dual-use design, useful both to a defense customer that wants a cheap attritable surveillance platform and to a commercial market that wants long-endurance inspection and survey flights. That dual-use character is the single most important fact about the company, since it shapes which agencies it approaches, what its commercialization story is, and whether it can survive beyond the awards, and it is the thread that the rest of the campaign follows. The company has a working prototype and promising flight data but no production contract and little capital, the exact position the programs exist to address.
The company begins where the introductory article began, by asking whether the programs fit it at all. They do, since it is a small for-profit developing high-risk technology that a government wants, so it reads the survey of the agencies to decide which to approach and concludes that the defense agencies are its natural first customer, both for the mission fit and for the volume of relevant topics on the defense innovation portal, with the broader program portal showing the civilian agencies as a later possibility. It chooses to target a defense agency for its first award and to keep a civilian agency in reserve for a parallel track, a portfolio decision made at the very start rather than left to chance.
Before it can compete the company must become eligible, the unglamorous groundwork the eligibility article laid out. It confirms it meets the size and ownership tests, registers in the federal systems the article described, obtains the identifiers an awardee needs, and sets up the records it will need later, and it decides at this stage between a single-firm SBIR path and a partnered STTR path, choosing the STTR route for its first proposal so it can draw on a university laboratory’s aerodynamics expertise under the required split of the work. The registration takes longer than the company expects, which is the ordinary experience, so it starts the groundwork well before the solicitation it wants to answer opens.
With the groundwork done the company hunts for the right topic, the discipline the solicitation article described. It finds a defense topic seeking exactly the endurance-per-dollar its airframe delivers, reads the topic with the care the article urged, and confirms that its technology answers the stated need rather than merely resembling it, then writes the Phase I proposal to prove feasibility. The Phase I work is small and short, a feasibility study and a modeling effort that takes the airframe concept from a low readiness level to the threshold of a prototype, and the proposal promises exactly that and no more, because Phase I buys the right to compete for Phase II rather than a finished product. The company wins, and the win is the first rung of the staircase.
Phase II is where the real engineering happens, the stage the commercialization-plan article covered. The company builds and flies an improved prototype, taking the airframe to a mid-range readiness level with its university partner performing its share of the work as the STTR structure requires, and alongside the engineering it writes the commercialization plan the agency now demands, the credible account of how the technology reaches a market beyond the award, which for this company rests on its dual-use character and names both the defense program it hopes to enter and the commercial inspection market it can also serve. The proposal that wins Phase II is therefore half engineering and half business, and the company that treated Phase I as a mere feasibility exercise without a transition in mind would struggle to write the second half convincingly.
Holding two awards in sequence forces the company to confront the matters the middle of the series treated. It builds the compliant accounting and the indirect rate the money article described, learning that the rate decides how much of a fixed award reaches the work, that the cash gap between spending and reimbursement can starve a company that won a large award, and that the gap between the end of Phase I and the start of Phase II is its own hazard to bridge, so it arranges a line of credit before it needs one. It marks its technical data and software to preserve the data rights the program grants, the cheap administrative act that keeps the government from sharing the company’s core design with a competitor. Because it took the STTR route, it also settles with its university partner, early and in writing, how the two of them allocate the intellectual property the work produces, the negotiation the STTR structure requires rather than leaves to chance. It performs the unglamorous duties the after-the-award article catalogued, reporting on schedule, invoicing promptly, surviving the audits, and closing each award out cleanly, because the past performance it builds is what wins the next award and the integrity rules it obeys are what keep it eligible at all.
Between a finished prototype and a production contract lies the gap the Phase III article called the valley of death, and crossing it is the whole point of the climb. The company does not try to cross alone, since a small firm rarely carries a technology into a program of record by itself, so during Phase II it cultivates a transition partner, a prime contractor whose larger platform can carry the airframe and a program office that wants the capability, and it positions itself for the sole-source Phase III follow-on the program allows. Phase III carries no program funds of its own, so the company finances it from the production contract and from private capital, and the airframe that began as a printed prototype becomes a product the government buys and the commercial market adopts, the top of the staircase reached.
One campaign is not a company, which is the argument the strategy article made. While the first award climbs toward transition the company runs the parallel civilian track it reserved at the start, stacks a state matching fund on top of its federal dollars, and uses its de-risked prototype to raise a modest private round on better terms than it could have managed before the awards paid down its technical risk. It treats the awards as a means rather than an end, choosing transition over the mill, and if it later wants to grow beyond the United States it has the international analogs to consider, a British or Canadian challenge contract or a European grant offering the same staircase under other names to a company willing to establish itself abroad. The single campaign, in other words, is the first element of a portfolio the company manages for years.
The same campaign read in reverse is a catalog of the failures the series warned against. The company that treated Phase I as an end and wrote no transition into it cannot win a credible Phase II, the company that ignored its indirect rate and its cash gap holds an award it cannot survive, and the company that never marked its data hands its core design to a competitor for nothing. The company that neglects its reporting and its audits forfeits the standing the next award depends on, the company that chases a mismatched topic wins work that pulls its airframe off its own road map, and the company that settles into the mill, winning award after award without ever transitioning, builds a dependence rather than a business and is fragile the day the program changes. Each of these is a rung missed or a step taken in the wrong direction, and the worked campaign succeeds precisely by avoiding them in the order the series presented them.
Several matters remain outside this capstone as they were outside the series. The constructed company is an illustration and not a template, so its particular choices, the STTR route, the defense-first targeting, the dual-use positioning, are reasonable for it rather than correct for every firm, and a different technology would climb the same staircase by different steps. The specific figures, timelines, eligibility tests, and program rules remain the time-sensitive and agency-specific matters each earlier article flagged, to be read from the current solicitations rather than from this synthesis, and nothing here is legal, financial, accounting, or contracting advice for a particular campaign.
The programs supply non-dilutive capital in stages against demonstrated risk reduction, and the worked campaign is that one idea carried from a printed prototype to a production contract by a company that understood the climb. Each award bought the next rung, the eligibility and the proposal won the feasibility stage, the feasibility won the prototype, the prototype and a transition partner crossed the valley of death, and a portfolio built around the first campaign carried the company past any single award, while the failures the series warned against were exactly the rungs a careless company would have missed. That is the whole of the series in one ascent, and with the staircase walked once in full from feasibility to prototype to market, the SBIR and STTR practitioner playbook is complete.
The series has been a United States playbook, the programs, the agencies, the proposal, the money, and the strategy all read from American law and American solicitations. This article steps outside the United States to survey the analogs other advanced economies have built, because the problem the programs solve is not peculiarly American and the instruments other countries use to solve it illuminate the American ones by contrast. One idea organizes the survey, that every advanced economy faces the same market failure, the private underfunding of early-stage high-risk technology that the valley-of-death article described, and each has built some public instrument to fund the risk reduction that private capital will not, so the analogs are not copies of a single design but different answers to one shared question. The answers differ along a few structural axes, the instrument used, a procurement contract or a grant or a tax credit or an equity stake, whether the money is non-dilutive or dilutive, whether it is competed against a stated challenge or open to any idea, and whether it is staged in phases or paid in one shot, and the survey is organized around those axes rather than around a tour of every country. The usual caution applies with unusual force here, that foreign programs change their names and their structures often, the British and the Dutch programs both having been renamed recently, so the specifics below are current-as-of and each country’s own program authority is the only reliable source.
The reason every advanced economy intervenes is the same one the American program rests on. Early-stage high-risk technology is a market failure, since the firm that develops it cannot capture all the value it creates and the private investor cannot price a risk that has not yet been reduced, so the work that would benefit the economy goes unfunded by the market that should fund it. A government that wants the technology anyway, for its economy or its defense or its public services, must therefore supply the capital the market withholds, and the choice of how to supply it is a choice of industrial policy that each country makes differently. The American answer, the staged competitive award that the introductory article laid out, is one design among several, and seeing it beside the others shows which of its features are essential to the problem and which are particular to the United States.
The closest analogs are the programs built deliberately on the American model, the challenge-driven staged procurement of research from small firms. The United Kingdom ran its Small Business Research Initiative on exactly this pattern for years and renamed it Contracts for Innovation in 2024, a scheme in which Innovate UK and a public body pose a specific challenge and award fully funded research contracts in phases, the firm keeping its intellectual property, which is the American staircase under a British name. The Netherlands ran a program named SBIR outright, a three-phase competition of feasibility then development then a market launch in which the government is the first customer, recently rebranded the Innovation Impact Challenge but structurally the same. Australia built its Business Research and Innovation Initiative explicitly on the American program and on its own states’ versions, a feasibility grant followed by a larger proof-of-concept grant against challenges its agencies nominate, and Canada runs Innovative Solutions Canada, whose challenge stream awards a feasibility phase and then a prototype phase to small Canadian firms in a structure that closely mirrors the two American phases. Japan reformed its own long-standing SBIR in 2021 to coordinate it across ministries under the Cabinet Office and to focus it on research-intensive startups, splitting its work into a procurement-needs type and a social-issues type and implementing it through agencies including the New Energy and Industrial Technology Development Organization, so the phased model has been adopted across several continents. What unites these is the recognizable American shape, a competed challenge, a staged award, a small-firm recipient, and the government positioned as an eventual customer.
The largest non-American instruments are European and they are mostly grants rather than procurement. The European Union funds research and innovation through its Horizon Europe framework, the umbrella under which most Union science money flows, and within it the European Innovation Council runs the instrument closest to the American program for small firms, the Accelerator, which funds high-risk high-impact innovation by single companies. Alongside the Union’s own programs the intergovernmental Eureka network, through schemes such as Eurostars, coordinates national funding so that firms in different countries can collaborate on a single funded project, a cross-border dimension the American program does not have. National grant programs sit beneath the Union ones, Germany running its Central Innovation Programme for the Mittelstand, the standing federal grant for its small and mid-sized firms that reimburses part of their research costs and funds cooperation projects pairing firms with research institutions, the collaboration the next section takes up. The European model differs from the American one in that the grant, rather than the procurement contract, is the usual instrument, so the European government funds the work without positioning itself as the customer for the result, which changes the transition path the firm must find.
The series pairs SBIR with STTR, and the two differ in one feature, that the eligibility rules require an STTR award to be carried out in partnership with a research institution under a minimum division of the work, so the international question is not only whether the single-firm model has analogs but whether the company-and-institution model does. It does, and abroad that collaborative model is often the default rather than a separate track, since the European framework funds many of its projects as consortia that must join partners across organizations and the Eureka and Eurostars schemes are built around collaboration between firms and research performers in more than one country. Germany’s cooperation projects fund the same firm-and-institution pairing, and South Korea has recently moved to add a program of the STTR kind alongside its existing schemes, so the research-partnering idea the STTR embodies is widespread and in several places the ordinary way of funding rather than a distinct program. The American separation of a single-firm SBIR from a partnered STTR is therefore itself a design choice, since other countries fold the partnership into the main instrument rather than running it as a parallel one.
A wholly different instrument funds research through the tax system rather than through an award. Canada operates the Scientific Research and Experimental Development program, a tax credit that reimburses a portion of a firm’s qualifying research spending, and many countries run broadly similar research-relief schemes. The contrast with the American award is sharp, since a tax credit is an entitlement that any qualifying firm receives for work it chose and funded itself rather than a competed award for work the government wants done, so it is non-dilutive and broad-based but it neither directs the research toward a public need nor supplies the capital before the work rather than after it. A firm that can fund its own research and wants no direction prefers the credit, while a firm that needs the capital up front and is willing to address a stated need prefers the award, so the two instruments serve different firms and the United States and Canada both in fact run versions of each.
At the dilutive end of the spectrum the government takes a stake rather than giving a grant. Israel built much of its technology economy on public innovation funding through the body now called the Israel Innovation Authority, whose grants have historically carried royalty obligations that repay the state from the resulting revenue, a structure partway between a grant and an investment. The European Accelerator has moved the same direction with its blended finance, combining a non-dilutive grant with a direct equity investment through a public fund, so that the Union takes an ownership position in the companies it backs rather than only funding their work. South Korea runs a matching model of its own, its Tech Incubator Program for Startups, in which the government matches the capital a private operator invests in a startup so that public and private money enter together. This model treats the public money as patient capital that shares in the upside, the opposite pole from the American program, which the money article described as deliberately non-dilutive, taking no equity and leaving the firm whole, and the choice between them is a choice about whether the public should profit from the technologies it funds.
Defense ministries fund innovation through their own analogs, and the newest of note is multinational. The North Atlantic Treaty Organization established the Defence Innovation Accelerator for the North Atlantic to develop emerging and dual-use technologies across its member states, running accelerator sites and test centers and awarding funding to startups whose technologies serve both commercial and defense ends. It is an alliance-level analog rather than a national one, and its dual-use focus echoes the commercial-and-government posture the strategy article recommended, so the defense end of the international landscape is converging on the same dual-use logic the American defense agencies follow.
Laid side by side the analogs map onto a small set of design choices. The table below places the representative programs against those four choices, the instrument used, whether the money is dilutive, whether selection is challenge-driven or open, and whether the award is staged in phases or paid in one shot.
| Program | Instrument | Dilutive | Selection | Staging |
|---|---|---|---|---|
| United States SBIR and STTR | Procurement or grant | No | Challenge | Phased |
| United Kingdom Contracts for Innovation | Procurement | No | Challenge | Phased |
| Netherlands Innovation Impact Challenge | Procurement | No | Challenge | Phased |
| Australia Business Research and Innovation Initiative | Grant | No | Challenge | Phased |
| Canada Innovative Solutions Canada | Grant | No | Challenge | Phased |
| Japan SBIR | Procurement or grant | No | Challenge | Phased |
| European Union EIC Accelerator | Grant plus equity | Partly | Open | Single-shot |
| European Union Horizon and Eureka | Grant | No | Open | Varies |
| Germany Central Innovation Programme | Grant | No | Open | Single-shot |
| Canada Scientific Research and Experimental Development | Tax credit | No | Open | None |
| Israel Innovation Authority | Royalty-bearing grant | Royalty | Open | Varies |
| South Korea Tech Incubator Program | Matched investment | Partly | Open | Phased |
| NATO DIANA | Grant and accelerator | No | Challenge | Phased |
These choices are not mutually exclusive, since most countries run more than one instrument, the United States and Canada each operating both a competed award and a broader mechanism. Against these axes the American program is a non-dilutive, challenge-driven, phased procurement, a combination that several countries copied precisely because that combination directs public money at public needs while leaving the firm its ownership, and the portfolio strategy the previous article described applies to any of these instruments since a firm operating internationally can stack a European grant, a national procurement award, and a tax credit much as an American firm stacks its federal award and its state match.
The running example would find a path under most of these regimes. The small company building its unmanned aircraft could pursue a British or Dutch or Australian or Canadian challenge contract on a staircase much like the American one, apply to the European Accelerator for a grant and a blended equity investment, claim a research tax credit on the work it self-funds, or seek a royalty-bearing grant of the Israeli kind, and as a dual-use airframe it could compete for the alliance-level defense funding as readily as for a national program. The catch is that these programs fund national firms, so reaching most of them in practice would require the company to establish a local entity rather than to apply from abroad, and what travels freely is the model rather than any single company’s eligibility. The strategic logic would not change, since the company would still use whichever non-dilutive capital it could reach to reduce its technical risk before raising the dilutive private capital that scales it, and it would still choose the instruments that advance its destination rather than the ones that merely happen to be open. The vocabulary and the agencies would differ, but the staircase from feasibility to prototype to market, staged against demonstrated risk reduction, is recognizably the same climb in every country.
Several matters belong elsewhere or to specialists. The detailed eligibility rules, the application mechanics, and the funding figures of each foreign program are matters for that program’s own authority rather than for this survey, and they change frequently enough that any figure quoted here would soon mislead. A full accounting of every national program is beyond one article, so this survey covers the instruments and the representative examples rather than an exhaustive list, and it omits the programs of countries it does not name not because they lack analogs but because the axes are better shown by a few clear cases than by many. Nothing here is legal, financial, or tax advice for pursuing any particular foreign program, and the worked capstone that follows returns to the United States.
Every advanced economy faces the same market failure in early-stage high-risk technology, and each funds the risk reduction the market will not, so the American program is one answer among many to a shared question rather than a unique invention. The answers differ in their instrument, a procurement contract or a grant or a tax credit or an equity stake, in whether the money is non-dilutive or dilutive, challenge-driven or open, and phased or single-shot, and the American combination of a non-dilutive challenge-driven staged procurement was deliberate enough that the United Kingdom, the Netherlands, Australia, Canada, and Japan all built programs on its pattern. Seeing the analogs beside the American program shows that the staircase from feasibility to prototype to market is the durable idea and the rest is national detail, which is the frame the concluding capstone will apply to one company climbing that staircase in full.
The series so far has followed a single award from the decision to pursue it through winning it, financing it, and closing it out. This article steps back from the single award to the company that wins them, and asks the strategic question the earlier articles deferred, what the company is using the awards to become. One idea organizes the subject, that an award is a means and not an end, and that strategy is the discipline of using a portfolio of non-dilutive awards, the kind of capital that funds the work without taking ownership in exchange, staged against the risk reduction the whole series has tracked, to build a company that eventually no longer needs them. The central choice that follows from this frame is the one between transition and the mill, between treating the awards as a bridge to a self-sustaining business and treating them as the business itself, and almost every other strategic decision is downstream of it. The usual caution holds, that the programs, the matching funds, and the investor rules change by agency and by year, so the specifics below are current-as-of and the official program portal and the Small Business Administration that coordinates the programs are the authority.
The award funds the reduction of technical risk, and that is all it funds. The grant or contract pays a company to take a technology from one readiness level to a higher one, and the company that mistakes the funding for the goal has confused the scaffold for the building. The strategic frame, then, is to ask what the company is building toward, a product, a defense capability, a licensable technology, an acquisition, and to treat each award as a stage in that larger arc rather than as an end in itself. A company with a destination uses the awards to get there faster and with less of its own equity at stake, and a company without one simply collects them. This frame is what separates the two strategic postures the rest of the article develops.
The central strategic choice is what role the awards play in the company. A company pursuing transition uses the awards to cross the valley of death into a product, a program of record, or a paying market, so the awards taper as real revenue takes their place, which is the outcome the programs were designed to produce. Transition rarely happens alone, since a small company seldom carries a technology into a program of record or a production contract by itself, so the company pursuing it cultivates a transition partner, a prime contractor, a larger integrator, or an end customer in a program office, who can pull the technology across the gap, and that cultivation begins long before the work is ready rather than after it. The sole-source Phase III follow-on the valley-of-death article described is the reward such a partner makes possible, a right the company positions itself to receive rather than one that arrives on its own, so the partner is a strategic asset the company builds deliberately and early. A company running as a mill, by contrast, makes serial award-winning its business model, living from one Phase I and Phase II to the next without ever transitioning a technology, so the awards never taper because nothing replaces them. The mill is not illegal and it can sustain a company for years, but it is fragile, since it depends entirely on continued winning and on the program continuing to exist, and it builds a commercialization record that the agencies increasingly scrutinize through the performance benchmarks the series has mentioned. The strategic recommendation is therefore to treat every award as a step toward transition rather than as an end, because the company built to transition can always choose to keep winning awards while the company built only to win awards cannot easily learn to transition.
A company that wins more than one award holds a portfolio, and a portfolio can be managed well or badly. The same logic that governs any diversified holding applies, that concentration in a single agency, a single topic, or a single government customer is a risk, since a shift in one agency’s priorities or one program office’s budget can end a company built entirely on it. A company spreads its awards across agencies where its technology fits, sequences its phases so that a Phase II is performing while the next Phase I is competing, and runs parallel tracks where the technology serves more than one mission, so that no single loss is fatal. Building that pipeline is partly proactive rather than merely reactive, since a company that cultivates relationships with the program offices whose missions it serves and anticipates the topics they will publish, reading the solicitations with the discipline the topic article described, shapes its portfolio instead of waiting to see whatever happens to open. There is a countervailing discipline, that a small company has finite people and cannot pursue every opening without diluting the focus that makes its proposals win, so the portfolio is balanced rather than maximized, broad enough to be robust and narrow enough to be coherent. The portfolio is the unit of strategy, and the single award is only an element of it.
The federal awards are not the only non-dilutive capital available, and a strategic company stacks them. Many states run their own programs that supply matching funds to companies that win a federal award, multiplying the federal dollar with a state one that costs the company no equity, and the Small Business Administration and several agencies fund proposal-preparation and commercialization-assistance programs that lower the cost of competing and of transitioning. Layering these sources, the federal award, the state match, the assistance funds, extends the runway that each award buys without surrendering any ownership, which is the entire advantage of non-dilutive capital over the alternative. The strategic company therefore treats the federal award as the anchor of a stack rather than as the whole of its funding, and learns the state and assistance programs in the official directory and at the administering agency as deliberately as it learns the federal solicitations.
At some point a transition-minded company needs more capital than the awards supply, and that capital is usually private and dilutive. Venture capital, an angel investor, or a seed round brings money the awards cannot, but it brings it in exchange for ownership, the equity dilution that non-dilutive awards avoid, so the two kinds of capital are complements rather than substitutes. The strategic use of the awards is to reduce technical risk cheaply, raising the company’s value before it raises private money, so that the equity it gives up buys more, and a Phase II that produces a working prototype is a powerful argument to an investor precisely because the government paid for the risk the investor would otherwise have priced. There is a structural wrinkle the eligibility article named, that majority ownership by venture firms can disqualify a company at some agencies absent a specific exception, so a company timing a large raise against its award eligibility must check the ownership rules before it closes the round. The bridge across the valley of death is usually built from both kinds of capital, the awards de-risking the technology and the private money scaling the company, and the strategy is to sequence them so each buys the most it can.
A company that transitions only into a single government program is still concentrated, and the broadest strategy reaches a market beyond it. A dual-use technology, one that serves a commercial market as well as a government mission, gives the company a second leg to stand on, so that a commercialization into private revenue protects it from the shifts in any single agency’s budget. Some agencies are organized around exactly this outcome, the National Science Foundation running its seed fund for technologies headed to a commercial market, and the defense and mission agencies increasingly valuing a commercial base that lowers their own costs. The strategic company therefore asks, early, whether its technology has a market that is not the government, because a dual-use position is both a stronger commercialization story in the proposal and a more durable company after the award.
Strategy is as much about what a company declines as about what it pursues. Every proposal costs scarce engineering and writing time, so the opportunity cost of chasing a poorly fitting topic is the better proposal not written for a topic that fits, and a company that wins a mismatched award can find the work pulling its technology away from its own road map, funded but off course. The discipline is to pursue the awards that advance the destination the company already chose and to decline the ones that merely happen to be available, however tempting a fundable opening looks to a company short of cash. A won award that distorts the company is a strategic loss even as it is a financial gain, and recognizing that is the mark of a company using the programs rather than being used by them.
The running example shows the portfolio in miniature. The small company building its unmanned aircraft does not treat its first award as the business but as the first stage of a company headed toward a transitioned product, a dual-use airframe that serves both a defense mission and a commercial inspection or survey market. It wins a Phase I with one agency, sequences a Phase II behind it, and pursues a parallel topic with a second agency where the same airframe fits a different mission, while stacking a state match on top of the federal dollars to extend its runway. It uses the de-risked prototype from its Phase II to raise a modest private round on better terms than it could have before the award, checking the ownership rules first, and it treats the money from all of these sources as one coordinated stack aimed at crossing the valley of death rather than as a series of unrelated wins. The strategy is the same at every scale, to use the awards to build the company and not to let winning awards become the company.
Several matters belong elsewhere or to specialists. The detailed terms of a venture financing, the tax treatment of the various funding sources, and the specific rules of any one state’s matching program are matters for counsel, an accountant, and the state authority rather than for this overview. The mechanics of the single award, its proposal and its money and its compliance, were the subjects of the earlier articles, the international analogs to these programs are the subject of the next, and nothing here is legal, financial, or investment advice for a particular company. The state programs, the assistance funds, and the investor rules change and must be read from the current authorities.
The strategy of the programs is to treat the award as a means and not an end, to build a portfolio rather than collect single wins, to stack the non-dilutive capital and bridge to private capital when the company outgrows the awards, and above all to choose transition over the mill. A company that does this uses the programs to build a business that eventually no longer needs them, while a company that does not builds only a dependence on continued winning, fundable for a time and fragile throughout. The award reduces the risk, but the company chooses the destination, and the whole of strategy is keeping the destination in view while the awards pay the way toward it.
The series so far has carried a company from deciding to pursue the programs all the way to winning and financing an award. This article is about what happens next, the unglamorous work of holding the award, because winning is the start of an obligation rather than the end of an effort. One idea organizes the subject, that an award is a binding agreement with continuing duties, to perform the work, to report on it, to invoice for it, to survive the audits of it, and to stay in good standing while it runs, and a company that wins but neglects these forfeits the standing and the eligibility that the next award depends on, or worse, exposes itself to liability. The work after the award is therefore not bookkeeping but the second half of the campaign, the half where past performance is built or destroyed. The usual caution holds, that the reporting systems, the audit thresholds, and the certifications change by agency and by year, so the specifics below are current-as-of and the agreement’s own terms and the agency instructions are the authority.
The award is a contract or a grant, and either way it binds. A contract carries the obligations of federal acquisition, and a grant or cooperative agreement carries its own framework, but both impose deliverables, milestones, reporting, and oversight that the company must meet, so the proposal that was a promise becomes a set of duties the moment the award is signed. The company now executes what it proposed, against the schedule and the budget it proposed, and the freedom of the proposal gives way to the discipline of performance, where the technology must actually be built and the claims actually made good. Understanding the award as an agreement with duties, rather than as a prize, is the frame for everything that follows.
Performance runs against the work plan, and it runs through two relationships. The company delivers against its milestones and produces the technical deliverables it promised, the reports and the prototype, managing the inevitable changes through the agreement rather than around it, since a change to the scope or the schedule or the budget is a formal modification and not an informal understanding. It is also responsible for its subcontractors and its STTR research-institution partner, flowing down the requirements the agreement imposes and monitoring their work, since the company answers to the government for the whole team and not only for its own part. Two officials matter, and the distinction between them is worth learning, the technical point of contact or program manager who cares about the work, and the contracting officer or grants officer who holds the legal authority over the agreement, since only the latter can actually change what the company is obligated to do. A company that confuses a friendly word from a technical contact for an authorized change to the contract learns the difference the hard way, so it takes direction on the agreement only from the official empowered to give it. When the work runs long the relief is a no-cost extension, more time and no more money, requested through that same officer, but the darker end of performance is termination, since an agreement can be ended for default when the company fails to deliver, a serious mark that can carry repayment, or ended for convenience at the government’s own choice with a settlement of the costs already incurred. Performance, in other words, is enforced, and failing it has named consequences.
Reporting is a continuing condition of the award, not a courtesy. The company files technical progress reports through the award and a final report at its end, the record of what the work achieved, and at the agencies that require it a final deliverable that the next phase or the customer will read. Separately, and consequentially, it reports its commercialization, the revenue and the investment and the transition the technology has produced, and that commercialization report is what feeds the performance benchmarks the eligibility article described, so it is the bookkeeping that keeps the company eligible rather than an idle form. A late report can draw a withheld payment or a formal cure notice rather than only a vague loss of standing, and a company that lets its reporting lapse damages its standing and its benchmarks even when the technical work went well, so the reports are treated as deliverables in their own right.
The money does not arrive on its own. The company invoices for its work through the agency’s payment system, a cost-reimbursement award billing its actual costs at its provisional rates and a fixed-price or milestone award billing as the milestones are met, and the payment follows the invoice rather than the work, which is the lag the money article warned of. Invoicing promptly and correctly is therefore a cash discipline as much as an administrative one, since a late or rejected invoice extends the gap the company must finance, and the systems and formats differ by agency and must be learned. The company that treats invoicing as a low priority finds its own cash starved by its own delay.
The government checks what it paid for, and the company must be ready. A cost-reimbursement award is subject to audit, the Defense Contract Audit Agency at the defense agencies examining the incurred costs, and each year the company submits an incurred-cost proposal that settles its provisional rates against its actual ones, the true-up the money article described that returns or recovers the difference. A grant, such as those the National Institutes of Health administers through its grants system, carries its own oversight, the single audit that applies once a recipient’s federal spending crosses a threshold, and all of it rests on the records the company kept, so a clean audit trail, the timekeeping and the cost segregation maintained throughout, is what carries a company through an audit rather than a scramble at the end, and those records must be retained for a defined period after the award closes, since an audit can arrive well after the work has ended. The company that kept its books well has little to fear from an audit, and the one that did not discovers the cost of the shortcut.
The award comes with rules whose violation is not a clerical matter but a hazard. The company certifies its compliance at points through the award’s life, it obeys the regulatory-compliance obligations the agreement imposes, and it operates under the program-integrity rules that guard against fraud, waste, and abuse. A company performing for the defense and mission agencies and handling controlled information takes on a cybersecurity obligation on its own systems too, the controlled-unclassified-information safeguards and the maturity-model certification the department now requires, a continuing burden a small company easily underestimates. The stakes are real, since a false certification or a charge for work not done is exposure under the False Claims Act the data-rights article named, and the program has seen genuine fraud and genuine enforcement, so the obligations are not theoretical. The consequences of a serious failure run to repayment, to suspension, and to debarment from federal awards entirely, which ends a company built on them, so integrity is not a virtue the program hopes for but a condition it enforces.
An award ends with a closeout, and a clean one matters. The company files its final technical report and its final invoice, settles its final rates, accounts for and disposes of any equipment as the agreement requires, and makes its final reporting of inventions and data under the obligations the data-rights article described. A closeout left ragged, with reports unfiled or invoices unsettled or inventions undisclosed, follows the company into its next proposal as a mark against its past performance, while a clean one closes the loop and leaves the company ready for the next award. The closeout is the last act of the award and the first impression for the next.
Through all of it the company maintains the standing that lets it keep competing. It keeps its registrations current, renewing the central award registration each year as the eligibility article required, it maintains the compliant accounting system the money article described, and it meets the performance benchmarks that its commercialization reporting feeds. The performance itself becomes the past performance that the proposal article said a future proposal rests on, so a well-run award is an asset that wins the next one and a badly run award is a liability that loses it. Standing is not a separate task but the cumulative result of doing the rest of this article well.
The running example finishes its award properly. The small company building its unmanned aircraft files its progress reports on schedule, invoices through the agency system promptly to keep its cash moving, and keeps the timekeeping and cost records that will carry it through the incurred-cost audit and the rate settlement. It reports the commercialization it achieves so that its benchmarks stay healthy, it certifies honestly and does the work it was paid for, and it closes the award out cleanly, final report and final invoice and final invention disclosure all in order. It treats the second half of the campaign as seriously as the first, because the clean record it builds is what makes it eligible and credible for the next phase and the next award.
Several matters belong elsewhere or to specialists. The detailed mechanics of an audit, the formats of the specific reports, and the law of contract modifications are matters for an accountant, a contract administrator, and the agreement itself rather than for this overview. The strategy of building a portfolio of awards across time is the subject of the next article, the data rights and the money were the subjects of their own, and nothing here is legal, accounting, or compliance advice for a particular award. The specific reporting systems and thresholds change and must be read from the current agency instructions.
After the award the work is to perform what was promised, to report on it, to invoice for it, to survive the audits of it, and to stay in good standing while it runs, and to close it out cleanly at the end. None of this is glamorous, but all of it is binding, since the award is an agreement and not a prize, and the company that holds it well builds the past performance and the eligibility that win the next award while the company that holds it poorly forfeits them or invites the liability the integrity rules carry. Winning is the start of the obligation, and meeting it is the second half of the campaign that the rest of the series began.
The earlier articles wrote the technical proposal and described the rights the company keeps, and along the way they kept deferring the money to a later article. This is that article, and it is about three things that decide whether an award is worth having, the cost proposal that fits the work into the dollars, the indirect rate that decides how much of the award actually reaches the work, and the cash flow that determines whether a company that won an award can survive it. One idea organizes the subject, that the award is a fixed pot and the company must do three things with it, justify it in a compliant budget, account for it in a way the government will accept, and finance the gap between spending it and being paid, and a company that can do the engineering but not these three loses the value of the award or the company itself. This is the one article in the series with arithmetic, because the indirect rate is a number and it matters. The usual caution holds, that the cost principles, the fee limits, and the rate mechanics change and depend on the company’s structure, so the figures below are illustrative and current-as-of and the cost regulations and the agency instructions are the authority.
The cost volume is the budget that accompanies the technical proposal, and it has its own logic. It must account for every dollar the work will spend, it must total no more than the cap the solicitation set, and it must match the work plan, since a budget that funds more or fewer people than the technical volume describes signals that the two were written by different hands. Unlike a commercial bid, an SBIR or STTR cost proposal is usually evaluated for reasonableness rather than scored on lowest price, so the goal is a budget that is realistic and justified rather than artificially cheap, because a budget too low to do the work is as damaging as one too high to be credible. The agency states the budget format and the cost categories in its instructions, the National Institutes of Health in its grant guidance and the contract agencies in their own, so the company fills the prescribed form rather than inventing one. The structure of that budget rests on a distinction that governs all of government cost accounting, the line between direct and indirect costs.
Every dollar a company spends is either direct or indirect, and the difference is whether it can be tied to one project. The direct costs are the ones attributable to the specific award, the labor of the people working on it, the materials and equipment it consumes, the travel it requires, and the subcontractors and consultants it engages within the work-split limits the eligibility article set. Equipment bought with award funds can carry title rules of its own, so a company may find it has budgeted for equipment it does not ultimately own. The indirect costs are the ones the company incurs that cannot be tied to a single project, and they fall into pools, the fringe benefits that load every salary, the overhead of facilities and indirect labor, and the general and administrative cost of running the company, its executives, its accounting, its business development. The fringe is the employee-benefit burden on labor, and the overhead and the general and administrative pools cover everything the company needs to exist but that no single project pays for, and the whole apparatus of cost accounting exists to sort these dollars correctly.
The indirect costs reach the award through a rate, and the rate is the most important number in the budget. An indirect rate is a pool of indirect cost divided by a base over which it is spread,
\[\text{rate} = \frac{\text{indirect cost pool}}{\text{allocation base}},\]so an overhead rate might be the overhead pool divided by direct labor, and a general-and-administrative rate the general-and-administrative pool divided by total cost. The effect is that a dollar of direct labor arrives at the award loaded by the rates stacked on it,
\[\text{loaded cost} \approx \text{direct labor} \times (1 + f) \times (1 + o) \times (1 + g),\]with $f$, $o$, and $g$ the fringe, overhead, and general-and-administrative rates, an illustrative chain whose exact application depends on the company’s accounting structure. A company with no history proposes a provisional rate, which it must build by modeling its costs forward without the data an established firm would have, and later settles it against its actual costs, while an established firm carries rates negotiated with its cognizant agency, and either way the rate decides how much of a fixed award funds the work and how much covers the company, so a rate set too high prices the company out of competitiveness and one set too low starves it of the overhead it genuinely needs. The settling of a provisional rate against the actual one is itself a risk, since a rate that comes in higher than billed leaves the company to absorb an under-recovery and one that comes in lower obliges it to repay an over-recovery, and on a fixed-price award the company bears the whole of the variance, so the provisional rate is estimated with care rather than optimism.
On a contract the company may also earn a margin. A cost-reimbursement award, in the family of the cost-plus contract, pays the company its allowable costs plus a fee, a reasonable profit commonly capped near a single-digit percentage on these awards, so the company is not merely reimbursed but earns something, while a fixed-price award pays an agreed amount for the work and lets the company keep the difference if it delivers for less. Grants generally carry no fee, since they fund the work rather than buy a deliverable, so whether a company earns a margin depends on the agency and the instrument, the grant-versus-contract distinction the survey drew. The program also generally requires no cost share, unlike some federal research funding, so the company need not contribute matching money of its own beyond the Phase II enhancement the earlier article described. The two contract types also differ in risk and in what they demand of the accounting, since a cost-reimbursement award requires the government to trust the company’s books in a way a fixed-price award does not.
The government will not reimburse costs it cannot trust, so it requires an accounting system that meets its standards. The system must segregate direct from indirect costs, accumulate costs by project, record labor through a timekeeping discipline, and exclude the costs the rules forbid, and for a cost-reimbursement award it must be judged adequate before the award, a determination that at the defense agencies involves the Defense Contract Audit Agency. For a small startup this is real and early work, since a compliant system is not the spreadsheet a founder kept before, and setting it up, with proper timekeeping and cost segregation, is a prerequisite for the cost-reimbursement awards rather than an afterthought. The standard is proportionate, since the smallest firms are spared the full cost-accounting standards that govern large contractors, but even the smallest must keep books the government can audit.
Not every real cost may be charged to the government. The cost principles of the acquisition regulations sort costs into allowable and unallowable, and a company may not charge the unallowable ones to an award however genuinely it incurred them, the entertainment, the alcohol, the lobbying, and certain interest and penalties among them. The company must therefore know the rules and structure its accounting to exclude the unallowable costs from the pools it bills, since charging an unallowable cost is not a clerical error but a finding in an audit and a source of the liability the compliance article will treat. The discipline is to learn the cost principles early and build them into the accounting rather than discovering them when a cost is disallowed after the fact.
The award that bankrupts the company is the one whose cash was never planned. Payment lags the work, since the company spends on payroll and materials now and invoices and waits for reimbursement later, and between phases there is the gap the Phase II article described during which no award money flows at all, so a company can hold a two-million-dollar Phase II and still miss a payroll. The discipline is to manage the cash flow as deliberately as the technology, to invoice promptly and track the burn rate and the runway it leaves, and to arrange the outside financing, the matching funds and the investment the Phase II and Phase III articles described, that bridges the spans the award does not cover. Beyond that, a company can finance the receivable itself, with a line of credit or the factoring of its government invoices, which turns a slow-paying invoice into cash now at a cost. A company that plans the cash survives the award, and one that treats a won award as money in hand discovers that the money arrives slowly and the bills arrive on time.
The program offers a small help with the business side. A company may request a modest amount of technical and business assistance funding, outside the award’s own cap, to pay for the commercialization help, the market research, and the intellectual-property advice that a small technical team often lacks, the support the strategy article will place in its wider ecosystem. It is not large, but it is non-dilutive money for exactly the business capabilities the program wants the company to build, so a company takes it where it is offered.
The money is lost in a few recognizable ways. A budget that does not match the work plan undermines the technical proposal, an indirect rate set carelessly either prices the company out or starves it, and an accounting system that is not compliant blocks the cost-reimbursement award the company won. Charging unallowable costs invites a disallowance and worse, underestimating the indirect burden makes a budget that cannot actually do the work, and failing to plan the cash strands a solvent-on-paper company without the money to make payroll. Each of these is the same error in a different place, treating the money as simpler than the engineering when it is governed by rules just as exacting.
The running example puts numbers to it. The small company building its unmanned aircraft sets up a compliant accounting system with real timekeeping before it needs one, computes its fringe, overhead, and general-and-administrative rates, and budgets its Phase II so that the loaded cost of its small team plus its materials and its flight-test travel fits under the cap with a reasonable fee on top. It learns which of its costs are unallowable and keeps them out of the billed pools, and above all it plans the cash, lining up the financing to carry payroll across the gap before Phase II and the lag within it. It treats the budget and the books as seriously as the airframe, because an award it cannot account for or finance is an award it cannot keep.
Several matters belong to specialists or other articles. The detailed cost principles, the mechanics of a rate negotiation, and the conduct of an audit are matters for an accountant and for the regulations rather than for this overview, and the precise fee limits and rate structures change and must be read from the current rules. The reporting and the audits that follow an award are the subject of the compliance article, the financing strategy is developed in the strategy article, and tax is outside this scope entirely. Nothing here is accounting, financial, or tax advice.
The money behind an award is where the technical plan meets the dollars, and it turns on three things, a compliant cost proposal that fits the work into the cap, an indirect rate that decides how much of the award reaches the work, and a cash plan that carries the company from spending to reimbursement. The company that masters them earns a margin, keeps its overhead funded, and stays solvent through the lags and the gaps, while the company that neglects them can win an award and still fail, blocked by an inadequate system or stranded without the cash to use the money it won. The money is governed by rules as exacting as the engineering, and a company built on funded research learns them as a core discipline rather than leaving them to chance.
The Phase III article said that the sole-source authority is valuable only because the company owns what it built, and it deferred the ownership itself to this article. This is that article, and it is the crown jewel of the whole series, because the intellectual property a company retains is the asset that the non-dilutive funding was meant to build. One idea organizes the subject, that the government funds the work but the company keeps the inventions and the technical data, so the program is non-dilutive not only in equity but in intellectual property, and the retained ownership is what makes the company sellable, investable, and the only place a government customer can buy the result. The corollary is the warning that runs through the article, that these rights are kept only by guarding them, since they can be given away in a subcontract, lost by failing to mark a document, or eroded by mixing the funding that paid for the work, and a company that loses them has given away the thing the funding was supposed to create. The usual caution holds with force, that the protection periods and the clauses change, so the specifics below are current-as-of and the current policy directive and the acquisition regulations are the authority.
Intellectual property in these programs divides into two bodies of law that are easy to conflate and important to separate. The first is patent rights, which concern who owns an invention made under the award, governed by the Bayh-Dole Act and its framework for federally funded research. The second is data rights, which concern what the government may do with the technical data and the software the company delivers, governed by the data-rights clauses of the acquisition regulations and by the program’s own special category. A company can own a patent on its invention and still mishandle the data rights in the deliverables, or guard its data and neglect a patent, so the two are managed separately even though they protect the same underlying technology. Under STTR a third party enters the picture, since the research institution the program requires is a co-creator, so the company and the institution must agree in writing, before the award, on how they allocate the rights between them, the partner relationship the eligibility article introduced.
For inventions, the law is generous to the company. Under the Bayh-Dole framework a small business that makes an invention in the course of a federally funded award may elect to retain title to it, so the company owns its patents rather than the government owning them, which is the foundation of building a business on funded research. The government keeps a nonexclusive, paid-up license to practice the invention for its own purposes, and it retains march-in rights, a rarely used power to require licensing in narrow circumstances, but neither of these takes ownership from the company. The practical consequence is that the company should treat its inventions as its own from the start, since the election runs on a clock, with the Bayh-Dole framework setting deadlines to disclose the invention, to elect title, and to file the patent, and missing one can let the government take the title, so the dates are tracked as carefully as the science. A company that licenses an invention exclusively also takes on a preference to manufacture the resulting product substantially in the United States, a condition that travels with the retained title.
For technical data and software, the program provides a special and unusually strong protection. The government receives a license to use the SBIR and STTR data and software it pays for, but during a protection period it may not release that data outside the government or use it to have the work performed by someone else, which is the protection that keeps a competitor or a prime from taking the company’s technical core. That protection period was historically four years from the completion of the project that generated the data, a term the policy directive has since lengthened, so the current period must be read from the directive rather than assumed. After the period the government’s rights broaden toward government-purpose or unlimited use, so the protection is strong but not permanent, and a company plans for the day the data becomes more freely usable by building its position on patents, trade secrets, and continued innovation rather than on the data rights alone. The rights also depend on when the technology was created, since the company’s background data, the technology it brought to the work rather than created under it, keeps its own and usually stronger protection, so the company identifies and asserts that background rather than letting it be swept into the foreground the award produced.
The single most consequential practical point in this article is that data rights are preserved by marking. The protected data must carry the SBIR or STTR data-rights legend, the notice that asserts the restriction, and data delivered without the proper marking can be treated as carrying unlimited rights, which means the government may do with it whatever it likes, including hand it to a competitor. The act of marking is therefore not a formality but the very thing that keeps the rights, so a company marks every deliverable that contains its protected data, consistently and correctly, and trains its people to do so, the same care the proposal article urged for the proprietary markings on the proposal itself. A company that builds a brilliant technology and delivers it unmarked has given the technology away as surely as if it had signed it over, and the loss is usually discovered too late to undo. The marking must also match the prescribed legend, since a nonconforming or unauthorized marking can be stripped, and the government may challenge a restrictive assertion, which the company must be able to justify from the funding records that show what it paid for.
The acquisition regulations sort data and software into categories that decide what the government may do with each. At one end are unlimited rights, where the government may use and disclose the data without restriction, the category that unmarked data falls into and that data developed entirely at government expense generally carries. In the middle are government-purpose rights, where the government may use the data and share it with other government parties and contractors for government purposes but not for commercial ones, and limited or restricted rights, which protect data and software developed at private expense. The SBIR data rights are a distinct and protected category created by the program, stronger than government-purpose rights during the protection period, and the defense data-rights clauses elaborate all of this in the contracts where the rights are most often contested. A company’s aim is to keep its core technology in the protected category and out of the unlimited one.
The balance the program strikes is worth stating plainly. The government, having paid for the work, keeps a license to use what it paid for for its own purposes, so it is not locked out of the technology it funded, and that is fair. The company keeps ownership, the patents and the copyright and the trade secrets, and above all the commercial rights, so it can sell the technology to other customers and build a business on it, which is the incentive the program depends on. Neither side gets everything, the government cannot freely commercialize the company’s technology and the company cannot deny the government the use it paid for, and understanding this balance keeps a company from either over-claiming and souring the relationship or under-claiming and losing the asset.
The rights are lost in a handful of recognizable ways, and each is avoidable. A subcontract or a teaming agreement with a prime contractor can quietly assign the company’s data rights to the prime, so the company reads the intellectual property terms of any agreement before signing and does not give away what the program let it keep. A failure to mark a deliverable forfeits the protection, the expiry of the protection period broadens the government’s rights, and delivering more data than the contract requires exposes data that need never have left the company. Mixing the funding that paid for the work blurs the rights, since data developed at private expense carries stronger protection than data developed at government expense, so a company keeps clear records of what was developed with which money. Software that incorporates open-source or other third-party code carries those licenses’ obligations into the deliverable and limits what the company can assert over it, so the company tracks what it has built on. Each of these is a way of giving away the crown jewel by inattention, and the defense against all of them is to treat the rights as the core asset they are.
The data rights are not merely defensive, since they are what make the company worth something. They are the reason the Phase III sole-source authority means anything, because a customer that cannot get the technology from anyone else must come to the company that owns it, so the rights and the authority together give the company a defensible position with a government buyer. They are an asset in a fundraising or an acquisition, since an investor or a buyer is purchasing the ownership of a technology, and a company that has kept its rights has something to sell while one that gave them away has far less. The non-dilutive funding built a technology, and the retained rights are what turn that technology into property, which is the whole point of keeping them.
The running example shows the stakes concretely. The small company’s autopilot software and its airframe design data are its crown jewels, the proprietary core that the whole business rests on, and it developed them with a mixture of SBIR money and its own, so it keeps records of which is which and marks every delivered file with the data-rights legend. When a prime contractor offers to integrate the aircraft and asks in the teaming agreement for government-purpose rights to the autopilot, the company recognizes the request for what it is and negotiates to keep its protected rights, since those rights are exactly what make its Phase III sole-source position defensible. It treats the data rights as the most valuable thing it owns, because for a company built on funded research they are.
Several matters belong elsewhere or to specialists. The detailed text of the acquisition data-rights clauses and the precise current protection period are read from the regulations and the policy directive rather than from this article, since they change and they govern. The prosecution of a patent, the law of trade secrets, and the negotiation of a specific intellectual-property clause are matters for counsel, and this article is an engineering-minded map rather than legal advice. Export control, which can restrict who may receive the data regardless of who owns it, was treated in the regulatory article and the eligibility article, and the money and the compliance that surround the award are the subjects of their own articles.
Data rights and intellectual property are the crown jewel of an SBIR or STTR company, because the program funds the work but lets the company keep the inventions and the technical data, so the retained ownership is the asset the funding was meant to create. The company owns its patents under Bayh-Dole, it holds a strong but time-limited protection on its technical data and software that is preserved only by marking, and it guards those rights against the subcontracts, the omissions, and the funding mixtures that would give them away. The rights are what make the Phase III sole-source position defensible and the company worth buying, so a company built on funded research treats them as the most valuable thing it owns, which they are.
The Phase II article ended with a prototype and a commercialization plan, the two halves of a result that is ready to become a product but is not one yet. This article is about the last and hardest step, Phase III, the commercialization that the whole staircase was built to reach, and the chasm that lies in front of it. One idea organizes the stage, that Phase III is a destination rather than an award, since it carries no program money at all, so the staged non-dilutive capital that funded feasibility and development simply stops, and the company must cross from a funded prototype to a self-sustaining product or a fielded government program on other money. That crossing is the valley of death, the gap where a technology that works has not yet become a business that sells, and where many funded results quietly die, and the SBIR-specific tools that help cross it, the sole-source authority and the data rights, are the subject of this article. The usual caution holds, that the authorities and the mechanisms change by agency and by year, so the specifics below are current-as-of and the live policy directive is the authority.
Phase III is the commercialization of the work the earlier phases matured, and its defining feature is the absence of program funding. It carries no SBIR or STTR set-aside money, no dollar limit, and no time limit, because it is funded instead by other sources, the procurement, operations, or research-and-development appropriations of a government customer, a prime contractor’s subcontract, or the private capital and revenue of a market, so it is less an award the company wins than a status the company reaches. On the technology readiness level scale the orientation article introduced, Phase III is the climb from a validated prototype toward a fielded and operational system, the high rungs at which the technology is no longer a project but a product. Phase III is not strictly sequential either, since it can begin while Phase II is still running and a company can hold several Phase III awards at once, there being no limit on their number or their value. The work must derive from or extend the SBIR and STTR effort that came before, which is what links it to the program and gives it the one tool the program provides at this stage.
The single most valuable thing the program grants at Phase III is a procurement authority. A federal agency may award Phase III work to the company that did the SBIR or STTR research on a sole-source basis, without recompeting it, as a direct extension of that prior work, an exception to the competition that federal buying normally requires. The authority is broad, since it is not limited to the agency that funded the original work, so any federal customer can buy the result directly from the company, and it does not expire, so it persists as the technology matures. This is the lever that lets a government customer adopt the technology without the company having to win an open competition against larger firms, and it is the reason the data-rights position the next article describes matters so much, since the company that owns its data and holds the sole-source authority is the one a customer must come to. The authority is permission to buy and not a commitment to, since it does nothing to create the requirement or the budget, so a company can hold the sole-source right and still have no sale until a funded customer decides to use it, which is the most common misreading of Phase III.
Between the Phase II prototype and a sustained Phase III the ground falls away. The prototype that ended Phase II is not a product, the government customer’s budget and acquisition cycle move slowly and on their own schedule, the program money has stopped, and private capital is often wary of a technology that looks dependent on a single government buyer or that is years from revenue, so the company can hold a working result and still have no money and no customer ready to buy. This gap is the valley of death, and it is where the largest share of funded technologies are lost, not because they do not work but because the company runs out of runway before a paying customer or a funded program arrives. Crossing it is the real test of the whole campaign, and the rest of this article is about the two ways across, the government transition and the market.
For a technology aimed at a government mission, crossing means transition into a program. The company needs a program of record or an operational user that will adopt the technology, a transition partner such as a prime contractor or a program office that will carry it, and a place in the customer’s budget, since a capability with no funded line and no requirement behind it has nowhere to land. The crossing is therefore as much about the customer’s acquisition process as about the technology, and it favors a requirement that pulls the technology in over a technology that pushes itself at an uninterested customer. Often the path runs through a prime contractor that integrates the small company’s technology into a larger system and subcontracts the work back to it, which is a route across the valley and also a risk, since a prime can capture the value or let the technology stall, so the company manages the relationship and guards its position. The tools that help are the ones the earlier articles named, the Phase II enhancement and the commercialization readiness program that bridge the gap with more funding, and arrangements such as a cooperative research and development agreement with a laboratory or a partnership with a prime, all resting on the technology transfer from the small company into the larger system, alongside the state programs, the commercialization assistance, and the accelerators that the money and strategy articles describe.
For a technology aimed at a commercial market, crossing means a product and customers. The company must turn the prototype into a manufacturable product, find and keep paying customers, and raise the capital that the program no longer provides, which is often where venture capital or revenue takes over from the non-dilutive money that bridged the company to this point. That non-dilutive funding, and the government validation it represents, is itself a credential that helps the company raise the private capital, the handoff from the program’s money to private money that the strategy article develops. Some markets add a regulatory crossing of their own, since a health technology must clear the Food and Drug Administration before it can be sold, and that path is its own long valley with its own cost. A dual-use technology can cross both ways at once, a government transition and a commercial market reinforcing each other, which is the strongest position and the reason the agencies favored the dual-use story all along, since commercialization into two markets is more robust than dependence on one.
Phase III is not an afterthought to the program but its entire purpose. The agencies fund Phase I and Phase II in order to produce Phase III outcomes, the fielded capabilities and the commercial products that justify the program, so the commercialization a company reaches here is what the performance benchmarks the eligibility article described actually measure, and a company that never crosses the valley is the one those benchmarks eventually bar. The pattern of winning award after award without ever reaching Phase III, the mill the strategy article will name, is precisely the failure to do the thing the program exists for. For the company, Phase III is where the years of non-dilutive funding either turn into a business or do not, so it is the stage against which all the earlier ones should have been planned.
The valley claims companies in recognizable ways. A company that built its technology with no customer in view, the technology push with no requirement pull, reaches Phase III with nothing to transition into, and a company with no transition partner or no funded budget line finds the government door closed however good the prototype. A company that planned no cash for the gap runs out of runway while the slow acquisition or fundraising grinds on, a company that gave away its data rights finds it has no defensible position from which to sell, and a company that treated Phase II as the finish line discovers that the finish line was always here. Each of these is the same error, mistaking the funded development of a technology for the unfunded building of a business.
The running example reaches the edge of the valley. The small company that built its unmanned aircraft prototype under Phase II now seeks a Phase III, a sole-source contract under which a service program office adopts the aircraft and funds its move toward a fielded capability, with a prime-contractor partner carrying it into a program of record. At the same time it pursues the dual-use commercial market, selling a version of the aircraft to civil customers and raising the private capital that the program no longer supplies, so that it does not depend on the single government buyer. It planned for the gap from the start, holding the cash and the relationships to survive the slow crossing, and it guards the data rights that keep the sole-source door its own.
Several matters belong to other articles. The data rights that make the sole-source position defensible are the subject of the next article, and the cost and cash-flow mechanics of surviving the gap are the subject of the money article. The strategy of building a portfolio of awards and avoiding the mill is the subject of the strategy article, and the detailed acquisition law, the budgeting process, and the specific transaction authorities a government customer may use are named here rather than worked. Nothing in this article is legal, financial, or investment advice.
Phase III is the destination the whole staircase pointed at, the commercialization that turns a matured technology into a fielded capability or a sold product, and it carries no program money, so the company crosses the valley of death on other funds. The program leaves it two tools for the crossing, the sole-source authority that lets a government customer buy the result directly and the data rights that keep that position the company’s own, and the crossing itself is made by a government transition into a funded program, a market entry to paying customers, or, best of all, both at once. A funded research result becomes a business at Phase III or it does not, and the companies that cross are the ones that planned for the valley from the first proposal rather than discovering it at the prototype’s edge.
The previous article wrote a Phase I proposal whose purpose was to retire an idea’s feasibility risk. This article takes up what happens when that bet pays off, the Phase II award that builds on a proven concept, and the document that now moves to the center of the case, the commercialization plan. One idea organizes the stage, that Phase II is the step where the program stops asking whether the idea can work and starts asking whether it can become a product, so the money grows by an order of magnitude, the work turns from feasibility to development, and the commercialization plan stops being a closing paragraph and becomes a scored deliverable in its own right. Phase II is where a funded research result either turns into a business or remains a research result, and the difference is largely the seriousness of the commercialization plan. The usual caution holds, that the dollar figures, the durations, and the enhancement mechanisms change by agency and by year, so the specifics below are current-as-of and the live solicitation and the policy directive are the authority.
Phase II is the development award, and its character follows from that. Where Phase I bought a feasibility study, Phase II buys a prototype, a working article that develops the proven concept into something close to a product, so the award is roughly an order of magnitude larger than Phase I and runs about two years rather than months. On the technology readiness level scale that the orientation article introduced, Phase II carries the technology through the middle rungs, from a demonstrated principle toward a validated prototype, the maturity at which a government user or a commercial customer can begin to take it seriously. The agency is now spending real money, so it expects real development against a real plan, and the Phase II proposal is judged on both the technical plan to build the prototype and the business plan to sell it. The award is not always one block, since some Phase II awards are built with a base and option periods or milestone gates across the two years, and the prototype and the data it produces are the company’s crown jewels, whose protection the data-rights article treats.
Phase II is not open to everyone, since it is normally the second step of a sequence. A company competes for Phase II on the strength of its completed or nearly completed Phase I, so the gate is the feasibility the Phase I work actually demonstrated, and the proposal builds directly on that result rather than starting fresh. Between the end of Phase I and the start of Phase II there is usually a gap, a stretch of months while the Phase II proposal is written and evaluated during which no award funds flow, and bridging that gap without losing the team is a real problem the money article takes up. Some agencies soften the sequence with a Direct to Phase II path, which lets a company that established feasibility by other means, its own funds or earlier work, skip Phase I and compete directly, an option that the agency survey noted exists at some agencies and not others. And selection is not yet award, since at a contract agency a Phase II selection is followed by a negotiation of terms and rates before work begins, a step between winning and starting that a company should expect.
The Phase II proposal resembles the Phase I proposal in shape but shifts in emphasis. It still has a technical volume that lays out the development work, the tasks and the milestones and the prototype to be delivered, and a cost volume for the larger budget, and it still presents the team and the facilities, though the work-split limit the eligibility article set binds harder now, since Phase II brings in manufacturing partners and subcontractors and yet the small business must still perform at least half the work. What changes is the weight on commercialization, since the criterion that was one of three in Phase I now carries much more of the score, and at many agencies a formal commercialization plan is a required document rather than a section. The proposal is written to the criteria as before, but the center of gravity has moved, so a Phase II that is technically strong and commercially vague is the characteristic way to lose at this stage, the development-phase counterpart to the Phase I overpromise.
The commercialization plan is the heart of Phase II, and it is a business plan for the technology. It states the market and sizes it through a credible market analysis, it names the customer and states the value proposition, the reason that customer would buy, and it confronts the competition honestly rather than claiming to have none. It describes the business model and the go-to-market strategy that carries the prototype to revenue, the financing the company will raise beyond the award, the team’s capacity to commercialize and not only to invent, and the milestones that mark the path from a Phase II prototype to a product with paying customers and product-market fit. A reviewer reads this plan to decide whether the company has thought past the research to the business, and a plan that is a page of optimism rather than a reasoned case concedes the criterion that now matters most. What makes the plan believable is not the market study alone but documented commitment, a letter of intent or a memorandum of understanding from a real customer or transition partner, since a reviewer trusts a signed commitment over an assumed market. The commercialization a company eventually achieves is also reported, and the reported result feeds the performance benchmarks the eligibility article described, so a Phase II commercialization plan is not only a proposal document but the start of the record that keeps the company eligible for future awards, a record the compliance article treats.
The commercialization plan comes in two flavors, set by the agency culture the survey described. At a mission agency the goal is transition, the carrying of the result into a government user, so the plan is a transition plan that names the program that will adopt the technology, the end user who wants it, and the acquisition path by which it becomes a fielded capability, often resting on the technology transfer from the project to a program of record. At a science agency the goal is market commercialization, the carrying of the result into a product sold commercially, so the plan is a market-entry plan that names the customers and the channel and the financing that reach them. A dual-use technology can pursue both, a government transition and a commercial market at once, which is the strongest position of all, and the plan an applicant writes is shaped first by which of these the agency it chose is looking for.
The program provides mechanisms to extend a Phase II toward commercialization, and they reward a company that has found real demand. A Phase II enhancement lets matching funds from a third party, an investor, a prime contractor, or a government customer, trigger additional program money, so that outside validation of the technology is met with more support to mature it. Some agencies offer a sequential or second Phase II, and several run a commercialization readiness program that funds the late-stage work of preparing a result for transition or market, the commercialization push that the gap between a prototype and a product requires. These mechanisms are the bridge across the gap the next article calls the valley of death, and a company plans for them from the start rather than discovering them at the end of Phase II.
Phase II sharpens the cash-flow problem that runs through the whole program. The gap between phases is one strain, and within Phase II the timing of payments against a cost-reimbursement or milestone schedule is another, so a company can hold a two-million-dollar award and still struggle to make payroll if it has not planned the cash. The commercialization mechanisms and the outside financing the plan describes are partly an answer to this, since matching funds and investment fill the gaps the award does not, and the company that has lined up that financing in advance is the one that survives the development phase rather than stalling in it. The money article treats the mechanics, but the strategic point belongs here, that a Phase II is a two-year business to be financed and not only a research project to be performed.
The characteristic Phase II failures are about the business as much as the technology. A proposal that is more research than development, with no clear product at the end, reads as a company that wants to keep studying rather than build, and a commercialization plan that is generic or optimistic forfeits the criterion that now dominates. A plan with no named customer or transition partner reads as demand assumed rather than demonstrated, an overrun of the technical risk that Phase I was supposed to retire suggests the feasibility was never really established, and a company that treats commercialization as an afterthought has misread what Phase II is for. Each of these is the same mistake in different dress, building the technology without building the case that someone will buy it.
The running example reaches its development phase. The small company that proved in Phase I that its unmanned aircraft could meet a capability now wins a Phase II to build the prototype, a flying article developed against milestones over two years toward the readiness level a service or a customer would trust. Its commercialization plan is a transition plan naming the program office that would adopt the aircraft and the acquisition path to a fielded system, and a market plan for the dual-use commercial application, and it has lined up a prime-contractor or investor relationship whose matching funds could trigger a Phase II enhancement. It plans the cash across the two years and the gap that preceded them, treating the award as the financing of a young business rather than a grant to spend.
Several matters belong to other articles. Phase III, the commercialization step that carries no program funds and that the whole commercialization plan points toward, is the subject of the next article. The cost volume, the indirect rates, and the cash-flow mechanics are the subject of the money article, and the data rights the company holds in its Phase II results are the subject of the data-rights article. The detailed craft of writing a business plan or a market analysis is a discipline of its own that this article points to rather than teaches, and nothing here is legal, financial, or investment advice.
Phase II is the step where the program stops asking whether an idea can work and starts asking whether it can become a product, so it funds the development of a prototype and demands a commercialization plan that is a real business plan for the technology. The plan names the market or the government user, the value proposition, the competition, and the path to revenue or transition, and it is the scored deliverable that now matters most, while the enhancement mechanisms and the outside financing it describes bridge toward the commercialization step beyond. A funded research result becomes a business at this stage or it does not, and the difference is the seriousness with which the company treats the commercialization plan, which points directly at Phase III, the subject of the next article.
The solicitation article ended with the company holding the right opportunity and understanding the rules under which it will be judged. This article is about the thing it now has to write, the Phase I proposal, which is the craft at the center of the whole series. One idea governs the writing, that a Phase I proposal is an argument that the company can retire the feasibility risk of an idea, written to the evaluation criteria the solicitation published, by a team a reviewer will believe, with a commercial promise the agency can see. It is not a description of a finished product and it is not a free essay, it is a response to a request scored against a rubric, and the proposal that wins is the one that answers the rubric clearly rather than the one with the cleverest idea buried in it. The usual caution holds, that the page limits, the required sections, and the forms change by agency and by year, so the structure below is the common shape and the live solicitation and the agency’s proposal-preparation instructions are the authority.
Phase I is a feasibility study, and remembering that is the first discipline of writing one. The agency is not buying a product or even a prototype, it is buying the answer to a question, whether the idea can work at all, so the proposal promises a proof of concept rather than a finished thing, and it carries the technology from the lowest rungs of the technology readiness level scale toward a demonstrated principle, a rung of the staircase the orientation article described. The single most common way to lose is to forget this and promise too much, a Phase I that reads as though it will deliver the whole system, because a reviewer reads that as a plan that does not understand the program. The proposal that fits states a crisp feasibility question and a believable plan to answer it in the months and dollars Phase I allows, and no more.
A proposal is not one document but a set, and the set has a predictable shape. There is a technical volume, the proposal proper, which makes the case and is where this article spends its attention, and there is a cost volume, the budget, which a later article treats in full. The two volumes must tell the same story, since a work plan and a budget that disagree, more tasks than dollars or more people than hours, signal carelessness to a reviewer, so they are written to match. There is company and commercialization material, the past performance and the plan to sell or transition the result, and at a contract agency there are the representations a contract requires. Each agency states the exact contents and the page limit in its proposal-preparation instructions, the Department of Defense in its innovation portal, the National Institutes of Health in its application guide, the National Science Foundation in its proposal instructions, and all of them indexed from the program portal, so the writer builds the proposal to the specific instructions rather than to a remembered template. A project summary sits ahead of the volume, read first and, on award, published as a public abstract, so it is written with care and without proprietary content, while the proprietary technical data the proposal does contain is marked to protect it, the regime the data-rights article treats. Some material, the letters of support and certain attachments, falls outside the page count, so knowing what is inside the limit and what is outside it is part of building the set.
The technical volume follows a standard arc whatever the agency. It opens by establishing the significance of the problem, the need the work serves, so the reviewer knows why it matters. It then states the innovation and the technical approach, what is new and how the work will be done, and the technical objectives, the specific questions Phase I will answer. It lays out the work plan, the tasks and their sequence, and it situates the work against the related work already done so the reviewer sees what is genuinely new. It presents the team and the facilities that will do the work, and it closes on the commercialization potential, the path by which a feasibility result becomes a product. Each of these sections exists because a reviewer is looking for what it contains, so the arc is not a formality but the order of the questions the reviewer asks.
Behind the sections are the criteria, and the criteria are usually three. The first is the technical merit, whether the innovation is genuinely new and the approach is sound and likely to establish feasibility. The second is the qualifications, whether this team, with these people and these facilities, can actually do the work. The third is the commercialization potential, whether a feasibility result has a credible path to a product and a market or a government user. The solicitation gives these criteria and often their weights, and the discipline the previous article urged is to write to them in proportion, so the heavily weighted criterion gets the most care, the criterion the company is weak on is shored up, and no criterion is left unaddressed, since an unanswered criterion is points simply forfeited.
The heart of the technical volume is the innovation, and it must be made unmistakable. The proposal states plainly what is new, how it goes beyond the current state of the art, and what technical risk stands between the idea and feasibility, because the risk is the thing Phase I exists to retire, and a proposal with no risk to retire has no reason to be funded. It states the feasibility question as a question with a yes-or-no answer the Phase I work will reach, rather than as a vague intention to investigate. And it does all this in plain technical writing, without the jargon that hides a thin idea, because the reviewer may be a generalist and because clarity reads as competence while obscurity reads as confusion.
The work plan turns the innovation into a believable project. It breaks the effort into tasks, a work breakdown a reviewer can follow, each task tied to a technical objective and to a deliverable, with milestones that mark progress and a clear statement of what finishing Phase I will have shown. It addresses the technical risk honestly through a risk management plan, naming what could go wrong and how the plan copes, since a proposal that pretends nothing can go wrong reads as naive while one that names and manages its risks reads as expert. And it fits the plan inside the months and the dollars Phase I allows, because a work plan that overflows the period or the budget is not a plan but a wish, and the reviewer sizes the ambition against the envelope the solicitation set. The strongest work plans are written with the next step already in view, since Phase I is the gate to Phase II, so the plan defines the quantitative go-or-no-go feasibility criteria whose success would justify a fundable Phase II, the path the next article takes up, and a reviewer scoring the proposal wants to see that the feasibility result leads somewhere.
A good idea with no one credible to execute it does not win. The proposal presents the principal investigator, who must meet the employment rule the eligibility article gave, and the key personnel, with the experience that makes the team believable for this particular work, and it presents the facilities and equipment the work needs. It may bring in subcontractors and consultants, within the work-split limits the eligibility article set, and under STTR it presents the research-institution partner and the division of labor with it. Past performance, the company’s record of having done related work, is part of this case, and for a first-time company that lacks it the burden shifts onto the strength of the individuals and the clarity of the plan.
Even in Phase I, the proposal must say who will buy the result and why. The commercialization potential is a scored criterion, not an afterthought, so the proposal sketches the path from a feasibility result to a product, the market or the government user that wants it, and the commercialization model that gets it there. A dual-use technology that serves both a government mission and a commercial market is the stronger story, and a letter of support from a prospective customer, the kind the solicitation article said to line up early, is the strongest evidence that the demand is real rather than assumed. A company that treats the commercialization section as a formality concedes a third of its score, and the reviewer notices the difference between a real plan and a paragraph of optimism.
The proposal is read by a person under time pressure, and writing for that person is its own skill. At a science agency the reviewer is part of a peer-review panel reading many proposals, and at a directed agency a government technical evaluator is scoring against the topic, so in both cases the reader is busy and is looking for specific things. The proposal earns its score by making those things easy to find, leading with the point rather than building to it, answering each criterion in plain sight, and using the structure and the white space that let a tired reader skim and still get the argument. A proposal is in this sense a sales document under technical scrutiny, and the sale is lost as easily by burying the answer as by not having it. The most useful check before submission is an internal one, since a colleague who did not write the proposal and reads it cold against the published criteria, the red-team review proposal shops rely on, catches the gaps and the unclear passages the author has gone blind to, and the time to find them is before the agency does.
What happens after submission is part of the craft too. The proposal is scored against the criteria, and most proposals are not selected, since the programs are competitive and a solicitation funds only a fraction of what it receives, so a rejection is the normal case and not a verdict on the company. A losing applicant can usually request a debrief, the reviewers’ feedback, and that feedback is the most valuable thing a loss produces, since it tells the company exactly where the proposal fell short. A revised proposal, addressing the feedback and resubmitted in a later cycle, is a standard path to an award, so the company that treats the first attempt as a draft to be improved rather than a verdict to be mourned is the one that eventually wins.
Beyond the compliance failures the solicitation article warned of, a handful of substantive mistakes sink proposals. A vague innovation that never says clearly what is new, a missing feasibility question that leaves the reviewer unsure what Phase I would prove, and the overpromise that treats Phase I as though it will deliver a product are the classic technical failures. A weak or formulaic commercialization story forfeits a scored criterion, a work plan with no risk and no mitigation reads as naive, and a proposal that ignores the published criteria answers a question the reviewer was not asking. Each of these is avoidable by the writer who remembers that the proposal is an argument scored against a rubric and writes accordingly.
The running example shows a Phase I in miniature. The small company holding a technology like the unmanned aircraft of the engineering series, having found a fitting Department of Defense topic, writes a Phase I that states a sharp feasibility question, whether its airframe or its autonomy can meet the capability the topic named, and a believable plan to answer it in six months. It names the principal investigator and the small team, it addresses the technical risk of the one hard thing the idea depends on, and it tells the dual-use story of a capability that serves both the military need and a commercial market. It writes the whole of it to the three criteria, and if it loses, it requests the debrief and resubmits a sharper version next cycle.
Several matters belong to other articles. The cost volume and the budget that justify the dollars are the subject of the money article, and the data rights the proposal asserts over what it will produce are the subject of the data-rights article. Phase II, the development award that a successful Phase I leads to, is the subject of the next article, and the agency-specific forms and portals change too often to document here. The decision to hire a professional proposal writer is a business judgment beyond this overview, and nothing here is legal advice on a particular proposal’s terms.
A Phase I proposal is an argument that the company can retire an idea’s feasibility risk, written to the evaluation criteria, by a team a reviewer will believe, with a commercial promise the agency can see. It states a crisp feasibility question rather than promising a product, it makes the innovation unmistakable and the work plan believable within the envelope, it takes the team and the commercialization story as seriously as the technical merit, and it is written in plain sight for a busy reviewer scoring against a rubric. Most proposals lose, the good applicant learns from the debrief and resubmits, and with a feasibility result in hand the company is ready for Phase II, which is the subject of the next article.
The eligibility article cleared the two gates, so the company is now allowed to compete and registered to submit. What it does not yet have is a target, and this article is about finding one and reading the document that governs it. The work divides into two tasks that the rest of the series depends on. The first is finding the opportunity, the topic or the funding announcement that matches what the company can do, which means something different at a directed agency than at an open one. The second is reading the solicitation, the document that states what the agency wants and the rules under which it will be judged, with enough care that the proposal does not lose for a reason that has nothing to do with its merit. The organizing idea is that the topic is where the company’s risk-reduction proposal meets the agency’s need, and the solicitation is the contract for the competition, so a misread topic wastes a good idea and a misread rule throws away a good proposal. The usual caution holds, that the topics and the solicitations change every cycle, so the specifics below are current-as-of and the live solicitation is the only authority.
Finding an opportunity means different things at the two kinds of agency the survey described. At a directed agency the company looks for a topic, a specific need the agency has published and will fund a solution to, so the search is for the topic whose problem the company’s technology already answers, and the proposal is a response to a request the agency wrote. At an open agency the company looks instead for fit, since the agency funds the applicant’s own idea within a broad area, so the search is for the area and the funding opportunity whose scope its innovation falls inside, and the proposal argues the merit of an idea the company chose. The distinction decides where the company spends its looking, hunting a matching topic in a long list at one kind of agency and assessing fit against a broad scope at the other.
The opportunities are published, and an applicant learns where. The cross-agency starting point is the official program portal, which lists the open solicitations across all the agencies and lets a company search them, and from there the trail leads to each agency’s own system. The directed agencies post their topics in their portals, the topics of the Department of Defense in the Defense innovation portal and those of NASA and the Department of Energy in theirs, each on the agency’s own calendar. The open agencies post funding announcements, the National Institutes of Health in its grant guide and through the federal grants portal that civilian agencies share, and the National Science Foundation through its solicitation and project pitch. The calendar the survey flagged is the practical burden here, since the windows open and close on each agency’s own schedule, so a company tracking several agencies tracks several calendars and watches for the openings.
A solicitation is a long document with a predictable structure, and reading all of it is the price of competing. It states the agency and the program and the phase, the eligibility it requires, and the instructions for preparing and submitting a proposal. It lists the topics or the scope, it gives the evaluation criteria by which the proposal will be judged, and it sets the administrative rules, the page limit, the format, the cost ceiling, the deadline with its date and its time and its time zone, and the system through which the proposal must be submitted. It names the points of contact and the period during which questions may be asked, and at a contract agency it carries the further apparatus of federal procurement that a grant does not. The temptation is to read only the topic and skip the rest, and it is a trap, because the administrative rules are where a good proposal is most easily lost. The solicitation is also not fixed once released, since it is amended, deadlines are extended, topics are clarified, and the answers published in the question period become binding, so a company tracks the amendments and reads the answers rather than trusting the version it first downloaded.
A topic statement repays close reading, because it says more than it seems to. It gives an objective and a description of the need, it states the phases the agency expects and the deliverables it wants from each, and it usually signals the maturity it is looking for in terms of a target technology readiness level, the rung of the ladder the orientation article described that the work should reach. It often states or implies a dual-use expectation, that the result should serve a commercial market as well as the agency’s mission, which the proposal must then address, and the time to begin lining up a letter of support from a prospective customer is when the topic is chosen rather than when the proposal is due, a point the proposal and commercialization articles take up. And its language and its keywords reveal the technical community that wrote it, so reading a topic closely tells the company not only what is wanted but who wants it and in what terms to speak to them. The company that answers the topic the agency actually wrote, rather than the one it wishes had been written, is the one whose proposal fits.
When and whether the company may talk to the agency is itself part of the rules, and it differs sharply between the two cultures. A directed agency typically opens a topic in a pre-release period before the solicitation formally opens, and during that window the company may contact the topic author directly to ask whether its approach fits, which is the single most valuable conversation available and the reason to watch for pre-release rather than wait for the opening. Once the solicitation opens, that direct contact closes, and questions move to an anonymous written channel visible to all applicants, the blackout that keeps the competition fair. The open agencies work the opposite way, since their peer-review culture expects an applicant to talk to a program officer, to test whether an idea fits the institute or the area and is worth a full proposal, a conversation that is allowed and encouraged throughout rather than shut off when the window opens. Knowing which regime applies, and using the contact it allows, is a free advantage many applicants leave on the table.
Two honest questions decide whether a found opportunity is worth pursuing. The first is fit, whether the company’s technology genuinely answers the topic or falls within the area, and the discipline here is to resist forcing a fit, since a proposal stretched to reach a topic it does not truly match reads as exactly that and loses. The second is whether the opportunity is winnable, because a topic can be written narrowly enough that an incumbent or a particular company is the evident intended winner, and a newcomer who recognizes the signs spends its effort elsewhere. The best evidence for both questions is the record of past awards, which the program portal exposes as a searchable database, so a company reads who has won similar topics, which agencies fund its area, and whether a topic is recompeted or has a standing incumbent before it commits. Choosing a topic also commits the team, since the company must have or hire the people the work needs, and under STTR it must line up its research-institution partner before the proposal rather than after, so the choice is a commitment of people as well as of technology. A company has only so many good proposals in it per cycle, so choosing the opportunities where it has a real technical edge and a real chance, rather than answering everything that brushes its field, is the strategic core of this stage.
The cheapest loss is the one a proposal suffers before anyone reads its merit. A solicitation states administrative requirements, the page limit, the typeface and the margins, the required sections and their order, the cost ceiling, and the deadline to the minute in a stated time zone, and a proposal that violates any of them can be rejected without review. The deadline in particular is unforgiving, since a submission a minute late into a system that closes on the clock is simply not received, and the systems are known to slow under the load of the final hours. The cost ceiling and the period of performance are not only limits to obey but the envelope the work plan must fit, so reading them scopes the effort the proposal can promise, a point the money article takes up. The practical discipline is to build a compliance checklist from the solicitation and to submit well before the deadline, treating the administrative rules with the same seriousness as the technical content, because a brilliant proposal that runs a page long or arrives a minute late earns the same score as a blank one.
A solicitation says how it will judge, and that is an instruction. The evaluation criteria, the technical merit and innovation, the qualifications of the team, and the commercialization potential, are listed with their relative weights, and they are the rubric a reviewer scores against, so the proposal the next article treats is written to them point by point rather than as a free essay. A criterion that carries more weight earns more of the proposal’s space and care, a criterion the company is weak on is the one to shore up before submitting, and a criterion left unaddressed is points simply forfeited. Reading the criteria before writing, and writing to them, is the difference between a proposal that answers the question asked and one that answers a question the reviewer was not scoring.
The open agencies deserve their own note, since their process front-loads a step. The National Science Foundation requires a short project pitch before it will accept a full proposal, a brief description it either invites or declines, which spares an applicant the labor of a full proposal that does not fit and gives a fast read on whether the idea is in scope. The National Institutes of Health asks the applicant to find the right institute and the right funding opportunity among many, to match its aims to that institute’s mission, and to talk to a program officer before committing, since a health innovation that fits one institute may be invisible to another. At both, the early, low-cost step of testing fit through a pitch or a conversation is the analog of the directed agency’s pre-release contact, and skipping it wastes effort on proposals that were never going to fit.
The running example shows the stage in miniature. A small company holding a technology like the unmanned aircraft of the engineering series searches the program portal, finds a Department of Defense topic calling for a small unmanned capability whose need its airframe answers, and reads that topic closely for the readiness level and the deliverables the service expects, while also considering an open National Science Foundation pitch for the same core technology framed as a broad innovation. It tailors each to the agency it is sent to, the defense topic as a solution to a named military need and the foundation pitch as an open innovation with a path to market, and it does not send the same words to both. The small company’s constraint is effort, so it picks the one or two opportunities where its edge is real and its fit is honest, and it lets the rest pass.
Several things are left to other articles. The writing of the proposal itself, the craft and the review and the resubmission, is the subject of the next article, and the cost proposal and the budget are the subject of a later one. The data rights that a solicitation invokes are treated in their own article, and the agency-by-agency mechanics of each submission portal change too often to document here. The specific current topics and open solicitations are read from the live systems rather than from this article, since they turn over every cycle, and nothing here is legal advice on a particular solicitation’s terms.
Finding a topic and reading a solicitation are the stage where a registered, eligible company turns its capability toward a particular opportunity. The company looks for a matching topic at a directed agency and for fit at an open one, it reads the whole solicitation rather than only the topic, it uses the contact the rules allow before the window closes, it judges fit and winnability honestly, and it reads for compliance because the cheapest loss is a formatting error. With the right opportunity chosen and its rules understood, the company is finally ready to write, which is the subject of the next article.