Technology CXO Case Studies — Anonymised Mandates, Outcomes and Lessons

Each case study generates operational lessons that compound into the next mandate. The pre-IPO SaaS CTO case reinforced the recruitment-pull-as-most-decisive-factor discipline; the listed platform CRO case shaped our B2B2C-ACV-expansion vignette design; the GCC MD case confirmed that parent-integration politics is the binding constraint at MD level; and the deep-tech AI CEO case codified our research-credibility vignette as a non-negotiable pre-qualification filter. These lessons are the compound intellectual property of running 140+ technology CXO mandates in the last 12 quarters.

No — not without explicit client consent, and not in any form that identifies the organisation. All case studies we publish are anonymised with fictionalised descriptors, while the underlying operational mechanics (timelines, shortlist size, vignette performance, compensation structure) are drawn from genuine Gladwin retained mandates. For prospective clients who wish to triangulate deeper, we provide reference conversations with former clients who have consented to speak on a named basis.

Three candidates is the standard shortlist size for a technology CXO mandate at Board level — whether CEO, CTO, CPO, CRO or CMO. Three is the best balance between optionality for the Board and depth of assessment-investment per candidate. Occasionally we shortlist four when two candidates are so close on context-fit that the Board benefits from an additional comparative axis. Shortlists of five or more are a red flag — they indicate insufficient pre-qualification discipline.

ESOP at the private-company cases above is structured as 4-year ratable vesting with a 1-year cliff, at fair-value grant basis, with IPO-window or milestone-triggered acceleration tranches. Leaver provisions distinguish good-leaver from bad-leaver. Worked examples are included in the appointment terms showing vesting outcomes in ordinary, IPO-success, and change-of-control scenarios. Gladwin-structured offers carry this architecture by default.

End-to-end mandate time from first Board conversation to candidate joining is typically 4–6 months for a technology CXO mandate: 55–85 days to offer acceptance, plus a 60–120 day notice-period, plus relocation / family-transition timelines for returning-diaspora candidates where applicable. Boards planning a CXO transition should engage search partners 9–15 months ahead of incumbent transition.

Two causes dominate. First, compensation envelope mis-scoping — typically Boards under-budgeting at stage-earlier bands when the candidate pool sits at a higher stage. Second, context mis-classification — running a SaaS CTO shortlist for what is actually a platform-CTO mandate, or a Run-mandate shortlist for what is actually a Build-mandate GCC. Both are preventable through rigorous mandate design, which is why Gladwin front-loads context classification at Step 1 of the 10-step process.

Published industry lists present CXO moves as point-in-time announcements without visibility into mandate origin, candidate pool architecture, shortlist composition, vignette design, or compensation structure. Gladwin case studies are written from the inside — what the Board brief looked like, how the longlist was segmented, where candidates were eliminated, how the shortlist was scored and presented, and what the 12–18 month operating outcome was post-joining. This depth allows prospective Boards to calibrate whether our methodology fits their specific mandate.