When quotes, orders and stock rely on several files and on the memory of a few people, the problem is no longer an IT one: it is how the company runs. A custom ERP does not copy a big software package: it is a simple, web-based tool built around your real workflow, from the first quote to delivery.
In a company of ten to fifty people, things can work well for years with an invoicing package, a few spreadsheets and well-established habits. Everyone knows where to find the information, who to call and how to unblock an order. Then the company grows.
A quote is prepared in one file, picked up in another, then retyped into the invoicing software. A purchase order is tracked in a spreadsheet the sales rep never opens. Theoretical stock no longer matches real stock. A reference has changed price, but the old rate is still circulating. Chasing a customer depends on a reminder written down somewhere. And when the person who knows how it all works is away, part of the company seems to go on holiday with them.
These are not necessarily big isolated problems. They are wasted time, data entry errors, contradictory information and decisions taken with incomplete visibility. Beyond a certain volume, those small frictions become a real running cost.
Generalist ERPs are not bad tools. They are designed to meet broad needs, in organisations with IT resources, project managers and people able to maintain the configuration. The problem appears when the company has to adapt the way it works to the software rather than the other way round.
You start by choosing modules, defining rights, configuring screens, importing data and training the teams. Then you discover that the real process does not exactly match the one that was planned. You have to add exceptions, work around certain steps, create parallel files or ask staff to enter the same information several times. The cost is not limited to the licence: it includes configuration, integration, training, maintenance and sometimes bespoke development. Some essential functions turn out to be options, extra modules or separately billed services.
The result can be paradoxical: a very complete piece of software, but a company that keeps using its spreadsheets because it is faster.
A custom ERP does not mean developing a different piece of software for every employee, with a function for every exception and a screen for every request. It means starting from how the company really works and building only what brings concrete value.
For a trading or manufacturing SME, the first scope can be very simple: the quote, the customer order, the purchase order, the item, the stock, the delivery and the follow-up. A single database links these together. The quote becomes an order. The order reserves stock or triggers the necessary purchases. Goods receipt updates the stock. The delivery is prepared from information already entered. The invoice is generated without retyping.
The owner sees the orders in progress, the purchases to be received, the stock available and the deals needing action. The sales rep finds his customers and his quotes. The workshop accesses the information it needs from a computer or a phone. The aim is not to multiply features: it is to remove the breaks between steps.
The first serious step is to look at how the company actually works. You follow a quote from its creation to its conversion into an order. You watch how items are created, how prices are set, how purchases are triggered, how stock is tracked and how deliveries are prepared. You also look at the workarounds: personal files, double entry, information kept in e-mails, or steps nobody dares to change because they rest on an old habit. That observation makes it possible to separate the real process from the imagined one.
The first version of the tool then stays deliberately limited. It covers one useful flow, it is simple enough to be used quickly and it produces visible results. Within a few weeks it is often possible to have a first working version on a well-defined scope. Then it improves through use: the teams use the tool, report what is missing, show what slows them down and suggest simplifications. The software evolves with the company, rather than imposing a fixed organisation from day one.
One of the most immediate gains comes from removing double entry. An item has a reference, a description, a price, a unit and, where needed, technical characteristics. A customer has contact details, commercial terms and a history. This information is entered once, then reused everywhere it is needed. The quote, the order confirmation, the delivery note and the invoice are all generated from the same base. The documents keep their usual layout, but their content no longer depends on manual copying.
That is also what makes simple dashboards possible. The owner does not need fifty indicators. He needs to know what has been sold, what has been ordered, what has been delivered, what still has to be bought and what needs chasing. A good tool does not replace the owner's judgement: it saves him from spending his time piecing the information back together.
For an industrial or trading SME, a web-based ERP has a decisive advantage: the information is no longer tied to a workstation or a local file. The sales rep looks at a quote on his phone. The workshop manager finds an order from his desk. The owner follows the business remotely. The information stays centralised and accessible according to each person's rights.
This does not mean imposing a complex mobile app or multiplying interfaces. On the contrary, the tool is adapted to each use: someone entering a goods receipt does not need to see every sales management function; a sales rep does not need to navigate production details to find a price. So bespoke also means simplicity. A clear interface, a few well-designed actions and automatically generated documents bring more value than a very complete system that is hard to use.
A business tool quickly becomes essential. That is a strength, but also a responsibility. The data has to be structured properly from the start: references, customers, suppliers, prices, stock and history. Backups must be planned, tested and protected. Access must be controlled. And the company must know how to recover its data if it changes provider or if the developer is no longer available.
Dependence on the developer is a real risk when a tool is built without documentation. So you need an understandable architecture, backup procedures, minimal documentation and a set-up that does not rest on one person alone. Good bespoke work is not a mysterious piece of software only its creator can maintain: it is a tool adapted to the company, but structured enough to evolve over time.
The return is not measured only in clicks saved. It is measured in hours of data entry removed, errors avoided, orders better tracked, stock more reliable and follow-ups that no longer depend on one employee's memory. It is also measured in the owner's ability to see his business without asking several people to reconstruct the situation for him.
The biggest gain is often continuity. When the information is in the tool rather than in someone's head, the company becomes less fragile. It can recruit, hand over, delegate and grow without rebuilding the way it works at every stage.
A custom ERP is not there to give a small company the same tools as a large group. It should give it a simpler, more reliable and more visible way of working, respecting how it actually operates. That is the approach Atare has taken in building this kind of tool for an agricultural equipment trading company, and then for its own needs. Our tools →
An industrial manufacturer does not build growth by stacking up dealers: it builds a brand those dealers have an interest in defending. And when it also supplies its direct competitors, a separate product brand becomes a genuine business development tool.
A company owner knows the business so well that he no longer sees what a new customer discovers in a few minutes. A useful audit follows exactly that journey: search for the company, look at what it shows, compare its competitors and try to contact it like a genuine prospect.
An industrial set-up in South-East Asia does not start with a plot of land or a construction quote. It starts with the product, the flows and the way you manufacture. Subcontract, assemble or produce: the right choice is made before the walls are drawn, and early mistakes are paid for long after start-up.
Let's talk about it directly. Reply within 48 hours, in France, in Asia and worldwide.