WHO IT'S FOR

Built for companies on Claude Team or Enterprise.

You bought Claude for your people. These are the signs it's time to bring in an architect.

Seats are bought, but use is uneven across teams.

Every team writes its own prompts; little is shared as projects or skills.

Claude isn't connected to your own systems yet.

Engineers use Claude Code without shared settings or a review practice.

Security wants answers on sign-in, retention, audit logs and spend.

You run on Microsoft and want Claude to fit that stack.

WHERE WE START

Claude Team TEAM PLAN

Projects and shared skills for each team
The connectors your plan supports
Claude Code settings and practice
Admin roles and spend
A plan for when you outgrow Team

Claude Enterprise ADDS

SSO with domain capture
SCIM or JIT provisioning from Entra ID or Okta
Custom roles, groups and spend limits
Audit logs, Compliance API and Analytics API
Data retention, encryption keys and IP allowlisting

WHAT WE DO

What we set up, build and teach.

Four services. Start with the rollout and add the others as your teams pick Claude up.

01

Claude Enterprise rollout

From the first admin settings to company-wide use.

SSO and SCIM provisioning with Microsoft Entra ID or Okta
Roles, groups and spend limits that match your organization
Connector, data-retention and usage policies
Projects and skills for your first teams
Adoption tracking with the Analytics API

02

Claude Code for engineering teams

Agentic coding with shared guardrails.

CLAUDE.md, settings and permissions per repository
Hooks, MCP servers and approved tools
Review and testing practice for AI-written code
Usage monitoring with OpenTelemetry
Hands-on workshops for your developers

03

Claude on Microsoft

Claude inside your Microsoft stack.

Claude for Microsoft 365: Excel, PowerPoint, Word and Outlook
The Microsoft 365 connector for SharePoint, OneDrive, Outlook and Teams
Entra ID sign-in and provisioning
Claude models in Microsoft Foundry for your own applications
A clear split of work between Claude, Copilot and Copilot Studio

04

Agents, MCP and skills

Your systems and workflows, inside Claude.

Custom MCP connectors to Dynamics 365, your ERP and internal data
Skills that capture your templates, standards and workflows
Agents built with the Claude Agent SDK
Architecture, permission and security review

Claude at work, team by team.

Examples of what teams do once Claude is connected and set up for them.

FinanceCLAUDE FOR EXCEL

Variance commentary drafted in Excel from your month-end export.

SalesCONNECTORS · MCP

An account brief from CRM, email and meeting notes before every call.

HRPROJECTS

Policy answers from your handbook, in a shared project, with sources.

LegalSKILLS

First-pass contract review against your own playbook.

EngineeringCLAUDE CODE

Bug fixes and refactors in Claude Code, reviewed like any other pull request.

OperationsCOWORK

A weekly report assembled from SharePoint files and BI exports.

HOW WE WORK

From review to agents in production.

1

Review

Usage, settings, security and your top use cases, in a short written review.

2

Configure

Identity, roles, connectors, policies and spend controls.

3

Enable

Projects, skills and workshops for each team, and Claude Code for engineers.

4

Build and run

MCP connectors and agents for your systems, with regular reviews.

Get the most out of Claude Team and Enterprise.

Dr. Mehmet Özgür Genç