Where we are proving outcomes.
The architecture is not industry-specific. What we publish is: two domains are being operationalised with named operators, and those are the two we will talk to you about today. A third appears here when it is paid for and repeatable, not when it is plausible.
Commerce & retail
The situation
A campaign is signed off centrally, in one language. Six weeks later it is live in three markets, half-right in a fourth, and the product data behind it has been touched by four people across the PIM, the shop, two marketplace back-ends and the spreadsheet marketing actually works from. Nobody can say which version is approved, whether the claim you cleared for Germany is legal in Poland, or whether the copy live on a marketplace still matches the copy live in your own shop.
What we own
One case per campaign or category, from global input to live and measured locally — including the marketplace rejection loops and the local claims approval, with brand-critical sign-off kept in your house. It stays open after go-live, because the expensive version of this problem is week six, when a local team has quietly changed something and you hear about it from a customer.
Where the money is
Launch days lost between “ready” and “approved”. Listings live with wrong local content. Rework nobody books as rework. And the new-market risk you cannot currently sleep through.
Project-based professional services
The situation
A client asks for something in a status call. Someone does it. It is in the timesheet, mentioned in a ticket, and never in a change request. Months later the invoice is disputed — or the project manager simply never raises the change, because he needs the reference — and reconstructing what was agreed costs three people two days. So it gets written off, because that is cheaper than the argument.
What we own
One case per project cohort, from delivered work to approved scope, accepted milestone, invoice and cash. Read-only to start, with no autonomous invoices and no autonomous disputes.
Where the money is
Unbilled delivered scope. Scope absorbed inside a fixed-price envelope, which never becomes a dispute and only ever shows up as margin. Milestones accepted late — which is your DSO, on every invoice behind them. And write-offs taken because assembling the evidence costs more than the amount in dispute.
The approval that produces cash is usually on the client’s side.
Everything on this site about named approvers is about a person in YOUR house. In project work, the sign-off that turns delivered work into an invoice belongs to your client’s project manager — waiting on their procurement, and their finance. We do not touch that, and no gate we run can.
What we produce is the pack that makes their approval fast and hard to dispute: what was asked for, when, by whom, against what was agreed, with every fact carrying the record it came from. That is a smaller claim than “we fix your billing”, and it is the one that is true.
Neither domain has a finished pilot yet.
We are saying so here because the alternative is a page of outcomes that read as delivered and were not. These two domains are where the workflows are designed, the operators are committed and the first pilots are being scoped. When one closes with a measured result, this page gains a link to the workflow and the number it moved — and until then it does not.
Four things, and we will say no without them.
- A sponsor and a bounded case. Someone whose number moves, and one recurring case family rather than a department.
- Data we can read first. An export or a read-only connection. Nothing is written in a pilot.
- A named approver. A person with the authority to release the action, named before we start rather than found afterwards.
- A baseline you agree to. The measure the pilot is judged against, agreed before it runs. Otherwise the result is a story.