Resources
Most vendor resource pages are a single undifferentiated list. This one separates three different jobs: guides that teach a decision, decks that brief a practice, and assessments that price real work. Each sub-hub says plainly what exists today.
Three resource types, one honest map.
Every entry here states plainly whether it exists today. Guides are complete records ready to read now. Decks and a self-serve assessment tool are described honestly as work still in progress, not finished.
Engineering Guides
Eighteen guides on cost, architecture and AI operations decisions, each answering one specific question a technical buyer actually asks.
Briefing Decks
Summaries of a practice built for internal circulation, described honestly while the actual deck assets are still in preparation.
Assessments
The real engagements that turn a codebase or backlog into a scoped plan, plus what a self-serve version would eventually cover.
What keeps every resource honest.
Every guide, deck and assessment description here follows one rule: state only what actually exists, and mark clearly what does not. No guide invents a benchmark, and no deck claims a slide count that has not been built.
Built for someone scoping real work.
These resources serve one audience: a technical decision-maker comparing a vendor before a conversation starts. Guides answer the questions asked before a call. An assessment starts once a plan is worth pricing.
Read the evidence behind these resources.
Guides and decks describe practice-level patterns. The case-study record shows a specific project executing on one. Reading both together connects a pattern to a delivered outcome.
See a pattern applied
A guide states what a decision usually turns on; a case study grounds the same reasoning in one project.
Read ongoing practice notes
The engineering blog carries reasoning between engagements, including the trade-offs a guide has not covered yet.