Picture the moment every founder works months to earn: a real discovery call with the ideal military office. The calendar invite lands, the right people show up — and then the company does the one thing almost guaranteed to stall it. They launch straight into their standard commercial pitch.
Here’s the trap. Most of the government doesn’t arrive at that call knowing what it wants. It has to be shown what’s missing. A polished product demo answers a question the room hasn’t asked yet — so it lands as noise, not insight.
During my years in the USAF, I sat through hundreds of these calls from the government’s side of the table. The companies that earned a second meeting did something different: they changed the dynamic from pitch to listening to our actual problem sets — the thrash we faced with the way we currently did business, the processes we knew were antiquated and costing us big time. Let me walk you through exactly how that works.
Why the pitch reflex backfires
When you lead with your solution, you’re implicitly asking the customer to map it onto a problem they may not have fully articulated — in real time, in front of their boss. That’s work, and it’s risky for them. So the safe answer becomes “interesting, send us a capability brief,” which is government for no.
The reframe is simple but it changes everything: understanding the problem is 90% of the issue, and your solution is the last 10%. People don’t know what they want until they can see it in action — or until you give them a use case that makes it real. So spend the call on their world, not your roadmap.
The 4-Step Pitch
Here’s the method I’d hand any team walking into a first conversation with a government office. Four steps, in order, problem first and ask last.
1. Find the problems worth solving
Before the call, do the homework. What process is this organization stuck with today, and why does it hurt? Get specific and quantify it where you can: what does that broken process cost them every single time they execute it — in hours, in dollars, in mission risk, in people? You’re not looking for any problem. You’re looking for the one that’s painful enough to be worth a budget and a champion.
2. Verify the intended solution is desired
Now test it with them, out loud. My favorite question to open this up: “If you had a magic wand and could fix this tomorrow, what would that actually look like?” Their answer tells you whether the fix you have in mind is the fix they want — and it invites them to describe the solution in their own words, which is far more powerful than you describing it in yours. You’re confirming demand before you’ve spent a single slide on features.
3. Project the ROI for the end users
Once the problem and the desired fix are on the table, make the value concrete for the people who’ll actually use it. How much time comes back? What risk disappears? What can the unit do now that it couldn’t before? This is where past performance earns its weight — a use case where your solution solved a verified military problem can move a wavering office from polite interest into genuinely exploring a relationship. Proof beats promise every time.
4. The ask
Only now do you ask — and the ask is small, specific, and forward. Not “will you buy this,” but the next concrete step: a follow-on technical session, a pilot scoped to the problem you just validated, an introduction to the contracting shop. By this point you’ve earned it, because the conversation has been about them the whole way.
You’re not there to convince them your product is good. You’re there to understand their problem so completely that your solution becomes the obvious conclusion — one they help you reach.
From discovery call to qualified opportunity
Run these four steps with the right stakeholders in the room and a discovery call stops being a one-off meeting. It becomes a qualified opportunity — a problem you’ve verified, a fix they’ve described, an ROI they can defend internally, and a next step you both agreed to. That’s the difference between “send us a brief” and “let’s get the right people on the next call.”
If you want help finding the problems worth solving inside your target agencies — or building the use cases that make your ROI undeniable — let’s map out your next steps together.
