Discovery calls for Series A companies: the 90-day install for cybersecurity in the Middle East
The exact 90-day plan for standing up discovery calls at Series A — the point where the founder can no longer be every function. Written for CISOs, VPs of security, and heads of GRC in the Middle East.
This edition of the Growth Broker playbook is written for CISOs, VPs of security, and heads of GRC 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.
Series A is the moment discovery calls stops being optional. The founder has to step out of some of the work, the plan requires a defensible growth number, and every quarter compounds toward the next raise.
Day 1 to 30: diagnosis and instrumentation. Name the constraint, write the ICP, wire discovery-to-opportunity conversion into the board pack.
Day 31 to 60: first live cycle at 20% of planned volume. Founder still in every review. Kill criteria written and enforced.
Inside cybersecurity, the binding constraint is almost always credibility and trust, not tooling, 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.
Day 61 to 90: ramp to full volume, hire the first dedicated operator, and hand off ops. Founder retains strategy and the weekly review.
By day 90 the metric is legible and the trajectory is defensible. This is what turns a Series A story into a Series B round.
Trap most Series A companies fall into: reading a script instead of running a diagnosis. It usually shows up around day 45 when the founder tries to hire ahead of the model.
The Series A version of discovery calls looks small compared to what you will build at Series B. That is the point — it is a foundation, not a monument.
Concretely for cybersecurity in the Middle East: the difference between a real security opportunity and a wasted quarter is one credible sentence, 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 · cybersec · Middle East — answered
- Does discovery calls work for cybersecurity in the Middle East?
- Yes — provided it is pointed at credibility and trust, not tooling and adapted to the fact that in the Middle East, Middle Eastern buyers reward in-person credibility, sovereign fit, and patient sequencing. The difference between a real security opportunity and a wasted quarter is one credible sentence.
- Should we start discovery calls before Series A?
- Yes if the founder has time; the Series A version is the same model at higher spend.
- How much of the round should fund discovery calls?
- Meaningful — often 20–30% of the growth line — but only after diagnosis.
- When do we hire the first discovery calls operator?
- Around day 60, once the model has run one full cycle with the founder.
- What Series A trap should we avoid?
- Reading a script instead of running a diagnosis — usually a premature senior hire.
- What is the Middle East-specific pitfall when running discovery calls for cybersec?
- 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 · cybersec · middle east