Please describe your company, your role, and the industry you operate in.
I run technology for Bauer Industrie GmbH, a growth-stage Construction company based in Munich, Germany. My role as Leiter Digitalisierung covers product engineering, platform operations, and our vendor relationships. We'd hit a point where our internal capacity just couldn't keep pace with what the roadmap demanded.
What specific problem or business challenge led you to hire this company?
Our previous vendor had maintained this platform for a few years, and the technical debt had piled up to the point where our delivery speed had dropped to a fraction of what it used to be. We needed fresh engineering eyes and an actual plan to deal with the underlying mess.
What services did the company provide for your project?
The scope ran the full ERP Development lifecycle — discovery, requirements, architecture, development across roughly a dozen sprints, integration testing, performance validation, deployment, and a four-week hypercare window afterward. They also handed over full documentation and ran a knowledge transfer session for our internal team.
Why did you choose this company over other providers you considered?
A peer in the Construction space had used them for something similar in ERP Development and recommended them without hesitation. Our own due diligence backed that up. Domain knowledge, ERP Development depth, and a track record of actually delivering — that combination made the decision easy.
How clearly did the company understand your requirements and business goals?
Really well, partly because they already had Construction experience that cut down on the amount of context we had to provide. They knew the terminology, asked the right questions, and translated our business requirements into technical specs accurately enough that development barely needed any clarification cycles.
How was your overall experience with their communication and project management?
Professional throughout. The project manager always had a clear view of the critical path and flagged changes to it honestly, without spin. The one significant scope change we made mid-project went through a clean process — fairly priced, clearly documented, and absorbed without knocking the rest of the timeline off course.
Did the company deliver the project on time and within your expected budget?
Both, yes. One sprint hit a one-week delay from a third-party API dependency outside anyone's control. The team flagged it three weeks ahead of time, laid out two options, and we picked an approach that clawed the schedule back within the same sprint. That's the kind of foresight that separates real project management from just reacting to problems.
What tangible results or business impact have you seen since the project was completed?
The clearest measure is how the system's actually performing in production. In the four months since go-live we've had zero major incidents, our page performance scores improved across every Core Web Vitals metric, and two enterprise clients who'd previously flagged our old platform's limits during renewal talks signed again without raising it.
What did you like most about working with this company?
What they did after launch. A lot of vendors treat go-live as the finish line. This team treated it as the start of a different phase — the hypercare period was substantial, the documentation held up in practice, and they checked back in at the thirty and ninety day marks to go over production metrics with us unprompted.
Would you recommend this company to others, and would you work with them again?
Absolutely, with one caveat worth mentioning: the value really starts in discovery, so clients who take that phase seriously will get the most out of it. We put real effort in upfront and it clearly paid off in what got delivered.