How long does an ERP implementation really take?

Ask a vendor how long an ERP implementation takes and you will usually hear “three to six months.” Ask a business that has just finished one and the honest answer is often longer. Understanding why is the key to avoiding the trap, and to seeing why a new generation of AI-built systems can go live in days.

Where the time actually goes

The software is rarely the bottleneck. The months disappear into human implementation work: discovery workshops, configuration, custom development, data migration, testing, and training. Each step waits on people, and each hand-off adds delay.

• Discovery and design — weeks of meetings to document how your business works before anything is built.
• Configuration and customisation — turning that document into a working system, one field and workflow at a time.
• Data migration — the riskiest phase, where messy spreadsheets meet a structured database and problems surface late.
• Testing and training — making sure it works, and that your team will actually use it.

Why estimates slip

Traditional projects are bespoke. Every business is treated as a blank page, so the same work is redone from scratch each time. Change requests mid-project reset timelines, and because the cost sits in labour, delays cost real money.

The faster path: propose, approve, build

makn attacks the part that actually takes the time. Instead of a consulting project, you describe your business in plain language, an AI agent proposes a blueprint, you approve it, and a deterministic engine builds a live, working ERP on a proven, battle-tested engine, in days. When something needs to change later, the same loop handles it in production.

The guiding principle is simple: AI proposes, you approve, the engine executes exactly. You get the speed of automation with the control of sign-off on everything.

What to ask before you sign

Whatever route you choose, press on the timeline: how long until we are actually live, not just started? What happens when we need a change after go-live? Is the system built around how we work, or are we adapting to a template? The answers separate a product from a project.

---

← All articles