Lotus is a Danish company building power and thermal solutions for the AI era, the kind of high-current, low-voltage power delivery that data centers and AI accelerators now depend on. It's a fast-growing business with a fast-growing product portfolio, and growth like that has a way of exposing the limits of however a company has been managing its product data so far.
This is Lotus's view on why they chose Highstage, what the implementation was like, and what they expect from it as they scale. It's a story about getting ahead of complexity rather than recovering from a crisis, and it's one a lot of growing electronics companies will recognise.
Growing into the problem
The honest version of why Lotus needed PLM is almost undramatic. The company has been scaling from a small organisation into a larger one, and both the product portfolio and the product complexity have grown with it. What worked for a smaller, simpler business wasn't going to support where Lotus is heading.
That's a different starting point from the company in crisis, and worth naming, because it's actually the more common one. Most teams don't replace their setup the day it breaks. They replace it the moment they can see it won't support the next stage of the business. For Lotus, the existing approach simply could not support the quality their customers would come to expect.
So the decision wasn't reactive. It was a deliberate move to put the right foundation in place now, before the cracks turned into something customers would notice.
The pain that mattered most: change traceability
Push past the framing and there's one concrete problem at the centre of it. Change traceability in product design.
In a power-electronics product, one change rarely stays contained. Adjust a part and you've potentially touched everything connected to it. The question that haunts a growing hardware team is simple to ask and hard to answer: if we make this change, how does it affect all the other parts it touches?
Without a system built for it, that question gets answered by memory, by whoever happened to be in the room, by hoping nothing slipped through.
For a company qualifying prototypes and tightening up against customer and regulatory requirements, hope isn't a process. The ability to trace a change through everything it affects was the capability Lotus most needed, and most wanted to lock in before scaling further.
Why Highstage, and not the system with more dashboards
Buying PLM is not a quick decision, and Lotus looked around. What they describe is a pattern a lot of engineering teams will find familiar.
The other systems had more. More features, more dashboards, more of everything on screen. And when those systems were demoed to the Lotus engineers, the reaction wasn't excitement. It was being overwhelmed. Highstage, by contrast, kept its focus on what actually delivers value. It was built for the electronics industry, it concentrated on the problems Lotus actually had, and the engineers found it intuitive to use.
That last point matters more than feature lists tend to admit. A PLM system only delivers value if people actually work in it. A system so dense that engineers need a manual open to know where to click is powerful right up until it becomes the thing everyone quietly avoids. Lotus chose differently.
There was also the conversation itself. Lotus came to Highstage with a defined set of requirements, and rather than a one-way pitch, what followed was a genuine back-and-forth, matching those requirements against what Highstage could do, and then improving on them. The Highstage team suggested approaches Lotus hadn't considered, ones that made the end result better than the original brief. The presentation was streamlined. The follow-up was a real discussion. For a company trying to make a careful, long-term decision, that mattered.
On time, on budget, no consultants
The implementation is where this story is most concrete, because it's already done.
Lotus set clear requirements up front, put a small team on it, and worked intensively for a relatively short stretch. From no system to a system up and running took a short time, on an ambitious timeline, landing inside both the schedule and the budget set at the start. Everything ran according to expectations, and was well supported throughout.
One thing stood out as a genuine positive: no external training was needed. The knowledge was built up through the implementation itself and carried straight into the team. No week-long workshop with outside consultants. No PLM specialists required for every small task.
Lotus stayed in control of the whole process, from requirements, to matching them against the system, to implementation and training. It wasn't consultants squeezing requirements out of the business. It was Lotus driving, with strong support from Highstage alongside them.
For anyone who has lived through an enterprise software rollout where the consultants never quite leave, that's a meaningful difference. The knowledge stays in the building.
Where they are now: the system in their hands
Lotus is at the start of using Highstage rather than deep into it. The users are onboarded, a migration plan is in place, the guidelines for the team are written. Full migration is still underway. So it's too early for results, time saved, errors avoided, audit outcomes, and Lotus is careful not to claim them before they're real.
But there's one shift the team can already feel, and it's the kind that tends to predict the rest. For the first time, the product exists as a single, inspectable structure. Every detail of it sits in one place, on screen, ready to open up and walk through.
That sense of control is exactly what Lotus set out to build. The thing they wanted is now something they can point at.
A system, or a partner?
Asked whether Lotus sees Highstage as a system provider or a long-term partner, the answer was immediate. A partner, without hesitation.
The reason is telling. Before they even committed, Lotus mapped out a timeline of which capabilities matter and when, and worked through it together with Highstage. Start here now. These features next. These ones further down the road. The relationship was built around where Lotus is going, not just what it needed on day one. As Lotus keeps improving its processes, the expectation is that Highstage will keep supporting that. For a company that intends to keep growing, a vendor who plans around your roadmap is worth more than one who simply sells you today's needs.
Would they recommend it?
Yes, with the kind of qualification that actually makes a recommendation worth having.
Lotus won't hand out a blanket "just buy it," and they're right not to. The recommendation comes with a question attached: what are your requirements, and do they fit? Highstage isn't the answer to every conceivable need. Heavier, more powerful PLM systems exist, the kind where you open a manual every time you want to do something, and for some organisations that trade-off is the right one.
For Lotus, it would be exactly wrong. They wanted intuitive, and they wanted streamlined. Their view is that Highstage is about as streamlined as a PLM system can be. So the recommendation is real, just honest about fit, which is the only kind of recommendation an engineer trusts anyway.
The one thing they're after
Asked to name the single benefit Lotus is most looking forward to, the answer wasn't anything grand. Three words: improve change management.
Not dashboards, not features for their own sake, not a transformation pitch. Just the ability to make a change and know, with confidence, what it touches and why it was made.
For a company building increasingly complex power electronics for some of the most demanding systems in the world, that's not a small ambition. It's the foundation everything else is built on.
Lotus chose Highstage before the cracks showed, on time and on budget, with the knowledge kept in-house. Now the work of growing into it begins.
Scaling a hardware company and want product data your engineers actually use, with full traceability on every change?
See how Highstage PLM works at highstage.dk.
