How long does it take to build a custom ERP?
"How long does it take to build a custom ERP?" is the second question almost everyone asks, right after the price. And the honest answer starts the same way: it depends. But a bare "it depends" doesn't help you plan anything, so this article is about what can be said: what the timeline of a custom ERP depends on, what stretches it, what shortens it and, above all, when you start using it, which is long before it's finished.
Why nobody serious gives you a fixed deadline
For the same reason nobody serious gives you a fixed price: before starting, nobody knows the full scope. Not your vendor, and not you. There are always exceptions that only come up when working with real cases: the customer who pays in two installments, the file that gets reopened, the document that's signed differently in your industry. A total deadline given in the first meeting isn't a commitment, it's a bet, and when it fails the client pays for it: with a trimmed scope, with delays or with a renegotiation. We go into it in be wary of anyone selling an MVP in six weeks, and with an ERP it's exactly the same.
The useful question: when do you start using it
An ERP isn't handed over in one piece on the last day. It's built module by module, and each module can be used as soon as it solves its process. If you start with whatever takes up most of your time (case files, customers or invoicing), your team can work with that part while the next one is being built.
In our case, the first delivery arrives two weeks after starting, and it's something real even if still small: the architecture decided and documented, the environments up and running and a first screen with your data and your vocabulary. From there, every two weeks there's a new delivery you can see and test. So the question "how long does it take?" really has two answers: how long until you use the first part, which is measured in weeks, and how long the complete system takes, which depends on how far you want to go. A good management system, on top of that, is never fully finished: it grows with the business.
Some guidance, with every caveat
As a reference, and it's the one we publish on our development page: a simple internal tool or an automation is usually solved in one or two months of partial dedication; a SaaS-type product, with user accounts, one core feature done well and a dashboard, typically lands between two and four months; and a custom ERP for a specific sector, somewhat more, because modeling a business's data properly takes time. It's not a promised deadline: it's the order of magnitude, so you know whether we're talking about weeks, months or years.
What really stretches an ERP project
It's almost never the programming. What moves the calendar is usually somewhere else:
Decisions that don't get made. A question like "what happens to a case file when the customer cancels?" can block part of the work for days if nobody has the time or the authority to answer it. Rules that only live in someone's head. If the real process isn't written down anywhere, it has to be uncovered by talking to whoever does it, and that takes sessions. Data migration. Moving years of spreadsheets into a new system means cleaning up duplicates, understanding what each column means and deciding which history is worth keeping. Third-party integrations. Connecting to an industry portal or to another company's software depends on what the other side offers, and nobody on your project sets their pace. Scope that grows without priorities. Adding things is normal and healthy; what stretches the timeline is adding them all at once without deciding what comes first.
What shortens it
The most effective thing costs nothing: having someone on your side who knows the business, can make decisions and has a slot every two weeks to test what was delivered. It also helps a lot to start with a single process instead of the whole system, and to work with real data from day one (even if it's just a sample) instead of made-up examples.
Adding people to the team also speeds things up, but only up to a point. A project with two or three people moves faster than with one; with many more, part of the time goes into coordinating. That's why we work with small teams on purpose, and why dedication can be adjusted month by month: if one month you want to move faster, people are added, and if a slow month comes, it's scaled down without stopping.
Is an off-the-shelf ERP faster to roll out?
To begin with, yes: the software already exists. But rolling out an off-the-shelf ERP takes time too, because configuration, data migration and team training don't disappear just because you bought a finished product. And if it has to be customized to fit the way you work, that part looks a lot like a development project, with the same kind of timelines. When each option makes sense is explained in custom vs off-the-shelf ERP.
And since timeline and cost go hand in hand, the other half of the answer is in how much a custom ERP costs.
How we approach it
We won't give you an end date in the first meeting, because it would be made up. What we will tell you is which module we'd start with, what you'd see in the first delivery and which decisions we'll need from your side so we don't slow down. After that, every two weeks you see the system move forward and you decide the next step with something working in front of you, not on paper. That's how we approach every custom ERP development. If you'd like a read on your case, tell us which process takes up most of your time and we'll tell you where we'd start.