Expanding a $200K POC Into a $1M Enterprise Agreement

The Challenge

A defense contractor had approved a $200K proof of concept for our endpoint security platform covering one division of 800 users. The POC was technically successful, but the customer showed no urgency to expand. Their procurement team was content to renew the POC at the same scope, treating it as the final deployment rather than a stepping stone.

The Approach

During the POC I had been quietly building relationships with leaders in the three other divisions that were not included in the pilot. Each division had slightly different security requirements, and I had been documenting their needs in preparation for an expansion conversation.

I requested a business review meeting with the CISO and VP of Operations to present POC results. In the meeting I showed metrics from the pilot — 99.7% uptime, zero authentication-related security incidents, and a 45% reduction in IT support tickets. Then I presented a side-by-side comparison showing the risk posture of the pilot division versus the unprotected divisions, quantifying the exposure gap.

The Objections

The CFO pushed back on the $1M price tag, asking why they could not just extend the POC to one more division. I showed that the enterprise agreement pricing was 35% cheaper per user than extending the POC pricing, and that the multi-year commitment qualified for additional volume discounts. The math clearly favored the enterprise agreement.

The Result

The $200K POC expanded to a $1M enterprise agreement covering all four divisions and 5,000 users. The three-year commitment provided our company with revenue predictability and the customer with cost certainty. The expansion was signed within 60 days of the POC completion.

Key Takeaway

A POC is not the finish line — it is the starting gate. Building relationships across multiple divisions during a single-division pilot creates internal demand that makes expansion a natural next step. Always design POCs with expansion in mind.