Custom ERP development that runs alongside the invoicing and accounting you already have.
Stock, orders, purchasing and management reporting in one system, starting where the most manual hours go today. What already works stays, and the new system connects to it directly or through a regular data handover.
12+ projects delivered
every one on deadline, in production
Fixed price and deadline
in writing, and if we slip, the next payment waits
Reply within 24 hours
on working days, to every enquiry
In writingFixed quote after scoping
One module end to end, connections and training included.
How stock and orders run today
You sell an item on Friday, find out on Monday it was not in stock, and the customer gets a cancellation.
The same order goes from the shop into a spreadsheet and on into invoicing, and every retype adds a mistake.
Someone builds the monthly report by hand, and by the time it is done the numbers describe last week.
At month end the accountant gets the invoices and the stock separately, and the two never match.
Which one is your situation?
Stock catches up after the fact
Stock and goods-in: incoming items are recorded in one place, and stock moves with every sale.
One order, typed three times
Orders and fulfilment: an order is entered once and reaches the warehouse and invoicing from there.
Purchasing is decided by email
Purchasing: the shortfall list builds itself from live stock, and the approval stays in the system.
Reports are assembled by hand
Management reporting: the numbers come from the same data the team works in, with no manual collation.
Orders and stock on one screen
The highlighted row is Friday's sale: the shortage shows the moment the order is entered, and the purchase request starts from there.
Open orders
- Customer and orderExample & Co.R-2418ItemOrderedAvailableValueStatus
- Customer and orderSample Builders Ltd.R-2417ItemOrderedAvailableValueStatus
- Customer and orderDemo Holdings Ltd.R-2416ItemOrderedAvailableValueStatus
Pump RX-200
Invoicing, shop, stock and accounts on shared data
- InvoicingInvoicing issues the invoice from the same order, without retyping.
- ShopWhat sells in the shop comes off warehouse stock, with no separate reconciling.
- StockThe warehouse records incoming goods in one place, and purchasing sees the shortfall from it.
- AccountsThe accountant gets a scheduled export where their software allows no direct connection.
The modules your system is built from
We start with one module, the one that eats the most manual hours, and the rest builds on its data.
Stock and goods-in
Stock movements, reservations and stocktake in one place, with incoming goods recorded line by line.
Orders and fulfilment
An order is entered once and can be followed from packing to dispatch.
Purchasing
The shortfall list builds itself from stock, with an approval step.
Quote and invoice
The quote, the order and the invoice come from the same line items.
Management reporting
Stock value, orders and revenue in one view, with no manual collation.
Sites and departments
Shared stock, with permissions and views set per site.
88%
of audited business spreadsheets contained at least one error, and most of those stay hidden until they cost money.
Panko, University of Hawaii: 113 real business spreadsheets across seven field audits.
Companies we've built for
What you get with the first module
- A data map: where each piece of data lives today, and who reconciles it
- A written, scheduled proposal for the first module, as one sum
- The first module taken live, its connections included
- Training for the people who run the stock and the orders
- Migration from the old system, as a separate line item
- Source code, credentials and documentation at handover
Example
At a wholesaler we would start with orders: orders from the shop and by phone land in one place, stock is reserved from there, and invoicing receives the line items. The purchasing list builds itself from what is short. Management reporting goes into the next module, on the same data.
How the first module goes live
We go through which data lives in how many places and who reconciles it. By the end we tell you which module to start with.
The map shows where data travels today and which steps are manual, and you get a scheduled, itemised proposal for it. That price holds until the first module is live.
The first module is built together with its connections, and the people in the warehouse or the office try it as it grows.
Go-live comes with training, and the next module builds on the same data under its own proposal.
Call
Scoping
Build
Live
Spreadsheets, a boxed ERP or your own
Many companies start on spreadsheets or a boxed ERP, and for standard industry processes that is the right answer.
Spreadsheets and manual reconciling
A boxed ERP
An in-house developer or a freelancer
Brecon
What it costs, and what makes it grow
Nothing while two people keep them. After that, the hours of reconciling and the cost of mistyped lines.
A licence fee and a rollout project, and every custom need is another configuration line.
A salary or an hourly rate, and the total shows up at the end.
One sum per module in the proposal, and if we slip, the next payment waits.
What happens to your existing systems
They stay, and a person copies between them.
Often replaces them, or leaves workarounds in between.
However they solve it, and the knowledge leaves with them if it is not written down.
Built alongside them, and the handover includes the source code, the accounts and the documentation.
Who owns the data and the system
In files anyone can overwrite.
The data can be exported, the configured process stays in the product.
It depends on the contract, down to one sentence.
It is yours, with your data in your own database, from the final invoice.
When this is the better choice
For few items, one site and one person running it.
When your processes are standard and the industry logic in the box fits them.
When the system changes daily for years and someone directs the work.
When you would start with one module and keep your invoicing and accounting.
What it costs, and what makes it grow
- Brecon
- One sum per module in the proposal, and if we slip, the next payment waits.
- Spreadsheets and manual reconciling
- Nothing while two people keep them. After that, the hours of reconciling and the cost of mistyped lines.
- A boxed ERP
- A licence fee and a rollout project, and every custom need is another configuration line.
- An in-house developer or a freelancer
- A salary or an hourly rate, and the total shows up at the end.
What happens to your existing systems
- Brecon
- Built alongside them, and the handover includes the source code, the accounts and the documentation.
- Spreadsheets and manual reconciling
- They stay, and a person copies between them.
- A boxed ERP
- Often replaces them, or leaves workarounds in between.
- An in-house developer or a freelancer
- However they solve it, and the knowledge leaves with them if it is not written down.
Who owns the data and the system
- Brecon
- It is yours, with your data in your own database, from the final invoice.
- Spreadsheets and manual reconciling
- In files anyone can overwrite.
- A boxed ERP
- The data can be exported, the configured process stays in the product.
- An in-house developer or a freelancer
- It depends on the contract, down to one sentence.
When this is the better choice
- Brecon
- When you would start with one module and keep your invoicing and accounting.
- Spreadsheets and manual reconciling
- For few items, one site and one person running it.
- A boxed ERP
- When your processes are standard and the industry logic in the box fits them.
- An in-house developer or a freelancer
- When the system changes daily for years and someone directs the work.
Who a custom ERP fits, and who not
This fits you if
- Stock, orders and invoices live in several places, and people reconcile them.
- You have invoicing and accounting software you do not want to replace.
- Several sites or departments work from the same stock.
We would point you elsewhere if
- A standard, industry ERP already covers your processes and only the setup is missing. Then that is the better route, and we will say so on the call.
- For stock tracking at a single site, an off-the-shelf warehouse tool costs less.
If an approval loop or an internal process is the problem, that is internal systems development.
How we work
Custom ERP from the first module to training
- One fixed price per module in the proposal, unchanged until it goes live
- Your invoicing and accounting stay; the new system is built beside them
- The source code, the credentials and the database are yours
In writing
Fixed quote after scoping
One module end to end, connections and training included.
How many modules go into the first round, and how many existing systems must it connect to? The first module gets a fixed-sum proposal.
Request an ERP reviewWhat happens after launch
As a new site or product line arrives, the system has to grow with it, so we keep working on it after handover.
First month
A clean handover, a watched launch
Source code, credentials and documentation in your hands, and we watch the first week with you, measurements included.
Every month
Maintenance that keeps it moving
Updates, fixes, extensions, and an eye on the measurements.
If something breaks
You write, we answer
A first reply within 24 hours on working days, to every enquiry.
What people ask before an ERP rollout
They stay. The new system is built alongside them, connected directly or through a scheduled export, and we only replace what causes manual work today. We recommend replacing a system only when that is genuinely cheaper.
We start with one module, the one that eats the most manual hours, and take it live. The next module builds on the same data under its own proposal, so every stage is useful on its own and you can stop at any point.
The price list says "Fixed quote after scoping", because the number of modules and connections decides it. After scoping you get a fixed-sum proposal with a schedule for the first module, and that price holds until it is live. Migrating from your current system is quoted as a separate line.
Where a system is open to integration (Számlázz.hu, Billingo, Shopify, Google Workspace), we connect it directly. Where it is not, we run a scheduled import and export, and if a transfer stalls you can see what went through and what did not.
You do. The source code, the accounts and the documentation are part of the handover, the data sits in your own database, and the system keeps running if we step away.
Most of it at the start: a few hours with the people who run stock and orders every day, because their workarounds are the real requirement. During the build we ask at decision points, and go-live comes with training.
At handover you get a monthly maintenance proposal: updates, fixes, extensions, as new modules or sites come in. The code is yours, so an in-house developer or another team can carry it on.
Start with the most expensive manual work
Tell us which invoicing tool and shop you run, and which data you type in twice: the first call starts there.
- 12+ projects deliveredevery one on deadline, in production
- Fixed price and deadlinein writing, and if we slip, the next payment waits
- Reply within 24 hourson working days, to every enquiry