A five-person structural engineering consultancy has one Ansys Mechanical license. Only one person can use it at a time, and because it's nominative — tied to a named user — they can't pass it to whoever needs it that day without calling vendor support or manually re-assigning it. Users described this exactly: 'licence management is nominative, making it difficult to share the tool with colleagues' and 'license sharing was sometimes problematic.'

The vendors keep nominative licensing because it's how they upsell: if sharing is painful, you buy more seats. The buyer is usually the IT manager or finance director who negotiated the contract and doesn't feel the daily friction; the engineers who feel it have no purchasing power. That structural disconnect means the complaint never turns into a canceled contract — it just becomes background frustration.

The specific failure is that there's no lightweight scheduling and handoff layer that sits on top of an existing floating or nominative license. Engineers have to coordinate by Slack message or a shared spreadsheet to figure out who has the license right now, who needs it next, and when it'll be free. When someone forgets to release it, the next person loses hours.

This is a business because small consultancies face this every working day. The cost of a blocked license is a billable engineer sitting idle — at $100-150/hour loaded cost, even one hour of blocked access per day per engineer is a real number. The need doesn't go away; it worsens as projects stack up. Vendors won't fix it because the fix reduces their seat-count upsell.

What to build

Build a lightweight desktop agent for Windows that monitors license checkout status across a team's shared floating license pool, shows who holds each license and for how long, sends a Slack or Teams ping to request release, and logs utilization so managers can justify (or push back on) buying additional seats.

Where to start

Start with teams running Altair's license model (Altair Units), which uses a well-documented token system and where multiple products (HyperMesh, SimSolid, HyperLife) share one pool — the multi-product contention problem is worse and the ROI of visibility is immediate.

The hard part

License server APIs vary across vendors (FlexLM, RLM, Altair Units) and some are poorly documented or locked down, so reading live checkout status reliably across multiple vendors without violating license agreements requires careful scoping of what data you can legally surface.

How it makes money

Flat monthly fee per license server monitored (e.g., $99-199/month per server), regardless of seat count — cheap relative to one wasted engineer-hour and easy for an engineering manager to approve without finance involvement.

See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Simulation & CAE.

More ideas in Simulation & CAE