Most companies do not need a new ERP. They need the part their ERP cannot do: the pricing grid, the quoting flow, the shipping desk that still runs on a spreadsheet. We build those modules, connected to the ERP you keep, and a complete custom ERP when the operation really is unlike any product.
Book a free 30-min intro call
Each of these replaced a spreadsheet or a manual process that the company's ERP or accounting system could not handle, and each is in daily use.
A 90-tab pricing workbook, every cuvée, format, zone and channel, turned into one web app that is now the single source of truth for every price.
Read the case study →A quotation and pricing platform where a single quote can run into the tens of millions of pesos: revisions, signatories, and PDF and Excel exports.
Read the case study →A shared shipping workbook replaced by a platform that prints service reports and packing slips, in production the day after we received the file.
Read the case study →An engine that turns WhatsApp voice notes from small merchants into structured orders, matched to each merchant's own catalog.
Read the case study →And when not to: if your accounting, inventory and invoicing are standard, keep a product for them. Replacing a working ERP to fix one process is the most expensive way to fix it. We will say so on the first call.
Custom ERP development covers very different projects. The right one depends on how much of your ERP still works for you.
| Option | What it means | When it fits |
|---|---|---|
| Configure | Set up the ERP you have properly: workflows, fields, reports, user roles. | The ERP can do it, and the problem is how it was set up. |
| Integrate | Connect the ERP to the tools around it so data stops being re-typed: e-commerce, CRM, quoting, shipping carriers, documents read by AI. | Each tool works, but the copying between them costs hours and causes errors. |
| Build a module alongside | A custom application for the one process the ERP cannot handle, synced with the ERP, which stays the system of record. | One process is specific to you, and the rest of the ERP is fine. |
| Build a custom ERP | An ERP designed around your operation, owned by you, replacing the product module by module. | The operation is the business, and every product forces workarounds across several departments. |
Most of our projects are option three: a module next to the ERP, which costs a fraction of a replacement and leaves the parts that work alone.
In stages, each one used in production before the next begins, while the business keeps running on what it has.
We work from the file or the process people actually use, with the people who use it. The exceptions, the special customers and the rules nobody wrote down come out here, before anything is built.
One process, live with real data and your team's existing sign-in, connected to the ERP where data has to flow. It replaces the spreadsheet completely rather than sitting next to it.
The next process, the next integration, each added and used before the next. Every stage has a fixed scope and price agreed in writing.
We host, monitor and maintain it, with security updates every week, or hand it to your team with the code, the infrastructure and the documentation in your name.
These are the ranges we work to, in US dollars. A custom module has no per-seat licence, but it does have running costs, and we list them too.
| Scope | Budget | What you get |
|---|---|---|
| One module | $5,000 to 18,000 | One process replaced and running in production, such as pricing, quoting or shipping, connected to your ERP where needed. |
| Several modules | $18,000 to 45,000 | Several processes, data migrated from spreadsheets or the old system, and integrations with your ERP, accounting or CRM. |
| Custom ERP | $45,000 and up | An ERP across several departments, replacing the product in successive stages against agreed milestones. |
| Running it | from $470 / month | Maintenance with weekly security updates and monitoring, plus infrastructure, often $50 to 100 a month. |
What moves the price: the number of exceptions in the process, how many systems the module has to talk to, and how much data has to be cleaned and migrated. The integrations are usually the largest share.
Custom ERP development is building enterprise resource planning software, or parts of it, around a company's own operation instead of adapting the operation to a product. In practice it is most often a custom module, such as pricing, quoting or shipping, connected to the ERP the company keeps.
At Reflekt Lab, one custom module costs $5,000 to $18,000, several modules with integrations $18,000 to $45,000, and a custom ERP across several departments from $45,000, delivered in stages. Running it starts at about $470 a month for maintenance, plus infrastructure.
Customize or extend the ERP you have when it handles most of your operation and one or two processes do not fit. Build custom modules alongside it when a process is specific to you. Replace it only when every product forces workarounds across several departments.
Yes, and that is most of our work. The module reads and writes through the ERP's API or exports, the ERP stays the system of record, and people stop re-typing data between the two.
A first module is usually in production within a few weeks. A larger scope is delivered in stages over a few months, and each stage is used before the next one starts.
Yes. Orders, invoices and quotes that arrive as email, PDF or photos can be read by a model and drafted as ERP records, with a person approving each one before it is written.
A free 30-minute call. Describe the process that lives in a spreadsheet, and leave with a view on whether to configure, integrate or build, and what it would cost.
