Forging
agrotechnics.forge
The platform an agricultural-machinery dealer runs on. Brands, folders, files and live data tables in one place, with strict control over who sees what, reservation and sales tracking, favourites, a full history of every change, and a view of who is online right now — installable on a phone, so the sales floor uses it like an app.
The problem
Machine stock, price sheets and customer reservations lived across shared drives, spreadsheets and chat. Two people could sell the same machine. Nobody could say who changed a price, or when. And sales, service and management each needed to see a different slice of the same data.
What we did
One database holding the brands, folders, files and tables, with a who-sees-what matrix enforced on the server — not merely hidden in the interface, so it can't be worked around. A machine locks the moment a deal starts, which is what makes double-selling impossible rather than merely discouraged. Every change is written to a history log with a name and a time. Files download straight from storage instead of through the app, so a large price sheet doesn't slow anyone down.
The result
One source of truth for the whole dealership. Double sales are structurally impossible, every price change has an author, and the team installs it on the home screen instead of digging through a shared drive.
Inside the build
99.9%
128
0.9s
Highlights
- Four roles, each seeing only its own slice — enforced on the server
- A machine locks when a deal starts, so it can't be sold twice
- Full history — every change has a name and a time
- Bulgarian interface, installs on a phone, survives a bad connection
- Updates go live without taking the system down
Got something worth building?
A few sentences is enough to start. You get a real answer from the person who will build it — usually within two days.