About
Mostafa Dardir.
Operations engineer. Software builder. Manchester, UK.
01 / Background
Background.
Trained as a manufacturing engineer. Since then I’ve led design work in industry, built predictive-maintenance ML models on real production sensor data, and run discrete-event simulations that surfaced material cost reduction in plant operations.
What that boils down to is two things. One: years of thinking about operations as a discipline. Process, throughput, KPI, benefit sizing, simulation, predictive analytics, lean. Two: years of shipping production software in Python, ML, FastAPI, Next.js, and TypeScript.
I started Valoren Digital because there’s no good buying option for ops-transformation consultants who need their methodology in software. Generic dev shops can’t model your calculations. Consultancies can’t ship clean code. The gap is wide enough that consultants spend hours of QA correcting tools someone else built. Valoren sits in that gap so you don’t.
02 / Why operations-fluent
Why operations-fluent matters.
Brief a generic developer on a benefit-sizing calculator and you spend the first half of the engagement explaining what a benefit case is, why the methodology has the assumptions it does, and which edge cases make a number wrong in a defensible way. By the end of that explanation, you’ve done half the work and the developer has built half the wrong thing.
Brief me on the same calculator and I’ve already had those conversations. I’ve done the simulation work. I’ve watched a plant manager cross their arms when a number doesn’t match their gut. I write the code and I read the calculations the way an operations practitioner would.
That’s the difference. Not magic, not marketing. Years of operations practice plus years of writing software, in one head.
03 / How I work
How I work.
Async-first, UK-based, fixed-price, 4 to 8 weeks per engagement. One active engagement at a time so the live client gets full focus. Weekly written updates, ad-hoc messaging on Slack or email, video calls only when needed and always with a written summary after.
No subcontracting. The person you scope the engagement with is the person who builds it. Subcontracted operational logic is where wrong calculations come from.
The principle holds as Valoren grows: every engagement gets one named senior builder who owns the methodology absorption, the spec, and the build end-to-end.
Want to talk?
Free 15-minute intro call to check the fit. No pitch, no work product. If there’s a fit, the next step is a paid 90-minute scoping session that produces a one-page tool spec and pricing recommendation.