One agent. One process. Thirty days. €3,000.
Not a pilot. A production run on one real process, with the before-and-after measured.
- Price
- €3,000, fixed. One invoice.
- Time
- 30 days from kickoff.
- Scope
- One business unit. One workflow. One agent. One number.
- Runs in
- Your environment, on your credentials.
- Control
- A human owner approves every real action, until you decide otherwise.
- If it doesn't work
- You stop. You keep the process documentation and the roadmap.
What actually happens
Four stages. Thirty days.
-
Week 1
Direction and baseline
- We pick the process with you, against something the company is already trying to do. Not the most annoying step. The one where a result would count.
- Then we write down what it costs today. Minutes per run, euros per unit, tickets per day. Captured now, at the time, by us and your owner together.
- This is a gate. No baseline, no go-live.
-
Week 2
Select and redesign
- We take the process apart and put it back together, then sort every task in it: person, shared, or agent.
- The human tasks get written up properly. Even if you stop at day 30, you keep a documented upgrade to how the work runs.
- Then we agree the rules: who approves what, what the agent is never allowed to do on its own, and what it does when it isn't sure.
-
Week 3
Configure and validate
- The harness gets compiled from your process. What the agent reads, what it writes, who approves, what counts as done.
- It runs in a sandbox first, against real data, with nothing reaching a customer. Your owner reads the output and tells us where it's wrong.
-
Week 4
Controlled production launch
- The agent goes live on the real process, with a human approving every real action.
- We measure against the baseline from week one. You get one page: what it cost before, what it costs now, and what that means at your volume.
- And you get the map: what to automate next, in priority order, for the next six months.
What we need from you
Three things. This is the whole ask.
One owner
A named person who knows the process and can make decisions about it. Not a project manager tracking us. The person whose number moves.
About half a day a week of their time
Kickoff, two working sessions, sandbox review, go-live.
Access to one process and the systems it touches
A scoped account, least privilege, named systems only.
And one thing we don't need: a written process
If you have it documented, we compile the harness from what you already wrote and it goes faster. If you don’t, we bring the framework and define it with you. Same price, same date.
Start with the 45 minutes.
You leave the call with a one-page opportunity map, the process we would start on, the number we would move, and a fixed price and date.
Darko Butina, Founder