Approvals that live where you already work
Describe your approval process to your AI. Branchsolve routes every request, records every decision, and lets people approve without opening another tool.
Free to get started. No credit card, no builder to learn.
Purchase request
$12,400 · New CNC tooling
- 1Queued
Manager
Dana Whitfield
- 2Queued
Finance
Sam Okafor
- 3Queued
CFO
Priya Raman
Routed by amount and category. Nobody configured this chain — it came out of the workflow’s own conditions.
The problem
Every company runs approvals. Most just slow things down.
The spreadsheet
Limits and delegations live in a tab someone maintains by hand. It is out of date the week after it is written, and nothing enforces it.
The email thread
Approval happens by reply-all. Six weeks later nobody can say who agreed to what, or whether the person who agreed was allowed to.
The six-week build
The proper fix needs a platform team, an environment and a licence. So the process stays broken, because fixing it costs more than living with it.
How it works
Four steps. None of them involve a canvas.
There is no builder, no drag-and-drop, and nothing to certify on. You describe the process; the AI writes the spec that runs it.
- 01
Describe it
Tell your assistant how approvals work today, in your own words. Thresholds, who signs off, what happens when nobody responds.
- 02
See where requests land
Before anything is live, the simulator derives the boundary cases from your own rules and shows you exactly who gets each one.
- 03
Publish
One confirmation. The workflow is live, versioned, and your team can submit against it immediately.
- 04
Approve in chat
Requests reach approvers where they already work. They decide without opening another tool, and the record lands in Branchsolve.
See it before you ship it
Know where requests land before the first one is submitted
Branchsolve reads the workflow’s own conditions and works out the cases that sit either side of every threshold. Nobody told it about $99, $1,000 or $10,000 — those came out of your rules.
It also warns you when a workflow would let something through with nobody approving it. That is the check most approval processes never get.
How routing worksSimulation · Purchase approval
$99Approved on submissionUnder the threshold$100ManagerFirst threshold crossed$1,000ManagerFinanceSecond threshold$10,000ManagerFinanceCFOThird threshold$10,000 + contractManagerFinanceCFOLegalLegal joins in parallel
Watch
Two minutes, start to finish
From describing a process to approving a real request in chat.
Reporting
Ask your AI anything about your work
No dashboard to configure, no report to build, no analytics seat to buy. Ask the question the way you would ask a colleague, and get an answer from live data.
This is what being AI-native actually buys you: the reporting gets better as the models do, without you upgrading anything.
Claude · Branchsolve connected
What's stuck with Finance over $10k?
Three requests. The oldest is CNC tooling at $12,400, waiting four days on Sam Okafor. Two others cleared Finance this morning.
What you get
A workflow engine that refuses to guess
The AI writes the spec. It never writes code, and nothing it produces is trusted — every workflow passes the same checks a hand-written one does.
Authored in conversation
Describe the process the way you would to a new hire. The AI writes a spec; you review where requests will land, then publish.
Routing you can predict
Conditions are checked when the workflow is written, not discovered six weeks later. A rule that reads a field you never collected is refused.
An audit trail nobody can edit
Decisions are append-only. Not even an administrator can change one. A correction is a new decision with its own actor and timestamp.
People and access, separated
Routing roles decide who does the work. Access roles decide who can change things. Confusing the two is how permissions rot.
Documents on the request
Quotes, certificates and signed PDFs attach from the app or from chat, readable only by people on that request.
Versions that hold still
A published workflow is immutable. Change it and in-flight requests finish on the version they started on.
Who uses it
If you can describe it, Branchsolve can run it
There is no template library to fit into and no list of supported processes. That is why it works the same for a twelve-person shop and a twelve-thousand-person enterprise.
Not on the list? That is rather the point. Tell us your process.
Trust
Get out of email
Approvals stop living in threads. One place, one record, one answer to “who approved this?”
How we handle securityNobody approves by email
There is no approve-by-reply link to forward, spoof or click by accident.
Opening is not deciding
A notification shows the request. Deciding takes a deliberate action from a verified identity.
You can't approve your own
Separation of duties is enforced by the engine, not left to whoever wrote the workflow.
Nothing is quietly edited
Decisions are append-only, and an AI's decision is never shown as though a person made it.
Describe your first workflow this week
We’ll set up your workspace, connect it to Claude, and walk through one real approval with you. Free to get started.