ERP customization is the work of bending the business system you already run — Odoo, NetSuite, SAP, Zoho, QuickBooks — around the one part of your operation it was never built to handle. Not a rip-and-replace. The specific module, report, or workflow your business actually needs, written and wired into the system you have.
Most businesses I talk to have already tried two or three things. Some of it works. Some of it almost works. And there's this one part — the part that really runs your operation — where every system falls short in the same frustrating way. Usually the software isn't bad. It's that your business doesn't fit the template, and the customization path looks painful: the vendor wants a six-month quote, a consultant hands you something impossible to verify, or the plugin you need was last updated in 2018. So the gap lives in spreadsheets, in macros, in a tool somebody built on a weekend, in one person's head. It works, mostly. Until it doesn't.
What can ERP customization actually do for you?
The work takes a few recognisable shapes. Yours probably fits one of them, or close enough that we can figure it out on a call.
Build the module your ERP doesn't have. Your system covers ordinary inventory or ordinary accounting fine — and then there's the part that's specific to how you make money: batch-level production tracking, compliance reporting, a pricing rule no template anticipated. I build that one piece and wire it into the system you already use.
Stop paying for seats and modules you never touch. A lot of ERPs are priced per user or per feature, and most teams use a fraction of what they're billed for. Sometimes the honest fix is a focused custom tool that does your job without the licence overhead.
Replace the spreadsheet that's quietly running a critical process. The Excel macro, the Airtable base stitched to eight Zapier connections, the shared sheet nobody dares touch. When a workaround becomes load-bearing, it needs to become real software before it fails at the worst moment.
Connect the systems that don't talk to each other. Your ERP, your CRM, your warehouse tool, your accounting — each holding a different version of the truth. I wire them together so your team stops re-keying the same data and reconciling by hand.
Retire the ancient system nobody wants to touch. Some old piece of software is still running a critical part of the operation, and everyone tiptoes around it. I move that function onto something maintainable, carefully, without breaking the day.
Why most clients call me
Most of the businesses who call me are in the same spot. Off-the-shelf ERP does seventy percent of what they need, and the last thirty percent is exactly where their operation lives. The customization quote came back too high, or the timeline too long, or the vendor disappeared mid-build. A consulting firm promised a digital transformation, the money got spent, and nothing really changed.
What they want is simple to say and rare to find: someone who'll sit down, listen to how the place actually runs, and write the software around that — not the other way around. Not a system sold to them, and then a year spent reshaping the business to fit it. That's the work I do. It usually starts with me asking a lot of questions about your operation that have nothing to do with software.
How does an ERP customization project work?
First, a thirty-minute call. I ask what your operation actually does — the real version, not the slide-deck one. What breaks. What takes too long. Who does the weird workarounds. We figure out which single fix, done first, would matter most. Free, usually this week.
Then I build your first version. I pick the most painful piece and build working software around it — real code, deployed to a staging environment your team can touch. AI is in the loop the whole way, which is what lets one engineer ship in a couple of weeks what an agency would still be scoping. This first version is free.
You try it, and you decide. Your team uses it, breaks it, lives with it for a week. No pressure to continue. If it's not a fit, you keep what I built and we part as friends.
Then we scope what's next, together. If it works, I write a plain-language scope for the next phase — what I'd build, in what order — and we keep shipping weekly. Each phase pays for itself before the next begins. Instead of a twelve-month waterfall that might fail, it's a sequence of small bets that work.
Custom or off-the-shelf?
I'll tell you straight: most of the time, you should not replace your ERP. Full replacement is a last resort, not a first move — it's expensive, slow, and risky, and it asks your whole team to relearn their day.
Off-the-shelf is the right answer when your need is genuinely ordinary — standard invoicing, standard inventory, standard payroll. A mature product has solved those a thousand times, and customising what a product already does well is just paying twice.
Customization is the right answer when the gap is specific to how your business works — the process that is your competitive edge, the compliance rule unique to your industry, the workflow no vendor anticipated because no other company runs quite like yours. That's the thirty percent worth building. On our first call, part of my job is telling you honestly which side of that line your problem sits on — even when the answer means less work for me.
Is ERP customization right for you?
Call me if:
- Your ERP covers most of the business, but the part that makes you money lives somewhere else entirely
- You're paying per user or per module for features your team will never use
- An Excel macro, a spreadsheet, or a weekend-built tool is doing the job real software should be doing
- A consulting firm promised a digital transformation, you spent the money, and nothing changed
- You've outgrown QuickBooks and stitched it together with Airtable and a stack of Zapier connections
- You want to own the code and the knowledge — no vendor lock-in
Don't call me if:
- Your need is genuinely standard — a mature off-the-shelf product will serve you better and cheaper, and I'll tell you so
- You need a fifty-person team, 24/7 on-call, and enterprise compliance theatre
- You're shopping the cheapest freelancer — that's not what I am, and pretending otherwise helps neither of us
- You want to specify every detail upfront and pay only when it's "done" — real software isn't built that way
- Your project is 3D games, casino software, adult content, or adversarial scraping
Frequently asked questions
Can you customize my ERP, or do you have to replace it?
Customize, almost always. A lot of my work is building the one module Odoo or NetSuite or SAP can't, or wiring together the stack you already have. Full replacement is a last resort — expensive, slow, and rarely necessary. If your existing system can be made to do what you need, that's the cheaper and safer path, and it's the one I'll recommend.
Which ERP systems do you work with?
Odoo, Zoho, NetSuite, SAP Business One, HubSpot, Salesforce, and QuickBooks setups stretched past their limits — those are the ones I see most. The customization itself is built in proven, boring languages with deep labour markets, so any engineer you hire later can maintain it. Your data stays on your servers.
What will this cost?
It depends on what we're building — every engagement is scoped individually. The honest way to find out: we have a thirty-minute call, I build your first version free, and if we continue, I write you a scope with a fixed price before any paid work starts. You know what you're paying before you commit to anything. No surprise invoices, no hourly billing.
Can my team maintain the system without you?
Yes — that's a core part of what I deliver. When the project wraps, I hand over everything — code, documentation, access — and train the people who actually use the system to make small changes themselves using AI, the same way I do. Adding a field, adjusting a report, tweaking a workflow: things that used to need a developer call now take minutes. You come back if you want to, not because you have to.
How do you avoid breaking the system we run every day?
Carefully, and in small pieces. I start with the most painful, easiest-to-verify part, build it on a staging environment your team can test, and only then put it into daily use. Nothing changes in your live operation until you've seen it work. Each phase is small enough to verify on its own — no twelve-month rebuild you have to trust on faith.
How fast can you start?
First call this week. The free first version typically starts within one to two weeks, depending on current bookings. If something is genuinely urgent, ask — sometimes there's slack.
Let's talk
Bring the specific gap — the part of your operation your ERP can't handle, the spreadsheet that's quietly running something critical, the integration that never quite worked. Tell me how the place actually runs, and I'll tell you honestly whether customization is the right call. A thirty-minute discovery call is free — no deck, no sales, just a real conversation.