2-week architecture review
$Who it’s for
Teams about to start an AI build — or quietly stuck on one.
What you get
A written architecture doc, a build-vs-buy call on each component, and a 30-minute walkthrough with your engineers.
AI consulting
AI architecture that survives
contact with production.
We scope the work the way a senior engineer would: read the actual problem, pick the smallest thing that works, and ship it where you can measure it. Most projects don’t need an agent. We’ll tell you when yours does.
Scope
What we actually do.
01/06
Strategy & architecture
Where AI fits in your stack, what to build vs. buy, what to skip. The plan a senior engineer would write — not a vendor pitch.
02/06
Model selection
Frontier, open-weight, hosted, self-hosted. We pick for fit and cost — and tell you when the smaller model is the right one.
03/06
Agentic system design
Tool calls, retries, state, evals. Scoped honestly: most workflows don’t need an agent. We’ll tell you which yours is.
04/06
RAG and data pipelines
Ingest, chunk, index, evaluate. Built so a tired engineer at 3 a.m. can still reason about why a retrieval missed.
05/06
GPU infrastructure planning
Capacity, topology, networking, cooling. We’ve specified GPU clusters that ran in production.
06/06
Responsible deployment
Evals, guardrails, auditability, kill switches. The boring parts that decide whether the system makes production or gets rolled back.
Method
How we scope.
- 01
Read the actual problem.
Not the prompt you were handed, not the buzzword on the roadmap. The thing your team is going to live with for two years.
- 02
Pick the smallest thing that works.
Often that’s a SQL query, a cron job, or a single fine-tune. Sometimes it’s an agent. We tell you which — honestly.
- 03
Ship it where you can measure it.
Evals before launch, monitoring after. If we can’t see the system breaking, we can’t tell you whether it’s working.
Most projects don’t need an agent. Most agent projects don’t need ‘agentic.’
Engagements
Three shapes that fit most teams.
We work in the shape your team can actually absorb. If none of these fit, we’ll tell you and point you to someone who does.
6-week build with your team
$$Who it’s for
Teams that need a first production system shipped — not a prototype.
What you get
Embedded with your engineers. A working system in your environment with evals, monitoring, and a runbook the on-call can actually use.
Fractional advisory
$$$Who it’s for
Founders and CTOs who need a senior voice in the room each quarter.
What you get
Standing weekly slot, async review on big calls, and a hands-on quarter when something gnarly lands. Quarterly retainer.