Product
There is no builder. That is the product.
Every other tool in this category hands you a canvas and a weekend. Branchsolve asks you to describe the process, then does the rest — and shows its work before anything goes live.
The spec, not the code
Your assistant turns a description into a declarative workflow spec — fields, steps, approvers, conditions. It is data, never a program, so nothing generated is ever executed.
The gate
That spec passes a schema check and a type-checked condition grammar. A comparison between a number and a word, or a rule reading a field that does not exist, never reaches a real request.
The renderer
One generic form renderer covers all ten field types, so a workflow written this afternoon looks and behaves like one written last year. Nothing is bespoke.
Routing
Conditions that are checked, not hoped for
Rules are written in a small, sandboxed grammar — comparisons, and / or / not, and a handful of helpers. It is parsed and type-checked, never evaluated as code.
- Keep your workflows bulletproof. Conditions instantly reference data from the request form and previous steps, ensuring every route is dynamic, accurate, and error-free from day one.
- Steps run in sequence or in parallel. A parallel group can require everyone, or anyone from a pool.
- Turn rejections into resolution. Send requests back for edits or close them out completely—with built-in guardrails that keep every process moving smoothly to completion.
Simulation · Purchase approval
$99Approved on submissionUnder the threshold$100ManagerFirst threshold crossed$1,000ManagerFinanceSecond threshold$10,000ManagerFinanceCFOThird threshold$10,000 + contractManagerFinanceCFOLegalLegal joins in parallel
Forms
Ten field types
Enough to describe real work, few enough that every workflow behaves the same way.
- Text
- Long text
- Currency
- Number
- Yes / no
- Choice
- Multi-choice
- Date
- File
- Person
Steps
Three kinds of work
The engine decides which outcomes each kind offers, so you can never record “approved” for work that was merely done.
- Approval
- A yes-or-no judgement from a named person or role.
- Task
- Work someone performs. It finishes as done, not approved, and can be required to collect data first.
- Integration
- Work in a named external system. Today a person marks it complete — so the process can honestly say “then create the PO in the ERP” instead of pretending the handoff is not there.
Questions
Frequently asked
Does the AI write code?
No. It writes a declarative workflow spec, and a generic renderer brings that to life. Nothing the model produces is ever executed, which is why a bad generation is a validation error rather than a security problem.
What if the AI gets the workflow wrong?
Every generated workflow passes the same checks a hand-written one does. A rule that references a field you never collected, or compares a price to a piece of text, is refused at authoring time. Then the simulator shows you where real requests land before you publish.
Can we edit a workflow after publishing?
Yes. You get a diff and a fresh simulation, then publish a new version. Published versions are immutable, so requests already in flight finish on the version they started on.
Do people have to use chat?
No. Branchsolve has a full inbox and request board in the browser. Chat is the fast path, not a requirement — approvals work with every connector switched off.
What happens when nobody responds?
A step can carry an SLA. On breach it can send a reminder or escalate to more approvers. It can also auto-approve or auto-reject, but those two require an explicit second confirmation before they can be published — deciding a request because nobody looked at it is not something a default should reach.