Pricing

Per contour.
Never per seat.

Adding a warehouse worker should not cost you anything, and it does not: the licence is not counted per user. What costs money is building the system and running it with you, and both prices are on this page before we start.

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

One fee to build, one a month to run, and you can stop the second whenever you like.

Ten to fifteen thousand to build a contour, the exact figure fixed in your scope before you sign, with the first six months of running it inside. A thousand a month, per contour, from month seven. Nothing grows with your headcount, and nothing switches off if you stop the monthly. What stops is the update stream, unless you take the updates-only plan; security fixes to the delivered foundation stay free for at least five years. Hosting is billed by your own provider.

One time

A contour, built

€10,000-15,000
Fixed in your scope · three weeks · per contour
  • Before you sign: a free two-day probe of your live systems under a signed mutual NDA, and a written scope you approve
  • Once accepted and paid: deployed to your server, your code assigned to you, the foundation licensed with no expiry
  • 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, where you keep one
  • Your team works a real day in it in week three
  • The first six months of running it included, twelve if you sign by 30 November 2026
Money back, in full, if you do not accept it. Acceptance closes that window.
Monthly

Running it with you

€1,000
Per month, per contour · from month seven · cancel any month
  • The system kept running and monitored, with a response to outages
  • Backups, and the documented path to restore them
  • Security patches for the system and what it runs on
  • Every foundation update for your vertical
  • Email support for the people who maintain it on your side
  • No user count and no ticket count. Changes within a monthly allowance set in your agreement; anything beyond it only on a written estimate you approve
Stop it and the system keeps running on your servers. The update stream stops unless you take the updates-only plan, and security fixes stay free for at least five years.
Worked example

A distributor with forty people, signing in October.

The whole first year of the entry contour, before VAT. Every line here is known before you sign, and anything outside the written scope is priced in writing before any work on it starts.

Founding client price · signing by 30 November 2026

The probeTwo days reading your live systems under a signed mutual NDA, counting real volumes, statuses and exceptions, and how many documents your people still handle by hand, ending in a written scope with a fixed price.
€0
Contour one, order to invoiceThree weeks on our stand, behind auth. Your team works a live day in it at the end. Deployment to your server, your code and the foundation licence follow acceptance and full payment.
€10,000
Running it, months one to sixIn the build fee. Monitoring, backups, security patches, updates, and email support while your person learns to hold it.
Included
Running it, months seven to twelve€1,000 a month. Monitoring, backups, security patches, updates, email support, and changes within the monthly allowance. Sign by 30 November 2026 and these six months are on us.
€6,000€0
Handover certificationThe checklist, the session, the rollback your person performs themselves.
Included
User licences, 40 peopleThere is no such line. The foundation licence is paid by the build fee and not counted per user.
€0
HostingThe build runs on our stand, on us. From delivery it runs on your server, in your account, billed by your own provider.
Your provider
Implementation and consultantsThe build fee is the implementation, with no partner standing behind us with a day rate. Work outside the written scope is priced in writing before it starts.
€0
The first year
€16,000€10,000

Year two is €12,000 on the monthly. If you stop it, the system keeps running under a licence that does not expire. Updates stop unless you take the updates-only plan at €3,000 a year per contour, and security fixes stay free for at least five years. A second contour, whenever you decide you want one, is another three weeks at its own scope price, €10,000 to €15,000. Your own infrastructure bill at this size is typically under €100 a month.

This year one as a one-page PDF, for the person who signs it off.

Agreements are signed with Oleksandr Azariyev under the a-systems brand until the company is incorporated, and then pass to it.

The arithmetic

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

Start from a published mid-market profile, or type in the proposal on your desk; every slider is yours to move. Count the partner line the way it actually happens: not once, but every year, for as long as the partner stays. It is the line most comparisons quietly drop.

Published guides put a mid-size Odoo implementation at €20,000 to €90,000, and partner development after go-live at €60 to €140 an hour. €50,000 a year buys about ten hours of it a week.

Published guides put a mid-size SAP Business One project at €30,000 to €90,000 to implement, licences at €90 to €230 per user per month, with maintenance and consultant days returning every year.

Published guides put a mid-market Salesforce implementation at €50,000 to €140,000, with the support contract behind it at 15 to 20 percent of that figure a year, plus an admin.

Published guides put mid-market NetSuite licences at €50,000 to €150,000 a year, implementation at €30,000 to €150,000, and year-two uplifts of 5 to 15 percent when no cap was locked at signing.

Your numbers now, not a preset. If the proposal on your desk says less, believe the proposal.

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 cheque that clears before the system exists.

Change requests, custom modules, upgrades, the support contract, per year. It starts when they go live, around month three, and it does not stop.

One flow is one contour: order to invoice, warehouse, purchasing. A mid-size operation runs on one or two. The whole business, accounting last, is usually three or four.

Their system€67,300
a-systems€10,000

What you hold at the end
What their licence terms say
What you hold at the end
Your data, your code, a licence with no expiry

Both columns count what leaves your bank account. Ours counts the entry contour, €10,000 to build; your scope fixes each contour between €10,000 and €15,000. The first twelve months of running are included when you sign by 30 November 2026 (six after that date), then €1,000 per contour per month; there is no partner behind us with a day rate. The presets are mid-market ranges from published 2025 and 2026 pricing guides, not anyone's quote. Your own server is in neither 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 during the build, which runs on our stand
  • Storage and records, however many you keep
  • Security fixes to the delivered foundation, for at least five years
  • A licence fee to keep using the system after you stop the monthly

What the probe is actually working out

  • How many of your processes fit into one three week contour
  • How many documents your people still handle by hand
  • 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 with the agreement.
  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. Everything you have paid is returned in full inside fourteen days. You keep an export of your data and your requirements. The rest of the system materials are deleted, and we certify the deletion of your data.

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. And the same speed is the product, not only the discount: a change you ask for after go-live takes a day of work, not a quarter. 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?+
Keeping the system running and monitored, with a response to outages, backups and the documented restore path, security patches, every foundation update for your vertical, and email support for the people who maintain it. No user count and no ticket count. Changes within a monthly allowance set in your agreement; anything beyond it only on a written estimate you approve.
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 foundation licence does not expire. The update stream stops unless you take the updates-only plan, and security fixes stay free for at least five years. We keep the monthly low enough that stopping it 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, and the monthly resumes at the rate current then. There is no reinstatement fee and no penalty for having left. Updates shipped while you were away are applied through a catch-up, estimated in writing first.

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

Two days of reading your live systems under a signed mutual NDA, counting real volumes, statuses and exceptions, and how many documents your people still handle by hand, 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

Which business should the demo be?

Two are open now. Invented data, rebuilt every few hours, no call and no card.

DistributionWholesale, channels and the ledger ManufacturingA factory floor, batch by batch

Service, clinic groups and schools follow, on the same foundation.