The moment this becomes a real problem is when a mid-career mechanical engineer sits down with a tool they use maybe twice a month — Ansys Mechanical, HyperMesh, LS-DYNA — and spends 20 minutes hunting for a setting they've found before but can't relocate. It's not that the tool lacks documentation. It's that CAE software has hundreds of deeply nested menus built up over decades of feature accretion, and the vendors have no structural incentive to simplify it. Their buyers are enterprise IT and simulation directors who evaluate on solver accuracy and licensing terms, not on whether a junior analyst can find the contact definition menu without help. The gap between buyer and daily user is wide enough that 'the UI is hard' never rises to a priority in the vendor's roadmap.
What's missing is not a tutorial or a help doc — it's a live, context-aware layer that sits on top of whatever CAE software is open and shows an engineer exactly where to go for their next step in a specific workflow. Not generic tooltips. A workflow for 'set up a nonlinear structural analysis in Ansys Mechanical from a clean geometry import' that walks through the actual menu sequence with step highlights, catches common wrong turns, and lets teams build and share their own internal workflows for their specific use cases. Users complained that 'options are hard to find' and that 'sub-modules are not user friendly for newer users' — this is the direct problem. Nobody has built a cross-product, workflow-specific overlay because it requires deep knowledge of each UI, ongoing maintenance as vendors update their products, and it sits awkwardly outside the vendor's own onboarding ecosystem.
The recurring need is real: every new hire to a simulation team, every engineer rotating into a new tool, every student joining an aerospace or automotive company represents months of ramp time where productivity is low and mistakes (like the LS-Prepost hang-and-lose-work complaint) are expensive. Training costs for CAE software are not trivial — companies pay for courses and still end up with analysts who can't find settings. A team lead who can record a workflow once and deploy it to five new hires has a concrete ROI to point to.
What to build
Build a desktop overlay application that reads the active window title and process of supported CAE tools, then displays a floating step-by-step workflow panel — with annotated screenshots of the actual UI — that a team can author once and share internally, covering the exact menu paths for their specific simulation workflows.
Where to start
Start with HyperMesh specifically, where the complaint about 'huge differences between the old menu and the new setup' reflects a known, documented transition that has frustrated entire teams simultaneously — giving you a concentrated cohort of buyers who just experienced the pain and are actively looking for a fix right now.
The hard part
Keeping step-by-step UI paths accurate after each vendor software update is a manual maintenance burden — a workflow authored against Ansys 2023 R1 may be partially broken by 2024 R1, so you need either automated UI diff detection or a fast community-correction loop before the product feels unreliable.
How it makes money
Per-seat annual subscription charged to the team lead or training manager, with a free single-user tier to seed organic adoption inside engineering orgs, expanding to team licenses when workflows need to be shared.
See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Simulation & CAE.
More ideas in Simulation & CAE