Why does a general contractor build its own ERP?
Industria 2000 is a general contractor based in Sárospatak — with its own fleet of machinery, projects running in parallel, and the same administrative headaches as any Hungarian construction SME. Tektana was born here, and today it runs here in production. This isn't a reference-customer story. It's ours.
Where we started
We didn't start from zero: we used an ERP system as well as construction-specific software — proven, decent tools. The bookkeeping was fine, the invoicing was fine. The problem wasn't that we lacked software. It was that the reality of our projects didn't fit into either of them.
Budgets lived entirely in Excel. Every project had its own patched-together spreadsheets: one for the quote, one for changes made along the way, one for final settlement — and these never talked to each other or to the financial system. What was in the software was the bookkeeping of the past. What was in Excel was the present of the project — maintained by hand, always lagging, held together in a single person's head.
The moment it became clear
The realization wasn't a dramatic failure but a quiet insight: a generic ERP system would never be able to serve this. Not because they're bad — but because the logic of construction is different. In the world of generic ERPs, a project is either ordered or it isn't. In ours, the project is alive: extra work comes in, the technical scope changes, items get flagged for later settlement — and all of this has to be tracked in a way that holds up towards both the client and the technical inspector.
Two paths remained: keep patching things together in Excel alongside our software forever, or build the system that speaks the language of construction. We chose the latter.
How we work today
Today, every one of our projects and every one of our assets runs in Tektana.
The biggest change is exactly where it used to hurt the most: mid-project changes on running jobs. The integration and tracking of extra work, technical scope changes, and items subject to later settlement is clear and transparent — in every direction. Internally, we see exactly how each change affects our margin; externally, towards the client and the technical inspector, what changed, when, and why is documented and traceable. What used to be a point of dispute in a meeting is now a query.
The cost of machinery and vehicles is no longer end-of-month cleanup work: the assets are connected, and engine hours and mileage are charged to wherever they were incurred. Quotes are built on our own actual data — we don't estimate cost price, we see it.
Honestly, about the transition
Employee adoption is never easy, and we're not claiming it was. What we deliberately built, though: running the system fully doesn't require loading functions onto the field workforce. The bricklayer doesn't become a data-entry clerk. The office and management side drives the system, data is created where it would be created anyway — field workers don't need to tap through an app for the company's numbers to add up.
Why should you trust a case study the developer wrote about itself?
Because we don't hide it — that's exactly the point: Industria 2000 is the company of Tektana's developer — and precisely because of that, its first and most demanding user. Every feature you see in Tektana exists because we needed it, and it works the way it has to work in a live construction operation. If something doesn't hold up, we're the ones who feel it first — and we're the ones who fix it first.
And we measure the numbers: we documented our operations before the switch, and as comparable data accumulates, we'll publish it — right here, on this page.