Reference architectures

What a typical engagement looks like

Last verified: June 2026· reference architecture

These are the engagements we run. The starting state, the work week by week, the deliverables, the end state, and the ownership boundary. Not a customer story — we publish a reference architecture so a buyer can pattern-match against their own situation before a 30-minute technical call.

Typical 4–6 week engagement · fixed-scope or outcome-priced→

Reference architecture: a 6-week LLM cost engagement

A typical 6-week LLM cost optimization engagement — the week-by-week plan, the deliverables, the end state, and what the buyer owns when the engagement ends.

Typical 6–10 week engagement · fixed-scope with optional monthly tuning→

Reference architecture: a 6-week AI coding workflow rollout

A typical 6-week AI coding workflow rollout (Claude Code + Cursor + Copilot) — the week-by-week plan, the deliverables, and what the team owns at the end.

Per-server 3–6 week engagement · fixed-scope with optional maintenance retainer→

Reference architecture: a 4-week MCP server build

A typical 4-week MCP server build (per server) — the week-by-week plan, the deliverables, the security defaults, and what the team owns at the end.