Drawings that arrive as CAD and have to become a model
Consultant sets, municipality submissions, an archive of legacy projects. Someone traces them into Revit by hand, and every trace is a chance to introduce something the drawing never said.
Service · Tehran · In person or remote
Revit plugin development in Tehran.
Custom Revit plugins and add-ins for Tehran architecture, structural, and MEP offices. The studio is here too, which means the workflow analysis can happen in your office, at your machines, watching the actual work.
01, What Tehran offices ask for
Three needs almost every office has
Tehran runs the largest concentration of BIM-capable offices in the country, and the same three problems surface across almost all of them. Which one you're in decides what the tool has to do.
A standard the office wrote but can't enforce
Naming, parameters, sheet setup, decided years ago, written down somewhere, and checked by whoever happens to open the model. Until it's a test, it's a preference.
Structural output that has to survive the trip to Revit
ETABS on one side, the drawing set on the other, and a person retyping between them. The discrepancies that come out of that gap are the ones nobody finds until coordination.
02, See it run
Two tools, recorded end to end
Both of these were built for a specific conversion problem a team was doing by hand. Nothing here is a mockup, these are screen recordings of the tools running.
ARTINEXT C2RCAD → Revit
Builds the Revit model from a coordinated CAD plan set
Instead of a team tracing linework by hand, the tool reads the plan set and creates native Revit elements from it, walls placed on their real wall types, floors, levels, and openings, so the model starts from the drawing rather than from someone's interpretation of it.
- Input
- Coordinated CAD plan set
- Output
- Native Revit elements
- Runs in
- Revit
Recordings are silent and play without sound.
ARTINEXT E2RETABS → Revit
Rebuilds an ETABS structural model as native Revit framing
The model is built live in Revit's isometric 3D view while the tool reports its own progress: elements processed, beams, columns and braces created, non-master members, and, the line that matters most, what was not created. Anything that didn't convert is visible on screen instead of silently missing.
- Input
- ETABS Excel export
- Output
- Revit structural framing
- Reports
- Per-element counts, including failures
Recordings are silent and play without sound.
03, Working with a studio in the same city
What being in Tehran actually changes
Most of this work is done remotely regardless of where anyone sits. Four things are genuinely different when both offices are in the same city, and they are all in the first half of the project.
Discovery happens at your machines
The first stage is watching the real workflow, not the documented one. Doing that in the room, at the workstation, with the actual model open, surfaces in an afternoon what a screen-share turns into three calls.
No timezone to schedule around
Same working day, same week. A question that comes up while a tool is being built gets answered the same afternoon rather than becoming tomorrow's blocker.
Handover can be in person
A tool nobody was taught to use is a tool nobody uses. Sitting with the team the first time they run it is worth more than the documentation, and in the same city it costs an afternoon.
The same standards conversation
Tehran offices are working against a shared set of consultant expectations and submission requirements. That context doesn't have to be explained from scratch before the real problem can be discussed.
None of this is a requirement. Plenty of projects run entirely remote, and the process is the same either way, this is what is available, not what is expected.
04, Process
Discover, define, build, evolve
Four stages. The first two are where most of the risk gets removed.
Discover
We watch the real workflow, not the documented one. What's actually done by hand, by whom, and how often it goes wrong.
Define
The problem gets stated in full, with a success measure that can be tested, before any tool is proposed.
Build
Built against your standards and your users. Every added layer of complexity has to earn its place.
Evolve
Systems are built to change shape as your work grows, so the tool doesn't become the next thing to work around.
05, Questions
Before you write to us
Can you come to our office?
Yes, for the stages where it helps, discovery and handover, mostly. The build itself doesn't get better with anyone in the room, so it isn't billed as if it does.
Do you build for a specific Revit version?
Whichever ones your office actually runs, including more than one at a time. The version range is a scoping question asked in the first stage, supporting three versions is not three times the work, but it isn't free either.
Can you work with our existing plugins and templates?
Yes, and it's usually the better answer. If something already installed does part of the job, the honest recommendation is to extend or connect it rather than replace it. If a tool doesn't solve the real problem, we don't recommend it, even when building it from scratch would look more impressive.
Who owns the code?
You do. It's your process encoded, it shouldn't live somewhere you can't reach it. Source and build instructions are handed over.
What does it cost?
There's no price list, because a plugin isn't priced by its button. Four things move the size of the job, and they're set out on the main Revit plugin development page. No estimate is given before the problem is stated in full. The four drivers are set out in the plugin cost piece.
Do you only work with Tehran offices?
No. The studio is based in Tehran and works remotely with teams anywhere. This page exists because being in the same city changes the first stage, not because it's a condition.
06, Start
Tell us the step you'd stop doing by hand
Bring the workflow, not the spec. If a plugin is the wrong answer, we'd rather tell you that in the first conversation than at the end of a build.
We are not a fit if you want a generic add-on installed without any process review, or an estimate before the problem is stated.