Custom ERP
A custom ERP for your small business — without the six-figure project.
One system for the whole business: invoicing, bookings, inventory, customers, reports — with AI doing the busywork. Built by one senior dev, first version live in a month, grown sprint by sprint at a fixed written price each step.
Fixed price · live in a month · your server, your code
Why owners end up here
“Most ERPs are either too generic or too expensive.”
That sentence, in some form, is how nearly every custom-ERP conversation starts.
Tool sprawl
A CRM here, invoicing there, bookings in a third tab, the real truth in spreadsheets. Every tool almost fits, and none of them talk to each other.
Per-seat fees forever
Five SaaS subscriptions times every employee, every month, for software that still makes you work around it. The bill only ever goes up.
Generic or gigantic
Off-the-shelf ERPs are either too generic to match how you actually work, or enterprise projects priced for companies ten times your size.
The honest comparison
Traditional ERP project, off-the-shelf suite, or built around you.
| Traditional custom ERP | Off-the-shelf ERP / SaaS | AI Makers build | |
|---|---|---|---|
| Price | $200K–$1.5M, quoted in phases | Per seat, per month, forever | Fixed written quote per sprint |
| Timeline | 1–3 years to go live | Fast start, then years of workarounds | First version live in a month |
| Fit | Configured from enterprise modules | Your business bends to the software | Built around how you already work |
| Who builds it | A rotating consultancy team | Nobody — you configure it yourself | One senior dev, the one you talk to |
| Ownership | License and lock-in | Their cloud, their rules, their exit fees | Your server, your code, no license fees |
Traditional figures are published industry quotes for enterprise custom ERP builds. If your business genuinely needs that shape of project, I will tell you on the first call.
How it's built
It starts small and grows into the system your business runs on.
Step 01
Your AI workspace
A private web app for your team, connected to Gemini, Claude and Codex through your own accounts. Live in a month, on your server.
Step 02
Your tools, connected
WhatsApp, email, sheets, your CRM, your bank. The system reads and acts across the tools you already run — one place, whole picture.
Step 03
Your modules, built
Invoicing, bookings, inventory, reporting, customer comms — built as custom pages and automations, one sprint at a time, each quoted before it is built.
Modules clients have built into theirs
- Invoicing and payment tracking
- Bookings and scheduling
- Inventory and stock control
- Customer records and follow-ups
- Quotes and job management
- WhatsApp and email customer comms
- Dashboards and daily reports
- Scheduled automations and alerts
Questions owners ask
Is this a real ERP?
It does what an SMB actually needs an ERP for: one system holding your operations — invoicing, bookings, inventory, customers, reporting — that every tool feeds into. What it skips is the enterprise baggage: no modules you will never open, no compliance suites for industries you are not in, no consultants configuring screens for a year. If you need multi-entity consolidation accounting out of the box, a traditional ERP serves you better, and I will say so on the first call.
What does a custom ERP cost for a small business?
Not enterprise money. Traditional custom ERP projects are quoted at $200K to $1.5M over one to three years. An AI Makers build starts with a working core in a month and grows sprint by sprint, each sprint quoted fixed and in writing before it starts — most AI Makers projects land between €5K and €150K in total, depending on how far you take it. The cost estimator on this site gives you a realistic range in 30 seconds.
Why not just use Odoo or another off-the-shelf ERP?
If an off-the-shelf system genuinely fits how you work, use it — it is cheaper on day one. Owners come to me after that experiment: the modules almost fit, the workflows almost match, and the team is living in spreadsheets around the edges. A custom build inverts that: the software matches the business, and the AI inside it does the busywork instead of adding admin.
How is an AI workspace different from a chatbot?
A chatbot answers questions. This is the system your business runs on: it is connected to your tools through your own accounts, it acts — reconciles the bank, chases invoices, books jobs, files reports — and it grows custom pages your team works in every day. The chat is just the front door.
Who owns the system, and where does it run?
You, and on your own server. Code, prompts, integrations, infrastructure — all signed over at handover. The AI models run through your own Gemini, Claude and Codex accounts, so there is no per-seat platform fee and no dependency on me to keep it running.
Start here
Tell me what your one system needs to do.
A 30-minute call, then a written scope and a fixed quote. No sales team, no runaround — you talk to the person who builds it.