When CSRD applicability guidance first circulated in mid-market finance and compliance departments in 2023, the default response was to call a Big 4 firm and ask for a scoping quote. Those quotes came back in the range of €150,000–€400,000 for year one, with annual renewal fees for ongoing data collection and disclosure management. For a 450-person manufacturing company without a sustainability function — which describes most mid-market industrial companies entering CSRD scope in 2025-2026 — that number produced a recognizable response: the project got deprioritized until the deadline pressure became unavoidable.
The assumption embedded in those quotes is that CSRD is fundamentally a consulting engagement requiring external specialists to perform the work. That assumption is partially correct and largely wrong. The correct framing is: some components of CSRD genuinely require specialist human judgment. The majority of the work is structured data collection, classification, and disclosure formatting — tasks that consulting firms price at specialist rates but that are, in practice, automatable.
What actually requires external expertise
Two components of CSRD preparation genuinely benefit from external specialist input, and it is worth being precise about why.
Double-materiality assessment facilitation. The assessment process itself — identifying impacts, risks, and opportunities, scoring them against a materiality threshold, documenting exclusion rationale — can be run internally. But for a first-year filer without prior ESRS experience, having a facilitator who understands EFRAG IG 1 requirements run the internal workshops and structure the IRO scoring process adds real defensibility to the output document. The materiality assessment documentation is one of the first items an assurance provider reviews. If the scoring methodology is undocumented or the threshold logic is implicit rather than explicit, an assurance provider will flag it. External facilitation for a mid-market company's materiality assessment is a focused engagement: three to five working days of specialist time spread over four to six weeks. At specialist consultant rates, this is a €15,000–€40,000 engagement — not a six-figure project.
Assurance readiness review. For companies filing under CSRD Article 19a for the first time, limited assurance under ISAE 3000 (or national equivalent) is required. Your assurance provider — typically a statutory auditor or specialist sustainability assurance firm — will conduct a review of your disclosure package and the underlying data. Preparing for this review benefits from the input of someone who has been through the assurance process before and knows what the assurance team will test. This is a pre-assurance advisory role, typically a few days of scoped external input, not a parallel project.
These two items represent, at most, €50,000–€60,000 in external costs for a well-managed mid-market engagement — not €240,000.
What can be handled in-house with software
The remaining scope — which is the majority of the CSRD compliance workload by time and cost — is data work: collecting activity data from financial and operational systems, classifying it against GHG Protocol categories, applying emission factors, assembling the ESRS E1 disclosure tables, and maintaining the methodology appendix and data lineage documentation. This is structured calculation work. It requires accuracy and completeness, not specialist sustainability judgment.
GHG inventory (Scope 1, 2, and 3). Your ERP, utility billing data, and travel expense system contain the activity data for Scope 1 combustion, Scope 2 electricity consumption, and the material Scope 3 categories (purchased goods, business travel, capital goods). Classification against GHG Protocol categories using NACE-based spend factors for Category 1, distance-based factors for Category 6, and IPCC combustion factors for Scope 1 is a calculation pipeline that software handles reliably. An internal finance and sustainability lead reviewing the output is a quality control function, not an original data-collection project.
ESRS E1 disclosure assembly. The disclosure format is specified by ESRS. Each disclosure data point maps to a specific ESRS E1 paragraph with defined data requirements. E1-5 requires energy consumption total and by source type. E1-6 requires gross Scope 1, 2, and 3 GHG by category. E1-7 requires GHG removal and sequestration data where applicable. E1-9 requires a description of physical and transition risk exposure. Software that maps classified emission data to ESRS disclosure templates removes the manual formatting work that consultancies bill substantial hours for. The compliance officer reviews and signs off the output; they do not write the disclosure from scratch.
Gap analysis documentation. Identifying which ESRS E1 disclosure requirements are fully met by available data, which have partial coverage with documented assumptions, and which require additional data collection — this is a systematic matching problem. A software-generated gap analysis is more complete and consistent than a manual checklist and updates automatically as new data is added to the system.
A worked cost comparison
Consider a 520-person specialty components manufacturer with SAP S/4HANA, SAP Concur for expense management, and manufacturing operations across three European sites. CSRD Article 25a applicability kicks in for their FY2025 reporting year, with disclosure due in 2026.
Consultancy-led Year 1 scenario:
- CSRD readiness assessment and double-materiality facilitation: €40,000
- GHG inventory data collection sprint (2 consultants, 12 weeks): €130,000
- ESRS E1/S1 disclosure drafting and internal review: €55,000
- Assurance readiness preparation: €20,000
- Year 1 total: approximately €245,000
Software-augmented in-house Year 1 scenario:
- Double-materiality workshop facilitation (external specialist, 4 working days): €22,000
- Greenopsiq Professional plan: $42,000/year — covers SAP and Concur connectors, full Scope 1-3 automation, ESRS E1 disclosure package, gap analysis
- Internal owner time: approximately 0.4 FTE over 14 weeks during initial setup and first disclosure sprint (internal cost, no incremental external spend)
- Assurance readiness advisory: €10,000
- Year 1 total: approximately €70,000–€80,000 (external cash outlay)
Year 2 is where the comparison becomes clearer. The consultancy model requires a repeat engagement for annual data collection and disclosure update — typically at 40-60% of year-one fees, so €100,000–€150,000. The software model's annual renewal is the subscription cost. The cumulative three-year cost differential is typically in the €300,000–€500,000 range for a company of this profile.
The honest counterpoint
This model is not the right fit for every company, and we should be clear about that. Three situations where the software-augmented in-house approach does not work well:
Complex multi-entity group structures. A company with 15 legal entities across 8 EU jurisdictions, with intercompany transactions that complicate reporting boundary definitions, has structural complexity that benefits from specialist project management. The data pipeline can still be automated — but coordinating the organizational scope across entities requires governance that often needs external facilitation.
Companies with significant ESRS S or ESRS G disclosure scope. Greenopsiq automates ESRS E1 and E2 data work. If your materiality assessment identifies ESRS S1 (own workforce) and ESRS G1 (business conduct) as material, the data collection for those topic standards — HR system data exports, workforce demographic analysis, anti-corruption control documentation — requires different tooling and process expertise that is not in the ERP data pipeline. Those workstreams may still benefit from external support.
Companies that want to outsource accountability. The in-house model requires a named internal owner with meaningful time allocation and organizational authority to get data from finance, IT, and operations. If the internal owner is the sustainability manager with a quarter of their time and no authority to direct IT or finance teams, the software model does not replace the organizational change management that a consulting engagement would provide (at a cost premium). The software automates the calculation; it does not substitute for the internal governance structure needed to manage the compliance process.
What the first 12 weeks look like in practice
For a company that decides to proceed with the in-house model, the typical timeline to a first draft ESRS E1 disclosure runs approximately twelve weeks:
- Weeks 1-3: Double-materiality assessment with external facilitator. Output: material ESRS topics list, IRO scoring matrix, signed-off materiality threshold documentation.
- Weeks 3-4: ERP connector setup. One afternoon for SAP Basis admin to configure OAuth credentials. Initial full-year data pull completes within 24 hours. First Scope 1, 2, and Category 1 Scope 3 estimates available for review.
- Weeks 4-7: Internal review of classification output. Finance team flags vendor miscategorizations. Concur connection configured for Category 6 data. Utility invoice documentation uploaded for Scope 1 and 2 activity-data precision. Gap analysis reviewed — Categories 4, 7, and 11 data collection plans documented.
- Weeks 7-10: ESRS E1 disclosure package generated from classified data. Internal review by compliance officer and CFO. Methodology appendix reviewed for completeness. Data lineage documentation prepared for assurance file.
- Weeks 10-12: Assurance readiness review with external advisor. Disclosure package finalized. Submitted to statutory auditor or assurance firm for limited assurance engagement.
This timeline assumes the materiality assessment is completed concurrently with ERP connector setup — which it can be, since those workstreams do not depend on each other until the gap analysis phase.
Request a walkthrough to see how this timeline maps to your company structure and ERP configuration. We will tell you honestly if your situation is one where the in-house model works well or where external project management support makes more sense.
