Manual work, repeated
Steps a person redoes on every project, the same way, from memory. Each repetition is another chance for the error nobody catches until it's already in a drawing set.
Digital-systems studio · Iran · working remotely
Build what's next.
Custom Revit content, digital tools, and office automation for architecture, structural, and MEP teams, built from your process, never off a shelf.
01, Where the time goes
Three frictions, in almost every office
Our time goes to three places: work still done by hand, data scattered across sources, and software that doesn't talk to itself. That's where the right system does the most.
Data with no single home
Quantities, statuses, and decisions scattered across files, people, and software. Nothing whole enough to decide from without someone rebuilding it by hand first.
Tools that don't talk
Each one is fine on its own. Together they never become one traceable flow from request to execution to report, so the seams stay manual, and invisible.
02, Products
Three paths into the work
Whichever one you start from, the first step is the same: understand the problem in full.
P·01
Specialist Revit content
A family that isn't just well-drawn, it behaves correctly inside a real model, under real project conditions.
- Product families for manufacturers
- Office libraries for design teams
- LOD-aligned project families
- Library optimization and standardization
P·02
Custom digital tools
Fewer clicks, fewer errors, more focus on the work that matters. Every tool is studied against how the team actually works before development starts.
- Custom Revit plugins and add-ins
- Model quality control and checksets
- Output and sheet management
- Data tools and Dynamo scripts
P·03
Intelligent automation
One controlled flow from request to execution to reporting. Automation moves things; control stays with the team.
- Workflow automation
- Software and data integration
- Operational dashboards
- Organizational AI assistants
03, 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.
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, Research & development
Small prototype, fast learning, better decision
New technology only enters a product once the problem, the data, and the success measure are clear and testable. Staged prototyping surfaces what works, what needs to change, and what shouldn't be built at all, before full investment happens.
How R&D works- Test the idea before committing the budget
- Learn what needs to change while changing it is still cheap
- Find out what shouldn't be built
06, Capabilities
What we work across
The technical surface behind the three product paths.
BIM & Revit content
- Parametric family authoring
- Manufacturer product families
- Office standard libraries
- LOD-aligned project families
- Library audit and optimization
Custom digital tools
- Revit plugins and add-ins
- Model QA/QC checkers and checksets
- Dynamo script development
- Output and sheet management
- Model and data conversion tools
Automation & data
- Workflow and process automation
- Software and data integration
- Operational dashboards
- Modeling and data systems
- AI readiness and assistants
07, Insights
Written from the work
All insightsNo listicles. Each one comes out of a decision we had to make on a real project.
Choosing a Revit plugin development company
The most dangerous problem in a plugin development partnership rarely comes from a weak portfolio. It comes from the small detail nobody checked during evaluation.
Custom Dynamo script development: what it actually replaces
A graph that runs once on its author's model is an experiment. The work that turns it into a tool is the part nobody sees on the canvas.
Where AEC workflow automation should start
The ceiling on what's worth automating is usually untested, not real.
08, Questions
Before you write to us
Can you just install a plugin we already picked?
No. If what you want is an off-the-shelf template or a generic plugin installed without any process review, we're the wrong studio, and we'll say so rather than take the work. Every project starts from the problem, not a pre-built product.
Where are you based, and can you work with our team remotely?
We're based in Iran and work remotely with architecture, structural, and MEP teams. Remote is how we normally work, not an exception we make.
How is a custom tool priced?
By workflow complexity, integration needs, and how many people will use it, not by a flat price list. A plugin that looks like one button is priced by the weeks of decisions standing behind that button.
Can we start with something small?
Yes, and often that's the right move. A staged prototype tests the idea, the data, and the success measure before full investment, including the possibility that the thing shouldn't be built.
Do you work in Persian and English?
Both. This site ships in Persian and English at matching URLs, and projects run in whichever language your team works in.
What happens in the first conversation?
We go through the workflow you want to change: what's done by hand today, where the data lives, what a good outcome would actually look like, and whether a tool is even the right answer.
09, Start
Tell us the process you'd change first
Bring the workflow, not the spec. If a tool 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 an off-the-shelf template or a generic plugin installed without a process review.