Architecture review
3 weeksReviews an existing or planned architecture against production AI norms. Identifies risks, missing components, scaling failure modes, and remediation order.
AI Architecture Advisory
A second opinion on a roadmap that’s stalled,
in writing, by senior engineers.
When the build has run six months over, when the vendor bake-off feels rigged, when the strategy deck doesn't survive a technical question — that's when you call us. We deliver a written architecture review, a vendor scorecard, or a reference architecture in two to six weeks. Fixed price. Senior engineers only.
A focused engagement aimed at a single decision: what should we build, what should we buy, why is the current build failing, which vendor wins. The deliverable is a written document your team can ship from — not slides, not a workshop summary. Engagements run 2–6 weeks and end with a debrief.
What we ship
Four deliverable shapes.
Vendor scorecard
2–3 weeksEvaluates 2–6 vendors against your requirements. Includes technical due diligence, pricing analysis, integration risk, and a recommendation.
Build-vs-buy memo
2 weeksCosts both paths over 12, 24, and 36 months. Covers TCO, vendor lock-in, internal capability requirements.
Reference architecture
4–6 weeksDetailed reference architecture for a specific use case, with technology choices, cost projections, and a phased delivery plan your team can execute.
Engagement model
How it runs
Timeline2–6 weeks
Pod size1 architect (lead) · 1 engineer (DD)
DeliverablesWritten document · 2-hour debrief
Pricing postureFixed-fee, banded by deliverable
Proof
A global energy company had a multi-year vendor build for an AI-driven inspection system. Eighteen months in, no production deployment. We delivered a 24-page architecture review in three weeks; the recommendations restructured the program into a 9-week internal rebuild on a managed pod. The system shipped before the original vendor's promised milestone.
Global energy company · Architecture review · 3-week delivery
Frequently asked
What buyers actually ask
How quickly can you start?
Most engagements start within 1–2 weeks. The architect is usually the constraint.
Do you defend the deliverable to our exec team?
Yes — that's the debrief. We've defended deliverables to boards and audit committees.
Can you stay on for implementation?
Yes, under a separate engagement (RAG, Agentic, LLM Integration, or Managed Pod). The advisory deliverable is independent of any follow-on commitment.
What if you tell us not to ship?
That's part of the value. The deliverable goes in writing, with reasoning. We've recommended program cancellations more than once.
Next step
Talk to an engineer, not a salesperson.
30 minutes. No slides. Bring an architecture, a stalled roadmap, or a vendor proposal you want a second opinion on. We'll tell you what we'd do.