Custom ERP and business software for companies that outgrew Excel.
Inventory, orders, invoicing, production and the people who run them - in one system that follows your process instead of renaming it after someone else’s menu. We design, build and maintain bespoke ERP systems and inventory software for small and mid-sized companies in Bosnia and Herzegovina, Serbia, Austria and across Europe.
- One database for stock, orders, invoices and production - nothing to reconcile on Friday.
- Only the modules you use, built in the order that saves the most manual work.
- Connects to accounting, web shop, banks, fiscal devices and e-invoicing where required.
- No per-seat licence: add people without adding costs.
One system instead of six spreadsheets
Most small companies already run an ERP. It is spread across six spreadsheets, two inboxes and the memory of the one person who knows which file is current - which works until the second warehouse, the web shop, or that person’s holiday. Packaged suites promise a fix, then ask you to adapt to their screens and pay per user for modules nobody opens.
A custom ERP takes the other route. We map how orders, stock, invoices and production actually move through your company and build the system around that flow: one PostgreSQL database as the single source of truth, a browser interface your staff learn in an afternoon, and connections to the tools you keep - accounting, e-commerce, banks, and fiscal devices or e-invoicing where your market requires them.
We build in stages. The first module, usually the one that saves the most retyping, goes live on its own and runs next to the old spreadsheets until the numbers agree. Then the next. No big-bang weekend, and the data and the roadmap stay yours.
How it works
What changes when the spreadsheets go
Three things a custom ERP does for a company that used to run on spreadsheets - shown for a small wholesaler.
-
Orders, stock, invoices and production stop living in six files and two inboxes. They move into one system, and everyone looks at the same numbers.
-
One new order reserves the stock, drafts the invoice and updates the sales figure - all at once. Nobody retypes anything, so nothing gets typed wrong.
-
When stock runs low, the system drafts a purchase order for the usual supplier. Someone checks it and sends it with one click.
In practice
Illustrative scenarios - the kind of work we take on, not client case studies.
Metal workshop with made-to-order production
- The problem
- Orders arrive by phone and email, production is planned on a whiteboard, and sheet metal is ordered when someone notices the rack is empty. Nobody can say when an order will ship.
- What we build
- Order intake with bills of materials, so confirming an order reserves material and shows any shortfall. A production board per workstation, fed from the same orders. Delivery notes and invoices from the finished job, exported to the existing accounting software.
- SvelteKit
- PostgreSQL
- Node.js
- PDF generation
- Accounting export
Wholesaler with a web shop and two warehouses
- The problem
- One warehouse keeps stock in an old desktop program, the other in a spreadsheet, and the web shop sells items that are already gone. Every evening someone exports CSV files to keep them roughly aligned.
- What we build
- One stock ledger with quantities per location, transfers as proper documents, and a web shop sync that reserves stock the moment an online order lands. Receiving and picking by barcode scan on ordinary phones.
- TypeScript
- PostgreSQL
- Redis queues
- Web shop API
- Barcode scanning
Service company billing hundreds of recurring contracts
- The problem
- Monthly invoices are made by copying last month’s file. Price changes and contract ends get missed, and the accountant types everything in again.
- What we build
- Contracts as records with price, period and indexation rules. A monthly job prepares all invoices for review, sends them by email or e-invoicing where required, matches bank payments and hands the journal to accounting.
- SvelteKit
- PostgreSQL
- Scheduled jobs
- Bank statement import
- E-invoicing
What you get
- Process mapping workshop and a written plan: modules, data model, integrations, rollout order
- Fixed-scope estimate per stage, so every module is priced before work on it starts
- Browser-based ERP for desktop, tablet and phone, with roles and permissions
- Data migration from spreadsheets and old software, with a conflict report you sign off
- Connections to accounting, web shops, banks, fiscal devices and e-invoicing where required
- Audit log of every change: who, what, when
- Admin training, plus a staging copy for testing changes safely
Typical stack
- TypeScript
- SvelteKit
- Node.js
- PostgreSQL
- Redis
- REST APIs & webhooks
- Python (reports, forecasting)
- PDF & barcode generation
- CSV / Excel import
- Docker
- Linux
Questions people ask
Your question is not on the list? Ask us directly - we reply within two working days.
Ask a questionHow much does a custom ERP system cost?
It depends on the number of modules, the integrations and how messy the data migration is - not on how many people log in. Send us a short description; we reply within two working days with a link to a 30-minute intro call, then follow up with a written plan and a fixed-scope estimate per stage, so each module is priced before it is built.
How long does it take to build an ERP?
Rarely as one block. We split the work into stages that each go live on their own, starting with the module that saves the most manual work, and run it next to your spreadsheets until the numbers agree. Duration depends on scope, integrations and how quickly decisions are made on your side; the written plan gives dates per stage.
Custom ERP or off-the-shelf software - which is better for a small business?
If a standard package fits your process with light configuration, use it - it is cheaper. Custom pays off when your workflow is part of your advantage (made-to-order production, unusual pricing, several locations) or when the real problem is tools that do not talk to each other. A common middle path: keep your accounting software and build the operational side around it.
Will it work with our accounting software, fiscal devices and e-invoicing?
Usually, yes. We connect through the accounting software’s API or import format, and to fiscal devices, e-invoicing platforms and banks where your market requires them. Where bookkeeping or fiscalisation must stay in specific approved software, the ERP feeds it clean data instead of replacing it. Details differ by country and product, so we check them during planning.
Can we start with just one module?
That is how we prefer it. The first module - usually orders, stock or invoicing - goes live on its own and runs next to your spreadsheets until the numbers agree. Each next module plugs into the same database, so nothing has to be rebuilt.
Can you replace the software we use now?
Yes. We start with an audit of the current software and data: what works, what breaks, what can be migrated. Sometimes the right move is to extend the existing system through an API; sometimes it is a staged replacement, retiring the old system one module at a time. Either way your data comes with you.
Tell us where the spreadsheets hurt.
Describe how orders, stock and invoices move through your company today. We reply within two working days with a link to a 30-minute intro call, then follow up with a written plan and a fixed-scope estimate.
Plan your ERP