Hr ops · Production

Jamf deploys Claude Enterprise across 285 use cases in all 16 departments via a three-road AI governance framework

The problem

As Jamf grew globally, skilled employees across service desk, infrastructure, and engineering functions were spending significant hours on documentation, communications drafting, information synthesis, and policy navigation — necessary work that crowded out the analytical depth and creative judgment their roles required, while AI adoption was spreading organically and inconsistently across departments.

Workflow diagram · grounded in source
1
Governance routing via three roads
Routing
Use cases are sorted into one of three paths — Express, Toll Road, or Off-Road — based on complexity and data security requirements.
▾ source quote
“The Express lane covers approved tools like Claude Enterprise with no special approval required. The Toll Road handles configured use cases (custom Skills, MCP connectors) that need documentation and department-level review. The Off-Road path covers fully custom API implementations requiring …”
2
Employee knowledge work via Claude Enterprise
Ai action
Claude Enterprise handles broad employee knowledge work through a governed interface any employee can use on day one.
▾ source quote
“Claude Enterprise handles broad employee knowledge work through a governed interface”
3
Embedded automation via Claude on Amazon Bedrock
Ai action
Claude on Amazon Bedrock handles developer-controlled API access for embedded workflows that don't need a human at every step.
▾ source quote
“Claude on Amazon Bedrock handles developer-controlled API access for embedded workflows that don't need a human at every step”
4
HR virtual agent deflects Tier 0 inquiries
Ai action
An HR virtual agent deflects Tier 0 inquiries before they hit the service desk.
▾ source quote
“The team built an HR virtual agent deflecting Tier 0 inquiries before they hit the service desk”
5
Multi-source department scorecard built
Output
Claude processed data from Okta, the company's learning management system, usage reports, and Jira into a self-contained HTML dashboard.
▾ source quote
“processing data from Okta, the company's learning management system, usage reports, and Jira into a self-contained HTML dashboard”
6
Weekly leadership review drives decisions
Human review
The scorecard is reviewed weekly by all 16 department leaders.
▾ source quote
“is now reviewed weekly by all 16 department leaders. The scorecard has driven specific decisions: identifying a department with low access despite strong training completion, surfacing a training gap that led to a gamification initiative, and helping redistribute licenses to …”
Reported outcome

Jamf reached 285 documented use cases across all 16 departments without compliance exposure, assigned the first 1,000 licenses within four weeks, already surpassed its 2026 goal of 60% active usage, and compressed project build times from weeks to hours on representative projects.

Reported metrics
Documented use cases across departments285
HR implemented use cases21
HR pipeline use cases55
Marketing use cases in production62.5%
Show all 17 reported metrics
documented use cases across departments285
HR implemented use cases21
HR pipeline use cases55
Marketing use cases in production62.5%
Enterprise Transformation licensed users who are Skills creators60%
Claude Enterprise licenses assigned1,000
Time to assign first 1,000 licenseswithin four weeks
Waitlist sizemore than 200
License expansion target2,000
Active usage goal (2026)60%
Department scorecard build time (with Claude)roughly eight hours
Department scorecard build time (prior engineering estimate)two to four weeks
Communications package drafting time (with Claude)about four hours
Communications package prior drafting timetwo to three business days
Review cycle rounds (with Claude)dropped from three rounds to one
Departments covered16
Manual new hire data work eliminatedeliminates five years of manual copy and pasting
Reported stack
Claude EnterpriseClaude on Amazon BedrockClaude CoworkOktaJira
◆ Does this fit your context?

Compare to your context

Tell us your scale, team, and constraints. We'll show what changes at your size, what fails at your scale, and whether this case is a fit, needs adaptation, or won't scale to you. Free demo, no signup.

Compare to your context →
~30 seconds · free
Source
https://www.anthropic.com/customers/jamf
Read source ↗

Frequently asked questions

What did this team achieve with this AI workflow?

Jamf reached 285 documented use cases across all 16 departments without compliance exposure, assigned the first 1,000 licenses within four weeks, already surpassed its 2026 goal of 60% active usage, and compressed pro…

What tools did this team use?

Claude Enterprise, Claude on Amazon Bedrock, Claude Cowork, Okta, Jira.

What results were reported?

Documented use cases across departments: 285; HR implemented use cases: 21; HR pipeline use cases: 55; Marketing use cases in production: 62.5% (source-reported, not independently verified).

How is this hr ops AI workflow structured?

Governance routing via three roads → Employee knowledge work via Claude Enterprise → Embedded automation via Claude on Amazon Bedrock → HR virtual agent deflects Tier 0 inquiries → Multi-source department scorecard built → Weekly leadership review drives decisions.

Related hr ops cases

WHAT TO DO WITH THIS

Now compare it to your context

This case is one data point. Whether its pattern fits you depends on your volumes, your stack, and your exception load — that comparison is the step no case study can do for you.

Browse the Hr ops cases →