Automate your daily ops
The recurring work that only happens if somebody remembers.
See what it involves
services
Replace your SaaS
One system you own instead of several you rent.
See what it involvesFive questions before any of it
Three or more on the build side and it is worth scoping.
- 01
Has the workflow been stable for six months without major changes?
Yes → Build risk is lower and the engineering hours pay back faster.
No → Defer. Volatile workflows burn rebuild budget.
- 02
Does the team work around the tool’s limits every week?
Yes → High. The workaround tax compounds and is the real cost.
No → No tool to work around means this one does not apply. A tool that fits the workflow is one to keep buying.
- 03
Does everything this build would replace add up to more than €500 a month in licences or three hours a week of someone’s time?
Yes → Either one clears the bar. Count the hosting and the API bill against the saving before you call it payback.
No → Neither the licence nor the hours are big enough yet. Leave it.
- 04
Can you write down what the build has to do on one page? For a tool you rent, count only the part your team actually uses.
Yes → The scope is real. Move to the cost math.
No → The scope is hidden. On a rented tool that means you use more of it than you think or there is real moat under the interface. On a manual job it means the work is bigger than one build.
- 05
Would losing this today put a compliance or payroll deadline at risk?
Yes → Critical compliance role. Replacing it is the wrong fight.
No → No compliance gate. Free to build.
Questions answered
- 01
Which lane are we in?
If it is work a person does by hand every week because no product does it cleanly, that is lane one and it lives on the AI agent development page. If the thing you want gone is a tool you pay for every month, that is lane two and it lives on the business process automation page. If it is both, the scoping call sorts it. The five questions above are what we use to do that.
- 02
How do you decide whether something is worth building?
The five questions above, run on an intake call. Three or more answers on the build side is a candidate. The one that gets skipped most often is stability: a workflow still being argued about will change shape before the code is finished.
- 03
What does it cost?
Lane one is one job at up to €3,000. Lane two is one system at up to €6,500. A stack of three tools or more is €14,000 to €24,000. Every one of those is a maximum rather than a fixed price. You are billed monthly on the hours the build actually takes and the invoice never passes the number agreed in writing before anyone writes code. Fewer hours than planned and you pay less. More hours and that is on me. We invoice in euro. The dollar figures on this site are a guide at a fixed rate.
- 04
What do we own at the end?
The repository, the deployment and the API accounts, in your name on final payment. No per-seat licensing and nothing to renew. What you pay afterwards is the API bill. Nothing is covered after handover: the code is yours and anything further is a new scope with its own number, approved before anyone starts.
- 05
What do I pay before you start?
Nothing. The 30 minute call is free. The written scope with its fixed number is free too and you keep it whether you hire us or not. You are invoiced at the end of each calendar month for the hours worked that month, then once more on handover for whatever is left. A two week build is one invoice. A ten week build is three. Anything outside the scope gets its own number and your approval before anyone starts. The repository, the deployment and the API accounts go into your name on final payment.
Still paying for tools you could own?
The call is free and the written scope with its fixed number is free too. You keep the scope whether you hire us or not. Nothing is paid before work starts.
The call is free and the written scope with its fixed number is free too. You keep the scope whether you hire us or not. Nothing is paid before work starts.