Business

Who says yes, and when.

Rules that decide what needs sign-off, an approver sequence, and a queue where requests wait — with the history kept.

A purchase over a limit, a discount past the maximum, a leave request — each fires a rule, lands in an approver's queue, and either goes through or comes back with a reason. Nobody chases a signature on a printout.

Get started All of Business
  • Rules with conditions and thresholds
  • An approver sequence, not a single bottleneck
  • A queue for each person, and a history

The approvals home

Yours, pending and resolved.

My queue

What is waiting for you, oldest first or most urgent first.

Pending

Everything in flight across the business, with who it is waiting on.

Resolved

Approved and rejected, by whom and when, filterable by period.

Only mine

Requested by me or approved by me — the personal trail.

Everything inside Approvals

One rule is enough to start. Add conditions and sequences as the business gets particular.

Approval rules

A rule fires on an action — a purchase, a discount, a request. Give it conditions and it applies only when they are met.

Conditions

Amount over a figure, a specific supplier, a specific contact, a specific team member. Combine them or take any.

Priority

When several rules match, the higher priority wins — or the highest only, if that is the policy.

Approver sequence

One approver, or several in order. The request moves to the next only when the previous has said yes.

Restrict to one person

A rule that applies only to one team member, one supplier or one contact — the exception, written down.

New request

Raise something for approval directly: what it is, the amount, the priority, and why.

Urgent and high

Priority on the request itself, so the queue is not first-come-first-served when it should not be.

Comments

Add context when you raise it; add a comment when you decide it. The reason travels with the decision.

Approve or reject

A decision with a comment. Rejected comes back to the requester; approved lets the action proceed.

Requested by, resolved by

Both names on the record, with the dates, for as long as the business exists.

Sort and filter

By date range, type, status, priority — newest or oldest first.

Export history

The approval trail for a period as a file, for the auditor or the board.

Raised, routed, decided

A request in three moves.

A request card travelling through two approver avatars with approve and reject chips and a rules panel.
  1. An action fires a rule. Or someone raises a request by hand. Conditions decide whether it needs sign-off at all.
  2. It waits in a queue. With the first approver in the sequence. Priority decides where in the queue.
  3. It is decided. Approved with a comment, and the action proceeds. Rejected, and it goes back with the reason.

Where the work happens

Three of the places you will spend time in Approvals.

Pending request cards stacked with priority flags and one lifted to the front
The queue — what is waiting for you
A rule panel with condition rows and a threshold dial pointing at an approver
Rules, conditions and thresholds
Resolved request cards with approved ticks, a date-range chip and an export document
The history, exportable

Works with

What fires an approval.

PurchaseOrders over the limit SalesDiscounts past the maximum HRLeave and expense requests AccountingPayments that need a second signature

Free to start. Friendly to scale.

Start with what you need today and switch the rest on when you grow.

Get Started