Submitters are free, forever
Anyone can ask for a new laptop
Requester gets it approved.
The system of record for requests and approvals. Your team asks in plain English; Requester routes each request to the right people, chases the ones that stall, and keeps a trail finance can stand behind.
Free plan, no card required. You pay for approvers and volume — never for the people asking.
One request, end to end
- 1
Ask
Type it in plain English — the AI builds the request
- 2
Route
To the right approvers, in the right order
- 3
Decide
One click, from the app, an email, or Slack
- 4
Record
Timestamped, attributed, and audit-ready
No training required. If they can send a message, they can use it.
This is what informal approvals actually cost
Chat tools were built for conversation, not for decisions that need a record attached. Every one of these is a normal Tuesday in a company that hasn’t written its process down.
The request nobody can find
Someone sent a purchase request in the group chat three weeks ago. It got buried under two hundred messages and nobody actioned it — now they're asking why nothing happened.
The approval with no paper trail
A decision got made on a call; someone said yes in passing. Three months later, nobody can say who approved the vendor contract, or when, or on what basis.
The follow-up that shouldn’t be your job
You sent a request to your manager four days ago. No status, no timeline, no idea whether they even saw it — so you end up chasing it down yourself anyway.
Ask. Decide. Done.
Every stage of the approval lifecycle, run for you — including the two nobody wants to own: the chasing and the record-keeping.
- 01
Ask
Type what you need. The AI asks the follow-ups an approver would and builds a complete request.
- 02
Route
It goes to the right approvers — by team, by group, by name, or conditionally on what was answered.
- 03
Decide
A clear card: what's asked, what it costs, what the AI suggests. One click, from anywhere.
- 04
Done
Reminders chase the slow, escalations catch the stuck, and the record writes itself.
Setup · AI workflow generation
Describe your process. Get a working workflow in seconds.
You know you need a real approval process, but building one means forms, spreadsheets, or an IT ticket — so it keeps getting pushed to next quarter.
- “Purchases over $500 go to my manager, over $2,000 also need finance.”
- That sentence generates the form, the branches, the routing, and the reminders
- Everything it produces is editable — nothing is locked to the generator
Decide & done · Routing & reminders
Nobody has to chase anybody. The process runs itself.
You send a request and sit in limbo — no status, no timeline, no idea whether to follow up or whether following up makes you the annoying one.
- Routed to the right person automatically, with cover when they're away
- Auto-reminded if it stalls past your window, then escalated to admins
- The submitter is notified the moment it's decided — and can watch it in the meantime
Submitted
Sarah K.
Manager review
Alex M.
Finance review
Jamie T.
Six surfaces, each with real depth
“Approval software” hides an enormous amount of detail — and the detail is what decides whether your team actually adopts it. Each of these is a page of its own.
Intake & forms
27 field types, conditional logic, and six ways a request can arrive.
Approvals
Any, all, or N-of-M — decided in-app, from email, or by outside guests.
Workflow automation
A visual canvas for routing, branching, delays, SLAs, and webhooks.
AI
Draft requests, generate workflows, summarize, and route — natively.
Tracking & audit
Dashboards, analytics, a full audit log, and shareable status pages.
Integrations
Slack, Teams, Discord, Google Chat, webhooks, Zapier, and the API.
Start with the process that annoys you most
Each page walks one real request through Requester end to end — the actual fields, the actual routing, the actual record at the end.
Purchase approvals
Spend requests routed by amount, approved with the numbers attached.
IT access requests
Tool and permission requests with an auditable grant history.
Time off & HR requests
Leave, equipment, and people requests that stop living in DMs.
Vendor onboarding
Collect vendor detail, route legal and finance sign-off, keep the file.
Expense approvals
Receipts, amounts, and cost centers captured before anyone decides.
Client & external intake
A public link that turns outside requests into tracked work.
Or start from one that already works
Proven request forms for purchases, access, leave, vendors, and expenses. Clone one into your workspace and edit it freely — it becomes yours.
Four teams, one recurring complaint
Finance, IT, operations, and people teams all end up as the bottleneck on decisions they never wanted to own personally.
Approvals fail at the edges
The one field nobody collected. The approver on leave. The outside vendor with no login. The breadth is the product.
- 27
- Field types, from currency and signature to data grids and member pickers
- 9
- Workflow node types: approvals, branches, delays, emails, webhooks, statuses
- 8
- Chat and webhook integrations, including interactive decisions in Slack
- 0
- Seats consumed by the people submitting requests, on every plan
The honest answers
- Is it actually free?
- Yes — a free plan with three approver seats and no card required. Paid plans add volume, advanced fields, analytics, and audit logs when you outgrow it. Multi-step approvals and conditional logic are included on every plan.
- How fast until my team sees value?
- Describe a process in plain English and you have a working workflow in seconds. From then on your team just types what they need — no quarter-long rollout, no training deck, no change-management project.
- Will my team actually adopt it?
- If they can send a message, they can submit and approve a request. Requests can also arrive by AI draft, public link, or inbound email — so the person who will never change how they ask still ends up in the same queue.
- What about people outside the company?
- They submit through a tokenized public link and approve by email, both without an account and without consuming a seat. Their decisions still land in the audit log, attributed to them.
- Where does our data go?
- Into a workspace isolated by row-level security, and out again whenever you want it. The full export is one JSON file with every team, template, request, answer, comment, and decision. No lock-in.
Ask for what you need. Get it approved.
Out of the group chat and onto the record. Describe one process, send one real request, and see what your current approach has been costing you. Free to start, no card required.