Sound familiar?
The spreadsheet, the inbox, and the ERP demo that didn't fit
Most growing businesses run on a patchwork that worked fine at ten orders a week:
- Quotes live in email threads and spreadsheets — versioned by memory, in files called final_v3.xlsx.
- The same order gets typed three times — into the quote, the work order, and the invoice — and every copy drifts a little.
- Nobody knows the real margin on a line until long after it's been sold.
- Every off-the-shelf ERP demo ends the same way: too big, priced per seat, and "your process will need to fit the software."
An ERP should encode how your business wins — not flatten it into someone else's template.
What we build
Modules, not a monolith
Every module is built for your process and goes live on its own, in the order your business needs it. The usual building blocks:
Quotes & sales
Product configurators, versioned quotes, review-before-send, and online acceptance — a request becomes a priced offer without retyping.
Production & work orders
An accepted quote becomes a work order in one step, with shop-floor notes generated from the sold spec, in the language your workshop speaks.
Invoicing & e-invoicing
Invoices, proformas, and advance settlements generated from the quote's own data — with Serbian eFaktura (SEF) built in where you need it.
Stock & inventory
A ledger where every movement is an entry and balances are derived, never typed — with low-stock flags before a shortage costs you an order.
Costing & margins
Rate cards feed a cost calculator inside the quote, so every price is set next to its real cost and margin.
Customer portal
Customers accept quotes, track orders, and download documents themselves, in their own language — "where is my order?" stops being a phone call.
Export & compliance paperwork
Customs, origin, and CITES declarations, packing specifications, and GDPR-ready data handling — generated from the same data, never typed twice.
AI agents on top
Agents that report on your ERP data — stock, stores, margins, cash flow — by email, and, where you want it, read incoming documents so your team reviews instead of retyping.
Want the busywork around the system automated too? See our AI agents
Why custom wins
Cut to measure beats off the rack
It fits your process
Your stages, your article codes, your documents — encoded as they are, not approximated by a template's settings.
It costs a fraction to run
Static hosting and one managed database. No per-seat licences, no server farm — a monthly bill closer to a phone plan than an enterprise contract.
It changes at the speed of your business
A new document type or workflow ships in days, not through a consulting engagement.
The code and the data are yours
Your repository, your database, standard technologies. No export fees, no lock-in — any developer can take it over.
How an ERP project runs
Shipped live, piece by piece
- 1
Map the real workflow
Not the org chart — the actual working day. Where a quote really starts, where paper gets retyped, where money leaks.
- 2
Revenue side first
The module closest to money — quotes, the storefront, or the customer portal — goes live first, on your real data.
- 3
Back office, module by module
Work orders, invoicing, stock, costing: each goes live on its own while the rest of the business keeps running.
- 4
Hand over the keys
Code, database, and documentation are yours. We stay as long as we're useful, not because you're locked in.
Proof, not promises
ERPs we've shipped
Both systems below run real businesses today.
DAS Handel
Custom ERP and trilingual B2B portal for a Serbian acacia-wood exporter: quote versioning, work orders, invoicing, customs and CITES paperwork, costing, and a stock ledger.
Read the case studyTsarski
Booking and operations system for independent hosts: an overlap-safe calendar, automated guest emails, a cleaning-agency portal, and Serbian tax-compliant receipts.
Read the case studyCustom ERP questions
What is a custom ERP?
An ERP (enterprise resource planning) system is the software a company runs its core operations on — sales, production, invoicing, stock, and reporting. A custom ERP is built for one business's actual process instead of configured from a generic product, so it holds the rules, documents, and languages that business really uses.
Custom ERP or an off-the-shelf product like Odoo or SAP Business One?
If your process matches a standard product, buy the standard product — we'll say so in the first conversation. Custom wins when a template would force you to change how you win work: make-to-order specs, export documents, customers in several languages, or rules the product can't hold.
How long does a custom ERP take to build?
It doesn't arrive all at once. The first module — usually the one closest to revenue — goes live early, on your real data, and each further module ships on its own. You're using the system long before it's "finished", and you decide what comes next.
How much does a custom ERP cost?
Each module is scoped and priced as a fixed increment before work starts — no open-ended hourly billing. Running costs stay low: static hosting and one managed database, no per-seat licences. Serbian SMBs can often co-fund the build through PKS digitalization grants or Innovation Fund vouchers.
Can a custom ERP handle Serbian e-invoicing and fiscalization?
Yes. Serbian requirements — eFaktura (SEF) e-invoicing, fiscal receipts, eTurista — are built in as working features or connected to the services the law requires, not bolted on as exports after the fact.
Who owns the ERP and the data?
You do — the code, the database, and the data, from day one. No per-seat licences, no export fees. If we part ways, everything keeps running and any developer can take it over.
Tell us how your orders really flow
Walk us through one order, from the first request to the final invoice. We'll tell you which modules would pay for themselves first — and whether you need a custom ERP at all.
Send us a message
Fill out the form below and we'll get back to you within 24 hours.