IT Service Catalog Development
Build IT service catalogs with service definitions, SLAs, request workflows, and self-service documentation for IT organizations.
Employees don't know what IT supports, what the SLAs are, or how to request services — so they email you directly for everything. A service catalog eliminates the 'can IT do this?' question and gives your team clear boundaries, request workflows, and measurable commitments.
Who it's for: IT directors building ITSM foundations for growing organizations, service desk managers documenting support offerings and SLAs, CIOs implementing ITIL-aligned service management, IT operations leads reducing ticket volume through self-service, managed service providers defining client service packages
Example
"Build an IT service catalog for our 500-person company" → Complete service catalog: 25 service definitions with descriptions and owners, tiered SLA matrix (gold/silver/bronze), request submission workflows for each service, self-service knowledge articles, and quarterly service review template
New here? 3-minute setup guide → | Already set up? Copy the template below.
# IT Service Catalog Development
## Your Role
You are an expert IT service management specialist. Your job is to build structured service catalogs that clearly define available IT services, set expectations through SLAs, and enable self-service where possible.
## Core Principles
- Business language, not IT acronyms
- Tier services: Standard, Premium, Custom
- Self-service first for automatable requests
- Measurable SLAs with response and resolution times
- Start with the top 20 most-requested services
## Instructions
Produce: service definitions with scope, service level agreements with measurable targets, request-to-fulfillment workflows, pricing/chargeback models if applicable, self-service documentation, and escalation procedures.
## Output Format
- **Service Entry**: Name, description, scope (includes/excludes), tier, SLA, request process
- **SLA**: Service, response time, resolution time, availability, measurement method
- **Workflow**: Request trigger, approval steps, fulfillment steps, notification, closure
## Commands
- "Service catalog" - Full catalog build
- "SLA definitions" - Service level agreements
- "Self-service docs" - User-facing guides
- "Request workflows" - Process documentation
Get new playbooks like this one
One email a week with new Claude Code workflows. Free, like everything here.
No spam. Unsubscribe anytime.
What This Does
Creates structured IT service catalogs that define available services, SLAs, request processes, and self-service options. Gives employees a clear menu of IT services and sets expectations for delivery.
Quick Start
Step 1: Download the Template
Click Download above to get the CLAUDE.md file.
Step 2: Inventory IT Services
List all IT services provided, current response times, and common requests.
Step 3: Start Using It
claude
Say: "Build an IT service catalog for our organization. We have 500 employees across 3 offices with services spanning hardware, software, access management, and support."
Catalog Components
| Component | Content |
|---|---|
| Service Definitions | What each service includes and excludes |
| Service Levels | Response and resolution time commitments |
| Request Processes | How to request each service |
| Pricing/Chargebacks | Cost allocation if applicable |
| Self-Service Options | What users can do without IT involvement |
| Escalation Paths | How to escalate if SLA is missed |
Tips
- Business language: Describe services in terms employees understand, not IT acronyms
- Tier services: Standard (free), Premium (approval needed), Custom (project request)
- Self-service first: Every request that can be automated should be
- SLAs must be measurable: Define response time, resolution time, and availability
Commands
"Build an IT service catalog for [organization size]"
"Define service levels with SLAs for each category"
"Create self-service documentation for common requests"
"Design the request-to-fulfillment workflow"
Troubleshooting
Too many services to catalog Say: "Start with the 20 most-requested services. Cover 80% of volume first."
SLAs not being met Ask: "Review if SLAs are realistic. Better to set achievable targets than aspirational ones."
Users don't know the catalog exists Specify: "Integrate into onboarding, Slack, and the company intranet."