The common failure mode is a full conversation that leaves each side with a different memory. This note is a reusable closing narrative: turn a 30-minute interview into meeting notes, not verbal promises.
- 1. Before the call: three questions only
- 1. Where business goals and financing / capital narratives are stuck (indicative, not an audit)
- 2. Seats already filled vs critical gaps (architecture / delivery / cross-border collaboration)
- 3. What written output you want to leave with (checklist / draft role plan / expert-intro intent)
- 2. During: timebox
- 0–5 min: confirm goals and out-of-scope (no promise of match close rates, fundraising outcomes, or fixed timelines)
- 5–20 min: walk structural completeness and verifiable facts by seat
- 20–25 min: capability gaps and fill priority (indicative)
- 25–30 min: restate three closing points + agree when notes will be sent
- 3. Three closing points (must appear in notes)
- 1. Gap list: role / capability layer / evidence gaps (verifiable items vs materials still needed)
- 2. Priority: what to fill first and why (vs business goals)
- 3. Optional next steps: written role plans and expert/advisor intros; technology proof of concept (PoC) assessed separately as a tech engagement
- 4. Within 24 hours: notes template
- Context and goals (client wording summary)
- Structure judgment and gaps (indicative tone)
- Suggested priority
- Explicit non-promises / items requiring written agreement
- Contacts and follow-up window
- 5. Boundary (public wording)
Structured interview and checklist output—not a promise of fundraising outcomes, match close rates, or fixed timelines. Meeting notes and written agreements prevail. Book via #/diagnosis
Related: #/updates/upd_talent_diagnose · #/updates/upd_ai_bench_seats_not_resumes · #/updates/upd_patent_path
