Product overview

Everything between “can I?” and “it’s done.”

Requester takes a request from the moment someone needs something to the moment it’s decided and on the record — with the intake, routing, approvals, and audit trail that journey actually requires.

Free plan, no card required. Submitters are always free.

What one request carries

Intake
27 field types, conditional logic, multi-page forms
Routing
Team, group, named approvers, or conditional branches
Rules
Any / all / quorum (N-of-M), mandatory or optional
Channels
In-app, email decision links, Slack, guest magic links
Record
Audit log, AI decision narrative, workflow map
Every row here is shipped and reachable in the product today.
01The lifecycle

One path, four moments, nothing improvised

Most tools cover one of these well and leave you to glue the rest together in chat. Requester runs the whole loop, which is the only way the record at the end is worth anything.

  1. 01

    It gets asked

    Someone submits a form, describes the need to the AI, emails it in, or files it through a public link. Nothing gets lost in a thread.

  2. 02

    It gets routed

    The workflow sends it to the right approvers in the right order — by team, by group, by name, or conditionally on what was answered.

  3. 03

    It gets decided

    Approvers decide in-app, from an email button, or in Slack. Any, all, or N-of-M. Guests can decide without an account.

  4. 04

    It stays on record

    Every action is timestamped against a person. The AI writes a readable decision record and the audit log keeps the raw history.

03By the numbers

Built wide, on purpose

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
16
Notification types across in-app, email, push, Slack, and five more channels
12
Permission verbs resolved in one capability layer, not scattered across routes

Run one process on it this week.

Pick a template, describe your approval rules in plain English, and send your first request today. The free plan needs no card and your submitters never cost you a seat.