8.0Contactrev 2026.08

Bring the block diagram, or the argument you’re having about it.

Thirty minutes. I’ll tell you whether the timing budget is realistic, where I think the state should live, and what I would architect differently — whether or not you hire me.

Commitment
One engagement at a time
Taking on
Review and architecture first
Briefs
Always open
Reply
Within one business day
8.1ChannelsBracketed values pending release
Channel
Address
Use for
Email
Anything. Preferred first contact
Calendar
30-minute technical call
LinkedIn
Work history and references
GitHub
Public code. Client work stays private
Phone
Scheduled calls, or something urgent
8.2Project briefFive fields

Prefer to write first? Send the shape of the system and the constraint that worries you. No funnel, no drip sequence — this becomes an email to me.

05 · WHAT YOU WANT FROM ME
Goes straight to my inbox. No list, no sequence.
8.3What happens next
STEP 1
A reply within one business day, with the two or three questions I need answered before the call is useful.
STEP 2
Thirty minutes on the system itself. You’ll leave with my read on the risk whether or not we work together.
STEP 3
A written scope: what I’ll do, what done means as a measurement, and what I need from your team to hit it.