How BAG Got a Clear Technical Roadmap for Their Pimcore Infrastructure in 4 Weeks

Basalt-Actien-Gesellschaft (BAG) is one of Germany's largest producers of building materials, with quarries, asphalt plants, and concrete production facilities across the country. Their digital infrastructure - specifically their Pimcore-based cockpit and highway management systems - had grown from a small internal tool into a business-critical platform used daily by operations teams.

The platform worked. But BAG's leadership had a deeper question: should they keep building on it? The codebase had been developed over several years by rotating teams. Documentation was sparse. No formal code quality assessment had ever been conducted.

BAG faced a high-stakes decision. Investing six figures into new features on a platform with hidden technical debt could mean compounding problems. But replacing the platform entirely - migrating data, retraining users, rebuilding integrations - could cost even more and disrupt operations for months.

What BAG needed wasn't another developer's opinion. They needed a structured, tool-backed technical evaluation that could quantify code quality, identify specific risks, and provide a clear recommendation: build on this foundation or start fresh.

BAG consulted three agencies. Two proposed rebuilding the platform from scratch - a recommendation that felt premature without rigorous analysis of what already existed. easy.bi proposed something different: a 4-week technical audit that would produce data-driven recommendations, not assumptions.

The deciding factor was easy.bi's deep Pimcore and Symfony expertise. Auditing a Pimcore codebase requires understanding Pimcore-specific patterns, Symfony conventions, and the common pitfalls of enterprise PHP architectures. easy.bi's team had this context from years of building and maintaining Pimcore-based systems for other enterprise clients.

The easy.bi team treated the audit like a medical examination. The goal wasn't to fix anything - it was to produce a complete, honest picture of the platform's health with specific recommendations for each finding.

Automated code analysis with PHPMD and PhpMetrics. The team ran both tools across the entire codebase, generating metrics on cyclomatic complexity, coupling, cohesion, code duplication, and dependency depth. These weren't subjective assessments - they were measurable indicators that could be tracked over time if BAG chose to improve the existing platform.

Architecture review against Pimcore and Symfony best practices. Beyond automated metrics, the team manually reviewed critical components: data models, event subscribers, custom bundles, and API endpoints. Each was evaluated against Pimcore's documented best practices and Symfony's architectural conventions. Deviations were cataloged with severity ratings and remediation effort estimates.

Scalability and maintainability assessment. The team simulated increased data volumes and concurrent user loads against the existing architecture. This identified three specific bottlenecks in the data layer that would surface at 2-3x current usage - well within BAG's growth projections.

The final deliverable was a 40-page technical report with a clear executive summary, detailed findings organized by severity, and a prioritized roadmap with effort estimates for each recommended improvement. No ambiguity. No generic recommendations. Every finding included the specific file, the specific problem, and the specific fix.