The discovery calls framework we install for every client for public sector and GovTech

This edition is written for public-sector business development leads and GovTech commercial teams. In public sector and GovTech, public-sector buying is procurement-led and rewards credentialed, patient engagement, so the way you install discovery calls has to reflect that reality from day one.

We have installed discovery calls inside more than fifty companies. This is the framework we reach for every time. Discovery calls is the 30 minutes that decide whether a deal exists at all, and the framework exists to keep that definition honest under real conditions.

Part one, diagnosis. Before you touch the model, name the constraint: finance, demand, access, or conversion. Discovery calls applied to the wrong constraint is theatre.

Part two, target. Narrow to one industry, one role, one trigger. Every extra dimension halves conversion.

The binding constraint we see in public sector and GovTech is almost always procurement cycles and credentials, not product-market fit. Discovery calls is only useful in this vertical when it is pointed at that constraint — not at a generic growth number borrowed from another category.

Part three, offer. What is the buyer's next step, and what makes it obvious? The offer, not the copy, is what carries.

Part four, engine. Tools, sequences, data. Buy the minimum you can operate; every extra tool is a future dependency.

Part five, operating rhythm. Monday plan, Friday review, weekly discovery-to-opportunity conversion. Nothing about the model is left to memory.

Parts six and seven, learning and allocation. What did we learn last week; where does next week's dollar go. Once those two loops are live, discovery calls compounds and the framework stops being visible.

Concretely for public sector and GovTech: one framework agreement unlocks years of downstream demand. That is the reason it is worth installing discovery calls properly rather than half-heartedly across three vendors.