About
A design team built for remote delivery, not adapted to it
We have never had a drawing office where everyone sits together. Since 2017 the work has been distributed, which means the processes that hold quality — written scope, version control, structured review — are the ones we started with rather than the ones we bolted on.
The founder's route here
The company started from the commissioning side of the industry, not the drawing side. Back in2008 that meant standing in plant rooms with a laptop and a set of drawings, making systems work that had been designed by someone who never had to start them up. Ventilation plant, heat substations, pump groups, fire alarm panels, building controllers — the equipment that a design either accounts for properly or doesn't.
That background shapes what we produce. Commissioning teaches you which drawing errors cost a day and which cost a month. It teaches you that a sequence of operation written in vague language will be interpreted by a programmer who was not in the design meeting. And it teaches you that a panel schematic without terminal numbers is a schematic that will be redrawn by hand on site.
In 2017 the work shifted from commissioning to design, and the model was remote from the first project — initially out of necessity, then deliberately, because it turned out that the discipline remote work demands produced better documentation than sitting in a room together ever had. 450+ projects later, the same model runs at a scale that would need a floor of a building to house.
Yuri Ezhkov, founder. If you would rather put a technical question straight to him than go through the form: yuri@ezpro.engineering or LinkedIn.
How the team is structured
A core engineering team holds the client relationships, the design decisions and the quality gate. These are the people who join your review calls, write the query log and sign off internally before anything is issued to you. They are permanent, they know your project, and they do not rotate off it.
A vetted specialist pool of around 25+ engineers and drafters provides the elastic capacity. Everyone in the pool has been through our internal standards induction and has worked on our projects before, which is why ramp-up takes about five working days rather than the month a fresh hire would need. They work under the core team's direction, never directly against a client brief.
The practical effect is that your project has a stable set of faces and a variable amount of drafting capacity behind them. You are not paying to keep eight drafters busy in a quiet month, and you are not waiting on recruitment in a busy one.
Where we sit on the project
We are a design production partner. We produce documentation under your company's standards and templates, and it is issued for review and sign-off by your licensed engineers. We do not act as engineer of record, we do not stamp drawings, and we do not make statutory submissions on your behalf. We design to the IEC framework that underpins GCC and Southeast Asian regulation, and we work from your authority's checklist — DEWA, Dubai Civil Defence or your local equivalent — where you supply one. That means we know what the deliverables need to contain, not that we can approve them.
This boundary is worth stating plainly because it is the question every serious consultant asks in the first call, and a vague answer to it is a reason to walk away.
Values
Four things we actually operate on
Predictable deadlines
A date we agree is a date we hold. Where a package is at risk, you hear it as soon as we know, with a recovery plan attached — not on the delivery date. Programme slippage that we cause is ours to absorb, not yours to explain to your client.
Review-ready quality
The measure we hold ourselves to is comments per hundred sheets. A package that generates a long comment list has cost you the time it was supposed to save, so internal checking happens before issue: cross-document reconciliation, calculation review, and a standards audit against your template.
Confidentiality by default
NDA is signed before project files move, as standard practice rather than on request. Client names stay off this website unless we have written permission. Project data lives in your environment where you can revoke access, or in a controlled exchange folder if you prefer.
Written over verbal
Scope, changes, queries and decisions are written down. The query log is a deliverable in its own right — it is how a package that runs across time zones stays coherent, and how a dispute six months later gets settled in ten minutes.
Working across time zones
Our delivery base runs at GMT+7 — three hours ahead of Dubai and in comfortable overlap with Singapore, Kuala Lumpur and Bangkok. In practice that means a question sent from Dubai at the start of the working day is answered before lunch, and work completed in our afternoon is on your desk in your morning.
Client communication runs in English through a single project manager per package. Drawing comments come back as cloud markups on the sheets rather than as prose in an email chain, so a review leaves a record on the document rather than in someone's inbox.
Talk to the people who would run your package
An intro call is 30 minutes with the engineer who would lead your project, not with a salesperson. Bring a live scope if you have one — you will get a useful answer on effort and duration in the call itself.