What is an ERP system, and which kind does your business need?

An ERP system is software that keeps the data behind your company's daily operations in one place: orders, stock, customers, invoices, purchasing, working hours and reports. Instead of piecing together the status of an order from five spreadsheets, three email threads and a notebook, everyone looks at the same up-to-date record. In this guide we cover what an ERP system is, its benefits and drawbacks, the main types, and how to decide whether your business needs an off-the-shelf product or a custom-built system.

I'm Zoltán Keresztes. I have been building business software for more than 16 years, eight of them as a software architect. We have built dispatch and fleet management systems for passenger transport companies, an auditable internal document management system for a Hungarian pharmaceutical manufacturer, and we provide architectural leadership for a market-leading HR platform. I wrote this guide for business owners and managers who are thinking for the first time about getting their company data in order.

What is an ERP system?

ERP stands for Enterprise Resource Planning. In practice, an ERP system is software that runs a company's main processes on top of one shared database. The point is not how many modules it has, but that the same data means the same thing for everyone. When a salesperson enters an order, the warehouse immediately sees what to pick, finance sees what to invoice, and management sees how much revenue to expect this month.

A typical ERP covers these areas:

• Sales and customer management: quotes, orders, customer records, contact history.
• Inventory and warehouse: stock levels, goods in and out, stocktaking, minimum stock alerts.
• Purchasing: supplier orders, deliveries, supplier prices.
• Finance and invoicing: invoices, receivables, payment deadlines, connection to accounting.
• Production or service delivery: work orders, scheduling, resources, deadlines.
• People: working hours, leave, permissions.
• Reporting: management dashboards built from live data, not manual summaries.

A system doesn't have to do everything. A 15-person trading company may only need orders, stock and invoicing connected. For a manufacturer, work orders and material usage come first. A good ERP covers what actually matters in your business.

What "integrated" really means

An integrated system means the modules are not separate programs that someone keeps in sync by hand, but parts of one system sharing the same data. Change a product's price and it changes in the quote, the order and the invoice. If a customer has an overdue balance, the salesperson sees it on the next order.

Integration can reach beyond the system too: your webshop, your bank, your accounting software, couriers, or the tax authority's e-invoicing service. In many companies these are exactly the connections that are missing, and someone spends an hour or two every day copying data by hand.

ERP or business management software: is there a difference?

Mostly it is a question of wording. Many people use "ERP" for the big international packages, such as SAP, Microsoft Dynamics or Odoo, which come with many modules and expect you to adapt your processes to their logic. "Business management software" is a broader everyday phrase that also covers simpler packaged tools, subscription cloud services and custom-built internal systems.

The name is not the real question. The real question is whether you buy a package and adapt to it, or have a system built that adapts to the way you work. We look at that choice in detail in our article on custom ERP vs off-the-shelf.

Benefits of an ERP system

When a company introduces a system that fits, the change is usually quiet rather than dramatic: fewer questions, less searching and less fixing after the fact. These are the most common benefits.

One version of the truth

Nobody argues about which spreadsheet is current. Everyone sees the same stock, the same order status and the same customer data. Something entered once doesn't get lost in an old email.

Less manual work, fewer errors

If an order automatically becomes a delivery note and an invoice, nobody types the same thing three times. Every manual copy is another chance for a typo. Automation here is not a buzzword; it simply means fewer wrong invoices and fewer annoyed customers.

Faster, better informed decisions

When the management report comes from live data, you don't wait on Monday morning for someone to compile last week's numbers. You see which products are selling, which customers pay late and where work gets stuck.

Transparency and accountability

You can see who recorded what and when. If something slips, you can trace where it happened. This is not about watching your staff; it is about spotting problems quickly so they can be fixed.

Easier growth

While everything lives in people's heads and spreadsheets, training every new hire takes weeks and every new site brings chaos. In a system, the process is written down and built in, so the company can grow without the owner having to keep everything in mind.

Compliance and auditability

In some industries, such as pharmaceuticals or finance, documents and decisions must be traceable by regulation. A well built system provides this by default instead of you collecting it after the fact.

Drawbacks of an ERP system

The downsides deserve an honest look too, because most bad experiences come not from the systems themselves but from side effects nobody expected.

Cost, and not just the first invoice

The licence or the development is only one line. Implementation, data migration, training, hosting and later changes all come on top. If you only look at the first price, you are likely to be surprised. We explain what drives the total in a separate article: how much an ERP system costs.

Implementation takes time and attention

Even the best system needs your team's time while it is being set up. Someone has to describe the processes, test, and help colleagues get used to it. If that is missing, the project drags on.

With a package, you adapt to it

Off-the-shelf systems work the way their makers imagined an average company. If you work differently, you either change your processes to fit the program or pay for expensive customization.

Dependence on the vendor

With a closed product, the vendor decides on pricing, new features and the future of the product. Moving your data out can be difficult if you ever want to switch.

Too many features nobody uses

It is common for a company to buy a package with dozens of modules and use only a small part of it, while the rest just clutters the screens. Staff then feel the system slows them down instead of helping.

These drawbacks are manageable if you know exactly what you need before deciding, and you can try out how the system will work before you buy or build it.

Types of ERP systems

There are four main routes a company can take. None is best for everyone; each has its place.

There is a fifth, hybrid route, and in my view it is underrated for most SMEs: keep what already works well (for example your invoicing or accounting software) and only have the missing part built, connected to your existing tools. That way you don't have to replace everything at once.

Cloud ERP and online systems

A cloud or online ERP runs in the browser, with nothing to install on individual computers. Staff see the same data in the office, at home or on a phone. This is the usual route today; programs installed on a local network are becoming rare.

"Cloud ERP" can mean two different things:

1. A rented service (SaaS): the vendor runs it, you pay a monthly fee, and you get what everyone else gets.
2. Your own system running in the cloud: the software belongs to you and simply runs on a cloud provider's servers. You decide on the features, and you can take it forward independently of the original vendor.

The difference between them is not technical but commercial: who owns the system and the data, and who decides its future.

ERP for SMEs: what small and mid-sized companies should look for

A small or mid-sized business is in a different position from a multinational. There is no IT department, no months-long consulting project, and every expense has to pay back quickly. So an ERP for an SME is a good fit when it:

• Can start small. You don't need to cover everything on day one. Start with the process that takes the most time or causes the most errors today.
• Makes sense to your staff. If the screens are full of fields nobody needs, the team won't use it. A good system is simpler than today's spreadsheet.
• Has predictable costs. Know in advance what implementation costs and what the monthly running cost will be. Open-ended hourly billing is a real risk for a smaller company.
• Connects to what already works. Invoicing, accounting, webshop, bank. You shouldn't have to replace them just because the new system can't talk to them.
• Can grow with you. When a new site, product line or service arrives in two years, the system should follow the company, not the other way round.

Signs it is time

When you need a system depends less on company size than on how much the current setup hurts. These are the most common signs:

• The same data is kept in two or more places, and they regularly disagree.
• Only one particular colleague can answer a simple question (how many are in stock, has the customer paid).
• Putting together the monthly report takes days.
• Spreadsheets are emailed back and forth, and nobody knows which one is the latest.
• A process stops while one person is on holiday.

If several of these sound familiar, the lack of a system is probably already costing you more than a system would.

Custom ERP or off-the-shelf?

This is the most important decision, and many people start it with the wrong question. The question is not which one is better, but how standard your way of working is.

Off-the-shelf is the right choice when your processes look like those of most companies in your industry, and the way you handle orders or stock is not what sets you apart. In that case there is no point reinventing the wheel.

Custom development is the right choice when your way of working differs from the norm and that difference is your strength. For example, you have your own pricing logic, a special production process, or dispatch and scheduling rules that no packaged product understands. Then customizing a package is often more expensive and slower than a well designed custom system.

For manufacturers, costing, order tracking and inventory are usually the first pain points. That is what our page on custom software for manufacturers is about.

Custom development used to have a reputation for being slow and expensive. That has changed a lot. We work with AI-supported workflows and engineering discipline: AI tools take over the routine parts such as boilerplate code, test scaffolding and documentation, while a human designs and oversees the architecture, the business logic and data security. Based on industry experience, a small or medium internal system used to need a development team of typically 3-4 people, and comprehensive automated testing, which keeps the system stable and easy to extend for years, pushed that cost even higher. Today, with the right methods, every project is led end to end by one lead developer, supported by a complete AI team, for a fraction of the traditional cost, including a large suite of automated tests. We can give you the exact scope and price after the one-hour call and the discovery phase. Read how we split the work between AI and engineers.

A common special case: warehouse and inventory

For many companies the first step is not a full ERP but getting inventory under control. If that is your main pain point, a focused inventory system, connected to the tools you already use, may be the right first project.

How to choose an ERP system

Choosing an ERP doesn't start with browsing product catalogues. It starts with writing down how your company works today. A few principles I recommend to every client:

1. Describe your processes before you look at software. How an order comes in, who does what with it, where it gets stuck. That tells you what the system has to do.
2. Rank the pain points. What takes the most time, what causes the most errors? Start there.
3. Ask the people who will use it. The warehouse staff, the administrators and whoever does the invoicing know exactly where it hurts. If they are left out of the decision, they won't use the system.
4. See it before you pay. Don't decide on descriptions and demo videos. Ask for a clickable prototype or a trial with your own data and processes.
5. Ask for the total cost, not just the licence price. Implementation, data migration, training, hosting, changes.
6. Clarify ownership. Who owns the data and the source code, and who can develop it further if the relationship with the vendor ends?

We turn this into a detailed checklist in our article on how to choose an ERP system.

How implementation works

A system is only worth something if the team uses it. That is why ERP implementation is not the last step but one of the most important parts of the project. In my experience, successful rollouts are decided on these points:

• Going step by step. Launch one process or one site first, not everything at once.
• Data migration. Data moved over from old spreadsheets and programs has to be cleaned first. Bad data stays bad in the new system.
• Training. Short, practical sessions on people's own tasks, not one long generic course.
• Quick fixes in the first weeks. Real use always brings small surprises. If they are handled quickly, the team keeps its trust in the system.
• Testing before go-live. Bugs shouldn't surface in front of your customers. With us, every feature gets automated tests, and a human reviews the code before release.

How much does an ERP system cost?

A responsible vendor won't name a number in the first conversation, and that is not evasion. The price depends on how many processes the system covers, how many users work in it, which external tools it must connect to, how much old data has to be migrated, and how strict the security or compliance requirements are. With packaged products, licences, customization and consulting fees make up the total; with custom development, it is scope and complexity.

That is why we don't estimate blind. After the intro call comes a short, fixed-fee assessment. At the end you get a clickable prototype of the planned system, and based on that we give you an itemized, fixed-price quote. If we continue into the full build, we credit the assessment fee against the project price. See how this phase works step by step.

We explain the factors that drive ERP pricing in detail in our article on ERP system cost.

How we work when you need a custom system

If you are leaning toward custom development, this is what a project looks like with us:

We start with a free initial consultation. Based on it, we design the system at a fixed price, step by step, so from the very beginning you see on a live prototype how it will work. After that, in a separate offer, we give a fixed price for development that covers everything we recorded during design.

1. Free initial consultation (1 hour, online, in English). We talk through how your company works, what the goal is, and what hurts most today.
2. Fixed-price system design with a live prototype (typically 1 to 4 weeks for a small to medium project). You don't get a text specification but a realistic, fully clickable prototype with the final colours and layout. We refine it until it is exactly what you want.
3. Separate fixed-price development offer. In writing, based on the approved prototype. No open-ended invoice, and if a new need comes up during the project, we flag it up front and only start on it with your approval.
4. Development with weekly updates. You get a short summary every week, and we demo working software as soon as there is something meaningful to show.
5. Go-live and training. We set up the system, hand over the user guide and train your team.

The finished product, the source code and the documentation are yours. If you ever want to continue with someone else, you can. A non-disclosure agreement is part of the standard package. See the full process here.