We scan new podcasts and send you the top 5 insights daily.
Facing resistance from CIOs protecting their domains, AWS's early government strategy targeted 'mission owners' like NASA JPL. These groups had immediate, critical problems that cloud could solve, creating powerful internal advocates and bypassing traditional IT gatekeepers.
Winning the CIA contract signaled to skeptical commercial companies that cloud was secure enough for their own use. This served as a massive credibility boost that transcended the public sector, effectively unlocking the broader enterprise market.
Faced with closed doors in Washington, Palantir adopted a bottom-up strategy. They provided their software directly to operators in the field, who were free from the government's monopsony power. By creating "facts on the ground" that demonstrated value, they forced adoption from the central command.
To get enterprise customers to trust your AI features, leverage a platform they already have a security posture with, like AWS Bedrock. This 'meet them where they are' strategy bypasses significant security and data privacy hurdles by piggybacking on their existing trust in a major provider, accelerating adoption.
The difficulty of enterprise procurement is a feature, not a bug. A champion will only expend the immense internal effort to push a deal through if your solution directly unblocks a critical, unavoidable project on their to-do list. Your vision alone is not enough to motivate them.
Selling to government is counterintuitive for impatient founders. Government can't fail or be disrupted in the same way. The winning strategy is to first solve an urgent, existing problem within their constraints, build trust, and then gradually introduce broader innovation.
At AWS, where revenue is tied to usage, the ideal salesperson wasn't a traditional deal-closer. They needed a consultative mindset, focusing on the customer's mission to drive adoption and delight, as their compensation depended directly on successful implementation.
A common B2G sales mistake is focusing solely on the end-user. In government, users rarely have decision-making authority. The key is to understand the distinct needs of the user, the budget holder, and the ultimate decision-maker, and align your pitch with the decision-maker's high-level mission.
AWS leadership insisted on getting public sector customers to publicly share success stories, shifting focus from AWS's technology to the customer's mission. This strategy of letting customers become the primary storytellers was crucial for building trust and legitimacy in a skeptical market.
In siloed government environments, pushing for change fails. The effective strategy is to involve agency leaders directly in the process. By presenting data, establishing a common goal (serving the citizen), and giving them a voice in what gets built, they transition from roadblocks to champions.
Instead of traditional sales, AWS hosted informal events for government tech leaders, demonstrating cloud's power with free credits. This hands-on, low-pressure education was crucial for a new category where buyers didn't even have a mechanism to purchase the service.