Your system. Not a platform.

Your operational system. Built in three weeks. Yours forever.

Built around the way your business actually works, proven live on a private stand, then on your server with the source the day you accept. Your own team keeps changing it with AI. From €16,000 for the whole first year, all in.

Get your free scope today See it running No call. No card. A few minutes.
3 weeks
From first call to a system your team uses
From €16,000
The whole first year, all in. Nothing per seat
100% yours
Source, server, data: all yours from acceptance day
Send your requirements

You already wrote the spec.
Get your scope back today.

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.

Get your free scope Paste it, or attach the PDF or DOCX you already have.
  1. Your entities and documentsIn your words, not our module names.
  2. Standard, custom, cutIncluding what we would leave out of the first contour, and why.
  3. The three weeks, week by weekWhat exists at the end of each one.
  4. Where we are further outIt says so plainly when your business is not what we have built.
The demo

The foundation is ours.
The nouns are yours.

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 are the six moves every one of these systems makes, named in the three we have already built. The demo is a working stand, not a picture of one, and it opens in a new tab.

The same six moves. Different nouns.

A business system is a small number of moves repeated over objects that happen to have different names. Read the first column and you are in a wholesaler; read across and you are in a factory, then in a clinic group. Same foundation, three sets of nouns.

The move
Apparel wholesaleShipped · the stand you can open
ManufacturingFoundation shipped · execution in build
Clinic group, two countriesPilot shipped
Yours

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.

Get your free scope
01CaptureSomething arrives that you have to honour.
A customer order, twenty one lines off a PDF
A production order for a batch
A visit, with the services it needs
02CommitThe system answers with what it can actually do.
Nineteen lines reserve, two are short
The recipe says what the batch consumes
Services priced from the list, in the clinic's currency
03CoverThe gap becomes somebody's job, attached to what caused it.
A purchase order for the short lines
A purchase of the material the batch is missing
Supplies and outside work bought against that visit
04ExecuteThe work happens where the work happens.
Picked in aisle order, every line scanned
Made at the workcenter, against the recipe
The visit is delivered and recorded
05Hand overIt leaves carrying the papers it is required to carry.
Delivery note, carrier label, tracking on the order
The finished lot into stock, with its cost
The patient's document, issued by the right company
06SettleIt is billed on what actually happened, and it lands in the ledger.
Invoice to the fiscal channel, margin on the same screen
The cost of the lot in the ledger
Invoice, payment, double entry, per company and consolidated

The apparel column is open to anybody: a working system with real screens, its own data and its own mistakes in it. Click through it before you talk to us.

Open the demo Talk about yours
The method

Three weeks, and the third one is yours.

The price is fixed, the date is fixed, and if you do not accept it every euro comes back within 14 days. We can write that because building is no longer the expensive part.

Week 01

Probe

  • We read your live system directly, not screenshots of it
  • Your real volumes, statuses and exceptions, counted
  • A written spec you approve before a line is built
  • What we will not build, and why, in the same document
Week 02

Build

  • Money, tax and stock logic written test first
  • Your existing ERP stays the ledger; we take the operation
  • Every integration has a real mode and a sandbox mode
  • Daily build on your data, on your private stand, visible the whole time
Week 03

Run, then accept

  • Your team works a real day in it, next to the old system
  • Per person logins, roles enforced in the database
  • The acceptance checklist from your scope, worked through and signed
  • Accept and we deploy to your server; decline and every euro returns
Handover

What you keep after we walk out.

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 source

The whole repository, with the specs, the tests and the deployment scripts that built it. Yours at acceptance, to use and change forever. The one limit: you cannot resell our template.

The server

From acceptance day it runs on your infrastructure, in accounts you own. We host only the three week pilot, so nothing ties you to us after we hand over.

The data

Yours the entire time, in a standard Postgres database you can dump, read and take anywhere without asking us.

The right to change it

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. Certified at handover: your person ships three changes and rolls one back.

Our access after handover is listed by name and expires on a date you set. If you want us back, it is the monthly again, or a priced piece of work, never a contract you cannot leave.

Reference builds

Industries we have already built the hard part for.

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.

Apparel wholesale distribution

Order intake across channels, pick and pack by barcode, multi location stock, purchasing with three way match, invoicing and the Italian fiscal chain. Runs beside your existing ERP.

Live demo

Medical centers and clinic groups

Patients and visits, services priced per country, invoicing and payments, double entry per company and consolidated, staff from contract through to payroll, and documents that can be signed. Two countries, two currencies, one group.

Pilot shipped

Made to order manufacturing with installation

Configurator to quote to production to install schedule. Windows, laser cut metal, fabricated parts. One shape, several trades.

In build

Field service and maintenance

Not started. Listed because clients keep asking and we would rather say what is real than draw nine grey boxes.

Planned
Why this is possible

You write it once.
Nobody translates it again.

Half of an ERP project is somebody turning what you said into what a developer builds. The other half is everyone finding out how far apart the two ended up. That half is gone here. The document you already wrote becomes the specification, the specification is what the system is built from and checked against, and it is handed to you with the source. Which is why three weeks is a date rather than a slogan, why one change is a day, and why your own people can keep going without us.

What one change costs
1 day
Specified in the morning, running in the system by the evening, with the checks that prove it. Seventy three have gone through that loop in the last thirty days across two client systems. Everywhere else the same thing is a change request, a quote and a release window.
A whole system, from nothing
0
An empty repository to a clinic group that invoices in two countries and two currencies, keeps double entry per company and consolidated, runs staff from contract through to payroll, and issues documents that can be signed.
Your real data, before cutover
0
Rows lifted out of a client’s live system in 3 min 20 and reconciled line by line as at the cutover date, not as at today. Their own people worked in that mirror before anybody depended on the answer.
Posted entries anyone can alter
0
Not your accountant, not us, not somebody holding the database password. Posted entries and the audit log are immutable in the database itself, every journal is a hash chain, and the chain is verified on a screen you can open.

Measured in the last thirty days on the two systems above, not collected from a brochure. One is a client’s working build and one is a pilot stand: what they do not prove yet is written out in full on the cases page.

Who builds it

A named person, not a vendor logo.

Systems like this are usually sold by a logo and delivered by whoever happened to be free. Here one person is accountable, his name is on the page, and he is the same person in week three.

a-systems is Alex Azariyev. Fifteen years of building the systems businesses actually run on: ERP, CRM, MRP, warehouses and eCommerce, from the first written spec to the day the client’s own team holds the keys. A finance degree first, then analyst, then project lead, then four and a half years running a forty person ERP department.

Along the way he founded Rteam, an ERP consultancy with more than fifty implementations behind it, and ships MyFinance MCP, an open source personal finance server that AI assistants plug into. a-systems is what those years concluded: most companies do not need a bigger platform. They need their own system, built around how they actually work, and handed over.

A contour here is built by one engineer directing a fleet of AI agents, under the checks in the section above. This is the engineer. If week three ends and you do not accept the system, he is the one who wires everything back within 14 days.

The founderOn the record
Alex Azariyev
Alex Azariyev
Founder · the engineer on your build
  • Building business systems15 years
  • DomainsERP, CRM, MRP, warehouse, eCommerce
  • RanA 40 person ERP department, 4.5 years
  • Also runsRteam, ERP consulting
  • Open sourceMyFinance MCP
  • LinkedIn/in/azariyev
  • Mailalex@rteam.top
Every promise on this site has this name on it
Pricing

Two numbers, and the second one you can stop.

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.

A contour, built

€10,000-15,000
Once · fixed in your scope · three weeks

The system, on your server, with the source, once you accept. The scope is free, a 50% deposit signs the build, and every euro comes back within 14 days if you do not accept.

Running it with you

€1,000
From month 7 · cancel any month

Building, incidents, fiscal changes, and every core update we ship to your vertical. Stop it at the end of any month: the system keeps running, the update stream stops.

A distributor signing in September with the entry contour pays €16,000 for the whole first year, all in: the build, six months of running included, then six on the monthly. There is no third line and nothing that appears in month four.

Look at it first.
Then send us your spec.

The demo is a working system with five orders in it. When it convinces you, send the requirements you already wrote and the scope comes back the same day.

Get your free scope Book a technical call No call. No card.