A production manager has a limited budget: invest in energy monitoring first, or digitize the paper tracking forms on the shop floor first? The honest answer is often “both,” but no business can fund everything at once. Sequence matters — a project started in the wrong order often means the data collected in step one has to be thrown out and rebuilt in step two.
This piece lays out a practical decision framework for an SME thinking about green and digital transition at the same time: which trigger points to which starting point, how to run both in parallel in practice, and the traps that come up most often.
Can the two really be separated?
On paper, green transition (emissions measurement, energy efficiency, CBAM/CSRD compliance) and digital transition (ERP, IoT, process automation, data analytics) are treated as separate budget lines, separate project teams, sometimes even separate consulting firms. In practice, both rest on the same foundation: accurate, timely, traceable data.
Reporting a factory’s energy consumption under Scope 1-2-3 requires machine-level electricity/gas data. The same data feeds a production planning system’s capacity calculations. A sensor installed once can feed both the carbon report and the production dashboard — installed twice, it means double the cost and double the integration headache.
So the real question isn’t “which one should I do,” it’s “which order lets me avoid rebuilding step one when I get to step two.”
A concrete example: one measurement point, two outputs
Picture a metal-processing plant. An energy analyzer is installed to monitor the electricity draw of a machine on the press line. That single device’s data can serve two purposes:
- On the green side: machine-level energy consumption feeds Scope 2 emissions calculations and the energy-efficiency report.
- On the digital side: the same data can flag capacity usage and abnormal pre-failure consumption (a basic form of predictive maintenance) in the production planning software.
The equipment and installation cost is paid once, and two separate benefits come out of it. The problem shows up when the two projects are handed to separate teams on separate timelines: the energy-monitoring project installs its own sensor, the production-automation project installs its own — two systems measuring the same machine twice.
When digital infrastructure should come first
If at least two of the following apply to your business, the starting point is most likely digital:
| Situation | Why digital first |
|---|---|
| Production data is still on paper or in spreadsheets | Data-collection discipline needs to be in place before a measurement system is |
| No ERP, or modules that don’t talk to each other (data silos) | Carbon/energy data falls into the same silo problem |
| Machine fleet is newer, sensor/automation integration is straightforward | Physical infrastructure is ready — adding a measurement layer on top is cheap |
| No direct EU customer or CBAM pressure yet | Compliance timeline isn’t urgent, giving room to build the foundation properly |
In this scenario the logical order is: data-collection infrastructure (ERP + machine-to-machine/IoT) → an energy/emissions monitoring layer on top → reporting. Details on digital transition.
When green goals should come first
The reverse is also common — for some businesses the trigger already comes from outside, with a real deadline attached:
- You export to the EU and a customer is asking for embedded emissions data. If you’re in one of the six CBAM sectors (iron and steel, aluminium, cement, fertilizer, electricity, hydrogen), that request may already be on your desk today — we covered this in detail in our CBAM definitive period piece.
- A large firm in your supply chain falls under CSRD/ESRS and is asking you for Scope 3 data.
- Energy cost is a visible share of your production cost and an efficiency improvement would show up directly in margin.
In this case, priority starts on the measurement and reporting side; digital infrastructure comes in as a second step to make that measurement sustainable over time. Scope and process are covered on the green transition page.
The practical way to run both together
For most SMEs, the realistic third option is running both in parallel at different speeds. That’s why İkiz Eksen’s methodology is built around a three-step cycle:
- Measure — clarifies the current state of your data, where the gaps are, and which trigger is the priority (compliance pressure, cost pressure, or operational inefficiency).
- Transform — starts from whichever data can serve both green reporting and digital process, so a single integration feeds two goals at once.
- Sustain — makes sure the system is an ongoing, monitored structure rather than a one-off project.
This sequencing largely removes the “digital first vs. green first” dilemma, because the first step already clarifies which trigger is more urgent. The full method is on the methodology page.
Common mistakes
- Collecting the same data twice. When an energy-monitoring project and an ERP integration project go to separate teams on separate timelines, the same machine can end up with two different sensors feeding two different systems.
- Investing early in reporting infrastructure without compliance pressure. If you’re not yet in CBAM/CSRD scope, building the digital foundation (ERP, data discipline) first is usually more efficient.
- Planning digitization completely disconnected from green goals. If energy/emissions data fields are never considered during a new ERP rollout, a second integration project is often needed a few years later.
- Picking a consultant for only one side. If the green consultant doesn’t know the digital side, or vice versa, the two projects proceed unaware of each other and the data models end up incompatible.
- Launching the pilot across the entire plant instead of one line or department. Rolling out to the whole facility before the data model and integration are validated on a small pilot area (one line, one machine group) is a real risk to both budget and schedule.
Scenario examples by sector and turnkey project scope are on the solutions page.
Frequently Asked Questions
Is it realistic for a small business (25-50 employees) to run both at once?
Usually not — running two major projects at the same time is risky for a resource-constrained SME. A more realistic path is to start with whichever side has the more urgent trigger (green if compliance pressure exists, digital if data discipline is missing), then build the second step on top of the first.
Can CBAM/CSRD reporting be done before digital transition is complete?
Yes — emissions data can be collected and reported manually or semi-automatically without a full ERP in place, and that’s a workable short-term solution. But as data volume grows, a manual process becomes error-prone and slow; building a measurement/data infrastructure becomes close to unavoidable in the medium term.
Is twin transition more expensive than doing digital or green alone?
If run separately, yes — because the same data source ends up needing two integration efforts. If the same sensor/data infrastructure is designed from the start to serve both reporting and operational process, total cost usually comes out lower than two separately run projects.
Which support/incentive programs fit twin transition?
KOSGEB runs separate support lines for both digital and green transition (for example, current calls like the COP31-focused acceleration support — see our KOSGEB COP31 support piece); current terms and eligibility should be confirmed through KOSGEB’s official channels.
Is picking the wrong order reversible?
Yes, but it’s costly. A project started in the wrong sequence usually requires rebuilding part of the data model or sensor infrastructure in the second project. A short assessment before starting — current data state plus the priority trigger — costs far less than that rework later.
Teams that want a clear recommendation on where to start can request a short assessment call through contact.