We build the operational system your business actually runs on. On your server, in three weeks. Then we hand it over with the source, and you keep changing it yourself, with your own AI.
Paste it or attach the document. Within minutes a private page comes back with the contour as we read it: the things your system has to hold, the documents it issues, the flows between them, what our build already does for you, what has to be written and roughly how many weeks that is.
Every system we build stands on the same skeleton: the same shell, the same lists, the same object cards with their history, the same report frame, the same trail under every write. What your business changes is what those objects are called and what has to happen to them. Below is one day inside one of them, an apparel wholesaler, and under it the same six moves in the other systems we have built.
In motion · apparel wholesale distribution · one Thursday
A reference build on invented data. Yours will be different, because it will be yours.
Open the demo Talk about yoursA business system is a small number of moves repeated over objects that happen to have different names. The day above is a wholesaler. Here are the same moves in a factory and in a clinic group, on the same foundation.
Your objects, under the words your team already uses for them. Send the requirements you have written and you get them back as a contour: what our build already does for you, and what has to be written.
Send your requirementsThis part is not designed again for each client. It is a build we already ship, and it is why the three weeks are spent on your business rather than on a shell.
A module rail, a module bar, and the Reporting and Configuration shelves at the end of it. The same navigation in every system we build, so what your team learns once keeps holding.
Search, filters, grouping, column sorting, counts and CSV, with the state kept in the address, so a filtered screen is a link somebody can send to somebody else.
Every card has its own address, an author and timestamps, a notes trail, counters, and buttons that land you on the list already filtered to what the number counted.
Period picker, the band of figures, the table under it, CSV out. Every report in every system we build has that shape, including the ones written for you.
Per person accounts, roles enforced in the database rather than hidden in a screen, every write carrying a name and a time, and accounting entries hash chained.
One codebase, and a build that carries the modules your business needs and refuses the routes it does not. Turning one off keeps its data where it is.
None of that is invented fresh for you, and it is kept under the same suite of checks that runs before any change reaches production. What current models changed is the speed of the part above it: reading your live system, writing the spec you approve before a line is built, and turning that spec into increments the tests judge. That is what makes three weeks a date rather than a hope.
The price is fixed, the date is fixed, and if you do not accept it you do not pay. We can write that because building is no longer the expensive part.
Every other vendor in this market is paid for you not leaving. We are paid for building the thing and then leaving, which is why the exit date is in the contract from the first day.
The whole repository, with the specs, the tests and the deployment scripts that built it. Not a compiled artefact and not a licence to use.
It runs on your infrastructure, in accounts you own. We were never the landlord, so there is nothing to move on the day we leave.
Yours the entire time, in a standard Postgres database you can dump, read and take anywhere without asking us.
A written map of what is safe to extend and what is load bearing, and a test suite that stops your own AI from breaking the second thing while fixing the first.
Our access after handover is listed by name and expires on a date you set. If you want us back, it is an hourly rate and a purchase order, not a subscription you forgot to cancel.
A reference build is not a product you buy. It is proof the domain is already understood, which is what turns six months into three weeks. Status below is what is actually true today, and the three cases behind the first row are written out in full, including what they do not prove.
Numbers from the reference build, measured rather than claimed. Your technical people will care about these more than about anyone else's customer count.
We are not going to print a certification we do not hold. Here is the whole picture, including the parts that are still ahead of us.
After handover, your data is not on our infrastructure at all. That is a stronger statement than any badge on this page.
Published because a hidden price in this market reads as a large one. Forty people cost the same as four, because there is no such thing as a seat when you own the system.
The system, on your server, with the source. The probe that produces the scope is free, and the fee comes back if you do not accept the result at the end of week three.
Building, incidents, updates, fiscal changes, and teaching your person to hold it. Stop it whenever you like and everything keeps running, because it is yours.
A distributor signing in September pays €22,000 for the whole first year, all in. There is no third line and nothing that appears in month four.
The demo is a working system with five orders in it. If it does not convince you in three minutes, no call from us was going to.