Pricing

Per contour.
Never per seat.

Adding a warehouse worker to a system you own should not cost you anything, so it does not. What costs money is us building it and running it while your people take over, and that is the whole of what you pay for. Every number below is fixed before we start.

See a real year one Compare with per seat Prices in EUR, excluding VAT
The two lines

Two numbers, and you can stop the second one whenever you like.

Ten thousand to build it. A thousand a month to run it, extend it and keep it current. There is no third line, nothing that grows with your headcount, and nothing that switches off on the day you stop paying.

One time

A contour, built

€10,000
Fixed · three weeks · per contour
  • A free probe of your live systems and a written spec you approve
  • The system, on your server, with the full source
  • Tests, merge gate, one deploy script and a rollback
  • Per person logins and roles enforced in the database
  • Sync with the ERP you already run
  • Your team works a real day in it in week three
Money back if you do not accept it.
Monthly

Running it with you

€1,000
Per month · cancel any month
  • We keep building while your business keeps changing
  • Your person is taught to drive an agent, not to code
  • Incidents, restores and updates handled, with you watching how
  • Fiscal and regulatory changes for your country
  • Improvements to your industry core, delivered to you
  • No user count, no ticket count, no overage
Stop it and everything keeps running. It is yours.
Worked example

A distributor with forty people, signing on the first of September.

The whole first year, with nothing left off it. Every line here is known before you sign, and there is nothing that appears in month four because somebody discovered a module was extra.

The probeTwo days reading your live systems, counting what is actually in them, ending in a written scope with a fixed price.
€0
Contour one, order to invoiceThree weeks. Built, on your server, with the source. Your team works a live day at the end of it.
€10,000
Running it, twelve months€1,000 a month. Building, incidents, restores, updates and teaching your person to hold it.
€12,000
Handover certificationThe checklist, the session, the rollback your person performs themselves.
Included
User licences, 40 peopleThere is no such line. The system is yours.
€0
HostingIt runs on your server, in your account, from week one.
€0
Implementation, consultants, change requestsThe build fee is the implementation. There is no partner standing behind us with a day rate.
€0
First of September to first of September
€22,000

Year two is €12,000 if you keep us, and nothing at all if you do not, because the system is yours and it does not stop. A second contour, whenever you decide you want one, is another three weeks at €10,000. Your own infrastructure bill at this size is typically under €100 a month.

The arithmetic

Do the maths yourself, with their quote in front of you.

We are not going to put words in a competitor's mouth. Take the proposal on your desk, type in its four numbers, and the comparison writes itself. Include the implementation fee, because that is the line that actually decides this.

Count the warehouse and the office. Per seat pricing usually does.

The figure on the quote, not the list price on the website.

Setup, configuration, migration, training. The line most comparisons quietly leave out.

Their system€133,600
a-systems€46,000

What you own at the end
A login, until you stop paying
What you own at the end
The system, the source and the data

Both columns count what leaves your bank account. Ours is one contour at €10,000 plus €1,000 a month, which already includes the engineering, the updates and the support; there is no partner behind us with a day rate. Your own server is not in either column and runs under €100 a month at this size.

What moves it

What you never pay for, and what decides how many contours you need.

Never charged

  • Users, seats, or the difference between a full user and a light one
  • Hosting, because it runs on your infrastructure
  • Storage, records, documents processed or orders per month
  • A module you find out in month four that you need
  • Support hours, tickets, or an hour of anyone's attention while you pay the monthly
  • Anything at all in any month you decide not to pay it

What the probe is actually working out

  • How many of your processes fit into one three week contour
  • How many channels, carriers and external systems have to be wired
  • Whether your current system has a usable API or has to be read another way
  • How much history has to be carried in rather than left where it is
  • How many warehouses and locations the stock model has to hold
  • How many languages the interface has to ship in

The money back is a clause, not a slogan.

  1. What is being promised. At the end of week three your team works a real day inside the system, on your data, doing the work named in the scope document you signed in week one.
  2. Who decides. You do, against that scope document and nothing else. Not a demo, not a checklist we wrote afterwards.
  3. What happens if it is no. The build fee is returned in full inside fourteen days. You keep the repository and everything in it. We keep the lesson.

We can write this because building is no longer the expensive part. It is also the fastest way to end an argument about whether three weeks is a real number.

Straight answers

What people ask before they send this to their CFO.

Why is this so much cheaper than everyone else?+
Because the expensive part of software used to be writing it, and for us it is not any more. A build that took a team of five a year now takes one engineer and a fleet of agents a matter of weeks. We could price against what the market is used to paying, or against what it now costs us. We would rather have twenty distributors who tell each other about us than five who felt the price. There is no catch hiding in the second line: it is a thousand a month and you can stop it.
What if we want the whole business, not one contour?+
Then it is several contours, each three weeks, each at its own fixed price, in the order you choose. We push back on doing them all at once for one reason: accounting should move last, after everything around it has been running for a while. A vendor who agrees to migrate your ledger in month one is agreeing to a problem, not solving one.
What if it takes four weeks instead of three?+
That is our problem, not yours. The price is fixed and the acceptance test does not move. If we overrun, we absorb it, and if we overrun far enough that you lose confidence, the guarantee is still there.
What is actually in the thousand a month?+
Continued building as your business changes, incidents and restores, security and dependency updates, fiscal and regulatory changes for your country, whatever we improve in your industry core, and teaching your own person to drive the agent. No user count, no ticket count, no overage. It is one number because a support contract with meters on it makes people avoid calling, which is the opposite of what we want.
Are we tied into the monthly?+
No, and this is the part worth reading twice. You can stop it at the end of any month and the system carries on running, because it is on your server and the source is yours. No software vendor with a subscription can say that: stop paying them and you lose access to your own operation. Stop paying us and you lose us. That is the whole difference, and it is why we keep the number low enough that stopping rarely feels worth it.
What happens to the price if we come back in two years?+
A new contour is priced as a new contour. There is no reinstatement fee, no penalty for having left, and no lapsed maintenance to back pay. Leaving cleanly is the product, so we do not put a toll on the way back in.

The price is already on this page.
The probe tells you what it buys.

Two days of reading your live systems and counting what is actually in them, ending in a written scope you either recognise as your business or you do not. You owe nothing for it, and if the answer is that we are wrong for you, it says that instead.

Book the probe Open the demo first No call needed to see the demo