Custom ERP Development: A Complete Guide for Business (2026)

What an ERP is, in plain words

ERP (Enterprise Resource Planning) is a system that brings a company's operations into one place: sales, inventory, purchasing, production, logistics and management finance. Put simply, it is the shared memory of the business, where every event is recorded once and immediately updates everything connected to it.

Here is how it works on a single order. A sales manager takes an order for 50 units. The system reserves the stock straight away and sees that 20 units are missing. It suggests buying them from a supplier or creates a production task. Then it calculates the cost and margin of this order, issues the invoice and waits for the payment from the bank. When the money arrives, the order moves to “paid” by itself, and the warehouse sees it can ship.

Without an ERP each of these steps lives somewhere else: in a spreadsheet, in the accounting software, in a chat message or in the head of an experienced manager. Data is copied by hand, so it drifts apart, and mistakes are found when the customer is already waiting.

It also helps to know what an ERP is not. It is not your tax and statutory reporting software: that job belongs to accounting tools such as QuickBooks, Xero, Sage, DATEV or, in Ukraine, BAS. It is not just a CRM, although an ERP usually has a sales module. And it is not a box you buy and switch on: an ERP always has three parts, namely processes, data and the people who work with it.

ERP vs CRM vs accounting software

The confusion comes from the overlap between these systems. The easiest way to tell them apart is to ask “who works in it every day, and what matters most there”.

System	What it is for	Who works in it	Examples
CRM	Customers and sales: leads, deals, communication history, reminders	Sales and support	HubSpot, Pipedrive, KeyCRM
Accounting software	Bookkeeping and tax, source documents, statutory reporting, payroll	Accounting	QuickBooks, Xero, Sage, BAS
ERP	All operations: orders, inventory, purchasing, production, cost, management finance	Almost every team and the owner	Odoo, Business Central, SAP Business One, NetSuite, a custom system
Spreadsheets	Quick tracking at the start, one-off calculations	Anyone	Excel, Google Sheets

In a real company they work together. The CRM brings the customer and the order, the ERP fulfils the order (reservation, purchasing, production, shipping), and the accounting software reflects it all in the books. Data moves between them automatically through integrations, with no manual copying. We showed what this looks like in practice in our article on integrating a CRM with accounting software.

What an ERP is made of: the main modules

An ERP is assembled from modules, like building blocks. Nobody needs all of them at once. Under each module we wrote the sign that tells you it is time for it.

The first module is most often “orders + inventory”: that is where a business loses the most money through mistakes and manual work. Production and finance follow as next steps.

ERP for manufacturing: what to know

Production is the hardest part of any ERP, and it is exactly where ready-made systems most often need customisation. Here are the concepts worth understanding before you talk to a vendor, without the jargon.

Concept	In plain words	Why it matters
Bill of materials, recipe	The list of materials and semi-finished goods per unit of product, with quantities	Without it the system does not know what to consume or what a product costs
Routing	The sequence of operations: which work centres, machines and people are involved	You see the load on the shop floor and where queues form
Production plan and material requirements	The system calculates how much material the plan needs and what to buy (this is called MRP)	Purchasing follows the real plan, not a guess
Work in progress	What is already in production but not yet finished goods	Money “frozen” on the shop floor shows up in reports
Batch cost	Planned and actual cost of materials, labour and overheads for a specific batch	You see which products and customers are really profitable
Lots and expiry dates	Tracking which lot of raw material went into which lot of product	For food producers: recalls and quality control

Think separately about how people on the shop floor will work. A supervisor next to the line will not fill in a twenty-field form: they need a tablet or terminal, a barcode scanner and two or three large buttons. If entering data on the floor is awkward, nobody enters it, and the whole system calculates the wrong numbers. We wrote about the specifics of food production on our page on AI for food manufacturing.

Example: how a company's day changes with ERP

To make the difference visible, take a typical scenario: a producer with its own delivery, about twenty people, sales through reps and a website, accounting in separate software. This is a composite example, not a specific client.

What happens	Without ERP	With ERP
Morning: orders	Reps collect orders from calls, messengers and the website into Excel	Orders from every channel land in one list right away, with statuses
Stock check	A rep calls the warehouse and waits for an answer	Stock and reservations are visible on the order
Plan and purchasing	The production manager works out the plan and materials in a spreadsheet	The system proposes a plan and a list of missing materials
Shipping	Carrier labels are typed by hand, documents printed separately	Labels and documents are created from the order in one click
Payments	The accountant matches the bank statement against orders	Payments come in from the bank, and the system suggests which order each belongs to
Evening: owner's report	The report is stitched together from several files, and the numbers do not match	A dashboard with today's sales, margin, stock and debts

When a business needs an ERP, and when it is too early

An ERP is not a badge of a “grown-up” company. It is a tool that pays off only when manual work and data mismatches already cost you money. Tick what already applies to you in the left list: if three or more items match, it is time to plan an ERP.

What to do instead of an ERP if it is too early

Situation	What fits better than an ERP
Sales are chaotic, inventory is simple	A CRM implementation that exchanges data with your accounting software
The data already sits in several systems, but reports are built by hand	A reporting and analytics dashboard on top of the systems you already use
One manual task eats hours: orders from email, shipping labels, invoices	Automating that one process, or an AI agent just for it
Accounting works, but the operational part is missing	A separate module next to your accounting software, connected by an integration

For example, we did not build an ERP for a cosmetics distributor: we pulled reports from their CRM and bank into one dashboard. The first working version was ready in 2 days, and that was enough for the owner to see sales, profit and debts in one place. When the business grows, such solutions are not thrown away: they become part of the future ERP.

Ready-made ERP, customised or custom-built

This is the main decision, and getting it wrong is the most expensive mistake. There is no honest “best” option: each fits its own situation.

Criterion	Ready-made ERP	Ready-made with customisations	Custom development
When it fits	Processes are standard, and you are ready to adapt to the system	Most processes are standard, a few are special	Processes are non-standard, or they are your edge
How the price works	A monthly licence per user plus implementation	Licences, implementation and customisations that must be maintained through upgrades	Staged development plus hosting and support, no per-user fee
Who adapts to whom	You adapt to the system	A compromise	The system adapts to you
Upgrades	From the vendor	Customisations can break after a version upgrade	You decide what changes and when
Who you depend on	The vendor and the implementation partner	The partner who built the customisations	The developer, if the code is not yours, so the code and access must be yours
Main risk	The business bends to fit the system	Customisation costs keep growing	Weak process analysis at the start

Quick test: four questions

1. Are your processes similar to most companies in your industry? If so, start with ready-made systems and see how much you would have to change.
2. Is there a process where you earn more than competitors? A special production cycle, pricing or logistics. Build that one around yourself rather than bend it to someone else's template.
3. How many people will work in the system? Ready-made ERPs charge a licence per user per month. Multiply it by the number of people and by 36 months: that is the real three-year cost.
4. Does your accounting software already work well? If so, it is often cheaper to add an operational module and an integration than to replace everything.

A route that is often forgotten is the hybrid. Accounting stays where it is, sales stay in the CRM your team knows, and custom work happens only where ready-made systems do not fit: for example, production tracking or cost calculation. You pay only for what is really missing.

Popular ERP systems for small and mid-size businesses

The market is large, but for small and mid-size companies the choice usually comes down to a few options. We compare them by who they suit, not by their marketing copy. We do not quote licence prices: they depend on the country, plan and number of users and change often, so check the current price on the vendor's website.

System	Who it suits	What to watch
Odoo	Small and mid-size businesses with standard trade, inventory and service processes	Modular open-source system: a free Community edition and a paid Enterprise edition priced per user
Microsoft Dynamics 365 Business Central	Mid-size companies already in the Microsoft ecosystem	Cloud ERP from Microsoft, implemented by partners. Licence per user
SAP Business One	Mid-size companies that plan to grow large or belong to a group running SAP	Powerful, and expensive to implement and support for a small business
Oracle NetSuite	Fast-growing mid-size companies, often with several entities or countries	Cloud subscription by modules and users, implemented by partners
Local accounting-led suites	Companies whose accounting already runs in a local system, for example BAS in Ukraine	Familiar to accountants and fit local reporting. Operational processes often need customisation
A custom system	Companies with non-standard processes, or those who need only part of a ready-made system	Built around your processes, no per-user licences. The code and data must belong to you

How ERP development works: stages and timelines

Reliable ERP development never goes as one big “everything at once” launch. It is built module by module, and every module has its own acceptance. Here is what it looks like in our practice.

1. Introduction and goals

   We find where it hurts most and agree on 2-3 numbers we have to change: order processing time, number of mistakes, stock accuracy. We show a demo of a similar system.

2. Process mapping

   We describe how orders, goods and money move today, where data drifts apart and who is responsible for what. Separately, we record how the process should work after the change.

3. Roadmap

   We split the system into modules and agree on the order. The module with the biggest losses goes first, most often orders and inventory. You see the scope and price of every stage before the start.

4. Prototype

   Users walk through the main screens before any code is written. A mistake in a prototype is cheap to fix, in a finished system it is expensive.

5. First module 4-8 weeks

   Development with regular demos. You see the working system in parts, not only at the end.

6. Data and integrations

   We clean and migrate master data: products, customers, suppliers, prices. We connect the accounting software, bank, carriers, website and marketplaces. For a few weeks the old and new systems run side by side, and we reconcile the numbers.

7. Launch and training

   We set up roles, train the team and appoint a person inside the company whom colleagues go to with questions. The old way of working is switched off, so nobody lives in two systems.

8. Next modules full system in 3-6 months

   Modules are added one by one, each with its own timeline and acceptance. The system grows with the business.

Integrations to plan from day one

Integrations are what people most often forget to budget for at the start, and later they eat the timeline. List them right away:

• Accounting software. Documents, counterparties, stock. Tax reporting and, where your country requires it, e-invoicing usually stay in the accounting software.
• Bank. Statements and payments through the bank's API or open banking, so each payment finds its order by itself.
• Carriers. DHL, DPD, GLS, UPS or local carriers: labels and delivery statuses without manual entry.
• Payments and tills. Online payments and point-of-sale systems, including fiscal receipts where the law requires them.
• Sales channels. Your website and marketplaces such as Amazon: orders and stock in both directions.
• Telephony and messaging. Calls and conversations are attached to the customer's record.

How much an ERP costs and what the price is made of

Nobody can quote an ERP price out of thin air: two companies with the same headcount can have projects that differ several times over. So it is more useful to understand what the price is made of, and to count the full three-year cost rather than the launch cost.

Cost line	Ready-made ERP	Custom ERP
Licences	Monthly, per user	None
Implementation or development	Configuration to your processes	Staged development of modules
Customisations	Separate, and they must be upgraded with each system version	Part of development
Data migration	Always	Always
Integrations	Accounting, bank, carriers, website: often separate	Separate, depending on how many
Hosting	In the vendor's cloud or on your server	In the cloud or on your server
Support	Subscription or a partner contract	Support and further development

What drives the price most

• Number of modules. Orders and inventory cost noticeably less than a full system with production and finance.
• Process complexity. Production with recipes, semi-finished goods and cost calculation is harder than a simple warehouse.
• Integrations. Every system you exchange data with adds work. A lot depends on whether the other system has a decent API.
• Data quality. Duplicate products and customers, different names for the same item: the more chaos, the longer the migration.
• Roles and access rights. The finer the “who sees what” rules, the more work.
• Reports and mobile workstations. Separate screens for the warehouse, drivers or field sales.

How to count honestly

For a ready-made system add up: licence × number of users × 36 months, plus implementation, customisations and support. For a custom one: development of all planned modules, plus hosting and support for 36 months. Compare these two totals, not the price of the first month.

What to include in the first-year budget

• development or implementation of the first modules;
• the integrations from the list above;
• data cleanup and migration;
• training and user guides;
• hosting and support after launch;
• your own people's time. The process owner joins demos and acceptance, key users test every module, someone owns the master data. This time is not on the vendor's invoice, but without it the project will not fly. Plan it the same way you plan money.

How to cut the budget without cutting quality

• start with the one module where losses are biggest, and measure the effect on real numbers;
• do not move chaos into the system: first describe how the process should work;
• reuse what already works: accounting in your accounting software, sales in the CRM;
• replace manual data entry with AI agents wherever people retype data from email or messengers.

We estimate custom ERP development after mapping the processes, broken down by module: you see the price and timeline of every stage before the start.

Why ERP projects fail and how to avoid it

Most ERP failures are about how the project is run, not about technology. These are the mistakes we see most often, and what to do about them.

How we check that a new system calculates correctly: we build it next to the old one and compare the result record by record. In the project with a cosmetics distributor, the dashboard became the main tool only after 184 orders in receivables matched the spreadsheet to the cent.

AI in ERP: what actually works today

In 2026 AI in an ERP is no longer an experiment but a way to remove manual data entry. These are the scenarios that work in our projects:

• Order processing agent. Reads orders from email, messengers and the website, checks stock, creates the document and notifies the customer. For an online fashion store this meant 4 fewer hours of manual work a day at 99.2% processing accuracy.
• Inbox agent. Classifies emails, answers the routine ones and hands complex ones to a person. At a logistics company 80% of emails get an automatic reply, and the manager saves 3 hours a day.
• Deviation alerts. Stock below the minimum, a late payment, an order margin below the norm. The system writes to the person responsible.
• Questions to the data in plain language. “How much did we earn on this customer this quarter?” without building a separate report.

One important nuance: AI works well only on clean, structured data, and that is exactly what an ERP provides. We covered tasks and integration in more detail in our article “AI agents inside CRM and ERP”, and our approach to rollout on the page about AI implementation for business.

How to choose a vendor: 10 questions before you sign

1. Show me a similar system in operation, not just a presentation.
2. How do you map the processes before the start, and what do I get at the end of that stage?
3. Can we start with one module, and how long will it take?
4. Who owns the code, the database and the access?
5. How do you migrate data, and how do you check that the numbers match?
6. Which integrations have you already built: accounting software, banks, carriers, marketplaces?
7. How often will I see interim results?
8. What happens after launch: who supports the system and how fast are bugs fixed?
9. How are changes priced if requirements shift mid-project?
10. If we stop working together, can another team take over the system?

If a vendor answers any of these vaguely, pin it down in the contract. This applies above all to questions 4 and 10.

Checklist: what to prepare before you start

• a list of the processes that hurt, and how you measure the losses today;
• sample documents: orders, delivery notes, invoices, the reports the owner looks at;
• exports of master data: products, customers, suppliers, prices, even if they contain errors;
• a list of systems you need to exchange data with: accounting, CRM, website, bank, carriers, marketplaces;
• roles: who sees what and who can change what;
• one person on your side who makes decisions and accepts the work;
• 2-3 numbers by which we will judge the result in three months.

Examples from our work

FAQ

What is an ERP system in simple terms?

It is one system where a company's sales, inventory, purchasing, production and finance work together. Every action is entered once and immediately updates everything connected: stock, cost, debts, reports.

What is the difference between CRM and ERP?

A CRM handles customers and sales: leads, deals, communication history. An ERP handles everything that happens after the sale and inside the company: inventory, purchasing, production, cost, money. They often work together, with the CRM passing orders to the ERP.

Which ERP systems do small and mid-size businesses use?

Most often Odoo, Microsoft Dynamics 365 Business Central, SAP Business One, Oracle NetSuite, local accounting-led suites such as BAS in Ukraine, or a custom system built around the company's processes.

How long does ERP development take?

The first module, for example orders and inventory, usually goes live in 4-8 weeks. A full system of several modules comes together in stages over 3-6 months.

How much does an ERP system cost?

It depends on the number of modules, process complexity, integrations and the state of your data. For ready-made systems the main cost is per-user licences, for a custom one it is module development. Compare the full three-year cost, not the starting price.

Will an ERP replace our accounting software?

Usually not, and it should not. The accounting software keeps the books and tax reporting, while the ERP takes over operations. The two are connected by a data exchange.

Ready-made or custom ERP for a small business?

If your processes are standard, start with a ready-made system. If you have production, non-standard inventory or several sales channels, and a ready-made system needs customisation at every step, a custom one often works out cheaper over three years.

Do we need an in-house IT team?

No. The system runs in the cloud or on your server, and the vendor handles support and development. On your side you need one person who makes decisions about processes.

Who owns the code and data?

You should, and it is worth writing into the contract. Then any team can develop the system further, and you do not depend on a single vendor.

Can we start with one module?

Yes, and it is the most reliable route. Most companies start with orders and inventory and add production and finance in later stages.

Summary

An ERP is not about “order for the sake of order”, it is about no longer paying for manual work and mismatched data. Start with an honest answer to whether it is time, choose the route (ready-made, hybrid or custom), and build the system module by module, starting where the losses are biggest.

If you want to look at your own case, see how we approach custom ERP development, or book a call: we will tell you which module to start with and show a demo of a similar system.