Firm-level statement · key-person risk · on the record

If the founder is hit by a bus.

A procurement team that spends a day on due diligence will ask this question. CROs ask it twice. Boards ask it once, in writing, and want the answer in the statement of work. This page is that answer. It is deliberately shorter than the stance paper and the procurement pack: one page, five concrete commitments, one clause the client can lift straight into the SoW. We do not mitigate key-person risk by pretending it does not exist. We mitigate it with contract, with discipline, and with a named second pair of senior hands standing by.

01 · The acknowledgementA founder-owned boutique carries key-person risk. Say so.

Ezelman is a founder-owned boutique with one partner and a roadmap to a second by end-2027 (see stance). That structure is deliberate. It is also the single largest operational risk that a bank’s Third-Party Risk Management team should price when engaging the firm.

We refuse to pretend the risk is absent. On mandates where it is materially larger than the bank can absorb — for example, a twenty-four month CRR3 programme with no internal alternative — we say so at the proposal stage and we decline. On every mandate we do take, the five commitments below apply. They are contractual, not aspirational.

02 · The commitmentsFive pledges that flow into every SoW longer than twelve weeks.

  • Named external senior backstop. A vetted ex-director-level practitioner from Ezelman’s senior-only delivery-partner network is pre-briefed on the mandate and holds current NDA coverage. The backstop is named in the term sheet — not described as “an equivalent senior resource to be nominated.” From end-2027, the backstop role is filled internally by the second partner.
  • 5-business-day handover SLA. On any qualifying founder unavailability (illness, force majeure, accident), the backstop is activated and briefed in a single working week. The bank can schedule the first supervisor-facing interaction with the backstop on day six of the unavailability.
  • Working-paper discipline. The mandate’s working-paper file (memo drafts, model calibration evidence, supervisor correspondence log, open-issue tracker) is maintained from day one at the standard required for a supervisor’s on-site inspection of our premises. That is the same standard required for a five-day handover. It is maintained irrespective of whether the handover is ever triggered.
  • Continuity clause, written into the SoW. Every statement of work longer than twelve weeks contains the continuity clause reproduced in section 04 below. The clause is non-negotiable on our side; it may be tightened by the client.
  • Extended-unavailability walk-away right. If founder unavailability extends beyond six continuous weeks and the backstop is not acceptable to the client for the remaining scope, the client may terminate the SoW at that point with no further fee payable beyond work-in-progress and reasonable close-out costs. This clause is ours, not the client’s — we include it by default.

03 · The SLAsContractual numbers, on the page.

The three numbers a TPRM team should hold Ezelman to, drawn from the Business Continuity Plan tested annually.

Handover
≤ 5 business days
Backstop fully briefed and supervisor-facing from day six of unavailability.
Working-paper recovery
RTO 4h · RPO 1h
Client working papers recoverable from a second EU member state. Drill tested annually.
Extended-unavailability trigger
6 continuous weeks
Client walk-away right activates if founder unavailability exceeds this window and backstop is not acceptable.

04 · The clauseLift straight into the statement of work.

The continuity clause below appears verbatim in every Ezelman statement of work for a mandate longer than twelve weeks. Clients are welcome to lift it into their own paper — it is drafted to survive being detached from the Ezelman template without loss of meaning.

Continuity clause · template

Continuity of senior-partner time. The Supplier warrants that the individual named as the Lead Partner in Schedule 1 (the “Lead Partner”) will personally commit at least [    ] hours per calendar week to the engagement, and will personally attend all supervisor-facing meetings, model-defence workshops and Pillar 2 dialogues scheduled under this Statement of Work, save where otherwise consented to in writing by the Client.

Named backstop. The Supplier has pre-briefed, and made available under NDA, [named senior practitioner] (the “Backstop”) as senior cover for any period in which the Lead Partner is materially unavailable. The Backstop’s CV and NDA are annexed to this Statement of Work.

Activation. On any Lead Partner unavailability exceeding five consecutive business days, the Supplier shall, within five further business days, activate the Backstop on the engagement and certify in writing to the Client that working papers have been briefed, the open-issue register handed over and the next supervisor-facing deliverable re-scheduled.

Extended-unavailability termination. Where Lead Partner unavailability extends beyond six consecutive weeks and the Backstop is not, on reasonable Client assessment, acceptable for the remaining scope, the Client may terminate this Statement of Work at that point with no further fee payable beyond (a) work-in-progress on a time-and-materials basis to the date of termination, and (b) reasonable documented close-out costs, capped at [    ]% of the signed SoW value.

Working-paper standard. The Supplier shall maintain the engagement’s working papers at the evidence standard required for an on-site inspection of the Supplier’s premises by the Client’s competent supervisor, at all times during the engagement and for the retention period specified in Schedule 3.

05 · The honesty clauseWhere this note reaches its limit.

A five-day handover is a real mitigant for most events that would otherwise disrupt a mandate: short-duration illness, scheduling collision, family emergency, extended travel. It is a partial mitigant for a catastrophic event in which the founder is permanently unavailable, because in that scenario the bank’s second pair of senior hands is not the backstop — it is the bank’s own internal team, possibly supported by a new supplier. The continuity clause is drafted so that the bank is not trapped in that scenario (termination rights are clear and fee is capped). It is not drafted to pretend the catastrophic event has no consequence.

For mandates where the bank judges that a catastrophic-event exposure would be materially damaging, the honest answer is that a founder-owned boutique is the wrong supplier at this stage of the firm’s life. That answer will change at end-2027, when a second partner is in place. Until then, we would rather name the boundary than hide it.

Last update: 2026-04-21. This page is edited, rather than archived, when any of the numbers or commitments on it change.

Want this drafted into your SoW?

The clause above, negotiated against your bank’s own continuity standard, takes one twenty-minute call with the founder and one pass with legal.

Sitewide figures policy: every figure on ezelman.com is either a public-source citation, an estimate with stated methodology, or an anonymised mandate outcome. The numbers on this page (handover SLA, RTO/RPO, extended-unavailability trigger) are firm-level operational commitments drawn from Ezelman’s Business Continuity Plan, not public-data figures.
Follow Ezelman on LinkedIn — Regulatory insights read by 2,000+ risk professionals across Europe & the GCC Follow →