Internal Service Request Catalog: Turn Free-Form Asks Into a Self-Service Menu

The problem this kills

Your shared-services team — IT, analytics, ops, the PMO — takes work from the whole company, and it arrives as a mess. A Slack message that just says "can you build me a report?" An email with no context. A ticket that's missing the one field you need to even start. So you spend your day chasing people: which system, what date range, who's the audience, what's the deadline, who approved this? Half your capacity goes to clarifying requests instead of doing them.

The free-form ask is the root problem. When anyone can write anything, you get everything except what you actually need. And because there's no menu, requesters don't know what you even offer or how long it takes, so expectations are set by whoever shouts loudest.

You don't need a six-figure ITSM platform to fix this, and you don't need to be a developer. You need a catalog.

What you'll build

A simple internal web tool with a self-service catalog of request types — new report, new dashboard, process change, small tool, data pull, access request, whatever your team actually does. Each type is data-driven: it defines its own required fields, its SLA (how fast you commit to respond), and a default owner. A requester browses the catalog, picks the type that fits, and fills out a form that asks for exactly the fields that type needs — nothing more, nothing less. The tool drafts a ticket, stamps it with the right SLA and routes it to the default owner.

Then the service owner reviews each submitted request, confirms it's the right type and the scope makes sense, fixes the owner or priority if needed, and clicks Approve. Only then does it become a tracked ticket and flow into your CSV export in the exact columns your system of record expects. Because the catalog itself is just data, a non-coder can add a new request type — with its own fields and SLA — without touching code.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — what kinds of work you take in, what each request type needs to be actionable, your SLA and ownership rules, your team and department list, your typical and peak request volumes, and the messy edge cases that bite you — and then it tailors the catalog schema, the per-type forms, the routing, and every later step to your answers. This is not a generic template; the agent reflects a short spec back to you and waits for your thumbs-up before it builds anything. From there it walks the agent through loading your catalog and people list from a sheet, building the browse-and-pick experience, generating type-specific forms with per-type required-field enforcement, the duplicate guard, the owner review-and-approve queue, and the CSV export — each step with a ready-to-copy prompt. There's also a fallback so you can build and run the whole thing today even with no integration to your ticketing tool.

The governance it includes (this is the point)

This is intake for real work, so it ships with the controls a shared-services team needs: login so only your company can submit and only your team can approve, row-level security so people only ever see their own organization's requests, a complete audit trail of who submitted, edited, and approved what and when, a hard human-in-the-loop approval gate so nothing becomes a tracked ticket or hits the export until the service owner signs off, and duplicate guards keyed on requester plus type plus normalized title within a 7-day window so the same ask can't be filed twice. Per-type required fields are enforced at submit time, so an incomplete request can't even reach your queue.

Who it's for

Shared-services and ops teams, internal IT, analytics groups, and PMOs that take work from the rest of the company and are tired of chasing people for the details. If you can list the kinds of requests you handle and what each one needs to get started, you can build this.

You've got this — start with the plan, paste the first prompt, answer the interview, and you'll watch your catalog and first tailored request form come to life the same afternoon.