Services
How I work with teams.
Four delivery modes for the same playbook: name the bottleneck, sketch the architecture, ship a system you can audit. Pick the one that fits where your team is today.
Tier 01
Workflow Audit
Most teams don't need a six-week discovery. They need someone with shipped pattern-matching to spend a week with their workflow and write down what's worth automating — and, just as important, what isn't.
- Format
- 1 week · async + 60-min readout
- Ideal for
- Founders and ops leads who already know the bottleneck and want a second opinion before they commit budget.
What you get
- Workflow map of the current process — sketched live with the operator running it today
- One-page hypothesis: problem · architecture · stack · risks · next step
- Annotated diagram you can hand to any engineer or vendor without translation
- 60-minute readout with the operator, founder, and (if relevant) lead engineer
- Recording, transcript, and editable source — yours to keep
Tier 02
Workflow Build
I ship one workflow end-to-end in three to six weeks. Same playbook as the case studies — bottleneck named, architecture sketched, system observable from the first commit.
- Format
- 3–6 weeks · fixed-scope sprint
- Ideal for
- Teams who've named the workflow and need it shipped to production — not a prototype, not a slide deck.
What you get
- Production-grade system shipped to your stack — Next.js, Python, or your existing infra
- Observability from day one: structured logs, eval harness, cost dashboards
- Operator console so the humans running it can audit, override, and trust the system
- Two-week support window post-launch — bug fixes, prompt tuning, eval iteration
- Loom walkthrough plus README so the next engineer can own it without me
Tier 03
Team Workshop
Workshops are a delivery mode for the same playbook I use on builds. Your team walks out with shipped workflow they can run on Monday — not slideware they forget by Friday.
- Format
- Half-day to two-day · on-site or remote
- Ideal for
- Five-to-fifty-person teams adopting AI as routed workflow — not chat. Engineers, ops, and product in the same room.
What you get
- Tailored curriculum built around your real workflows — no generic exercises
- Hands-on labs: each participant ships a working AI workflow by end of day
- Eval-first mindset — how to measure quality, cost, and latency before you optimize
- Operator playbook so participants can run the same exercise with their own teams
- 30-day async follow-up: questions answered, code reviewed, blockers unblocked
Tier 04
Speaking & Briefings
I speak the way I build: specific. Three patterns that work, three that don't, and the moment you can tell which is which.
- Format
- 30–60 min keynote or executive briefing
- Ideal for
- Conferences, leadership offsites, and cohort programs that want a working operator on stage — not a futurist.
What you get
- Talk tailored to your audience — operators get tactics, executives get strategy
- Live demos of shipped systems, not screenshots from someone else's deck
- Q&A window scoped to the audience's actual questions, not pre-canned ones
- Slides and recording rights yours to keep and share internally
- Optional half-day workshop add-on for follow-up depth
Not sure which fits?
Thirty minutes on a call is usually enough to tell. No pitch, no slides — we map your workflow and you decide.