Closed beta. EU finance and operations teams.
Hand over the routine. Decisions stay with you.
Start with one recurring job, such as matching invoices to purchase orders. It handles the routine cases, brings decisions back to you, and records every step.
- IntakeDocuments, email, records
- ProcessHandles routine cases
- ValidateChecks against the source
- ApproveYou decide what may leave
- ActCarries out your decision
- RecordLeaves a receipt
What changes on your desk
Routine cases move. Decisions return with context. Every result leaves a record you can inspect.
Routine work moves. Decisions stay.
The workflow is built to stop for you.
Where it stops for you is decided when the workflow is built, not by whoever set it up, so it cannot be left out. You see what is about to happen and choose whether it should proceed, and you can allow routine cases to continue without asking again.
It gets quieter the longer you use it.
Once you confirm how a recurring case should be handled, it stops asking, within the work it was set up for. A correction replaces the earlier answer without erasing it, and agreeing to one action is never agreeing to a standing rule.
Interruptions arrive ready to decide
The reason comes with the request.
You see what triggered the stop and what the workflow needs from you.
The result stays inspectable
The workflow follows the agreed route.
Its steps are fixed before a run. It cannot invent a new step midway through the job.
Each step does one job.
The work is split across steps that each do one thing, so a step can be checked on its own: it sees exactly what it was given, its result has to fit a fixed shape before it moves on, and anything that can be worked out — a sum, a comparison against a rule — is handed to a tool instead of written out in words. A narrow job also does not need a large model, so each step runs on the smallest one that can do it.
Every step leaves a receipt.
The record shows the steps, what they read and wrote, and what the run cost.
A document cannot change the rules.
A document can supply information, but it cannot change where the workflow writes, what it remembers, or where it stops for you.
How it works
Start one of two ways: import a ready-made automation from the library, or describe the recurring problem in your own words. You review the workflow before it runs.
Choose how to start
Import a ready-made automation from the library, or explain the job: “Match each invoice to its purchase order and flag exceptions.”
Review the workflow
You see what it will do, which systems it will use, and where it will stop for your decision.
Confirm the rules
Once you confirm the rules, known cases can continue. Payments, filings, and other outside actions still come back to you.
Check the result
Every run leaves a receipt with the steps, inputs, outputs, and cost, so you can see what happened without redoing the work.
What you see before and after
The record follows the decision. You do not have to reconstruct the run from a generic success message.
- Before action
The action
What is about to happen and what information will leave the system.
- At the pause
The reason
What triggered the stop and what the workflow needs from you.
- Your decision
Approve, edit, or stop
You choose whether the action should proceed and can correct it before it does.
- After the run
The receipt
The steps, inputs, outputs, and cost remain available for review.
A request should take a look, not an investigation.
When the record does not support an answer, the system says it does not know.
Closed beta
If a reconciliation, invoice-to-order match, or expense review crosses your desk every month, show us the job. We are working with a small number of finance and operations teams who want to shape the product around real recurring work.
Tell us what the job is and roughly how often it runs. That is enough to start a useful conversation.
Or email tudor@sophtus.ro