The conversation with Jon Hirschtick continues
The following is part 2 of a transcription of an episode of the Being an Engineer podcast series by Aaron Moncur, edited and published here by permission. Read part 1 here.
Aaron Moncur: Can you explain how Onshape differs from traditional CAD systems like SolidWorks?
Jon Hirschtick: Sure. The biggest difference is that Onshape is cloud-native, which is fundamentally different from traditional CAD systems like SolidWorks. Traditional systems like SolidWorks use installed software, which means you have to install the software on every machine you want to use it on. They are also file-based, which creates a lot of complexity when it comes to managing files, versions and collaboration.
Onshape, on the other hand, is built more like systems such as Google Docs or NetSuite, where everything is centralized in the cloud. There are no files, no local installations and no version mismatches. Everyone is always working on the same version of the software because there’s only one instance of the software and it’s in the cloud. You never have to worry about installations, upgrades or version control issues. Onshape runs on almost any device — whether it’s a Linux machine, Mac, Chromebook, iPad, Android tablet or even a phone.
This means real-time collaboration is seamless. Multiple people can work on the same model simultaneously and there’s no risk of conflicts or version errors because everyone interacts with the same cloud-based database. It fundamentally changes how teams work together, allowing faster, more efficient collaboration.
Moncur: How do companies transition from a system like SolidWorks to Onshape, especially if they have years of SolidWorks files?
Hirschtick: Transitioning depends on the situation and the business’s needs. There are three main areas to consider: moving people, data and processes.
The data depends on what you need to do with your old SolidWorks files. If all you need is the geometry from those files — for example, if you’re using old designs as a starting point for new ones — then Onshape handles that very well. We can import geometry easily. If you need the entire feature history or assembly mates, that becomes more complex, but we work with customers to determine what’s necessary and how to approach it. Some businesses have migrated hundreds of thousands of files into Onshape.
Moving people involves training. Some engineers resist change — they’ve been using SolidWorks for decades and are comfortable with it. But as you’ve seen with your kids, younger generations are far more comfortable with cloud-based tools. They’re used to working on platforms like Google Docs or using Chromebooks in school. They’re not accustomed to managing files and local installations. That makes them more adaptable to tools like Onshape, which are built for modern workflows.
The hardest part is process migration. Onshape enables teams to work faster, but that often requires a change in workflow. In traditional systems, teams work in a more waterfall-style process. In Onshape, they can work more collaboratively and agilely. That’s where the real benefits come in — the ability to innovate faster and get changes into products quicker. But it also means changing the way teams are used to working, which can be uncomfortable at first.
Moncur: Does Onshape offer any advantages in terms of pricing?
Hirschtick: Yes, Onshape’s pricing is simple – it’s an annual subscription per user and that’s it. There’s no upfront license fee and no hidden costs. People often ask, “What happens if I stop paying? Does my data disappear?” The answer is no. Your data is still there. You lose the ability to edit it, but you can still access and download it. If you decide not to renew your subscription, we don’t delete your data – it’s still available.
We also offer a free plan, like the one your kids used. It’s available for makers, hobbyists or professionals who want to experiment with the system before committing to a subscription. For professionals, we have a trial program where you can use the full-featured version of Onshape for a few weeks, complete with training and support to help you get started.
Moncur: What about compatibility with SolidWorks? If a company’s customers are all using SolidWorks, does that cause issues when switching to Onshape?
Hirschtick: That can be a consideration, but it depends on what you need to do with the data. There’s no issue if you’re sending models to customers who only need the geometry. Onshape can export models in standard formats like STEP or IGES, which any CAD system can read.
If you’re worried about customers needing to edit your models, it’s worth noting that Onshape lets you share models with anyone. They don’t need to buy Onshape to view or interact with the models. You can share a link, and they can open the model in their browser and collaborate with you in real time if needed. In many cases, compatibility is less of a problem than people might think.
At the same time, you must ask yourself what’s more important — the occasional need to exchange a file with a customer or the ability to innovate faster and collaborate more effectively within your team. Onshape can give you a competitive edge in terms of speed and efficiency, and that’s often more valuable in the long run.
Moncur: Onshape seems to have many advanced features. Are there any specific areas where it’s particularly strong compared to other CAD systems?
Hirschtick: Absolutely. Onshape was designed with several advanced capabilities that set it apart from traditional CAD systems. One area where we excel is multi-part modeling. In SolidWorks, multi-part modeling was more of an afterthought — it was added over time but wasn’t part of the original design. In Onshape, it’s built into the core of the system. You can create and edit multiple parts in the same environment, and the system handles them as individual parts with complete control over how they relate to each other. This makes it much easier to work with complex assemblies.
Another area is our sheet metal tools. Onshape allows you to edit the flat pattern, the 3D model and the bend table simultaneously. Changes made in any of these views automatically update across the board, saving time and effort.
We also have FeatureScript, which allows users to create their custom features. This differs from traditional user-defined features in systems like SolidWorks, which don’t integrate as smoothly with the rest of the system. With FeatureScript, you can create custom features that behave just like the built-in ones and can be shared across teams. We wrote all of Onshape’s standard features — things like fillets, extrudes and sweeps — in FeatureScript, and we’ve open-sourced that code so anyone can modify or build on it.
And let’s not forget cloud-based rendering and simulation. Onshape leverages the power of the cloud, so you’re not bogging down your local machine with resource-intensive tasks. You can run simulations or renderings on any device, even a Chromebook, because all the heavy lifting is done in the cloud.
Moncur: What’s the security like in a cloud-based system like Onshape?
Hirschtick: Security is one of the strengths of a cloud-based system. People used to worry about how secure their data would be in the cloud, but the reality is that it’s often more secure than keeping files on a local machine. When you store files locally, they’re vulnerable to theft, accidents or hardware failure. How often have we heard about laptops being stolen or lost with sensitive data?
In Onshape, all your data is stored in the cloud. There are no local files to lose, and access is controlled centrally. You can share models with colleagues or customers without sending files back and forth, which reduces the risk of version mismatches or unauthorized access. The difference between keeping your money in a secure bank vault versus under your mattress is that the cloud offers better security protocols than most local systems.
Moncur: What should we expect from Onshape in the next few years?
Hirschtick: We have big plans for Onshape. It’s still the only cloud-native CAD system, but we’re also the fastest-evolving system in the industry, with updates every three weeks. That means our users are always on the latest version and don’t have to wait for annual releases to get new features or improvements.
In 2022, we had our biggest year yet, with major new features like simulation, rendering and an ECAD-MCAD integration tool. We also doubled the rate at which we deliver improvements to core modeling and drafting tools. Looking ahead, we recently acquired a CAM company and are working on integrating that into Onshape. We’re also developing generative design capabilities, allowing users to generate optimized designs based on input parameters automatically.
Our parent company, PTC, fully supports Onshape and our vision for the future. We’ve got a lot of exciting things in the pipeline, and our users can look forward to even more powerful tools and faster innovation in the years to come.
Moncur: As someone who founded SolidWorks and Onshape, do you ever feel conflicted about competing with your former company?
Hirschtick: Not really. My focus has always been on the users — the engineers and designers who rely on these tools to create great products. When I started SolidWorks, my goal was to make powerful CAD tools accessible to more people, and that’s still my goal today with Onshape. It’s all about serving the needs of the users.
Yes, competing with SolidWorks is a little strange now, but I’m not trying to do anything wrong to my old company. I’m trying to keep pushing forward and delivering.
Moncur: Do you have any advice for engineer entrepreneurs out there who might be working towards launching their own products, be it software or hardware?
Hirschtick: Be persistent. It’s been nice to talk about two great successes in my career, Onshape and SolidWorks, but we have yet to talk about the things I’ve tried that didn’t work. My first company, Premise, could have been more successful. I could have given up. I could have given up when people said no to SolidWorks. I can’t guarantee you’ll succeed, but I can guarantee that if you don’t try, you won’t succeed. So you have to keep trying. The other thing is that failures and problems are the neighbors of success. Some people think they’re opposites. They try to build something and it’s a total failure. Total failures live in the same neighborhood as successes and in different neighborhoods than mediocrity. I encourage everyone to keep trying. Don’t be reckless. Don’t endanger your family finances or your career. Those can be endangered by trying to achieve success. Don’t bet it all. Try to understand that uncertainty and risk are part of it, and it may take a bunch of tries to get where you want to be. That’s more typical than any great success story. I love seeing our customers build new products. I love product development. But some products work, some don’t, but you have got to keep trying.
Moncur: Great advice. One last question: in your role as an engineer, what is one thing that frustrates you, and conversely, one thing that brings you joy?
Hirschtick: What frustrates me is the bad user experience. I recommend Donald Norman’s “Design of Everyday Things” or Steve Krug’s “Don’t Make Me Think” about website design. They teach you about thinking, about good UX. Bad user experiences, like elevators with confusing buttons, bother me, and light switches in hotel rooms that don’t work the way I expect. Those kinds of things bug me. It happens in software and hardware, too. It bothers me when I see it in my products. That’s my biggest frustration.
And one thing that brings me joy? That’s an easy one: when my customers build great products using Onshape and tell me they did it faster and easier because of Onshape. That’s exciting to me. I love building CAD. I love the cool features I was telling you about. I love that we have lots of users. Still, none of that means anything until a customer says to me, Jon, I built this product… whether it’s a water bottle or a water balloon launcher or a watercraft or a car or a rocket ship or a medical device or a bicycle, medical device, fitness wearables… that’s what brings me the joy.
Moncur: That’s a great insight. As engineers, we love it when we see our users succeed because of something we brought to the world. What a treat this has been. Thank you so much for giving up your precious, busy time and sharing it with us here on the show.
If someone wants to get ahold of you, is LinkedIn the best way to do so?
Hirschtick: Yes, LinkedIn is the best way (https://www.linkedin.com/in/jonhirschtick/), and you can also reach me on X [formerly Twitter] at @jhirschtick.
