Outcome Snapshot
MOREgroup, a national architecture and engineering organization with 720 employees across 19 offices, used Maestro to move Revit automation delivery into a digital-practice-owned workflow.
Instead of waiting on packaged add-in releases or asking users to manage Dynamo dependencies, the digital practice team can now build or adapt a tool, test it, target it to the right audience, and deploy it directly inside Revit.
At the time of the interview, MOREgroup had rolled Maestro out to roughly 500 Revit users, deployed approximately 40 tools, and recreated about a dozen workflows from traditional add-ins or existing automation sources. Josh Harris estimated that idea-to-delivery time had been reduced by approximately 90-95%.
| Before Maestro | After Maestro |
|---|---|
| Before MaestroTool updates waited for IT packaging and deployment cycles. | After MaestroDigital practice can deploy approved tools directly. |
| Before MaestroDynamo workflows depended on local packages and data-center access. | After MaestroUsers access approved tools from inside Revit. |
| Before MaestroBroad add-ins added commands many users did not need. | After MaestroTools can be targeted by role, office, project, team, or person. |
| Before MaestroFeedback often waited for a future release. | After MaestroUpdates can reach active project teams while the need still matters. |
The Challenge
MOREgroup already had useful automation. The problem was getting that automation to the right people quickly and cleanly.
Dynamo helped project teams solve real problems, but package management became harder to support at scale. Scripts could be stored centrally, but required packages still had to be copied and maintained locally. In MOREgroup’s multi-data-center environment, Josh explained that opening Dynamo Player could take 20-30 seconds when hardware and storage were nearby, but as long as 30 minutes when scripts and packages were hosted in another data center.
The firm also maintained an internally developed C# Revit tab. Digital practice owned the ideas and maintenance, but IT still had to package and deploy updates. A tool could be ready before it could be used.
The result was a familiar automation gap: good tools existed, but adoption depended on installation timing, update cycles, package access, and whether users could find the right command in a crowded Revit ribbon.
The Shift With Maestro
Maestro changed the operating model. MOREgroup’s digital practice team can now manage more of the automation lifecycle themselves: creation, testing, targeting, deployment, updates, communication, rollback, and retirement.
The biggest operational change has been that we now can operate almost entirely independently in delivering automation and tools to teams.
MOREgroup’s launch message captured the user experience:
Just what you need, only what you need, and right when you need it.
That targeting matters at enterprise scale. A specialized tool can go to one person, one project team, one office, or a defined Azure-managed group through SSO and SCIM. Users can also personalize their Revit workspace by hiding tools they do not need and enabling tools that fit their role.
Proof In The Work
Sheet-View Renumbering
One of the most positively received tools in the rollout was also one of the simplest: a sheet-view renumbering tool. Josh originally created it with Maestro’s AI assistance in approximately 30 minutes after another tool failed to support the workflow the team needed.
The tool handles numbering conflicts and quickly became a visible example of useful, everyday automation. During an office-hours session after launch, users asked whether it could support letter-based workflows as well as numbers. The digital practice team revised the script, sent the update, and confirmed the version with users almost live during the session.
That is the new operating model: feedback no longer has to wait for the next packaged release.
Revision-Cloud Reporting
One project team used comments on Revit revision clouds to track revision information. Extracting that information required manual copying into Excel, especially when revision clouds existed both in views and on sheets.
The digital practice team created and delivered a Maestro workflow that collected comments from revision clouds in both locations and associated them with revision numbers, sheets, and other delivery information. Josh estimated that the tool replaced approximately eight hours of manual data entry for the team.
Other Maestro-delivered workflows include printing sheets from linked and nested Revit models in sheet-index order and creating publish sets from sheet indexes for cloud-hosted Autodesk projects.
The Impact
Maestro does not remove IT from the technology ecosystem. It changes the kind of work IT needs to own.
IT still manages program updates, identity, security, and enterprise controls. But IT no longer has to package and deploy every individual workflow update. Program updates can remain scheduled and controlled, while process updates can move at the speed of project delivery.
Josh summarized the distinction this way:
For IT, Maestro means the digital practice team has now taken ownership of automation. And for them, they only have to install program updates instead of process updates.
For digital practice, the impact is direct ownership. The team can respond to project needs faster, iterate on feedback, test internally, and deliver tools to the exact audience that needs them. When users say a tool is missing one thing, the team can often respond, “Give us a day.”
That responsiveness also helps preserve internal knowledge. Once a script is loaded into Maestro, it is no longer dependent on one developer’s desktop. The tool becomes part of an organizational library that can be found, maintained, updated, and retired over time.
MOREgroup is now beginning to sunset its internally developed C# add-in as useful functions are recreated in Maestro. The firm also plans to measure tool value by combining Maestro usage data with operational data in Snowflake, looking at adoption, command usage, click reduction, estimated labor time avoided, support activity, and time from request to production availability.
Josh summarized the bigger opportunity this way:
If there are fewer barriers for people to use tools that help them every day, let’s find that path. And Maestro is that path.
Reported Outcomes
| Measure | Reported value |
|---|---|
| MeasureOffices | Reported value19 |
| MeasureTotal employees | Reported value720 |
| MeasureRevit users | Reported value500+ |
| MeasureTools deployed through Maestro | Reported value~40 |
| MeasureTraditional add-in tools migrated or recreated | Reported value~12 |
| MeasureEstimated reduction in idea-to-delivery time | Reported value90-95% |
| MeasureDynamo load time across data centers | Reported valueUp to 30 minutes |
| MeasureRevision-reporting manual effort avoided | Reported value~8 hours |