# Anthropic's enterprise playbook, *read from Muscat.*

[Notes](https://www.orfloat.com/notes) · Reading · 24 May 2026

Anthropic published a 35-page enterprise guide called *Building trusted AI in the enterprise*. We read it end-to-end this week. The short version: it describes a four-stage spine that almost exactly matches the engagement model we already sell, and one we now have explicit language for. The longer version is what the playbook leaves out — what a Muscat operator needs to add to make it land.

You can read the original guide in full on [anthropic.com](https://www.anthropic.com/news) — we won't reproduce it here. What follows is our commentary as forward-deployed engineers operating in the Gulf: what we adopt from it as written, where it has to be translated to land in a family-led GCC business, and where Orfloat's own thinking goes further than the guide.

## The four-stage spine

The guide organises an enterprise AI programme into four sequential stages: develop a strategy, create business value through a pilot, build for production, and then deploy with LLMOps. Anthropic notes that companies with the right motivation can compress what they otherwise frame as a 13-month rollout into a few months — citing FeatherSnap integrating Claude on Amazon Bedrock in under 90 days and DoorDash building a voice contact-centre solution in two months. We are familiar with that timeline. Our typical engagement runs about 16 weeks from on-site Discovery to first production system.

The four-stage model maps cleanly onto our own:

- **Stage 1 (Strategy) ↔ Orfloat Discovery.** Their guide says to start with people, process, and technology. Our 15-day on-site Discovery does exactly that — three of the deliverables (governance map, opportunity priority list, technical-readiness audit) are Anthropic's three dimensions, named differently.
- **Stage 2 (Business value) ↔ Service Agreement.** Anthropic's seven-criterion pilot test — LLM-suited work, measurable metrics, clear ROI, business-critical but low security risk, abundant data, minimal disruption, scalable — is the same checklist we apply when we draft the milestone-based scope after Discovery.
- **Stage 3 (Production) ↔ Forward deployment, weeks 1–8.** The prompt-engineering structure they spell out (task+role, background, rules, history, request, format, prefill) is our default scaffold. Their emphasis on evaluation-before-deployment is non-negotiable for us.
- **Stage 4 (LLMOps) ↔ Forward deployment, weeks 9–12 + 90-day handover.** Their five LLMOps practices — monitoring, prompt version control, security by design, scalable infrastructure, continuous QA — are the operating discipline we install before we leave.

## People, Process, Technology — translated for a Muscat family business

The guide's three-dimensional model is correct, and it is also written for a different kind of company than the ones we work with. Three places where translation is necessary:

> The guide assumes you have an executive sponsor, a steering committee, and a head of AI. Most Omani family businesses have a managing director, his cousin who runs operations, and an IT vendor.

**People.** Anthropic prescribes "executive alignment and sponsorship" and an "AI review board." In the GCC family-business context, that is the founder and the COO sitting in the same Discovery workshop, and the AI review board is the same group that already meets weekly to talk supplier prices. We don't create new committees. We meet the existing ones where they already convene, and we hand them better questions.

**Process.** Anthropic's pilot-graduation criteria — performance thresholds, operational readiness, risk management infrastructure — are the right gates. The guide implicitly assumes you have a product analytics practice in place to measure those gates. Most of our clients don't. Part of our forward-deployed work is instrumenting the operation enough that the criteria can be measured at all. The pilot doesn't fail; the measurement framework fails first.

**Technology.** The guide describes a clean three-level technical maturity: basic chat, intermediate with RAG and tools, advanced agents. In a Muscat operation, you may need to be at all three levels simultaneously — a basic chatbot for guests, a RAG-equipped concierge for returning customers, and an autonomous nightly reconciliation agent for the back office. The progression in the guide is accurate at the enterprise level; at the individual-business level, you pick the right level for the right workflow.

## The 12-month clock, in practice

Anthropic's four-phase rollout — Foundation (months 1–3), Pilot (4–6), Strategic Scaling (7–12), Broad Adoption (13+) — is the right cadence for a large enterprise. For a GCC family business with 80–400 staff, we compress it considerably: Foundation in weeks 1–3, Pilot in weeks 4–10, first production system live by week 12, second production system by week 16. The four-phase logic is preserved. Only the calendar shrinks. Anthropic's own note that "motivation and partnership" can condense the timeline to weeks is exactly the lever we pull.

## The LLMOps gap is the engagement

Anthropic cites a BCG survey of 1,400 C-suite executives in which 62% identified shortage of talent and skills as the biggest obstacle to their AI strategy. Inside an Omani operator's building, that number is closer to 100% — not because the talent doesn't exist, but because no single hire fills the shape of the role. The shape is one part LLM engineer, one part operations specialist, one part data architect, one part compliance reader. Hiring that profile in Muscat in 2026 is not a recruitment problem; it is a scarcity problem. Forward deployment exists to fill the shape without making the client own it.

## What we adopt, and what we add

We adopt the playbook's spine — the four stages, the three dimensions, the seven pilot criteria, the five LLMOps practices — directly. We treat it as the published standard for serious enterprise AI work. Where we add: a translation layer for the GCC family business, a measurement-instrumentation layer that the playbook assumes you already have, a Muscat-aware governance cadence, and a forward-deployed delivery model that compresses the calendar.

If you are running an operating business in the Gulf and the four-stage model above sounds like a useful map — the right next step is to find out what your Stage 1 looks like honestly. [Start a Discovery Phase.](https://www.orfloat.com/contact)

— Akram Ahmed, CTO · Orfloat · Muscat

## References

1. Anthropic. *Building trusted AI in the enterprise — Anthropic's guide to starting, scaling, and succeeding based on real-world examples and best practices.* See [anthropic.com/news](https://www.anthropic.com/news) for the latest enterprise resources. Trademark and attribution acknowledged on our [Trademarks page](https://www.orfloat.com/trademarks).
2. Bain & Company. *Technology Report 2024.* [bain.com](https://www.bain.com/insights/topics/technology-report/)
3. McKinsey & Company. *The state of AI in 2024.* [mckinsey.com](https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai)
4. BCG. *Five Must-Haves for Effective AI Upskilling.* [bcg.com](https://www.bcg.com/publications/2024/five-must-haves-for-effective-ai-upskilling)
5. Anthropic. *Prompt engineering documentation.* [docs.claude.com](https://docs.claude.com)

[← Back to Notes](https://www.orfloat.com/notes)