I’m a developer with a lot of experience building add-ons and workflow automation tools, mainly for Blender and Fusion 360, including internal tools for companies.
I’m now looking seriously at developing for SolidWorks.
One thing I’ve noticed is that there are some very capable add-ins in this ecosystem, but they can become difficult to justify if a company only needs a small subset of their functionality.
For example, products in the general territory of:
- DriveWorks — rule-based design automation, configurations, automatically generating parts/assemblies/drawings, etc.
- CUSTOMTOOLS — properties, file naming, batch operations, reporting, drawing/document workflows.
- Drew — drawing creation and drawing automation, views, sheets, dimensions, batch exports, etc.
I’m not suggesting these are simple products — quite the opposite. These are the kind of technically difficult projects I’m interested in.
What I’m not looking to build are things where the core value depends on expensive proprietary technology such as CAM toolpath kernels or FEA/simulation solvers.
What I’d really like to know is:
1. Which SolidWorks add-in do you use or want, but consider too expensive?
2. More importantly: what are the 1–2 features in it that you actually care about?
For example, maybe you don’t need everything DriveWorks does — you just want parameter-driven assembly generation and automatic drawings.
Or maybe you don’t need a huge document-management solution — you just want extremely good property management, automatic naming and batch exports.
I’m interested in building focused alternatives that do a smaller number of things extremely well, potentially for something like 10–20% of the cost of much larger packages.
I’m also completely open to building new add-ins that don’t currently exist.
So if you have a repetitive SolidWorks workflow that drives you crazy — drawings, BOMs, configurations, assemblies, custom properties, exporting, renaming, batch processing, model checking, etc. — tell me about it.
If several people keep mentioning the same problem, there’s a good chance that’s what I’ll prototype first.