Meet the Experts
The insights in this guide come directly from Strucsoft’s implementation team, who have supported manufacturers, engineering firms, and prefab companies through hundreds of Autodesk® Revit® Based Solutions deployments. Rather than relying on theory, this article shares the lessons learned from real-world implementations.
Thaïs Blinovas
Product Manager
Specializes in customer implementations and workflow optimization.
Burhan Bustillos-Francis
Solutions Technical Specialist
Works directly with customers implementing framing automation for manufacturing and prefabrication.
In Brief
Most companies don’t struggle with Revit framing software because they selected the wrong solution. They struggle because they underestimate the implementation process.
According to Strucsoft’s Product Manager Thaïs Blinovas and Solutions Technical Specialist Burhan Bustillos-Francis successful implementations share four characteristics:
- They begin with a proof-of-concept project instead of a production project.
- Teams understand that learning the software takes time.
- The Revit model is properly prepared before framing begins.
- Automation is viewed as a way to accelerate proven workflows—not replace engineering expertise.
After supporting hundreds of implementations of Autodesk® Revit® Based Solutions such as Wood and Light Gauge Steel Framing Software, Strucsoft has observed a clear pattern.
Companies that achieve the best results tend to share the same habits, while unsuccessful implementations often fail for similar reasons.
| Companies That Succeed | Companies That Struggle |
|---|---|
| Start with a Proof of Concept | Jump into production |
| Standardize workflows | Customize every project |
| Expect a learning curve | Expect instant productivity |
| Work closely with implementation experts | Treat implementation like software installation |
| Continuously improve | Expect perfection on day one |
The Real Reason Companies Look for Framing Automation.
If you’re evaluating Revit framing software, chances are you’re trying to solve one or more challenges:
- Your BIM team spends too much time on repetitive framing tasks.
- Your manufacturing process is waiting on models.
- Your company wants to scale prefabrication.
- Or you’re simply wondering whether automation will actually deliver the ROI vendors promise.
The good news? Companies are achieving significant productivity gains with framing automation. The bad news? Software alone doesn’t guarantee success.
Revit Framing Software Is Changing…Fast
Five years ago, many companies were simply looking for software capable of automating framing. Today, automation alone is no longer enough.
As off-site construction and prefabrication become standard across the industry, the role of BIM has expanded. Revit models are no longer created solely for coordination—they are expected to support the entire framing workflow, from design and shop drawings to manufacturing, quality assurance, and CNC production. As a result, BIM teams are under pressure to deliver models that are both highly accurate and production-ready.
Customers expect faster modeling, higher accuracy, streamlined quality assurance, and seamless integration with manufacturing workflows. Every unnecessary manual step reduces profitability, especially in high-volume prefab environments.
Thaïs Blinovas, Product Manager at Strucsoft, has witnessed this evolution firsthand.
Five years ago, everyone was just thankful we had software that could automate panel creation. Today, that’s not enough anymore. Everything has to be faster. Quality assurance has to be faster. The entire process has to be streamlined so it’s profitable.”
This shift explains why implementing Revit framing software has become more strategic than ever. Companies aren’t simply purchasing software—they’re redesigning how they design, coordinate, manufacture, and deliver projects.
Why Implementing Revit Framing Software Is Different From Installing Software
One of the biggest misconceptions is that implementing framing software is similar to installing any other design application.
It isn’t.
Framing automation sits at the intersection of multiple disciplines:
- Architectural modeling
- Structural engineering
- Prefabrication
- Shop drawing production
- Manufacturing
- CNC machinery
- Project coordination
Each organization also has its own standards, framing methods, naming conventions, fabrication requirements, and production processes.
That means success depends just as much on implementation as on the software itself.
Many companies approach the evaluation process with ambitious goals. Some want to reduce a project that currently takes a month down to just one week. Others are transitioning from AutoCAD, replacing another framing solution, or moving their entire manufacturing workflow into Revit.
These goals are achievable—but only when expectations, training, and implementation are aligned.
As Thaïs explains:
Customers usually come to us because they want to speed up their process. Sometimes they’re looking to reduce a month-long project to five days. It is possible—but only if everything is prepared properly. The Revit model needs to be clean, the workflow needs to be established, and the process has to run smoothly.”
This shift explains why implementing Revit framing software has become more strategic than ever. Companies aren’t simply purchasing software—they’re redesigning how they design, coordinate, manufacture, and deliver projects.
Mistake #1: Going Live Without a Proof of Concept and Proper Implementation
The most expensive implementation mistake doesn’t happen during software installation.
It happens on the first production project.
According to Strucsoft’s implementation team, many companies complete their initial training and immediately begin framing a live customer project.
Unfortunately, basic software training isn’t designed for that.
Instead, it teaches users where the tools are located, what they do, and how they interact. It doesn’t prepare a team to deliver an entire manufacturing-ready project under production deadlines.
Thaïs Blinovas sees this scenario repeatedly.
“The biggest mistake is they start right away. They complete the basic training and jump directly into an actual project from scratch. We always recommend starting with a proof-of-concept project first, or using implementation and consulting hours if they’re going directly into production.”
A proof-of-concept project allows teams to validate:
- Company framing standards
- Automation templates
- Shop drawing outputs
- Manufacturing workflows
- CNC integration
- Internal review processes
Most importantly, it gives teams the opportunity to make mistakes before those mistakes affect schedules, fabrication, or customers.
Skipping this phase often creates a chain reaction.
Problems that begin with an improperly prepared Revit model may not become visible until shop drawings are complete—or worse, when panels are ready for fabrication.
By then, correcting the issue can require rebuilding significant portions of the project.
As Thaïs describes it:
They realize the issue later, when they’re already trying to manufacture the panels. Then they have to go back and forth through the project. It’s a nightmare.”
Unfortunately, avoiding the first production mistake doesn’t guarantee success. The next challenge begins as soon as users start learning the software.
Mistake #2: Underestimating the Learning Curve
One of the biggest misconceptions about Revit framing software is that once users complete training, they’ll immediately be able to work at full speed.
In reality, becoming productive takes much longer.
Like any advanced BIM workflow, framing automation combines software knowledge with practical experience. Users need to understand not only how the tools work, but also how those tools fit into their company’s design standards, manufacturing process, and quality control procedures.
According to Strucsoft’s implementation team, this is where many companies struggle.
The biggest mistake is completing the basic training and then jumping straight into a real project. Twenty hours of training gives you an idea of what the software can do and how to use the tools. It’s not enough to start a production project.” — Thaïs Blinovas, Product Manager, Strucsoft
Thaïs compares it to learning Revit itself.
Completing introductory training doesn’t mean you’re ready to manage a complex hospital, multifamily building, or panelized manufacturing project.
It’s much like earning a private pilot’s license. Passing the exam means you understand the fundamentals, but no one would expect a newly licensed pilot to captain a commercial airliner the next day. That level of responsibility comes through practice, mentorship, and experience in increasingly complex situations.
The same principle applies to framing automation.
Learning where the commands are located is only the beginning. Becoming efficient requires repetition, experience, and an understanding of real-world construction workflows.
Why Revit Framing Has a Steeper Learning Curve
Many BIM professionals are already familiar with Revit before they evaluate framing automation software. Naturally, they assume learning the new solution will be similar to learning another Revit add-in.
However, framing introduces another layer of complexity.
Instead of simply creating geometry, users must consider:
- Framing standards
- Structural requirements
- Panel layouts
- Manufacturing constraints
- Shop drawing production
- Coordination with architectural and structural models
- Downstream fabrication workflows
Burhan Bustillos-Francis, Solutions Technical Specialist at Strucsoft, explains that framing itself is significantly more complex than many users initially expect.
Framing is more complicated than doing structural modelling. People think learning the software will be easy, but they also have to learn the framing process itself.”
This is why implementation should never be viewed as simply installing software.
It is the adoption of an entirely new workflow.
Why Product Demos Can Create Unrealistic Expectations
Software demonstrations are designed to showcase what’s possible. Experienced application specialists can complete workflows in minutes because they have years of experience with both the software and the underlying framing principles.
Customers sometimes assume they’ll reach the same level of productivity immediately after training. Burhan believes this expectation is understandable—but unrealistic.
“Our demos are done by our most talented people, and they make it look easy. Then customers come in with those expectations.” — Burhan Bustillos-Francis
The software is fully capable of delivering those results.
The difference lies in experience—and in having the right implementation partner.
Just as an experienced Revit user approaches a project differently than someone opening the software for the first time, experienced framing specialists know how to configure projects efficiently, troubleshoot challenges, and standardize repetitive tasks. That level of expertise develops over time through hands-on experience.
Fortunately, customers don’t have to navigate that journey alone. One of Strucsoft’s greatest strengths is its dedicated technical and implementation team, which works closely with customers throughout every stage of the implementation process. From initial training and proof-of-concept projects to workflow optimization and production readiness, the team is available to answer questions, provide guidance, and help customers overcome challenges as they arise.
Rather than simply delivering software, Strucsoft partners with customers to help them build efficient, repeatable framing workflows that continue to improve long after the initial implementation is complete.
Why Your First Project May Feel Slower
One insight from the interview stands out because it challenges a common assumption. Many companies expect to become faster immediately after implementing new software.
In practice, the opposite often happens.
The first project frequently takes longer than the company’s previous workflow.
That doesn’t mean the implementation has failed.
It means the organization is still learning.
According to Thaïs, companies are simultaneously:
- Learning new tools
- Adapting internal standards
- Validating templates
- Testing manufacturing outputs
- Reviewing quality assurance procedures
- Changing long-established habits
As she explains:
They already have a process in place. It may not be the fastest process, but it’s one they know. During the transition, they’ll often feel slower because people are still learning and adapting.”
This temporary slowdown is a normal part of digital transformation.
Organizations that recognize this upfront are less likely to become frustrated or abandon the implementation before realizing its long-term benefits.
Implementation Is About Changing Processes—Not Just Software
Another important lesson from the interview is that technology alone doesn’t improve productivity. Successful implementations require organizations to rethink how they work.
For manufacturers, this often extends beyond the BIM department.
Implementation may involve:
- Updating company standards
- Refining Revit templates
- Coordinating with production teams
- Validating CNC workflows
- Reviewing quality control procedures
- Training multiple departments
For some organizations, this represents the first major workflow transformation in years. That explains why implementation timelines often extend well beyond software installation.
The companies that achieve the greatest return on investment don’t simply purchase new software—they invest time in redesigning the way their teams work.
Expert Takeaways
Before moving a production project into a new Revit framing workflow, Strucsoft’s experts recommend keeping these principles in mind:
- Training teaches the tools—not the complete workflow.
- Expect your first project to take longer than future projects.
- Treat implementation as a company-wide process, not an IT task.
- Allow time for users to build confidence before measuring productivity.
- Focus on long-term efficiency rather than immediate speed.
These recommendations come directly from years of supporting manufacturers, engineering firms, and prefabrication companies as they transition to automated framing workflows.
Once companies understand the learning curve, they often face a second misconception: believing the software should automate every decision.
Mistake #3: Expecting 100% Automation Instead of Building a Repeatable Workflow
One of the biggest misconceptions surrounding framing automation is that software should handle every design decision automatically.
In reality, no advanced framing solution works that way.
Automation is incredibly powerful when projects follow repeatable rules and standardized construction methods. But every project still requires engineering judgment, quality assurance, and decisions that cannot—or should not—be automated.
During the interview, Burhan Bustillos-Francis explained that many companies enter the evaluation process with unrealistic expectations about what software should accomplish.
There are more and more people saying technology should work [flawlessly] 100% [of the time]. I think it’s crazy to believe that’s true. We’re already around 85–90%. Sometimes competitors promise 100%, but that’s just not the reality of construction”
This doesn’t mean automation isn’t valuable.
Quite the opposite.
It means companies should evaluate automation based on the amount of repetitive work it removes—not on whether it eliminates every manual task.
Automation Depends on How Standardized Your Workflow Is
Automation isn’t determined solely by the software. It’s largely determined by the company’s own workflow.
Organizations with well-defined standards, repeatable panel configurations, and consistent design rules typically achieve much higher levels of automation than companies that redesign every project from scratch.
Thaïs Blinovas explained that the percentage of automation can vary significantly depending on the customer’s process.
Some companies have very straightforward configurations. In those cases, automation can be close to 90%. Others have much more complex configurations with many custom details. Those projects may be closer to 70% automation.”
The software isn’t changing.
The workflow is.
That’s an important distinction.
Why Repetition Makes Automation More Powerful
Automation performs best when companies repeatedly build similar framing systems.
This is particularly common in prefabrication and panel manufacturing environments, where standardized wall types are used across many projects.
Burhan summarized the concept with a simple observation:
If you can repeat it in construction, you can repeat it in software. That’s where software becomes really successful.”
In practice, this means organizations that invest in standardized framing templates and repeatable production methods typically see greater productivity gains than organizations that treat every project as entirely unique.
Rather than recreating framing decisions for every building, teams can reuse proven workflows, allowing automation to handle much of the repetitive modeling work.
Why Some Companies Reach 90% Automation
During the interview, the team discussed examples of customers who have achieved exceptionally high levels of automation.
These companies share several characteristics:
- They have standardized framing rules.
- They build similar panel types repeatedly.
- They have mature internal BIM processes.
- They maintain consistent manufacturing standards.
- They have invested time in implementation and optimization.
Thaïs highlighted one long-term customer as an example. The company had refined its internal standards to the point where automation handled nearly all routine framing tasks. Rather than constantly introducing new configurations, the team focused on repeating proven workflows, making automation significantly more effective.
This reinforces an important point: High automation is usually the result of operational maturity—not simply installing new software.
Client Spotlight
Digital Building Components (DBC)
Digital Building Components (DBC), a leading manufacturer of prefabricated light gauge steel wall panels, uses Strucsoft Metal to automate repetitive framing tasks and streamline its design-to-manufacturing workflow. By standardizing its processes and integrating BIM with fabrication, DBC has improved efficiency while maintaining the precision required for offsite manufacturing—a great example of how mature workflows unlock the full potential of framing automation.
Why Wood Framing Can Be More Challenging
Not every framing workflow offers the same opportunities for automation. During the interview, Thaïs explained that wood framing projects often involve greater variability than light gauge steel projects.
Different structural approaches, changing panel configurations, value engineering decisions, and project-specific requirements can introduce additional manual work.
For wood customers, the variation is much higher. That means more manual work may still be required, at least for now.” — Thaïs Blinovas
This doesn’t reduce the value of automation.
Instead, it highlights why automation should always be viewed as a way to reduce repetitive work while allowing engineers and BIM professionals to focus on the unique aspects of each project.
Automation and AI Are Complementary
One of the most interesting themes from the interview is that Strucsoft doesn’t see artificial intelligence replacing its automation engine. Instead, AI is expected to make automation easier to configure and more accessible to users.
Rather than manually creating every panel template, users will increasingly be able to describe what they need using natural language—or even begin with a simple napkin sketch.
Thaïs described this as the next evolution of framing automation.
The automation engine continues performing the repetitive work it already does well, while AI helps users create templates, configure workflows, and manage custom requirements more efficiently.
In other words: Automation builds the framing. AI helps users tell the software how that framing should be built.
Why the First Project Usually Takes Longer (And Why That's Completely Normal)
One of the biggest surprises for companies adopting framing automation is that their first project may actually take longer than the projects they completed before implementing new software.
At first glance, this seems contradictory.
After all, the goal of automation is to save time.
But productivity gains don’t happen the moment software is installed. They happen once people, processes, and technology begin working together efficiently.
According to Thaïs Blinovas, this temporary slowdown is completely expected.
Most companies already have an established workflow. It may not be the fastest workflow, but it’s one their teams know well.
Introducing a new process means everyone has to adapt before productivity begins to improve.
They already have a process in place. It may not be the fastest one, but it’s a process they know. During the transition, they’ll often feel slower because team members are not yet familiar with the new workflow and need time to adapt” — Thaïs Blinovas, Product Manager, Strucsoft
Organizations that understand this temporary adjustment period are much more likely to stay committed and realize the long-term benefits of automation.
Successful Implementations Are Partnerships—Not Purchases
One of the strongest themes throughout the interview was that successful implementations are built on collaboration. Purchasing software is only the beginning.
For many customers—especially manufacturers—the implementation process includes:
- Configuring company standards
- Validating framing templates
- Testing production workflows
- Reviewing shop drawings
- Confirming CNC outputs
- Refining internal processes
Because every company operates differently, implementation cannot be reduced to a simple installation checklist.
Thaïs explains that Strucsoft’s team often remains closely involved throughout the transition.
The transition needs to be a partnership between the company and us. Otherwise, it becomes a mess between the company and our team. Otherwise, even the best initiatives can struggle to gain traction, leading to inconsistent workflows and teams reverting to familiar, but less efficient, methods “
That partnership becomes even more important when manufacturing is involved.
Even companies using the same CNC equipment may have completely different machine configurations, production standards, and fabrication workflows.
Testing those processes before full production reduces risk and helps teams build confidence in the new workflow.
Client Spotlight
Blueprint Robotics
Blueprint Robotics partnered with Strucsoft to implement Strucsoft Wood during a live production project—without disrupting factory operations. With hands-on support from Strucsoft’s implementation team, the company increased production capacity by 2.5×, demonstrating how the right implementation strategy can accelerate adoption while minimizing risk.
Is Your Organization Ready for Revit Framing Automation?
Not every company is at the same stage of digital transformation.
Based on the experiences shared by Strucsoft’s technical team, organizations are generally well positioned to implement framing automation when they can answer “yes” to most of the following questions:
- Do you already use Revit as your primary BIM platform?
- Are you trying to reduce repetitive modelling work?
- Are you moving toward prefabrication or panelized construction?
- Do you have internal standards for framing?
- Are you prepared to invest in implementation?
Successful companies understand that software adoption includes training, testing, process improvement, and continuous optimization.
Implementation is not a one-day event. It’s a strategic investment.
Article Key Takeaways
Companies often begin their search for Revit framing software by comparing features.
But after supporting hundreds of implementations, Strucsoft has learned that successful projects are rarely determined by features alone.
They succeed because organizations invest in their people, standardize their workflows, and work with experienced implementation specialists throughout the transition.
The software is an important part of the equation. The implementation strategy is what ultimately determines whether automation becomes a competitive advantage.
The experience shared by Strucsoft’s Product Manager and Solutions Technical Specialist highlights several important lessons:
- Begin with a proof-of-concept project before moving into production.
- Allow your team time to learn the workflow—not just the software.
- Standardized processes consistently achieve higher levels of automation.
- Expect the first project to be slower while new workflows are being validated.
- Treat implementation as a partnership between your organization and your software provider.
- Focus on continuous improvement rather than immediate perfection.
Companies that embrace these principles typically achieve a smoother transition, faster adoption, and a stronger return on their investment.
Frequently Asked Questions
How long does it take to implement Revit framing software?
Every organization is different, but implementation should be viewed as a phased process rather than a single installation. Training is only the first step. Teams also need time to validate workflows, build templates, and gain practical experience before reaching full productivity.
Why shouldn't we start with a production project?
According to Strucsoft’s implementation team, beginning with a proof-of-concept project allows organizations to identify workflow issues before they affect schedules, fabrication, or customers.
Can Revit framing software automate every task?
No. Automation removes repetitive modelling work, but engineering judgment, project-specific decisions, and quality assurance remain essential parts of the framing process.
Why is the quality of the Revit model so important?
Automation depends on accurate input. A well-prepared Revit model allows framing tools to work efficiently and reduces downstream coordination and fabrication issues.
Is artificial intelligence replacing framing automation?
No. According to Strucsoft’s product team, AI is expected to complement automation by simplifying configuration, creating templates more efficiently, and making advanced workflows easier to use—not by replacing the underlying automation engine.
