Purchase Requisition Intake & Approval Router

The problem this kills

Right now "can I buy this?" lives in your inbox. Someone emails a request, you eyeball whether it needs a manager or a director, you forward it, you wait, you chase, you forward again, and three days later you finally have a yes you can act on. Nothing is validated up front, so half the requests are missing a cost center or a need-by date. There's no record of who approved what, the same request gets submitted twice under slightly different wording, and your ERP import is a copy-paste job that breaks the moment a column is out of order.

That's not a person problem. It's a missing tool problem. You need a single front door for purchase requests that checks the request the moment it's submitted, knows your own approval rules cold, routes to the right people automatically, and refuses to create an "approved" requisition until every required sign-off is actually recorded.

What you'll build

A small web app, tailored to how your team actually buys, that does the whole intake-to-requisition loop:

• A clean requester form (item, quantity, estimated cost, cost center, category, need-by date, suggested supplier, justification) that validates as you go.
• Master-data checks against your uploaded cost-center list and category list, so nothing slips through with a bad code.
• An approval-matrix engine that reads your own thresholds (by amount band, category, and cost center) and computes the exact chain of approvers required for this request.
• In-order routing: each approver is notified, reviews in-app, and clicks Approve or Reject with comments. Reject re-routes back to the requester. Stalled approvals get reminder emails.
• A hard commit step: only when every required approval is recorded does the request become an approved requisition of record, with a unique requisition number.
• A CSV export in the exact column order your ERP's requisition import expects.

What's inside the Implementation Plan

• It starts by interviewing you about your business. Before any code is written, the plan has the AI agent ask you about your current process, your real cost-center and category codes, your approval thresholds, your typical and peak request volumes, and your messy edge cases. It reads back a short tailored spec, you confirm it, and only then does it build. You get a tool shaped to your buying rules, not a generic template you have to bend to fit.
• The full data model for requests, approval matrix, cost centers, people/roles, approvals, and the audit log.
• Step-by-step build instructions, each ending in a ready-to-paste prompt for your AI coding agent.
• The approval-chain logic explained in plain language so you can sanity-check it.
• The "No API yet?" fallback: pull your matrix and cost centers from a Google Sheet and export approved requisitions as a CSV your ERP can import today, with zero integration work.

The governance it includes (this is the point)

This isn't a toy form. The plan builds in the controls procurement actually needs:

• Login so only your team can submit or approve.
• Row-level security so people only see their own organization's requests.
• A complete audit trail: who submitted, who approved or rejected, with what comment, and exactly when.
• A hard human-in-the-loop gate: the AI validates and drafts the routing, but a named person must click Approve in-app. Nothing becomes an approved requisition or reaches procurement until every required approval is recorded.
• Duplicate guards: the same requester + item + cost center + need-by inside a 24-hour window is flagged before it can be processed twice.

Who it's for

Procurement coordinators, office and operations managers, and department admins who today collect purchase requests over email and chase approvers by hand. If you understand your own approval rules but you're not a developer, this is for you.

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