for clients

first customers · september 2026

What you buy. What you bring. What you decide.

Reference offers for the first customers, the first step, and what stays on your side of the table. The exact scope and price come out of the readiness study.

Talk to us The four offers

§01 who it is for

01 / 06

A recurring operation, with or without agents already running.

One workflow worth putting into production, an owner who can say what correct means, and systems we can be given access to.

01 a recurring workflow

Order intake, refunds, collections, account adjustments, exceptions

Work that arrives every day, follows rules, touches two or three systems and is done by people today. The kind where minutes per case and cases reopened can be counted before and after.

02 agents already running

A pilot that stalled, a platform that was bought

An automation that grew past what anyone tests, a deployment that was rolled back. Recovery starts from the agent’s own cases, inside the access you already grant it.

03 regulated operators

Where the approval and the rule must be on the record

Financial services and other supervised sectors: the workflow owner and Risk approve, Compliance agrees, the evidence is attached to your change record, and on-call stays yours.

§02 what you buy

02 / 06

A defined result and a clear scope of operation.

Four offers. Setup is priced once; operation monthly; inference at cost on your own keys. Each ends in a decision that is yours.

scene 02 the point of action

allowed · held · refused

Scene 2 · what operation looks like: each action evaluated as it arrives. Most pass, some wait for a person, one is turned back. Illustrative sequence.owno.ai

offer	duration	what you receive	decision at the end
Readiness studyworkflow economics and readiness	2–3 weeks	Baseline, access map, acceptance criteria, costed plan. Valuable even when the answer is “do not automate”.	implement, narrow or stop
Implement and launchone bounded workflow	8–12 weeks after access	Adapters, executor, tests from real cases, runbook, supervised launch. Deposit at signature.	accept the production scope
Operate and improveone workflow in operation	monthly	Included cases, service window, review workload, change budget. Inference at cost. Human review priced, never implied.	renew or resize on measured value
Recover an existing agentknown workflow, authorised intervention	by scope	Failure map, acceptance set, targeted correction, release evidence.	continue as bounded improvement

the rule

First-year fees stay under half the cost your operation stops having

If the numbers from the readiness study do not clear that bar, the right answer is not to do it, and the study says so. Reference bands for the first customers are shared in the first conversation; the exact price comes out of the scope.

what is not in the price

Nothing implied

Inference runs on your own provider keys and is shown at cost. Human review is counted in hours and priced. A second change of scope is priced on its own. There is no per-seat fee and no charge per agent.

§03 the first step

03 / 06

Start with one decision you can inspect.

The readiness study is useful even if the conclusion is not to automate. Two to three weeks, five outputs, one decision.

01 baselineVolume, cost, human minutes, exceptions. The numbers the result will be measured against, agreed before any work.
02 concrete scopeOne channel, one catalogue, what stays manual. A bounded workflow, not a programme.
03 access mapSystems, APIs, test environments, who authorises. The delivery clock starts when this exists.
04 costed planDeliverables, timing from access, price. What the launch will contain and what it will not.
05 go / no-goA clear decision, yours, with the numbers on the table.

§04 already have agents?

04 / 06

Already running agents? Recovery starts from what exists.

The hard cases arrive after the demo: incomplete context, rules that change, tools that fail. The problem is rarely the model.

01 what blocks wide use

Integration, supervision, evaluation or data

A failure map from the agent’s own cases says which one. Most rescues are not a model change.

02 execution joined to the outcome

What the agent did, joined to the ERP, the CRM, the finance system

Until the join exists, “working” is a guess. The case record is the number.

03 every change with a test

Hard cases preserved, versions compared

The cases that broke it become the acceptance set. Critical failures are counted apart.

04 in your environment

Inside the agreed access, without changing platform

The agent stays where it runs; the record goes to your warehouse; the release leaves evidence.

How a rescue fits the implementation, from readiness study to operation, is on the implementation page. Implementation →

§05 what to bring

05 / 06

Which workflow do we look at first?

Bring the process owner, a representative sample and the current cost. One working session sets the next decision.

who

The process owner, and who authorises the next step

The person who can say what a correct result is, and the person who can say yes to the readiness study.

what

Ten to twenty real cases, with the outcome they had

Including the ones that went wrong. They become the first acceptance set, and they are what the study is priced on.

how much

Today’s cost, or the bottleneck nobody measures

Minutes per case, people on it, the queue that waits. If nobody knows, that is the first finding.

§06 data, access and evidence

06 / 06

What stays on your side of the table.

The answers procurement, security and compliance will ask for, before they ask.

Your keysInference runs on your own provider accounts, through the broker, at cost. Agents hold decoys; the real keys stay inside owno.
Your warehouseThe case record and the ledger live in your data warehouse. owno works on them; it does not take them.
Your tenantData does not leave your environment. owno signs the same data-processing terms as any processor, and names its sub-processors.

AccessNominal, temporary and logged. Inside the map agreed in the readiness study, and revoked with proof when the engagement ends.
AuthorityWhich steps run alone and which wait for a person is your policy, set by the workflow owner and enforced at the action. Human review is priced, never implied.
EvidenceRelease evidence and signed packets: the agent’s history, its owner, its rules, its tests, the incidents and their remediation, verifiable without an owno account.

§06.1

Terminated is not finished until the keys are revoked with proof.

the first step

OWNO-WEB-1.2 · 2026-09-09

Start with one decision you can inspect.

The process owner, ten to twenty real cases and today’s cost are enough for a first session. A readiness study of two to three weeks turns them into a baseline, a scope, an access map, a costed plan and a go or no-go.

Talk to us How an implementation runs

owno.ai · São Paulo