[ 01 ]
The demo, not the workflow
A demo handles the clean case. Real work has missing customer numbers, odd PDFs and exceptions. An agent without a plan for them creates more work than it saves.
[ AGENTIC WORKFLOWS & PROCESS AUTOMATION ]
Stop retyping. Let an agent draft it and a person approve it.
Orders, invoices, tickets and reports eat hours every week, and the rules live in a few heads. We build an agent that does the routine in your environment, hands over what it is unsure about and logs every step.
Human in the loopRuns in your environmentEvery step logged
[ 01 — WHERE IT GOES WRONG ]
Why agent projects usually stall.
Most agent demos work. Most agent projects stall between the demo and Monday morning.
- [ 02 ]
Nobody owns it
Without a named owner, nobody watches the output. Prompts drift and trust fades after the first wrong answer. - [ 03 ]
Too much freedom, too soon
An agent that can send, pay or delete on day 1 makes IT say no, and rightly so. Access has to be earned by the numbers. - [ 04 ]
No baseline
Without a before number, nobody can say whether it worked. The pilot never ends, or it gets killed by opinion.
[ 02 — WHAT YOU GET ]
The guardrails are the product.
The model is the easy part. The work is in what the agent may do, when it hands over and what happens when it does not know.
- [ 01 ]
The workflow
One agent per routine, connected to the mailboxes, files, ERP or ticket system it needs. It runs in your tenant or a cloud you choose. - [ 02 ]
Guardrails
What it may read, what it may write and what it never does alone. Configured and tested, not hoped for. - [ 03 ]
Human approval
Sending, paying, deleting and committing stay with a person. The agent prepares, people decide. - [ 04 ]
Own identity and full log
Every agent works under its own controlled identity, so each action traces back to an actor and a time. - [ 05 ]
Documentation and owner
Sources, prompts, owner and an off switch, written down and handed over. No black box to inherit.
[ 03 — HOW WE DE-RISK IT ]
How niivo takes the risk out.
Each risk above has a specific counter-measure built into the pilot.
- [ 01 ]
Drafts first
The pilot starts with drafts. A person approves every case, and rights widen only as the numbers justify it. - [ 02 ]
Own identity, least privilege
The agent works under its own identity in your tenant, with only the access its routine needs. worxspace's ops team can run identity and permissions. - [ 03 ]
Baseline and a decision
The before number is measured, the number to beat is agreed in writing and after 4 to 6 weeks you decide: go, extend or stop. - [ 04 ]
Nothing to inherit blind
Sources, prompts, owner and off switch are documented and handed over. Your team can run it, or we can under a separate agreement.
[ 04 — PROCESS ]
Proven small, then shipped for real.
No agent goes live without a pilot, a baseline and a go decision. If it does not pay off, we stop it.
- 01
From the audit
The workflow with the most hours saved becomes the pilot. Scope, baseline and number to beat are agreed in writing.1 week - 02
One workflow, one agent
The agent drafts, a person approves every case. A weekly update shows volume, corrections and time per case.4 weeks - 03
Go, extend or stop
We compare the pilot with the baseline and you decide. Running costs are stated before you do.1 session - 04
Production
Monitoring, audit trail and a monthly review of what the agent did. Approval steps loosen only when the data supports it.Ongoing
[ 05 — USE CASES ]
Routines that fit.
Typical workflows. None of these describe a specific client.
Order intake
- Today
- Orders arrive as mails and PDFs and are retyped into the ERP.
- With the workflow
- The agent reads the mail, drafts the ERP entry and waits for approval. Without a customer number it stops and hands over.
Invoice matching
- Today
- Finance matches supplier invoices to purchase orders by hand.
- With the workflow
- The agent matches, flags differences over a set tolerance and queues the postings for a person to approve.
Ticket triage
- Today
- First-level support reads and routes every incoming ticket.
- With the workflow
- The agent tags, prioritises and drafts a first reply. A person sends it or takes the case.
Weekly reporting
- Today
- Someone collects numbers from four systems every Monday.
- With the workflow
- The agent assembles the report and lists the gaps it could not fill. The owner reviews and publishes.
[ 06 — SCOPE & PRICE ]
A pilot first. Then a decision.
Put the pilot price next to what the routine costs today: hours per week times your hourly rate, taken from the audit baseline. If the routine costs less than the pilot, we tell you not to build it.
Agentic workflow pilot · 4 to 6 weeks
from CHF 18,000fixed scope · excl. VAT
Production is quoted after the go decision, with running costs stated up front. Extensions: CHF 2,200 per day.
- One workflow, one agent
- Baseline and number to beat, agreed in writing
- Weekly pilot update
- Documentation: sources, prompts, owner, off switch
[ 07 — QUESTIONS ]
What people ask about agents.
What happens to our data?
The agent runs in your tenant or a cloud region you choose, with the access you grant. We tell you which model provider sees what, we check the provider's terms on training with you, and a log records every step.
What if the agent gets it wrong?
It stops and hands the case to a person when it is unsure, and nothing is sent, paid or deleted without approval. Corrections are counted in the pilot report, so you see the error rate before you scale.
What if a pilot does not pay off?
Then we stop it. Every pilot has a baseline and a number to beat, agreed before we start, and you keep the documentation and what we learned.
Will IT and security accept this?
They see it from day 1: data flow, access rights, the agent's own identity, logs and the off switch. Identity and tenant operations can stay with worxspace or your IT team.
What happens when the model behind it changes?
Models change, so the workflow is kept separate from the model. We re-test on the same sample before you switch, and prompts and code are yours.
Who owns the agent, and who runs it afterwards?
You do. It is documented with sources, prompts, a named owner on your side and an off switch that does not need us. If you want ongoing support, that is a separate agreement.
Does it replace people?
No. The team stops retyping orders. They still check every one before it goes out.
Pick the routine. We build the agent.
Bring one workflow. We tell you honestly whether an agent pays off, and what it would cost to find out.