We are looking for the person who ends up understanding this system better than anyone else — every flow, every button, why it exists and what breaks if you change it.
Metricor Technologies Global SRL is a software company in Bucharest, founded in 2026, with three partners. We build custom software — not off-the-shelf products, but systems built for one company and embedded in its daily operations.
The team is small. That means there is no management layer between you and a decision: if you propose something good, it gets built.
A full ERP for West Beton, a concrete producer in Bucharest. Not a CRM, not a website — the system the company actually runs on: from first client contact to concrete poured on site to the invoice.
Roughly 22 human actions and 6 handoffs between people before an order is ready to invoice. 18 of them happen before the first cubic metre leaves the plant.
The 7 areas: My work · Commercial · Operations · Purchasing · HR · Configuration · Oversight. The roles — sales agent, commercial, dispatcher, station manager, station operator, driver, purchasing, legal, laboratory, admin — are some global, some tied to a specific station: the same person can be manager at one plant and operator at another.
There are separate surfaces for drivers (a mobile web app: timesheet, my deliveries, weighbridge, expenses, leave) and for the end client (a portal with projects, offers, orders, documents, invoices). Underneath: concrete recipes, ingredients and per-station stock, fleet, quality checks, declarations of conformity, credit limits, multi-level approvals, audit log.
The interface and the documents are in Romanian, because the users are Romanian. The code is in English.
You are the bridge between what the client needs and what the technical team builds.
It does not mean you have to write code. It means knowing exactly what the app does, seeing where it hurts, and translating a dispatcher's complaint into a requirement clear enough that a developer can implement it without asking a single follow-up question.
Every screen, every state, every rule. Why an order cannot be created without an approved protocol. Why an offer below the base price needs a separate approval, and why the agent cannot approve their own discount. When someone asks “why does it do that?”, you have the answer — or you know where to find it in ten minutes.
Not “let's improve deliveries”, but: which screen, which button, who presses it, what happens next, what happens when it goes wrong, who is allowed. Your requirements are the raw material the technical team turns into software.
Before it reaches the client, you walk through the feature as a real user and say “yes, this is it” or “no, it breaks here”. You are the last gate.
The most interesting part. The main spine has ~22 human steps — some of them probably no longer earn their place. Where is time lost? What could the app do automatically? What report would tell the owner something he doesn't know today? We don't want to have to ask.
The ERP is built for West Beton, but the problem it solves belongs to every concrete plant in the country. What would have to change for us to sell it to others? What is specific to them and what is universal? That's a conversation we want to have with you, not in front of you.
You get access to the app and walk it role by role: log in as an agent and build an offer, as a dispatcher and make a schedule, as a driver and take a delivery all the way to the end. You talk to the client's people. At the end, you present the system back to us — that's how we see you have understood it.
You take over client feedback. You write the first complete requirements. You test and accept what the team delivers. You keep a living list of what needs doing and in what order.
You come with your own improvement list, argued: which steps we can remove, what can be automated, what's missing. And with a point of view on what the product would look like if we sold it to other concrete plants.