12 years of shipping software — interfaces that feel like nothing, APIs that don't wake you at 3am, and infrastructure that quietly compounds. Currently freelance, taking 1–2 contracts per quarter.
Five stages, no deck-ware, no theater. Engagements run 6–14 weeks.
A 60-min unstructured call. I want to understand the actual problem before pitching a solution.
A short written brief — what we're shipping, what we're explicitly not shipping, where the risks are.
Week 1 ends with a clickable prototype or a working spike, not a deck. We pressure-test it together.
I work in 2-week chunks. You see something real every Friday. Production deploys are uneventful by design.
Documentation, runbooks, a Loom walkthrough, and a 30-day stabilization window. Nothing surprises you on day 31.
You have a thesis and need it shipped. I take it from sketch to production — frontend, backend, infra, the lot.
Best for: pre-seed → series A teams that need a senior engineer who owns outcomes.
Drop into your existing team for a quarter. Code reviews, architecture, mentoring, and shipping the gnarly tickets nobody else wants.
Best for: small-to-mid teams hitting a complexity wall.
Architecture review with a written report — what to fix now, what to fix later, what is fine despite what your CTO believes.
Best for: teams about to do a rewrite. (Spoiler: usually you shouldn't.)
I read everything. Even the cold pitches. Tell me what you're building and what's getting in the way.