Custom ERP

Interconnected first. Replaced flow by flow. Accounting last.

First your channels, warehouse, carriers and e-invoicing are connected into one record, beside the ERP you have. Then the system takes over one flow at a time, and the books move last, only when you decide. Three weeks per flow, accepted by your team on a real working day, or every euro paid is refunded.

Request a scope read Open the working demo The scope read is free and commits you to nothing. To speak first, book a call with the engineer who would build it.
3 weeks
Per flow, from signed build to acceptance by your team
Your code
Assigned to you on acceptance, on your own servers. Nothing per seat
Full refund
Every euro paid, within 14 days, if your team does not accept
The method

ConnectReproduceReasonRepeat

  1. 01 ConnectFirst, everything around your ERP gets connected to it: the channels, the carriers, the e-invoicing chain, the warehouse.
  2. 02 ReproduceNext, the system reproduces the work your people do today, on a real working day, beside your current one.
  3. 03 ReasonOnly then does it answer the questions that matter: where the margin is, what is short, what the batch really cost.
  4. 04 RepeatThen the same loop runs for the next flow, and the next, until the whole business works on one record: accounting 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 record
  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-invoicing chainInvoice out, status back
Your ERP, the ledgerThe books move last
Every arrow is a connector, written and tested against a sandbox before it touches your live system.
Before you sign

Scope

  • Scoped with the people who do the work, not only the people who sign: each function shows us how it runs today, and that becomes the checklist it accepts against
  • Your requirements read against the foundation, the same day
  • A two-day probe of your live system under a signed mutual NDA, at no charge: real volumes, statuses and exceptions, how many documents your people still handle by hand, and which of your systems still do not talk to each other
  • A written scope with the price, the dates, the acceptance checklist, and what will not be built, and why
  • Your signature and a 50% deposit start the three weeks
Weeks 01-02

Build

  • Money, tax and stock logic written test first
  • Accounting moves last: until then the books stay where they are kept today, and the documents flow back there
  • Every integration built against a sandbox before the live connection
  • A daily build on your data, on a private pilot stand in the EU that your people sign into
Week 03

Run, then accept

  • The first test is not whether it is new: your team does yesterday’s work in it, today, beside your current system
  • Per-person logins, roles enforced in the database
  • The acceptance checklist from your scope, worked through and signed
  • Accepted and paid: deployed to your servers. Not accepted: every euro paid returns within 14 days
The demo

One foundation under every system,
shaped to each business.

Every system we build stands on the same foundation: the same lists, the same record cards with their history, the same audit trail under every write. What changes from one business to the next is what the records are called and what has to happen to them. That shared foundation is what makes a fixed price possible. The demo is a working system with real screens. It opens in a new tab, and you do not need to speak to us first.

The same six moves, in three different businesses.

An operational system is a small set of moves repeated over records with different names. Read down the first column and you are in a wholesaler. Read across and you are in a manufacturer, then a clinic group. Each column shows only what is shipped or in build.

The move
Apparel wholesaleLive demo · open to anyone
ManufacturingShipped · live demo
Clinic group, two countriesPilot shipped
YoursScoped from your requirements

Your records, under the names your team already uses. Send the requirements you have and they come back as a scope read: what the foundation already covers, and what has to be written.

Request a scope read
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 deliver.
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 someone'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 is recorded where it is done.
Picked in aisle order, every line scanned
Made at the workcenter, against the recipe
The visit is delivered and recorded
05Hand overIt leaves with the documents 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 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

Two demos, the same platform.

One record, connected end to end: from where it arrived to the line it leaves in the ledger. Pick the trade that looks like yours. Invented data, rebuilt every few hours, no call and no card.

Distribution

Wholesale, channels and the ledger

Ten orders, five of them arrived from a channel. Follow one to its invoice, pick it on a scanner, read what it did to the P&L.

Open the distributor demo

Manufacturing

A factory floor, batch by batch

Four doors: Run the floor, Release a held batch, Buy the ingredients, Cost the batch. A premix weighed outside its tolerance is holding a work order until somebody signs it.

Open the factory demo

The apparel column is open to anyone: a working system with real screens and its own data, exceptions included. The manufacturing column is open too, on a stand of its own, and the clinic column describes a pilot that has shipped.

Open the working demo Book a call with the engineer
Reference builds

Reference builds,
with their status as of today.

A reference build is not a product you buy. Where the status is Live demo or Pilot shipped, the domain is already written and tested on the foundation, which is part of why a price can be fixed in advance. Each status states what exists today. The 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 national e-invoicing chain. Runs beside the client’s existing ERP.

Live demo

Manufacturing

Production orders on a shopfloor screen, work orders through their states, weighing with a tolerance that holds a batch until somebody signs it, lots and their expiry, and the cost of every batch down to the ingredient it consumed. Made-to-order with a configurator and an installation schedule is in build on the same foundation.

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 to payroll, signable documents. Two countries, two currencies, one group: a pilot built in 10 days, from an empty repository on the shared foundation.

Pilot shipped

Field service and maintenance

Not started. Listed as planned, with no build behind it yet.

Planned
Evidence

Measured results,
and the controls behind them.

Every system here is built and changed by AI agents directed by one accountable engineer, and any release can be rolled back by redeploying the one before it. In practice, a requirement written in plain words becomes a day of work. Each figure below says what it covers.

Everything interconnected, one connector at a time. Five of the eleven sales channels mapped, carriers, a national e-invoicing chain and an ERP with no usable API have each been wired in days, because each connector is written and tested against a sandbox before it touches the live system.

Changes shipped through the one-day loop
220+
In the 30 days to 8 October 2026, across three systems: a client build, a pilot and our own. Each one specified, tested and released within a working day.
Rows migrated and reconciled
630,000+
Lifted 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
A figure can be checked without asking the person who produced it. Database rules block edits to posted entries and the audit log. Every journal is hash-chained, so a change made around those rules would show, and the chain is verified on a screen you can open.
Automated checks
8,700+
On the reference build, with more than 41,000 assertions between them, every one green before a change can merge.
Browser journeys
100+
End to end journeys driven through a real browser, the way a person uses the system.
Specification increments
180+
Each written and approved before it was built, with every task in it ticked.
Channel order accepted
<100 ms
A marketplace or web-shop order taken in with its whole stock chain, measured on the server that serves it: 73 ms at the 95th percentile, against a budget of two seconds.
Slowest screen at production volume
150 ms
Every list a person waits on, with a client’s production volume behind it: 92,000 products, 187,000 order lines, 867,000 stock moves. The budget 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 fresh environment.

The 220+ changes were counted over the 30 days to 8 October 2026 on three systems: a client’s working build, a pilot and our own internal build. The migration figure comes from one client’s cutover. The checks and increments were counted on the reference build on 8 October 2026, the browser journeys on 17 September 2026. The speed figures come from one client’s production volume: the order and the load test measured on 2 August 2026, the screens on 7 September 2026. What these systems do not yet prove is written out on the cases page.

Handover

What you control after handover,
in the contract’s own terms.

Four terms decide what you control after go-live: where the system runs, the format of your data, who holds the code, and what the licence allows. Each is written into the contract you sign. We expect to keep working with you as your business changes, and the contract makes sure that stays your decision.

The code and the licence

The code written for your business is assigned to you on full payment, and control of its repository moves to your own account. It runs on our shared foundation, licensed to your company and the companies it controls: worldwide, with no expiry and no user count, paid for by the build fee. The foundation’s core arrives as a compiled package, with its source deposited in escrow after delivery. The foundation may not be resold, redistributed or run as a service for others, though the whole installation can pass to a buyer of your business.

The servers

Once the system is accepted and paid for, it runs on your infrastructure, in accounts you hold. We host only the three-week pilot. Nothing switches off if you stop the monthly.

The data

Connected to the rest of your stack, not locked away from it. Yours throughout, in a standard Postgres database you can export, read and move without asking us.

Your team’s ability to extend it

A written map of what is safe to extend and what is load-bearing, and a test suite written to fail when load-bearing behaviour changes. Certified at handover: your own person, driving an AI agent, ships three changes and rolls one back.

Our access after handover is listed by name and expires on a date you set. If you stop the monthly and want us back later, there is no reinstatement fee.

Continuity

If we become unavailable,
the system keeps running.

A build led by one accountable engineer raises a fair question: what happens if he is unavailable? The contract answers it before you sign, along with the data questions a security review asks next.

Where it runsYour infrastructure, in accounts you hold, under a licence that never expires and is not counted per user. Nothing switches off if you stop the monthly.
Source escrowThe source of the foundation’s core is deposited in escrow after delivery. It is released to you if we cannot continue the contract, or if a year passes without a core update while you pay for updates.
Security fixesFree for the delivered foundation for at least five years from delivery, whether or not you pay for anything else.
Changes without usYour certified person ships them with an AI agent, against the same test suite, and can roll a release back.
Updates without the monthlyAn updates-only plan at €250 per month per contour, billed annually.
Our accessListed by name after handover, ending on a date you set.
Your data in the pilotOn a private stand in the EU, under the signed DPA. If you decline, you receive an export of it and a signed certificate of deletion.

Subprocessors, backups and incident terms in full: Trust.

Pricing

Published prices,
and the cost over three years.

A contour is one complete flow, such as order to invoice, warehouse or purchasing. A mid-size operation starts with one or two; the whole business, with accounting last, is usually three or four. The prices are published so your finance team can set them beside an implementation quote for Odoo, SAP Business One, NetSuite or Dynamics before any meeting. The licence is not counted per user, so forty people cost the same as four. Prices exclude VAT, and hosting is billed by your own provider.

A contour, built

€10,000-15,000
Once · per contour · fixed in the written scope

Three weeks from signed build to acceptance, with months 1 to 6 of running included. A 50% deposit starts the build and the balance is due on acceptance. If your team does not accept, every euro paid returns within 14 days. Once accepted and paid, it is deployed to your servers, your code is assigned to you, and the foundation is licensed to you with no expiry.

Running it with you

€1,000
Per contour, per month · from month 7 · cancel any month

It covers keeping the system running and monitored, backups, security patches, every foundation update for your vertical, email support for your people, and changes within a monthly allowance set in your agreement; anything beyond it only on a written estimate you approve. Stop at the end of any month and the system keeps running. Security fixes to the delivered foundation stay free for at least five years, and an updates-only plan is €250 per month per contour, billed annually.

Founding client · signing by 30 November 2026
€10,000

For the entry contour’s first year instead of €16,000: the build and twelve months of running, with months 7 to 12 on us. The offer is open to any vertical.

The entry contour over three years
€34,000

The build and the first three years of running, at today’s prices and before hosting and VAT. Without the founding offer, €40,000.

Agreements are signed with Rteam FZE LLC (Sharjah, United Arab Emirates), Alex Azariyev’s company, which runs a-systems.

Who builds it

The engineer accountable for your system,
named on this page.

Responsibility for your system is not passed between teams. The engineer who writes your scope directs the build, works through acceptance with your team, and is the person you deal with while we run the system with you.

a-systems is founded and run by Alex Azariyev. He has spent fifteen years building business systems (ERP, CRM, MRP, warehouse and eCommerce), from the first written specification to the day the client’s own team takes over. A finance degree came first, then work as an analyst and a project lead, then four and a half years running a forty-person ERP department.

Behind him are more than fifty ERP implementations. He also publishes MyFinance MCP, an open-source personal finance server that AI assistants connect to. a-systems rests on one conclusion from that work: a mid-size company should run on a system built around how it works, on its own infrastructure, with a partner it keeps by choice.

Each contour is built by this engineer 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 · the engineer on your build
  • Building business systems15 years
  • DomainsERP, CRM, MRP, warehouse, eCommerce
  • EducationFinance degree
  • RanA 40-person ERP department, 4.5 years
  • Implementations50+ 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, however complete it is. A private page comes back with your requirements read against the foundation: what the system has to hold, the documents it issues, the flows between them, the systems it has to connect to, what the foundation already covers, what has to be written, and an estimate in weeks. It is a reading, not a quote. The price is fixed later, in a written scope that follows 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 it is deleted after 30 days. If you would rather send the requirements as they actually are, sign the mutual NDA first. It takes a minute, it is already signed on our side when you open it, and it covers personal data.
  1. Your entities and documentsIn your team’s words, not module names.
  2. What has to be connectedEvery system the flow touches, and how each one is reached: an API, a file, or nothing usable yet.
  3. Standard, custom, left outWhat the first contour would not include, 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 beforeStated 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: one order, connected end to end, from the channel it arrived on, through the scanner, to the line it leaves in the ledger. If it fits how your company works, send the requirements you have. The scope read comes back the same day and names what has to be connected; the price is then fixed in a written scope you approve.

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

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.