Prep brief for paid Deep Dive — cal.com/willianpinho

prep-brief-public.md

Prep Brief — Deep Dive (60 min)

You booked a paid Deep Dive. Thanks. To make this 60 minutes worth your money, I need this brief returned at least 24 hours before the call. Reply to the booking confirmation email or send to me@willianpinho.com.

No prep brief = call gets rescheduled (your payment is held, not lost).

Five questions. Aim for one page total — not a dissertation. Bullet points are fine.

---

1. The problem in one sentence

What's the specific decision, stuck point, or question you want answered? If you can't compress it to one sentence, the call won't help — keep iterating until you can.

Your answer:

2. Where you are now

Brief current state: stack, team size, timeline, anything that constrains the answer. 3-5 bullets max.

Your answer:

3. What you've already tried or considered

So we don't re-derive your dead ends together. List options you've evaluated and rejected, with one-line reasoning. Empty answer = you haven't thought hard enough yet; reschedule.

Your answer:

4. What "good" looks like

How will you know this call was useful? What decision do you need to walk away with? E.g., "a yes/no on whether to migrate from LangChain to a custom orchestrator", not "some clarity".

Your answer:

5. Hard constraints

Budget, deadline, must-have tech, regulatory (HIPAA/SOC2/LGPD), team skills, on-call posture. The boring stuff that kills "the right answer" if I don't know about it.

Your answer:

---

What to expect on the call

• First 5 min: I confirm I read your brief. You add anything you forgot. We agree on the call's success metric.
• Middle 45 min: working session — diagrams, code on screen, real architecture talk. I push back when I disagree.
• Last 10 min: crisp action items, owner per item, what would warrant a follow-up.

After the call you get a 1-page summary with the recommendation and reasoning, sent within 24h.

---

Out of scope (won't cover, even if asked)

• Recruiting / hiring decisions (use Recruiter Intro instead).
• Code I haven't seen by 24h before the call.
• Topics not in your prep brief — surprises burn time we paid for.
• Implementation work — this is advisory. If you want me to ship code, that's a separate engagement.