Discovery calls for agencies: how to productise the offering for public sector and GovTech in the Middle East
The service design, pricing, and delivery model for running discovery calls as a productised offering inside a services firm. Written for public-sector business development leads and GovTech commercial teams in the Middle East.
This edition of the Growth Broker playbook is written for public-sector business development leads and GovTech commercial teams operating in the Middle East. In this market, Middle Eastern buyers reward in-person credibility, sovereign fit, and patient sequencing, so the way you install discovery calls has to be shaped to that reality from day one.
Discovery calls is one of the highest-margin offerings an agency can add in 2026. It is the 30 minutes that decide whether a deal exists at all, and clients will pay a premium for the discipline they cannot install themselves.
Productise around outcome, not activity. Sell discovery-to-opportunity conversion moving to a defined level in a defined window, not a monthly retainer of vague ops.
Delivery pod: one strategist, one operator, one editor. Fewer people than that risks quality; more than that dilutes margin.
Inside public sector and GovTech, the binding constraint is almost always procurement cycles and credentials, not product-market fit, and in the Middle East it is compounded by the fact that senior-relationship access, not product is what actually gates growth. Discovery calls is only useful here when it is pointed at both constraints at once.
Onboarding takes two weeks: diagnosis, list build, trigger definition, kill criteria. Do not ship anything live before the diagnosis is signed off.
Pricing: outcome-linked base plus a monthly ops fee. The base rewards results; the ops fee funds the delivery pod.
Client failure mode: reading a script instead of running a diagnosis. Write it into the engagement letter as a shared risk, not something you absorb quietly.
The agencies making the most from discovery calls are the ones with the tightest playbook. Documented, versioned, and improved every quarter.
Concretely for public sector and GovTech in the Middle East: one framework agreement unlocks years of downstream demand, and one sovereign or family-office win in the Middle East justifies a full year of program spend. That is the reason it is worth installing discovery calls deliberately for this market rather than importing a playbook designed for somewhere else.
Frequently asked questions
Sales · public sector · Middle East — answered
- Does discovery calls work for public sector and GovTech in the Middle East?
- Yes — provided it is pointed at procurement cycles and credentials, not product-market fit and adapted to the fact that in the Middle East, Middle Eastern buyers reward in-person credibility, sovereign fit, and patient sequencing. One framework agreement unlocks years of downstream demand.
- How should agencies price discovery calls?
- Outcome-linked base plus a monthly ops fee. Avoid pure retainer.
- What is the minimum delivery pod?
- Strategist, operator, editor. Three roles, not necessarily three headcount at small scale.
- How long is agency onboarding for discovery calls?
- Two weeks: diagnosis, list, trigger, kill criteria.
- What client behaviour breaks the engagement?
- Reading a script instead of running a diagnosis — bake shared risk into the contract.
- What is the Middle East-specific pitfall when running discovery calls for public sector?
- Importing a playbook that was built for another market. In the Middle East, Middle Eastern buyers reward in-person credibility, sovereign fit, and patient sequencing — the install has to reflect that.
Growth Broker editorial
Filed under sales · public sector · middle east