Defense Business Brief: End-of-fiscal-year advice for founders; Navy drone boats; Powerus to go public

The Pentagon's chief financial officer advises technology founders seeking to do business with the military to focus on providing solutions for the program offices and portfolio acquisition executives, recognizing that these entities control success. Success requires fitting into existing cycles, which might involve subcontracting or shaping future requirements, rather than merely offering a good idea. The CFO stresses the necessity of hiring individuals familiar with government contracting and finding program managers who prioritize change to facilitate opportunities across the department. Furthermore, companies must demonstrate manufacturing capability to scale their technology, advising founders to either manufacture goods themselves or hire personnel experienced in manufacturing to prove scalability if a purchase occurs.
The US Navy is acquiring 30 medium-sized unmanned surface vessels from three companies: Galliano Marine Services, HII, and Saronic. Six of seven companies successfully completed sea trials for the Navy’s Medium Unmanned Surface Vessel (MUSV) program. Those companies that did not secure production contracts but passed trials will transfer to the marketplace as part of phase two requirements. The MUSV program is undergoing changes, including a lawsuit. Phase two is expected to involve broader requirements allowing other services, such as the Army, to share needs, potentially impacting the Indo-Pacific region. Dronemaker Powerus is set to go public upon finalizing its merger with Aureus Greenway Holdings.

* The Pentagon's comptroller advises founders to make technology that troops like and find out who can buy it for them, and hire someone familiar with government business.
* Jules Hurst stated that program offices and portfolio acquisition executives (PAEs) have the power to make a company successful.
* Founders must fit into the existing program cycle, potentially by subcontracting or shaping requirements for future capabilities.
* Companies must demonstrate the ability to manufacture things to scale technology.
* Founders should hire people experienced in manufacturing if they do not manufacture things themselves to show the government the necessary talent for scaling a product.
* The Navy will buy 30 medium-sized unmanned surface vessels from Galliano Marine Services, HII, and Saronic.
* Six out of seven companies successfully completed sea trials for the Navy’s MUSV program.
* Three companies that did not get production contracts but had successful trials (Leidos, PacMar Technologies, Sea Machines) will transfer to the marketplace for phase two requirements.
* Phase two of the MUSV program is expected to start testing evaluations around November 16 and continue over five years.
* Dronemaker Powerus is expected to go public on October 1 following a merger with Aureus Greenway Holdings, forming Powerus Corporation.

The narrative presented by the financial advice centers on navigating systemic inertia within the defense acquisition cycle. The core tension lies between the agile innovation of startups and the slow, highly structured bureaucratic processes of the Department of Defense. Hurst’s advice shifts the focus from pure technological novelty to strategic alignment: success depends not just on the quality of the product but on understanding and maneuvering the decision-makers—the program offices and PAEs. This suggests that market viability is secondary to institutional fit; a disruptive solution must be framed within an existing budgetary or programmatic context, rather than existing outside it.
The emphasis on manufacturing capability as a prerequisite for government acceptance highlights a critical gap between theoretical development and practical execution within the defense industrial base. The push to hire manufacturing expertise over pure software talent reflects a systemic demand: the government requires demonstrable capacity to meet timelines and cost schedules, suggesting that "paper deep" innovation is insufficient against established budgetary realities. This pattern points toward an environment where success is determined by integration into existing operational workflows rather than independent market disruption.
The context of the MUSV program suggests that even large-scale defense modernization efforts are characterized by iterative change and contingency planning, demonstrated by the shift from initial contracts to phase two evaluations involving inter-service collaboration. This mirrors the advice to "shape requirements for a future capability." The implication is that opportunity resides in bridging organizational divides—aligning with specific program managers rather than fighting the overall structure—to unlock opportunities across the entire defense ecosystem. The pattern suggests that influence flows through relational capital (who you know and what problems you solve for them) as much as demonstrable technical capacity.
Bridge Questions: If organizations prioritize embedding within existing cycles, how can they simultaneously maintain a high degree of disruptive, outside-the-cycle innovation? What structural changes are necessary to decouple program execution from bureaucratic legacy constraints without sacrificing accountability? Does focusing on personality shopping for decision-makers risk creating silos that hinder cross-agency capability building?