Service · Tehran · In person or remote
Parametric families for Tehran manufacturers and design offices, built to your product or your office standard. The studio is here too, which means the source can be measured in a room rather than inferred from a PDF.
01, What Tehran offices and manufacturers ask for
Tehran holds the largest concentration of BIM-capable offices in the country, and almost every library here has at least one of these. Which one you have decides whether the answer is new content or an audit.
A specifier can only place what they can find. A product with no family gets substituted for one that has one, and the substitution happens quietly, at the exact stage where nobody is asking the manufacturer anything.
Content from four sources, four naming schemes, imported mesh inside half of it. Each file was free; the model that has to open every day is paying for all of them.
It looks right and it schedules empty. Parameters that don't match the reviewer's file, naming that doesn't match the submission, classification missing, so the model gets drawn from and counted by hand.
02, Built work
A curtain-wall system delivered as two panel types, one company, one set of connection details, two positions on the elevation.
The frame, the brackets and the anchor detail are identical across both units. What changes is the infill and the head condition, because the two sit in different parts of the façade and answer to different requirements.
That shared half is the argument for having families built rather than collected. It is shared by construction rather than by coincidence, so a change to the frame is one change, made once, and not a hunt through a library for everything that happened to look similar.
Drawn from the delivered families themselves, the outlines above are the real geometry, reduced to boundary and crease edges. Nothing here is a stand-in.
03, What being in Tehran changes
Most of this work is done remotely regardless of where anyone sits. Four things are genuinely different when the source is an hour away, and they are all in the half of the job that costs the most.
A dimensioned drawing is a specification. A brochure is a reconstruction job, and reconstruction is where the hours go. Being able to go and put a tape on the real unit turns the most expensive stage into an afternoon.
The fastest way to settle whether content is right is to open it next to the person who knows the product, on their template, and let them point. That review is a meeting here and a fortnight of comments otherwise.
Same working day, same week. A question about a connection detail gets answered the same afternoon rather than becoming tomorrow's blocker.
Tehran offices are working against a shared set of consultant expectations and submission requirements. Naming, parameters and classification land against a context that doesn't have to be explained from scratch first.
None of it is a requirement. Plenty of family work runs entirely on files and calls, and the process is identical either way, this is what is available, not what is expected.
04, Process
Four stages. The first two are where most of the risk gets removed.
We watch the real workflow, not the documented one. What's actually done by hand, by whom, and how often it goes wrong.
The problem gets stated in full, with a success measure that can be tested, before any tool is proposed.
Built against your standards and your users. Every added layer of complexity has to earn its place.
Systems are built to change shape as your work grows, so the tool doesn't become the next thing to work around.
05, Questions
Yes, for the stages where it changes the answer, establishing what the product actually is, and reviewing the first family against it. The rest doesn't get better with anyone in the room, so it isn't billed as if it does.
Whatever actually exists, dimensioned drawings, a CAD file, a spec sheet, or a family that nearly works. The first stage establishes what is specification and what is a guess, because those are two very different jobs and they shouldn't be quoted as one.
That's the usual case. Naming, shared parameters, subcategories and line weights come from your standard, and where the standard is ambiguous, the ambiguity gets raised rather than silently resolved in a way you find out about later.
The ones your team and your clients run. Families are delivered in the oldest version in scope so they open forward, the range is agreed in the first stage, since it affects which features can be used at all.
There's no price list, because a family is priced by its behaviour rather than its geometry. Four things move the size of the job, and they're set out on the main Revit family creation page. No estimate is given before the problem is stated in full. What behaviour means in practice is set out in the parametric family piece.
No. The studio is based in Tehran and works remotely with teams anywhere. This page exists because being in the same city changes how the source gets established, not because it's a condition.
06, Start
Bring the file and the model it has to live in, not a specification of what you think it needs. If your library needs an audit rather than new content, we'd rather say so first.
We are not a fit if you want geometry traced from a brochure with no dimensions, or a family count quoted before anyone has looked at the source.