ERP for manufacturing companies: why a prototype and user testing come before code

In short: ERP projects in manufacturing usually become expensive not because of programming, but because code is written before anyone understands how people really work. We build ERP in 10 steps: research with every department, a prototype, tests with at least 5 users and 10 scenarios, repeated tests until every scenario runs smoothly, design, and only then development. The result: you save money and get a system that does exactly what your company needs, instead of forcing your company to adapt to a large system’s rules.

Where this approach comes from

I have been managing IT projects since 2007 and have led the implementation of several systems in projects such as the manufacturing company Biroja tehnikas eksperts (BTE), Latvijas Pasts, Venden, the training centre “Liepa”, Andele Mandele and others. Each time the same thing happened: the most expensive changes came not from buggy code, but from a misunderstood process.

A warehouse worker works differently from how management describes it. Accounting needs a different report than sales expected. If you learn this after development, the fix costs weeks. In a prototype, it costs hours.

That is why in CREATING.LV ERP projects programming is the last step, not the first.

What ERP gives a manufacturing company

Off-the-shelf ERP systems often fail in manufacturing precisely because every company has its own recipes, components, work sequence and cost logic. A custom system connects all of it:

  • Recipes and components: each product has its own bill of materials and cost price, which changes with raw material prices.
  • Production planning: from the order to the production task for each workshop.
  • Timely procurement: the system shows which components to order and when, based on planned products.
  • Warehouse with scanning: raw material and finished goods stock, inventory with barcode scanners.
  • Staff: time tracking, productivity and cost per order or product.
  • Accounting: invoices and data flow automatically into your accounting system, for example Tilde Jumis.

The main benefit: a system that fits you and belongs to you

With large off-the-shelf systems, the company adapts to the software: you pay for licences, every user and every extra module, and part of the process still stays in Excel. A custom ERP works the other way round: it is built around your processes, with no monthly subscription and no per-user fees.

One system can combine everything the company needs:

  • procurement and warehouse;
  • products and recipes;
  • timely component procurement based on planned production;
  • staff time tracking;
  • staff productivity and cost analysis;
  • barcode scanning and inventory;
  • delivery module;
  • invoicing module;
  • reports and statistics;
  • data transfer to accounting systems, for example Tilde Jumis.

10 reasons why your own ERP pays off better than an off-the-shelf solution

Your own ERPOff-the-shelf
1. Monthly feeNonePaid every month
2. Per-user feesNone, unlimited usersGrows with every new employee
3. OwnershipThe system and code are yoursThe system belongs to the vendor
4. Fit with processesExactly your way of workingThe company adapts to the software
5. FeaturesOnly what you useYou also pay for what you don’t use
6. New modulesAdded when you need themDepends on the vendor’s plans
7. IntegrationsAny, including Tilde Jumis and scannersOnly those the vendor supports
8. DataStored with youOn the vendor’s servers and terms
9. Price riskNot affected by vendor price increasesSubscription prices can rise
10. IncomeYou can rent or sell the system to other companies and cover part of the costNot possible

One of our clients already rents out its ERP system to other companies, so it is not only a working tool but also a source of income.

The system still needs hosting and, if you wish, maintenance, but these costs do not depend on the number of users.

The 10 steps we use to build an ERP system

  1. On-site research. We talk to every department: procurement, warehouse, production floor, sales, accounting and management. We look at how the work really happens, not how it is described in instructions.
  2. Collecting information. Processes, statuses, roles, data and integrations are collected in one document. The client approves it before we move on.
  3. Preparing the prototype. From this we create a list of screens and user scenarios, such as “accept an order”, “reserve stock”, “issue an invoice”.
  4. Building the prototype. We build a clickable prototype that looks and works like the system, but without code yet.
  5. User testing. At least 5 real employees of the client complete at least 10 scenarios. Every hesitation, question and mistake is recorded.
  6. Analysis and adjustment. Problems are prioritised and the prototype is fixed.
  7. Repeated testing. Tests are repeated until every scenario runs smoothly: users complete them without help and without errors.
  8. Design. Only once the logic is approved do we add the visual design.
  9. Testing with the design. We check that the design has not broken anything that already worked and that the system is comfortable for daily use.
  10. Development. We code what has already been tested. Rework is minimal and the budget is predictable.

Why 5 users and 10 scenarios

With just 5 people from different departments, most of the significant usability problems usually surface. 10 scenarios cover the main daily tasks the system is built for. If a scenario does not run smoothly, the process is not yet fully understood, and it is better to find that out now.

Common mistakes in ERP projects

  • Only management writes the requirements. Daily users see the system for the first time on launch day.
  • Everything at once. All modules are built at the same time and the first result appears a year later.
  • Design before logic. Beautiful screens that don’t match the process and have to be redrawn.
  • Integrations left until the end. Accounting, warehouse and the online store must be understood during research.

When a custom system is not needed

If an off-the-shelf solution such as Odoo, SAP Business One or Microsoft Dynamics fits your processes, we recommend it. A custom ERP is worth it when the ready-made tool requires too much manual work, customisation or licences for features you don’t use. Even then we start with one, most important module, from EUR 8,500 + VAT.

Frequently asked questions

How much does an ERP system for a manufacturing company cost? The first, clearly defined module starts from EUR 8,500 + VAT. In previous years a complete ERP system cost around EUR 500,000, but with AI tools in development the same work can now be done at least 5 times cheaper. We set the price of a full system after on-site research.

How long does the prototype stage take? It depends on the number of departments and scenarios. We give an exact schedule after the on-site research.

Isn’t the prototype an unnecessary expense? No. A change in a prototype takes hours, in finished code it takes weeks. The prototype reduces the total cost rather than increasing it.

Who tests the prototype? Your employees who will use the system every day, not just management.

What do you build it with? Laravel, Filament and Livewire. The code belongs to you.

Ready to start an ERP project?

Tell us which departments and processes you want to bring into one system. We will suggest which module to start with and describe what the on-site research would look like.

Custom business systems · Contact us

Contact

Start a project

Describe your project or question — we will reply and suggest the most suitable solution.

Request about: General request Change

Optional. Names and prices are taken from our price list.

Optional · one file · PDF, JPG or PNG · up to 10 MB

required · Privacy policy

Request a project

Describe your project or question — we will reply and suggest the most suitable solution.

Message us on WhatsApp (opens in a new tab)