Enterprise Platform Lead — Claude Cert Academy

Scale Claude across the org, not just the app.

The certification for the person who owns Claude as a platform — not as an app. Procurement and contract structure, identity & SSO, governance and acceptable-use policy, org-wide cost management, audit and SIEM integration, and the internal enablement playbook that turns "we have Claude" into measurable adoption. Less code, more decisions, frameworks, and reusable artifacts.

What you'll learn

• Structure an Anthropic enterprise relationship: contract dimensions, BAA scope, and procurement evidence
• Stand up identity and access for Claude: SSO, SCIM provisioning, role design, and least-privilege workspace structure
• Author governance artifacts: acceptable-use policy, data classification map, model-card review process, and risk register
• Run org-wide cost: budget allocation, chargeback or showback, cost attribution, and abuse detection
• Operate the audit posture: log integrity, SIEM forwarding, retention contracts, and the evidence pack auditors actually ask for
• Build an internal enablement program with adoption metrics that survive a CFO review

Course content

01. Procurement, Contracts & Vendor Strategy

• The four ways to buy Claude
• Anthropic enterprise contract dimensions you need to negotiate
• BAA scope: when it applies and what it does not cover
• Bedrock & Vertex: shared-responsibility deltas vs direct API
• Vendor security review: the questionnaire that actually matters
• Pricing models, commit structures, and committed-spend negotiation
• Multi-vendor strategy: when to keep a second model provider
• Scenario: write the executive memo justifying a 3-year Claude commit

02. Identity, Access & Workspace Architecture

• SSO for Claude: SAML, OIDC, and IdP setup paths
• SCIM provisioning and the deprovisioning gap
• Workspaces, projects, and the org-structure mapping question
• Role design: admin, billing, developer, and the principle of separation
• API key custody: rotation, scoping, and the secret-leak playbook
• Service accounts vs personal keys for production workloads
• Just-in-time access and break-glass for incident response
• Scenario: a contractor leaves and four API keys are unaccounted for

03. Governance, Policy & Responsible Use

• Acceptable-use policy for Claude: the seven clauses you cannot skip
• Data classification: mapping classes to allowed Claude usage
• Model card review: turning the spec sheet into a go/no-go
• Risk register entries for an LLM platform
• Human-in-the-loop policy for high-stakes outputs
• EU AI Act, NIST AI RMF, and ISO 42001: which apply, which do not
• Shadow IT detection: finding Claude usage you did not authorize
• Scenario: legal flags a feature 48 hours before launch — review and decide

04. Cost Management & Audit Posture

• Allocating an org-wide Claude budget across teams
• Chargeback vs showback: which actually changes behavior
• Cost attribution: tagging prompts so finance can read them
• Abuse detection: anomaly signals on usage
• Audit logging in the Console: what is captured, what is not
• SIEM forwarding patterns and log-integrity requirements
• The evidence pack: what an external auditor actually asks for
• Scenario: spend doubled overnight — diagnose and present to the CFO

05. Enablement, Adoption & Measurable Impact

• The Four Enablement Archetypes
• Training Paths: Persona-Mapped and Self-Serve vs Cohort
• Communities of Practice: Keeping Them Alive Past Month Three
• Internal Documentation: What to Centralize, What to Federate
• Adoption Metrics That Are Not Vanity
• Productivity Measurement: The DORA-Style Frame for AI Tooling
• The QBR Pack: Telling the ROI Story Without Inflated Numbers
• Scenario: The Six-Month Executive Sponsor Review

Continue to Claude Cert Academy