Steps and owners
Each step has one owner: a person, a role, or a named AI associate. There is always someone to ask.
AI Business Process Studio · preview
Draw the process once. Let it run every time.
Describe how work should flow in plain words. The Studio drafts the steps, the owners, the approvals and the gates, and publishes it as a workflow people and AI associates run together.
Try it
A sentence in, a process out.
Here is a refund process drafted from one sentence. Four steps go to AI associates, two to people, and the two gates sit exactly where judgment matters.
Describe the process
When a customer asks for a refund over $500, check the order, get a manager’s OK, pay it, and tell the customer.
✓ Drafted: 6 steps, 2 gates, 4 AI associates, 2 people
- 1Take the requestReads the message, opens a cardAI associate
- 2Check the orderReads the orders brainAI associate
- 3Approve over $500Poll · 24 h · recommended answer markedManager
- 4Pay the refundWithin the finance budgetAI associate
- 5Tell the customerMessages · in their languageAI associate
- 6Review and scoreNot the doer · 1 to 5Reviewer
Describe it
Start from what you would tell a new hire.
No diagrams to learn and no notation to master. Say what happens, who decides, and what counts as done. The Studio asks about anything it cannot infer, instead of guessing.
- Drafts steps, owners and hand-offs from plain language.
- Flags a missing owner, approver or definition of done.
- Keeps your words next to the draft, so the intent is never lost.
Staff it
People where it takes judgment. AI associates where it takes stamina.
Assign each step to a person, a role, or a named AI associate. AI associates work over MCP with their own token, under the same rules as everyone else, and every action is on the record.
- Swap an owner without redrawing the process.
- Mix people and AI associates within one process.
- Each owner sees only what their role allows.
Guard it
Gates where they matter, and nowhere else.
An approval is a poll with a deadline and a recommended answer. The reviewer is never the doer. Spending runs against a budget. Anything destructive asks first and records how it will be restored.
- Approvals that do not stall: silence adopts the recommended answer on routine matters.
- Reserved decisions always wait for an explicit answer.
- Every gate leaves a line in the audit trail.
Publish it
Versioned, measured, improved.
Publishing turns the draft into a live workflow on the board. Each run is a card you can follow. Scores and cycle times show where the process works and where it needs another pass.
- Versions never touch work already in flight.
- Lead, cycle and review times, per process.
- Star a process to follow every run.
In the Studio
Everything a process needs to be trusted.
Approvals as polls
A decision is a poll with a deadline and a recommended answer, asked on the card where the work is.
Budgets per process
Each process spends from your organization’s budget. Admins are warned at 90% before anything stops.
Context from the brains
AI associates read the organization brain for the facts a step needs, and record what they learned.
Reviewed by someone else
The last step is always a review by someone who did not do the work, with a score from 1 to 5.
Versioned
A published process has a version. Changing it never changes work already in flight.
Your board is waiting.
Arishem is invitation-only. Accept your invitation to join, or sign in with a code by email or text, or with Microsoft Entra ID.