IT/Facilities Service Catalog

The problem this kills

Someone needs a second monitor. Someone else is moving desks. A new hire needs a name badge, a software license, and door access by Monday. Right now these land on the service desk as a one-line email - "can I get a monitor?" - with none of the details you actually need. So you reply asking for the cost center. Then the manager's name. Then which building. Then whether it's a 24" or a 27". Three days of back-and-forth before anyone can lift a finger to fulfill it.

And when it's an office move or an access change, the stakes are higher: was that approved by the right manager? Who signed off on the budget for the new standing desk? Did we already order this person a monitor last week? The "process" is a tangle of inboxes, a shared spreadsheet, and a lot of chasing people for the same information over and over.

This tool replaces the guesswork with a real service catalog - a menu of the things your team can request, where each item already knows what information it needs, who has to approve it, and who fulfills it. Requests arrive complete, pre-approved, and ready to action.

What you'll build

A small internal web app, just for your organization, that:

• Shows staff a browsable catalog of the services you offer (new monitor, software install, office move, name badge, access change, and whatever else you provide).
• Gives each catalog item its own form with its own required fields - so a software request asks for the app and the cost center, while an office-move request asks for the from/to location and the move date. No more half-baked requests.
• Shows the expected fulfillment time for each item up front, so requesters know what to expect.
• Routes each submitted request to that item's designated approver (the manager and/or budget owner), with cost and approval thresholds so a $40 cable skips approval but a $900 monitor needs a sign-off.
• On approval, turns the request into a fulfillment task assigned to the owning team for that item, and tracks its status from submitted to approved to in-progress to done.
• Dedupes so the same person can't open two identical open requests for the same item by accident.
• Exports a clean CSV of approved requests in the exact columns your fulfillment process (or procurement, or your ticketing system) expects.

What's inside the Implementation Plan

The plan is a single markdown file you paste into Claude Code (a free AI coding agent). It walks the agent through building the whole tool, step by step, each step ending with a ready-to-paste prompt.

The most important part: the plan opens by interviewing you about your business. Before it writes a single line, the agent asks which services you actually offer, the real required fields and naming conventions for each one, who approves what (and above which cost), which team fulfills each item, your typical and peak request volumes, and your messiest edge cases (an office move that touches IT, facilities, and security at once; an urgent request that needs to skip the queue; a requester filling it out on someone else's behalf). It reads a short tailored spec back to you, you confirm it, and only then does it build - so you get a catalog shaped to your services, not a generic template you have to bend to fit.

Inside you'll find:

• The discovery interview and how the agent turns your answers into per-item forms and routing rules.
• The full build: database, login, the catalog browser, the per-item dynamic forms, the approval gate, the fulfillment task board, and status tracking.
• The cost/approval threshold logic and the duplicate guard.
• Verification steps so you can prove it works, and the CSV-export fallback so it's fully usable even before you connect it to any existing ticketing or procurement system.

The governance it includes (this is the point)

This isn't a toy. The plan builds in the controls a shared-services team actually needs:

• Login so only your organization can see or touch anything.
• Row-level security so people only see the requests and catalog data that belong to your organization.
• A complete audit trail - every submission, approval, rejection, assignment, status change, and export is logged with who and when.
• A hard human-in-the-loop gate - a request becomes a fulfillment task only after the item's designated approver reviews and approves it; nothing is auto-fulfilled.
• Cost/approval thresholds enforced in code - an over-threshold request physically cannot become a fulfillment task without its approval.
• Duplicate guards so the same requester can't open two identical open requests for the same item.

Who it's for

IT and facilities service-desk owners, shared-services and ops managers, and anyone who runs an internal "please request things here" function and is drowning in incomplete, unapproved, hard-to-track requests. You don't need to write code. You need your list of offered services (with their fields, cost, approver, and fulfillment owner), and an afternoon-to-a-weekend.

You've got this - paste the first prompt and let the agent interview you.