Which EPD route suits your company?
For product groups, variants and growing portfolios, we clarify which EPD coverage makes technical and economic sense – and whether a project-based, hybrid or software-supported route fits best.
First understand the need. Then choose the solution.
Many companies start with a single EPD. As soon as further products or variants are added, the question of the right approach becomes more complex.
How much of our product portfolio will we need to cover with EPDs in future?
Do we need a separate EPD for every product variant?
Which products can sensibly be grouped together?
When is EPD software worthwhile?
Which licence, implementation and internal costs arise?
Is a combination of services and software more economical?
We first analyse the actual need — and then recommend the appropriate route. Not the other way round.
How we clarify the right route
Industry and target markets → customer requirements → product portfolio → future EPD needs.
- 01
Assess coverage
Are a few targeted EPDs sufficient, or does broader portfolio coverage make sense?
- 02
Define the EPD strategy
Product groups, variants, data situation, updates, competencies, total costs.
- 03
Compare economic viability
Licence and implementation costs, resources, maintenance, flexibility — not just prices.
- 04
Declare variants sensibly
Product-specific, average, worst-case or representative EPD – where appropriate based on a calculation model for product groups.
Not every company needs the same solution
What matters is which implementation route fits the product portfolio, data situation, update requirements and available resources – technically and economically.
We take care of preparation
Sensible for a few targeted declarations and limited internal capacity.
- Single EPDs for key products
- EPDs for product groups
- Personal expert support
Combining consulting and digital support
We combine expert support with targeted software support. The tasks of our team and your company are agreed on a project-specific basis.
- Structured product data
- Reusable LCA models
- Expert support and agreed division of tasks
In-house preparation in the tool
Sensible for many products, regular updates and in-house LCA expertise.
- For broad portfolios
- Recurring updates
- Predictable licence costs
A concrete recommendation, not an abstract list of options
You receive a transparent basis for decision-making — with reasoning, sequence and economic estimate.
A recommendation might, for example, look like this:
“Start with two single EPDs, then declare these product groups jointly and do not invest in your own software for the time being.”
- Recommended coverage
- 6 of 42 products
- EPD types
- 2 × product-specific · 2 × representative
- Implementation route
- hybrid
- Software investment
- not recommended at present
Why brands & values?
Methodology. Consulting. Software.
We combine many years of LCA and EPD experience, expertise in structuring product data and our own software development. This allows us to evaluate different implementation routes technically and economically – and to recommend the solution that fits the actual need.
EPDs in Transition
From proof of compliance to strategic instrumentOur study shows how companies use EPDs and which challenges arise around data, processes and scaling.
Ready for the next step?
A short initial conversation is enough to classify your portfolio, requirements and data situation. We will get back to you within two working days.
Frequently asked questions
When is EPD software worthwhile?
Whether software pays off does not depend on the number of EPDs alone. Decisive factors include product variants, update frequency, data situation, internal resources and the desired degree of automation. For few or irregular EPD requirements, project-based implementation can be the right choice. For larger portfolios, frequent updates or recurring declarations, standardised models and software can offer advantages. Which solution is economically suitable should therefore be assessed for the specific use case.
Do we need a separate EPD for every product variant?
No. Depending on product structure and the applicable rules, product-specific EPDs, average EPDs, worst-case EPDs or representative EPDs are permissible. Which EPD type makes sense depends on variants, data situation and the required significance.
Which costs arise in addition to preparation?
Consider licence and implementation costs for software, internal resources, maintenance and updates as well as fees for programme operators, verification and publication. We compare total effort, not just quoted prices.
Can we prepare the EPD ourselves or with AI?
AI can support structuring, data preparation and documentation. A robust EPD nevertheless requires a suitable LCA modelling environment, LCA datasets, expert decisions on system boundaries and allocation as well as verification and publication.
We only need a single EPD for now — is this the right place?
We also prepare individual EPDs for you: clarify requirements, collect data, model the LCA, verify, publish. You can find more about the process on our EPD preparation page.
How does the consultation on the right EPD route work?
The initial consultation takes around 45 minutes. We discuss your starting point, the product portfolio and existing requirements. We usually develop a robust recommendation on EPD coverage, EPD types and the appropriate implementation route within two to four weeks – depending on how quickly the required product and data overviews are available.