בס״ד

Underwriting Engagement Playbook (how Sam runs an underwrite client)

docs/services/engagement-playbook.md · last changed (pre-VM history) · rendered from GitHub master

Underwriting Engagement Playbook (how Sam runs an underwrite client)

The point: a repeatable lifecycle so you know your time, protect your scope, and get paid —
the same for Arsen or anyone. Two shapes: one-off underwrite or monthly retainer.

The lifecycle (7 steps)

# Step Who/where Your time Paid?
1 Scope call — understand the deal, ask the 5, see if it's a fit phone, 10–20 min 0.25–0.5 hr FREE
2 Proposal + deposit — send 1-page scope + fee + deposit; he signs + pays deposit email 0.25 hr
3 Materials in — he sends docs (P&L, bank stmts, receivables aging, etc.) 0 (clock starts here)
4 The underwrite — normalize books, model, receivables analysis your desk 6–12 hr yes
5 Review call — walk him through it, screen-share screen-share, 30–60 min 0.5–1 hr yes
6 Deliverable — the one-pager + model + recommended structure email (in step 4) yes
7 Closeout — balance due on delivery; mark done 0 balance paid

Rule that protects you: real work (step 4+) only starts AFTER the deposit. The scope call is
free; the underwrite is not. Never underwrite to "win" the deal — that's the Passover trap.

How much TIME (so you can price + plan)

Format

Payment + contract (what to set + save)

Scope guard (don't let it creep)

What to nail on the scope call (his ops questions → your answers)

Source trail · docs/services/engagement-playbook.md @ master · rendered 2026-07-02 7:23 PM EDT by scripts/build-docs.py · the .md in the repo is the truth; this page is the phone-readable view