Approve the purchase order.
A real decision, made in a chat.
Wosool, a business operating system
Wosool takes over the procedures, starting with purchasing, and leaves the decisions to you.
The problem
Most owners find out where the business stands only when something is late or wrong. The purchase request is in an email, the approval is in WhatsApp, the price is in a spreadsheet, the order number is in the system, and the context is in one person's head. Every operation waits for someone to remember its next step.
Approve the purchase order.
A real decision, made in a chat.
Did the supplier reply?
It's stuck, and no one knows where.
Stock is below the reorder point.
The data is there. Who acts on it?
PO-1042
The record is there. The story behind it isn't.
I know why we did that.
When they're away, so is the story.
Did we order this before?
With no memory, work gets done twice.
What actually happened?
The work got done. Nobody can say how.
The work still gets done.
At a cost: lost time, repeated mistakes, and decisions made on half the picture.
From procedures to decisions
Purchasing, inventory, collections and sales look different, but their days look the same: repeated steps around one decision. Wosool takes the steps and brings the decision to the person who owns it. Try it: pick an operation and hand its steps to Wosool
Click a step to hand it to Wosool
An interactive example. Numbers are illustrative, and nothing leaves this page.
Night, 22:00
Once your main system is connected, anything allowed to run on its own runs overnight and is recorded. Anything that needs you waits for the morning. Built, not yet proven in production.
One night in WosoolExample. Built, not yet proven in production
Three steps ran on their own. Two decisions are waiting for you. Nothing else happened.
In the morning, two decisions are waiting for you, each on its own card.
What runs on its own, and what waits for you
Not every step needs you. Every action in Wosool has a declared risk level. Low-risk steps inside Wosool run on their own and are recorded. Anything that leaves your company or writes to your system waits for a signed card.
Reading inventory from your main system.
Opening an operation, updating its status, preparing its card.
A request for quote sent in your company's name, a purchase order in your system.
Recording a payment confirmation.
Any action without a declared risk level is treated as high risk and waits for a signature.
Who proposes, who decides, and who executes
This isn't a technical detail. It's why you can trust what happens in your business: no AI model executes anything by itself. A person signs every decision. Only the low-risk steps your policy allows run without a signature.
Understands, gathers the context, and proposes the step. It executes nothing itself: anything that writes to your system, sends in your name, or records a payment waits for a person's signature.
Reads the card, then signs or declines. The decision carries their name and the time, and it stays on record.
Executes what was decided, in the system that owns the change, and records what it did.
It prepares the step and shows the source.
A card appears, and nothing happens before you sign.
It declines the step, and the declined step changes nothing.
It is recorded with the operation, with its time and its status.
Where we stand
Each line says how far it has been proven, and where the evidence is.
| Capability | Status | Proof |
|---|---|---|
| A purchase on a real company, from the need to "the price is in" | Proven in production, 8 to 10 September 2026 | Run end to end in production |
| A person signs every decision. Only the low-risk steps your policy allows run without a signature. | Proven in production on 8 September 2026 | Run end to end in production |
| An explicit decline when information or identity is missing | Proven in production on 10 September 2026 | A documented refusal, in the product's own words |
| Every data set shows which system it came from, and when it was last read | Built, not yet proven in production | Built for Odoo and Daftra |
| Payment confirmation, receiving, and closing the operation | Built, not yet proven in production | No proof in production yet |
| Operations other than purchasing | Later | No proof yet |
Last updated 26 September 2026, from the last recorded state.
Start with one real operation in your business, and we'll prove it with you.
A business operating system. It gathers work scattered across email, messages, files and systems into clear operations, prepares each one until it reaches you as a single decision, then executes what you decided and keeps the record.
It doesn't replace your accounting or inventory system. It runs on top of them, and runs each process across the systems and channels you already use.
An ERP keeps your records. An integration tool moves data between systems. An automation tool runs a fixed rule. Wosool runs the whole operation on top of them: it gathers the context, knows who owns the decision, waits for a signature where it must, then executes and keeps the record.
Any business where the same operations repeat every day, like purchasing and inventory, spread across people, systems, channels and files. Small or large.
NILScript is the open research behind Wosool: a language and protocol for describing business actions so they can be governed. Read about it at NILScript.org.
It tells you what's missing, instead of guessing or doing something it wasn't authorized to do. The step it declines changes nothing.
Wosool is built to run on top of Odoo and Daftra, as you have them today. We set up the connection with you before we start. If you use another system, we check it with you first, and tell you plainly whether we can work with it.
Nothing is written to your system or sent in your name without a signed card, like a purchase order after it's approved, except the low-risk steps your policy allows. Everything else is a read.
Your business data stays in the system you choose as its owner: your Odoo or Daftra, or Wosool itself. What Wosool keeps is set out in detail in the Trust Center.
That's exactly how we start: one real operation in your business. We expand once you've seen it work.
It takes the chasing, follow-ups and hand-offs off your team's plate, and leaves the decisions that need a person with a person.
Tomorrow morning, 07:30
You open Wosool in the morning and find the decisions that need you, each on its own card. We start with one operation from your business, on the systems you already use.
A world where businesses run themselves.