← All blueprints
Approval Workflow
Purchase requests get lost in Slack, and nobody knows who approved what.
A short request form, a defined chain of approvers, and a decision screen that works on a phone. Every decision is recorded.
- No.
- 007
- Department
- Ops
- Build time
- 1–2 hrs
- Difficulty
- Intermediate
- Team size
- 5–100 people
- Replaces
- Kissflow
Parts
- 1
Request
What, why, how much and by when, in one short form.
- 2
Approve / reject
Approvers get a link and decide in one tap, with an optional comment.
- 3
Approval trail
Who approved, when, and what they said, kept forever.
- 4
Rules
Over a set amount, it goes to finance as well as the manager.
Data model
- Request { title, amount, reason, requested_by, needed_by, status }
- Step { request_id, approver, order, decision?, comment?, decided_at? }
- Rule { min_amount, approver }
Build prompt
Build an internal tool for my team: "Approval Workflow".
The problem: Purchase requests get lost in Slack, and nobody knows who approved what.
Who uses it: a team of 5–100 people.
What it should do:
- Request: What, why, how much and by when, in one short form.
- Approve / reject: Approvers get a link and decide in one tap, with an optional comment.
- Approval trail: Who approved, when, and what they said, kept forever.
- Rules: Over a set amount, it goes to finance as well as the manager.
Data:
- Request { title, amount, reason, requested_by, needed_by, status }
- Step { request_id, approver, order, decision?, comment?, decided_at? }
- Rule { min_amount, approver }
Constraints:
- Built for one team inside one company. Simple sign-in (or none), no billing, no multi-tenant setup.
- Fast, calm and obvious enough that teammates need zero training.
- Data must persist and be shared across the team.
- Ship the simplest version that works, then tell me what you'd add next.Works with Claude, ChatGPT, Cursor, Lovable, Replit or Type.
Variations
- Use it for time off, discounts or contract sign-off
- Reminders after 24 hours of no decision
- Monthly export of everything approved
A new blueprint every week
Sent on Sundays. One tool per email.
More blueprints
Client Onboarding Tracker
Client onboarding lives in one person's head, and things fall through the cracks.
- No.
- 006
- Dept.
- Ops
- Build
- 1–2 hrs
- Replaces
- Rocketlane
Project Status Board
Every Monday I rebuild the same status report from scratch.
- No.
- 008
- Dept.
- Ops
- Build
- 1 hr
- Replaces
- Monday.com
Simple CRM
We pay for a giant CRM and use about ten percent of it.
- No.
- 001
- Dept.
- Sales
- Build
- 2 hrs
- Replaces
- HubSpot