Custom ERP

Interconnected first. Replaced flow by flow. Accounting last.

We bring all your business data into one system: sales, purchasing, warehouse, delivery, invoicing, HR, production, IT, service and accounting. It does not matter whether you already have an ERP. Then the system takes over one flow at a time, and you switch off the old systems. No implementation that takes years, and no licence for every employee. Each flow takes three weeks, and accounting moves last.

Request a scope read Open the working demo A scope read is our free written reading of your requirements. It commits you to nothing. To talk first, book a call with the Project Engineer who would build your system.
Weeks, not months
From signing to a real working day in your system
Your data
Exportable at any time, in open formats, free
Full refund
Every euro paid, back within 14 days, if your team does not accept
The method

ConnectRunAnalyseRepeat

  1. 01 ConnectFirst we connect the systems around your ERP: sales channels, carriers, e-invoicing and the warehouse.
  2. 02 RunThen your team does a normal working day in the new system, side by side with the one they use now.
  3. 03 AnalyseAfter that, the system answers the questions that matter: where your margin is, what stock is short, what a batch really cost, and where your orders wait.
  4. 04 RepeatWe repeat the same steps for the next flow, until the whole business runs on one system. Accounting moves last, and only when you decide.
Where work starts
CRM and salesWeb shop, marketplaces, email, phone, messengers
Contracts and purchasingSupplier terms, orders, three-way match
ManufacturingRecipes, batches, the cost of each lot
One system
  1. Capture
  2. Commit
  3. Cover
  4. Execute
  5. Hand over
  6. Settle
What it connects to
Warehouse floorEvery line scanned
CarriersLabels out, tracking back
E-invoicingInvoice out, status back
Your ERP, the ledgerThe books move last
Each arrow is a connector. We test each one in a sandbox, a safe test copy, before it touches your live system.
Before you sign

Scope

  • We define the scope with the people who do the work, not only with those who sign. Each team shows us how it works today, and that becomes its acceptance checklist
  • Your requirements checked against our foundation (the base all our systems share), the same day
  • A free two-day probe: a look inside your live system, under a signed mutual NDA. We count real volumes, statuses and exceptions, the documents your people still handle by hand, and the systems that are still not connected to each other
  • A written scope: the price, the dates, the acceptance checklist, and what we will not build, and why
  • Your signature and a 50% deposit start the three weeks
Weeks 01-02

Build

  • We write the tests for money, tax and stock logic before the code
  • Accounting moves last. Until then your books stay where they are today, and documents flow back to them
  • Every integration is built in a sandbox before it connects to the live system
  • A new version every day, on your data, on our private server in the EU (the stand), where your people sign in
Week 03

Run, then accept

  • Your team does a normal working day in the new system, side by side with the one they use now
  • Each person has their own login, and roles are enforced in the database
  • Your team works through the acceptance checklist from the scope and signs it
  • When you accept it, it goes live and the monthly price starts. If you do not accept, we return every euro you paid within 14 days
The demo

The same foundation in every system,
shaped to each business.

Every system we build uses the same foundation: the same lists, the same record cards with their history, and the same audit trail for every change. What changes between businesses is what the records are called and what must happen to them. This shared foundation is why we can fix the price. The demo is a working system with real screens. It opens in a new tab, and you do not need to talk to us first.

The same six steps in three different businesses.

An operations system repeats a few basic steps on records with different names. Read down the first column and you see a wholesaler. Read across and you see a manufacturer, then a clinic group. Each column shows only what is shipped or in build.

The step
WholesaleLive demo · open to anyone
ManufacturingShipped · live demo
Clinic groupPilot shipped
YoursScoped from your requirements

Your records, under the names your team already uses. Send us your requirements and you get a scope read back: what the foundation already covers, and what we have to write.

Request a scope read
01CaptureA request arrives that you must fulfil.
A customer order: twenty-one lines from a PDF
A production order for a batch
A visit, with the services it needs
02CommitThe system says what it can deliver.
Nineteen lines reserved, two out of stock
The recipe sets what the batch uses
Services priced from the list, in the clinic's currency
03CoverWhat is missing becomes a task for someone, linked to its cause.
A purchase order for the missing lines
A purchase of the material the batch lacks
Supplies and outside work bought for that visit
04ExecuteThe work is recorded where it is done.
Picked in aisle order, every line scanned
Made at the work centre, following the recipe
The visit takes place and is recorded
05Hand overIt leaves with the documents it must carry.
Delivery note, carrier label, tracking on the order
The finished lot goes into stock, with its cost
The patient's document, issued by the right company
06SettleIt is invoiced for what actually happened and posted to the books.
Invoice sent through e-invoicing, margin on the same screen
The cost of the lot posted to the books
Invoice, payment, double entry, per company and consolidated

Two demos on the same platform.

Each demo follows one record from where it arrives to its line in the books. Pick the business that looks like yours. The data is invented and rebuilt every few hours. No call, no card.

Distribution

Wholesale, sales channels and the books

Ten orders, five of them from sales channels. Follow one to its invoice, pick it with a scanner, and see what it did to the P&L.

Open the distributor demo

Manufacturing

A factory floor, batch by batch

Four ways in: Run the floor, Release a held batch, Buy the ingredients, Cost the batch. One premix was weighed outside its tolerance, so its work order is on hold until someone signs it off.

Open the factory demo

Anyone can open the wholesale column: a working system with real screens and its own data, exceptions included. The manufacturing column is open too, on its own demo server. The clinic column describes a pilot that has shipped.

Open the working demo Book a call with the Project Engineer
Reference builds

Reference builds,
and their status today.

A reference build is a system we built for one kind of business. It is not a product you buy. Where the status is Live demo or Pilot shipped, the logic of that business is already written and tested on the foundation. That is part of why we can fix a price in advance. Each status shows what exists today. The cases behind the first row are written out in full.

Distribution

Orders from every sales channel, picking and packing by barcode, stock in several locations, purchasing with three-way match, invoicing and national e-invoicing. Replaces the client’s existing ERP step by step.

Live demo

Manufacturing

Production orders on a shop-floor screen, work orders through each stage, weighing with a tolerance that holds a batch until someone signs it off, lots with expiry dates, and the cost of every batch down to each ingredient it used. Made-to-order production with a configurator and an installation schedule is in build on the same foundation.

Live demo

Medical centers

Patients and visits, services priced per country, invoicing and payments, double entry per company and consolidated, staff from contract to payroll, documents to sign. Several companies and currencies in one group. We built the pilot in 10 days, from scratch on the shared foundation.

Pilot shipped

Field service and maintenance

Not started. Planned, with nothing built yet.

Planned
Evidence

Measured results,
and the controls behind them.

AI agents build and change every system here, directed by one Project Engineer who is accountable for it. Any release can be undone by putting back the version before it. In practice, a requirement written in plain words becomes a day of work. Each figure below says what it covers.

Everything connected, one connector at a time. We connected five of the eleven sales channels we mapped, carriers, a national e-invoicing system and an ERP with no usable API. Each took days, not months, because we write and test every connector in a sandbox before it touches the live system.

Changes, each shipped within a working day
220+
In the 30 days to 8 October 2026, across client and internal builds. Each change was specified, tested and released within a working day.
Rows migrated and reconciled
630,000+
Copied from a client’s live system in under four minutes and reconciled line by line as at the cutover date. The client’s own people worked in that copy before anyone relied on it.
Posted entries changed unnoticed
0
Anyone can check a figure without asking the person who entered it. Database rules block changes to posted entries and to the audit log. Every journal is hash-chained: each entry is sealed to the one before it, so a change made around those rules would show. You can check the chain on a screen in the system.
Automated checks
10,000+
On the reference build and its foundation. Every check must pass before a change goes in.
Browser journeys
100+
End-to-end tests that use the system through a real browser, the way a person does.
Written specifications
180+
Each one approved before we built it, with every task in it done.
Channel order accepted
<100 ms
To take in a marketplace or web-shop order and update all the stock behind it, measured on the server: 73 ms for 95% of orders. The limit we set is two seconds.
Slowest screen at production volume
150 ms
We timed every list a person waits for, with a client’s production volume behind it: 92,000 products, 187,000 order lines, 867,000 stock moves. The limit we set is one second.
Rows loaded in a load test
<1 min
More than 1.3 million rows at a client’s production volume, loaded into a new, empty environment.
What you can count on

What you can count on,
written into your agreement.

Before you sign, ask any vendor four things: where the system runs, how you get your data out, what leaving costs, and what happens if the vendor stops. Our agreement answers each one.

Where it runsOn our servers in the European Union, in a system of your own that no other company shares.
Your dataExportable at any time, in open formats, free.
If we stopSource escrow is part of your agreement. If we stop the service, the source code is released to you.
Your way outA published price to run the system on your own server.
UpdatesEvery week, included. Never an upgrade project.
Your data during the moveOn our servers in the European Union, under the signed data processing agreement (DPA). If you do not accept, you receive an export of your data, a signed certificate of deletion and all of your money back.

Subprocessors, backups and incident terms in full: Trust. How the system is built, with speed and security measured: the technical overview.

Pricing

From €290 a month.
Every user, every module.

One monthly price, set by how many transactions you run a month: orders and invoices, counted by the system itself. Migration fixed before you sign. We publish every price, so your finance team can compare it with the quote on their desk before any meeting. Prices exclude VAT.

See every price, and a first year line by line

Who builds it

Project Engineer.

Your system is not passed between teams. The Project Engineer who writes your scope directs the build, goes through acceptance with your team, and stays your contact while we run the system with you.

Alex Azariyev founded and runs a-systems. He has built business systems for fifteen years (ERP, CRM, MRP, warehouse and eCommerce), from the first written specification to the day the client’s own team takes over. He studied finance, worked as an analyst and a project lead, then ran a forty-person ERP department for four and a half years.

He has more than seventy ERP implementations behind him, on Odoo, Salesforce, NetSuite and similar platforms. He also publishes MyFinance MCP, an open-source personal finance server that AI assistants connect to.

He builds and runs each system by directing AI agents, under the controls described in Method and Evidence. If your team does not accept the system, he returns every euro you paid within 14 days.

The founderOn the record
Alex Azariyev
Alex Azariyev
Founder · your Project Engineer
  • Building business systems15 years
  • DomainsERP, CRM, MRP, warehouse, eCommerce
  • EducationFinance degree
  • RanA 40-person ERP department, 4.5 years
  • Implementations70+ ERP projects
  • Open sourceMyFinance MCP
  • LinkedIn/in/azariyev
  • Mailalex@a-systems.pro
Accountable for every commitment on this site
Scope read

Send the requirements you have.
Receive a scope read the same day.

Paste the text or attach the document, complete or not. You get back a private page that checks your requirements against our foundation. It lists what the system has to hold, the documents it issues, the flows between them, the systems it must connect to, what the foundation already covers, what we have to write, and an estimate in weeks. It is a first reading, not a quote. We fix the price later, in a written scope, after a probe of your live system.

Request a scope read Sign the mutual NDA Paste the text, or attach the PDF or DOCX you already have. We read it to produce your page and delete it after 30 days. To send your requirements as they really are, sign the mutual NDA first. It takes a minute, we have already signed it, and it covers personal data.
  1. Your records and documentsIn your team’s words, not software module names.
  2. What has to be connectedEvery system the flow touches, and how we can reach it: an API, a file, or nothing usable yet.
  3. Standard, custom, left outWhat the first contour would leave out, and why.
  4. The three weeks, week by weekWhat exists at the end of each week, and how to check it.
  5. Where we have not built beforeWe say so plainly when your business is outside what we have built.

Start with what
is not connected yet.

The demo is a working system with real screens. Follow one order from the channel it came from, through the scanner, to its line in the books. If it fits how your company works, send us your requirements. The scope read comes back the same day and names what has to be connected. We then fix the price in a written scope you approve.

Request a scope read Book a call with the Project Engineer The scope read costs nothing. The call is with Alex Azariyev, the Project Engineer who would build your system.

Which business should the demo show?

Two are open now. The data is invented and rebuilt every few hours. No call, no card.

DistributionWholesale, sales channels and the books ManufacturingA factory floor, batch by batch

Next: service companies, clinic groups and schools, on the same foundation.