A fixed price per flow, agreed before each one starts. That way you can stop after the first if you do not like the result.

What if we want to stop halfway?

You stop. The flows already in production stay yours and keep running. We do not build dependencies that hold you in.

Do we need someone technical on our side?

Not for the build. It helps at handover, though you can stay on the managed service precisely so you do not need to.

What happens when an external system changes?

During the warranty period we fix it. After that, either you handle it with the documentation you were given, or you move to the managed service.

Will you start without an advisory phase?

Yes, if you already know what you want built and why. If you are unsure which flow deserves to be first, advisory costs less than one flow built wrong.

Who owns the code at the end?

You do, from the start. We work in your repository if you have one, or hand you a complete one. No licensing and no components you cannot inspect.

Delivery: we build it, run it, hand it over

We build the system and put it into production

Something working in two weeks, not a plan in six months

An automation project that ships nothing until month six has already failed — nobody just knows it yet.

What you get

Something real, early

The first flow reaches production in two to three weeks. Not a test environment nobody uses.

Built on what you already have

We connect to the systems you run today. We do not ask you to migrate so that we can start.

No black boxes

The code, the flows and the documentation are yours from the start, not at the end of the contract.

Failure is visible

When something breaks, the system says so. Nothing passes silently as though it had worked.

How it goes

The flow, step by step

Days 1–3 — the frame
We confirm the first flow, get access, and agree what "working" means in terms we can check.
Weeks 1–3 — the first flow
We build one flow, end to end, and put it into production on real volume. One thing that works beats five demos.
Weeks 4–8 — widening
We add the next flows in the planned order, each under the same rule: it goes into production or it does not count.
Handover
Documentation, full access and a session with your team. You can carry on without us — plenty do.

What you own

Access to the systems that need connecting
The business decisions on rules and exceptions
One person who can answer within the day

What we own

Building, testing and putting it live
The documentation and handover to your team
Fixes during the warranty period

How it is priced

Fixed price per flow, agreed before each one, with no hourly billing

Related services

Frequently asked questions

How is it priced?: A fixed price per flow, agreed before each one starts. That way you can stop after the first if you do not like the result.
What if we want to stop halfway?: You stop. The flows already in production stay yours and keep running. We do not build dependencies that hold you in.
Do we need someone technical on our side?: Not for the build. It helps at handover, though you can stay on the managed service precisely so you do not need to.
What happens when an external system changes?: During the warranty period we fix it. After that, either you handle it with the documentation you were given, or you move to the managed service.
Will you start without an advisory phase?: Yes, if you already know what you want built and why. If you are unsure which flow deserves to be first, advisory costs less than one flow built wrong.
Who owns the code at the end?: You do, from the start. We work in your repository if you have one, or hand you a complete one. No licensing and no components you cannot inspect.

Got a process that should be running itself?

Claim a free audit