Service
Commissioned software
You have repeating work done by hand or with a system that already gets in the way — we turn it into software written for you.
Who it is for
A company with repeated work that still has no system, or a system that now gets in the way.
What it covers
- A written scope and an order of work
- An architecture that fits on one page
- Short cycles with a working result
- Handover of the code and a note on how to run it
What you get
- The scope is text, not a spoken “we will see”
- You see software during the work, not only at the end
- You are not locked to us as the only party who can run the project
How we do it
It starts with a conversation and a written scope: what goes in, what stays out, and in what order we build. The price follows the scope, not an example from someone else’s site — there is no public price list, because every task is different. We build in short cycles, and each round you see something doing real work, not a presentation.
The first version does one real thing instead of showing all future screens. At the end the code is yours — after completion and payment, with no lock-in to us. And the proof we finish things is our own products — the machine network, the fiscal bridge and the private cloud are living systems, not slides.
How an engagement runs
01. Scope
We write the goals, the boundaries, and the first useful version.
02. Plan
Data, integrations, and the order of release.
03. Build
Cycles with a demonstration.
04. Handover
Code, deployment, and a list of known limits.
Questions on this topic
Is there a public price list?
No. After a conversation we give a written scope. The sum follows that scope.
Can the first slice be small?
Yes. The first version should do one real job, not show every future screen.