Prepared tackled the slow GovTech market by providing its initial product for free. This strategy bypassed cumbersome procurement, built a large user base, and established the credibility needed to overcome the authority of entrenched, larger competitors.

Before committing resources to a proof-of-concept (POC), build a preliminary ROI case. If the potential return isn't substantial enough for the customer to reallocate budget or personnel, the deal is unlikely to close. This step prevents wasting both your and your customer's time on unwinnable evaluations.

Startups can bypass the lengthy NRC process for initial reactor tests by using Department of Energy (DOE) and Department of Defense (DOD) pathways. The DOE, with national labs, can regulate test reactors for faster innovation. Crucially, the Army can now license its own reactors, creating a direct regulatory and commercial path to a key market.

Stop trying to convince executives to adopt your priorities. Instead, identify their existing strategic initiatives—often with internal code names—and frame your solution as an accelerator for what they're already sold on doing. This dramatically reduces friction and speeds up deals.

Enterprise leaders aren't motivated by solving small, specific problems. Founders succeed by "vision casting"—selling a future state or opportunity that gives the buyer a competitive edge ("alpha"). This excites them enough to champion a deal internally.

A major software vendor pitched a $50M deal directly to the DOE Chief of Staff, assuming top-level access was a shortcut. The pitch failed because they hadn't validated the need or built internal champions. High-level meetings are useless without foundational sales work proving a real problem exists for the organization.

Carl Coe, Chief of Staff for the U.S. Secretary of Energy, found that foundational principles from his aggressive tech sales career—urgency, persistence, and qualification—are surprisingly effective for navigating and reforming the Department of Energy. These core tenets of high-growth business translate directly to pushing massive government initiatives forward.

Instead of large, multi-year software rollouts, organizations should break down business objectives (e.g., shifting revenue to digital) into functional needs. This enables a modular, agile approach where technology solves specific problems for individual teams, delivering benefits in weeks, not years.

In government, digital services are often viewed as IT projects delivered by contractors. A CPO's primary challenge is instilling a culture of product thinking: focusing on customer value, business outcomes, user research, and KPIs, often starting from a point of zero.