
Home · Work · Manufacturing and industrial
A custom ERP gave a stone manufacturer true order costs within six months
A natural stone manufacturer ran three facilities on informal records and memory. We specified and governed a custom ERP, got a low-literacy shop floor to use it, and gave every quote a true cost.
- Client
- A natural stone products manufacturer and exporter with three specialized facilities
- Engagement
- Custom ERP recommendation, specification, build governance, and shop-floor rollout across three sites
- Result
- Three sites on one system, true order costs, and cost and lead time estimates within 6 months. Still in use today.
- How we worked
- Embedded from specification through adoption, with a specialist agency writing the code. Handed over with periodic advisory support.
Published . Client name withheld.
The situation
A natural stone products manufacturer and exporter ran three specialized facilities with no system connecting them. Each site kept informal records. There was no shared inventory position, no production tracking, and no order status beyond what individuals carried in their heads. The business could not work out the cost of any order, so quotations went out without anyone knowing whether the work would make money. Its books of account were not kept to a standard that could support management reporting or external financing.
The owners needed to know what each order cost, which orders to take, and at what price. They wanted a one-time investment rather than a permanent internal technology function, and they had no IT capability of their own.
What made it hard
- Each facility ran different specialized processes and combined manufacturing with warehousing, so neither a standard warehouse system nor a standard factory system fit any of them.
- Packaged ERP covers generic accounting, sales, purchasing, and inventory well, but anything beyond that needs scarce, expensive localization specialists, which changed the cost case for buying.
- Operations were being restructured while the system was specified, so the target process was still moving during design.
- The people who had to enter the data were day-wage laborers and craftsmen with limited literacy, limited digital literacy, and no English, on a dusty, wet stone-cutting floor where standard tablets would not last.
- Production could not stop for training or cutover, the client had no internal IT team, and this was the first custom ERP Armstrat had deployed.

How we worked
We worked inside the business from specification through adoption, and scoped the system around the decisions it had to improve: what an order costs, whether a quote makes money, and whether the books would support financing. A specialist agency wrote the code. We owned the specification, governed the build, and stayed until the floor data could be trusted.
- 01
Build where the process differs
We advised against a packaged ERP. Off-the-shelf systems handle generic accounting, sales, purchasing, and inventory, but each site’s process was unique and specialist localization is scarce and costly. We designed a core platform with independent modules, and integrated proven open-source accounting rather than building it from scratch.
- 02
Design each site for its work
Each facility got its own facility management module, built for the hybrid of manufacturing and warehousing it actually ran. A Kanban-style production view timestamped every stage, so order progress and stage duration became visible for the first time. Procurement, inventory, HR, quotation, and sales modules connected to the same core.
- 03
Turn timestamps into true cost
With every stage timed, we implemented time-driven activity-based costing: stage duration, direct material, and that period’s labor wage give the real cost of each order. The quotation module holds each customer’s specification in one record and feeds the costing engine, so every quote can be tested for profit before issue.
- 04
Engineer adoption, not just training
Rollout ran as its own change program, site by site, with production running throughout. Bilingual, low-text screens with large touch targets, photo capture as the main input, and ruggedized tablets suited a dusty, wet floor. We secured the founders’ mandate and chose not to lead with it.
- 05
Make the data serve the floor
When laborers asked to be paid per entry, we said no. Instead, the system became their record: verified output protected them from blame, and new salaried performance metrics were tied to what they captured. We also turned long-tenured managers’ tacit knowledge into documented SOPs and a knowledge base.
The results
Measured against the outcomes agreed at the start.
- Three previously independent facilities brought onto a single operating system, with every production stage tracked and timestamped.
- Within 6 months, the system could estimate order cost and lead time from its own production history, with error margins applied.
- Every quotation can be tested for profitability before issue, and profitability per order improved sharply.
- Pricing and order selection discipline contributed an estimated 2 to 3 percentage points of the business’s 10 point EBITDA expansion.
- Books of account brought to financing standard, directly enabling the external funding secured during the engagement.
- Shop-floor adoption achieved at all three sites despite significant literacy barriers, and long-tenured managers’ tacit knowledge captured in documented SOPs.
What leaders can take from it
Buy where the process is generic and build where it is the differentiator. Packaged ERP is cheap until it has to fit, and the specialists who make it fit are scarce and expensive.
Costing systems pay back through pricing, not cost cutting. Once every stage carries a duration, you know which orders to accept and at what price, and quoting stops being guesswork.
The system is not the deliverable, adoption is. A mandate buys compliance and only self-interest buys adoption. Plan for the dip and say so upfront: orders were disrupted here during cutover, and delivery recovered.
Questions about this work
Should a manufacturer build a custom ERP or buy an off-the-shelf system?
Buy where your processes are generic and build where they set you apart. Packaged ERP handles accounting, sales, purchasing, and inventory well, but fitting it to specialized processes needs scarce, costly localization specialists. For this stone manufacturer, Armstrat recommended a custom core with site-specific modules and integrated open-source accounting, because accounting is not where the business differs.
How do you get shop-floor workers with low literacy to use an ERP?
Design for the actual user and make the data serve them. Here that meant bilingual screens with minimal text and large touch targets, photo capture as the main input, and ruggedized tablets. Armstrat also tied new performance metrics to captured output and refused to pay per entry. Data quality supported costing and lead time estimates within six months.
More work
+10 ptsPercentage points of EBITDA margin, against a mandate to hold flatGrowth strategy that added 10 points of EBITDA margin
30%Approximate reduction in electricity use, with no new machinery boughtLean operations across three stone plants, zero CapEx
3 gatesquality checkpoints, from supplier intake to pre-shipment inspectionQuality gates and in-house packaging for a stone maker

Bring us the hard problem.
We agree the outcomes first, then work inside your business until they hold.