Frequently asked questions.

We work with architecture firms, real estate developers, government planning bodies and consultancies across design and engineering. We have built for studios in Paris and Bengaluru, and we work with AEC teams anywhere. Distance has never decided whether we take on a project.

We build around the tools your studio already uses, including Revit, AutoCAD, Rhino and Grasshopper. Automations run as custom Revit plugins, Dynamo scripts or standalone tools, and we read and write IFC where a project needs it.

Yes, and BIM automation is one of the most common places we start. Sheet naming, parameter updates, schedules, standards checking and quantity extraction repeat on every project, so we build them as one click tools inside Revit where your team already works.

Artificial intelligence is useful in a studio when it is pointed at your own work rather than at a general model. We train on the drawings, images and project data your practice has already produced, so what comes back sits inside your standards. That covers generative work as well, so generated plans, sections and visuals come out in your own language rather than a generic one. As these systems move from AI toward superintelligence, the practices whose own data is organised are the ones that will benefit first.

Yes, because we set these systems up to run on infrastructure you control. A secure LLM setup keeps your drawings, client information and commercial data inside your own environment, so nothing is handed to a public model.

We do both. Most engagements begin with one specific workflow problem, and the tool we build for it is yours to keep using. Where that tool turns out to be useful beyond one studio, we develop it into a SaaS product other teams can license.

You own what we build for you and you keep using it after the engagement ends. We keep the underlying engine, which is what lets us build your next version faster. We agree all of this in writing before any work starts.

A focused automation usually takes a few weeks. A larger system, such as a studio database or a machine learning tool trained on your own archive, takes a few months. We give you a timeline after the first call.

No. We handle the build, the integration and the deployment. Your team uses the finished tool inside the software they already know.

Usually yes. Most practices are sitting on years of drawings, models, surveys and spreadsheets that nobody can search. We clean that material up and turn it into a dashboard your team can question, filter and make decisions from.

Pricing follows the scope of the work. We give you a written quote once we understand the problem, and the discovery report tells you what each opportunity is worth before you commit to building it.

Our office is in Bangalore, India and our clients are spread across Europe and Asia. We run projects remotely across time zones as a matter of course, so where your studio is makes no difference to how we work together.