01 / THE SHAPE OF AN ENGAGEMENT
Four weeks in, you should not need me in every meeting.
Engagements are scoped to leave something behind: a written architecture, a team that can run it, and a decision log so the next person knows why.
WEEK 01
Read the system
Code, tickets, incidents, and one conversation with every engineer.
WEEK 02
Write the read
Risks, costs, and the shortest path to the next release. In writing.
WEEK 03+
Ship with the team
I take a real slice of the work, not just the review column.
EXIT
Hand over
Named owners, a decision log, and a month of availability on call.
GOOD FIT
- Pre-seed to Series B, 3–30 engineers
- A product decision blocked on technical judgment
- An AI feature that has to survive real users
- Founders who want the trade-offs said plainly
AI BUILDER
- AI organizational strategy
- MVP build
- Forward deployed engineer
- AI-native team