Service
dotNET lab builds business software around the processes and the packages you already have. We do not simply replace your ERP or accounting software: we build the custom layer that integrates with it, and replace only where that is genuinely better.
Purchasing, sales, stock and invoicing in one coherent whole that follows your operation. No more double data entry between scattered tools.
The problem
The question for an ERP rarely starts with software. It starts with double work.
Explained
A custom ERP is business software that brings all your core processes together in one system that follows your operation: purchasing, sales, stock, planning and invoicing.
ERP stands for enterprise resource planning, but do not let the term put you off: for an SME it simply means that data is entered once and is correct everywhere afterwards.
With us, custom rarely means replacing everything. Usually your accounting software or package simply stays and we build the layer around it that covers your processes. Which route fits, you see below.
The result runs in the browser: at the office, in the warehouse or on the road, the same current figures for everyone.
More about custom web applications See our full custom software offering
Three routes
Which route fits depends on how much of your operation is already well covered. This is how we look at it:
Your accounting software or ERP, such as Odoo or Exact Online, may cover 80 percent of your operation. We build the custom layer next to it for the processes that set you apart: quote flow, warehouse, planning or site follow-up. Connected through APIs, so updates of your package keep working.
For those happy with their package, but watching workarounds and Excels grow.
If your processes are your edge, we build the whole thing to measure: from order to invoicing in one system that follows your flow exactly, without package limits.
For unique operations no package fits.
If you are stuck with an outdated or overpriced system, we replace it in phases, without halting daily operations. Your data moves along.
For those who have outgrown their current system or are done with the licences.
You often hear that custom software is expensive and fragile next to a package. That is true for custom work inside the core of a package. A layer next to it, connected through APIs, leaves updates untouched and you pay only for what sets you apart.
Sectors
The processes differ per sector; the principle does not: entered once, correct everywhere.
Client-specific prices and discounts, orders that flow straight through to delivery and invoice, and B2B clients who place orders themselves.
Stock that matches the shelves, barcode scanning at receipt and dispatch, and shipments that follow themselves up.
From quote with post-calculation to production planning and material requirements, with work orders on the floor instead of paper.
Integrations
The heart of a custom ERP is not the screen but the data flow: every order, delivery and invoice landing in the right place by itself.
Accounting in Odoo or Exact Online? It stays the accounting. The custom layer sends invoices and payments to it and pulls the figures back, with the Odoo integration experience we built up in earlier projects.
B2B traffic belongs there too: EDI messages with large buyers and e-invoicing through Peppol run in the same flow.
For example with
Running something else? With an API or an export option we will work it out together.
Drawing the line
An ERP streamlines your internal operation: purchasing, stock, planning and administration. A CRM streamlines your sales: contacts, quotes and follow-up.
If the frustration is growing mainly on the selling side, start there.
Approach
An ERP project does not have to take a year. We cut it into releases that each save work on their own.
You walk us through your operation: where does work happen twice, and which systems already run?
You hear which route fits: a custom layer next to your package, full custom, or replacing. A figure follows from the analysis.
We pick the process that costs the most today, for example order processing, and pin down its scope and price.
Every month we deliver a concrete piece of working software that your team actually uses, next to the systems that simply keep running.
Data moves along in a controlled way, your team is trained, and the old way of working is switched off only once the new one has proven itself.
Costs
A fixed price list does not exist. What you invest follows from three things:
€9,500
per program goal, delivered every month
A fixed budget per program goal. After each delivery you decide: keep building, pause or stop.
Included per program goal
A delivery every month: a concrete piece of working software
* We also charge a one-time program setup of €6,000: that is where we get to know your organisation and pin down the scope of the first release.
What else determines the price:
We aim for growing along: every release has to earn itself back in hours won.
You do not have to buy an ERP in one go. The first release tackles the most expensive process; every next one builds on it.
Compare it with per-user licences that return every year: here you invest deliberately, and what is built stays yours.
A clear answer within two working days, no obligation.
Client cases
Building and renewing business-critical systems is our daily work. Three glimpses.
How an outdated desktop application became a manageable, modern web application.
Read the caseLegacy modernisation without halting daily operations.
Read the caseCustom development, with AI and machine learning, for the Department of Agriculture & Fisheries.
Read the caseOrganisations we build for
FAQ
ERP stands for enterprise resource planning: one system that brings your core processes together, from purchasing and stock to sales and invoicing. For an SME it comes down to this: enter data once, and it is correct everywhere.
That depends on the route, the release rhythm and the integrations. We work in program goals: every month we deliver a concrete piece of working software, from €9,500 per program goal, with a one-time program setup of €6,000 beforehand. A custom layer next to your existing package usually asks less than replacing everything; after an intro call you hear within two working days which route fits.
Usually not. If your package covers most of your operation, it stays and we build the custom layer next to it, connected through APIs. We only replace when the system is genuinely at the end of its life, and then in phases.
No. SAP is one brand of ERP software, aimed at large enterprises. For SMEs there are packages such as Odoo, and custom software for those who want their processes followed exactly. ERP is the category, not the product.
Not an eighteen-month project with a big bang at the end. We scope the first release around the process that costs the most, put it live while your current systems keep running, and build on release by release. Data migration and training are part of the standard package.
Yes. EDI traffic with large buyers and e-invoicing through Peppol join the same data flow as your orders and invoices, so B2B documents leave and arrive without manual work.
The first release, for example order processing without retyping, is often up within a few program goals. You notice the gain while the rest is still being built, and you decide after each delivery whether we continue.