The ERP stays. The manual work goes away.
I connect the ERP you already have to e-commerce, CRM, Excel and supplier PDFs. Where there's a document to understand, I put AI agents on it, with a person confirming. You pay for the result, with the price written up front: a connection starts at €500, VAT not applicable (Italian flat-rate scheme). Your vendor stays your vendor: nothing changes.
Tell me which ERP you use and what you do by hand · Price written up front · I reply within 24 hours
The ERP works. It's everything around it that's done by hand.
- Orders come in from the online store and somebody retypes them into the ERP, one by one.
- Supplier invoices arrive as PDFs and get keyed in by hand: lines, codes, quantities.
- Every Monday someone exports an Excel from the ERP, tidies it up and emails it around.
- CRM and ERP don't talk: the same customer record exists twice, and now and then the two disagree.
- The report the owner needs is one the ERP doesn't produce: export everything, rebuild it in Excel.
- The reseller said "it can't be done", or that it needs a module that costs as much as the ERP.
It's not which ERP you have. It's how you get in.
With AI agents the specific connector is no longer the problem: it gets written within a day for any product. What decides whether an integration is easy or impossible is the door the ERP leaves open. There are four, and they're the first thing I check.
Documented APIs
EasyThe ERP exposes an interface for programs. The easy case: the connection is written and tested within a day.
File export and import
EasyCSV, Excel, e-invoicing formats. Almost every ERP has them, even the old ones. You work on files: robust and simple to verify.
Database access
DoableThe ERP runs on your own server and the vendor grants access to the data. Doable, with care: read everything, write only where it's safe.
Screen only
AvoidNo API, no export, no database: the only way in is clicking. It can be automated, but it's fragile and breaks at every update. I advise against it, and I tell you beforehand.
If your ERP is the fourth case, I tell you after the check and that's all you pay for. Not a project to find out it couldn't be done.
A layer on top of the ERP, not a new ERP.
The ERP is good at keeping data. It's terrible at understanding a PDF, an email, an Excel price list made by a supplier. A model does that, alongside it: reads, proposes, and the ERP receives a record already in its own format.
Reads documents for you
Invoices, orders, price lists, supplier emails: the AI reads them, extracts the lines and prepares the record in the format the ERP expects. Manual entry becomes a glance-and-approve check.
A person confirms, always
Nothing writes into the ERP on its own. The AI proposes, a person sees the proposal and approves. That's how you get the speed without the risk of a wrong figure in the books.
If AI isn't needed, I say so
Half of all integrations don't need a model: a well-built connection is enough. In that case that's what gets built, it costs less and doesn't break. AI goes where there's a document to understand, not where it's fashionable.
What changes, department by department.
These are the jobs I run into most often. No percentages: it depends on how many documents go through your company. The pattern is always the same: the manual work goes away, and where it matters a person confirms.
Supplier invoices
- Today
- PDFs arrive by email and someone retypes lines, codes and amounts into the ERP.
- After
- The PDF is read and the lines reach the ERP already matched to the supplier and the items.
- Who confirms
- Whoever books the invoices, with one click.
Supplier price lists
- Today
- Every supplier sends a different Excel. Prices get updated by hand, or they don't.
- After
- The price list is read and compared with the master data: differences arrive as a proposed update.
- Who confirms
- The purchasing manager.
Orders from the store and email
- Today
- Orders are retyped into the ERP one by one, and so are the ones customers send by email.
- After
- Online orders flow in by themselves. Email or PDF orders become a draft order.
- Who confirms
- The order desk, on the drafts.
Stock in sync
- Today
- Online availability doesn't match the warehouse, and now and then you sell what isn't there.
- After
- Stock aligned between ERP and store, with an alert when an item drops below minimum.
- Who confirms
- Nobody: it's a connection. You read the summary.
CRM and ERP
- Today
- Duplicate customer records, and the salesperson can't see revenue and overdue invoices for the customer on the phone.
- After
- One customer record, kept in sync: the ERP data that matters shows up in the CRM.
- Who confirms
- Whoever owns master data, only when two values disagree.
Customer requests
- Today
- Customer emails are read one by one, the order is looked up in the ERP, then someone replies.
- After
- The request is classified and arrives with the order already found and a draft reply.
- Who confirms
- The operator, who edits and sends.
You pay for the result, with the price written up front.
An integration is built one piece at a time, verified on real data. Each piece has a result you can see and a price written before it starts. All prices: VAT not applicable (Italian flat-rate scheme), no subscription.
One connection
When it's a single, well-defined connection: a price written before starting, and that's it.
- An import that needs fixing
- A missing connection (e-commerce, carrier, CRM)
- An export that's done by hand today
- You pay for the result, no subscription
An integration project
When there's more than one flow, or documents for the AI to read. It's split into pieces, each with its own result and its own price.
- The first piece is checking how to get into the ERP
- Each piece goes live on real data before the next one
- Each piece's price is written before it starts
- Stops when you say so, no penalties
For comparison: an add-on ERP module is paid as a subscription forever and does what the vendor decided. A custom connection does what you need, is paid once, and the code is yours.
Four steps, the first one is a check.
30-minute call
You tell me which ERP you use and what you do by hand. If automating it makes no sense, I say so there.
The check: how to get in
I check APIs, exports, access, at a fixed price written up front. If the ERP is closed and there's no way in, it ends here and you know for certain.
The first flow, in production
Start with what costs you the most time, with its price written up front. It works on real data before moving to the next one.
Handover
Your code, documented, with what it does and what to do if it stops. No dependency on me.
I work on the code myself, with AI agents: you talk to the person doing the work. If the ERP really does need replacing, the path is a custom ERP; if the missing piece is the online store, see e-commerce development.
The questions I get about ERP integration.
How much does an ERP integration cost?
You pay for the result, with the price written before starting. A single, well-defined connection starts at €500, VAT not applicable (Italian flat-rate scheme). A project with several flows is split into pieces, each with its own price, and the first is checking how to get into the ERP: if there's no way in, it ends there and you've paid only for the check, not for a project to find out.
Do we have to change ERP?
No, that's the whole point of this page. The ERP stays yours, the vendor stays yours, the subscription you pay stays what it is. A piece is added next to it that does what you do by hand today. If one day the ERP really has to be replaced, that's a different conversation with a different page.
Our ERP has no API. Can it still be done?
Almost always, through files: CSV or Excel export and import exist even in twenty-year-old ERPs, and e-invoicing formats are a standard. If the ERP runs on your own server, the database can often be read with the vendor's permission. The one case I advise against is when the only way in is clicking on screen: it can be done, but it breaks at every update.
Can the ERP vendor object?
They can, if the contract forbids access to the data or if they won't hand over credentials. That's why the first step is a check and not a project: read the contract, ask for access, try. In most cases the vendor would rather someone builds the connection than be asked for a module they don't have.
What if the AI misreads an invoice?
It happens, and that's why nothing enters the ERP without a human confirmation. The AI proposes the lines, a person sees them and approves with one click. You still save the time, because checking a proposal is ten times faster than typing from scratch, but the error never reaches the books.
How long does it take?
A single connection, with API or files, usually takes one or two days of work. A flow with documents read by AI and human confirmation, three to five. Those are orders of magnitude, not promises: exact timing and price come out of the check, once I've seen how to get in.
The file that actually works, and the three points where it stops holding up: more users, variants and bills of materials, configurable quotes.
If the problem isn't a connection but the whole ERP: real price ranges and the break-even point against a subscription.
Tell me what you do by hand.
30 free minutes: you tell me which ERP you use and which job eats your time. I tell you how to get in, what to connect first and what it costs. If it isn't worth it, I say so there.
30 minutes · Connection from €500 · Price written up front · VAT not applicable (Italian flat-rate scheme) · Reply within 24 hours