ESG and CSRD Reporting Software: Build the Collection Layer, or Buy Workiva and Watershed
Site and entity count decides this, not emissions volume. Below roughly twenty five reporting sites, buy: Workiva for the disclosure document, Persefoni or Watershed for carbon accounting methodology, and put the difference into data quality.
On this page
Site and entity count decides this, not emissions volume. Below roughly twenty five reporting sites, buy: Workiva for the disclosure document, Persefoni or Watershed for carbon accounting methodology, and put the difference into data quality. The build case turns above that, where response rate rather than calculation becomes the bottleneck, or where restatement after acquisitions has become a recurring event. Most single country groups reading this should buy, and a single entity with five utility accounts should not build at all.
When is off the shelf genuinely the right call here?
Buy if you are a single entity in one country with a handful of utility accounts. A consultant and a well built workbook will get you through, and a build would be theatre.
Buy if your primary need is the disclosure document itself with strong controls over drafting, review and sign off. Workiva does that job well and rebuilding it is not a sensible use of capital. If carbon accounting methodology is your main gap and your estate is simple, Persefoni or Watershed will get you further faster than a bespoke engine. Sphera is the right answer where operational health, safety and environment depth is your centre of gravity, and Novata is built for private markets portfolio collection rather than for an operating group. Each of these is strong in its lane and none of them is a weak product.
Buy also if your group structure is stable. The expensive part of a custom build is effective dated consolidation, which earns its money when you acquire, divest or change the consolidation approach for a joint venture. If none of that has happened in five years, you are paying for a capability you will not use.
The test that settles it: count the sites or legal entities you collect from, and count the disclosure regimes you report under. One country, under twenty five sites, one regime and a stable structure means a product will fit you. Do not commission software to solve a problem a competent consultant closes in a fortnight.
When does a custom build actually pay off?
Two or more of these need to hold.
You collect from more than about twenty five sites or entities and response rate is the bottleneck rather than calculation. Your group structure changes often enough that restatement is a recurring event rather than an exception. You report under several frameworks and are currently collecting the same data more than once, which means you have several sets of numbers that disagree with each other. Your assurance provider has already raised traceability as a finding. Or you have bought a platform and your team still runs the real process in a spreadsheet and uses the platform as a place to put the answer.
That last one is the most common story in this sector by some distance, and it is the clearest signal available. It means you are paying for storage of a number produced somewhere else.
The structural reason is that no product can solve your group's data reality. Which entity owns which meter, which lease is triple net, which joint venture is consolidated financially but not under operational control, which site in Poland reports district heating in gigajoules while a site in Texas reports gas in therms, and which of your forty two site controllers answers email during a reporting week. That is organisational, not technical, and it sits upstream of every platform.
Our position is that the calculation engine is the commodity and the collection layer is the differentiator. Anyone can multiply an activity figure by a factor. Getting a facilities manager in Ohio to upload the right invoice on time with evidence attached is what decides whether your reporting survives assurance.
How do they compare on the things that matter in this industry?
- Collection reality. Platform vendors solve this with survey modules. Surveys work when the question is simple and the respondent is motivated, and they fail exactly where your data is hardest: the site with three electricity accounts, one closed mid year, and a landlord invoice bundling water with service charge.
- Factor versioning. Every calculation should store the input, the factor identity, the factor version, the publisher, the conversion path and the code version. Without that you cannot separate a data improvement from a factor revision when a prior year moves, and those mean entirely different things to a reader.
- Effective dated consolidation. An entity and site register carrying ownership percentage, consolidation approach and operational control over time is what lets any period be reported as published or restated on the current perimeter. Group controllers already have this discipline for financial consolidation.
- Assurance traceability. The provider picks a disclosed figure and walks backwards to the source document, the calculation and the approvals. Engagements expand in scope, and cost, when the first few samples cannot be traced.
- Multi framework economics. Model each data point once and map it, at $22,000 to $42,000 for the mapping layer. Run a separate collection per regime and you multiply your collection cost by the number of regimes.
- Archive longevity. The question about a figure published this year can arrive several years later. The evidence archive has to outlive your software vendor and probably your current framework.
What does total cost of ownership look like at your scale?
In Digital Heroes delivery experience a first release is $70,000 to $150,000 over 12 to 18 weeks, covering the entity, site, meter and lease register, a collection workflow with named owners and escalation, document extraction for the invoices that will never arrive as structured data, a calculation engine with versioned factors, and an evidence trail from a disclosed figure back to a utility bill. A full platform adding supplier engagement, target and scenario tracking, multi framework mapping and disclosure drafting is $180,000 to $450,000 phased over 7 to 14 months.
A manufacturing group with 42 sites across nine countries, four automated data sources, two statutory regimes plus investor questionnaires and an acquisition completed last year prices out at $401,000: register assembly $24,000, collection workflow $46,000, document extraction $33,000, calculation engine $58,000, evidence trail $39,000, effective dated consolidation $35,000, four automated feeds $48,000, mapping layer $31,000, supplier portal $38,000, target tracking $27,000 and disclosure drafting $22,000. Add ten per cent contingency, because the register will turn up three sites and two meters nobody had on any list, and the committed number is $441,000 across roughly thirteen months.
Running cost is 15 to 20 per cent of build for support, plus $12,000 to $30,000 a year for the factor library update, $10,000 to $25,000 for integration maintenance, $10,000 to $28,000 for archive hosting and retention, and $8,000 to $25,000 per business acquired. Each new framework mapping is $15,000 to $40,000.
Compare against four things rather than one: your platform subscription, consultant fees for what the platform does not cover, your assurance fee and specifically how it has moved year over year, and internal hours, which are usually the largest and never appear on an invoice.
What does the hybrid look like, and when is it the honest answer?
The hybrid is the answer for most groups with a real case, and it splits cleanly. Buy the disclosure document, build the collection layer.
If a document platform already handles your drafting, review and sign off well, keep it and feed it. Rebuilding controlled document assembly is not where your money earns anything. What you build is everything upstream: the register, the collection workflow, the extraction, the versioned calculation and the evidence chain. Those are the parts shaped entirely by your organisation, which is precisely why no product can supply them.
Inside the build the sequencing matters as much as the split. Start with direct and purchased energy emissions across your largest twenty sites. That is usually most of your operational footprint and it establishes the collection habit, which is the part that actually decides whether anything downstream is defensible. Leave value chain categories, supplier engagement and disclosure drafting to phase two, because they are worth nothing while your own sites report unreliably.
Assemble the entity, site, meter and lease register as a finance workstream before the build starts. It is the task that most often runs long, it is a reconciliation exercise rather than a workshop, and doing it ahead of kickoff costs you nothing in development time.
Get one regime's disclosure right end to end, then add mapping. Trying to satisfy three at once in release one produces a data model that fits none of them cleanly. European requirements have moved through a simplification process and continue to be adjusted, so confirm which wave and which standards apply to you with your auditor rather than with any article, this one included.
Which should you choose, by operator size and stage?
Single entity, one country, a handful of utility accounts: buy, or use a consultant and a workbook. Revisit when you cross into multiple entities or a second regime, not when a vendor demo lands.
Groups under twenty five sites in one or two countries with a stable structure: buy. Workiva for the document, Persefoni or Watershed for methodology, and spend the difference on the data quality work that actually moves your numbers.
Groups above twenty five sites where response rate is the bottleneck: hybrid. Keep the document platform, build the collection layer and the versioned calculation engine, and expect $70,000 to $150,000 over 12 to 18 weeks for a release your sites use in the next cycle.
Acquisitive groups publishing a target against a base year: build the effective dated register early even if you defer everything else. Base year recalculation becomes a rule applied against a threshold rather than a manual reconstruction, and groups that skip it discover the problem the first year the baseline no longer describes the company.
Anyone whose assurance provider has raised traceability as a finding: build the evidence trail first. It reduces the risk of the fee rising, which is the more honest claim than reducing the fee, and avoided scope expansion is a real saving rather than a soft one.
Private markets investors collecting across a portfolio: buy Novata rather than building. It is designed for exactly that shape and an operating group's collection layer solves a different problem.
When the shortlist is down to two and you need a tiebreaker, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 76% of organizations report that less than half their CRM data is accurate and complete, and 37% experienced direct revenue loss attributable to poor data quality (survey of 602 CRM users across the US, UK, and Australia). Source: Validity (2025) →
- Flexera's 2025 State of the Cloud Report (survey of 750+ technical and executive leaders) found that 84% of respondents believe managing cloud spend is the top cloud challenge for organizations today, with cloud budgets already exceeding limits by 17%. Source: Flexera (2025) →
- This World Bank report argues that digital technology adoption raises SME competitiveness, productivity and resilience, while documenting that smaller firms consistently lag larger ones in digital adoption - a gap that constrains their growth and market reach. Source: World Bank (2022) →
- Poor software quality cost the US economy an estimated $2.41 trillion in 2022, including roughly $1.52 trillion in accumulated technical debt, driven partly by unsuccessful development projects and low-quality legacy systems. Source: Consortium for Information & Software Quality (CISQ) - Herb Krasner (2022) →
Frequently asked questions
What does it cost to move off our current ESG platform?
In the recommended hybrid you do not move off the disclosure platform at all, which removes most of the switching cost. What migrates is the underlying data and the evidence, and that is bounded by how much history you choose to carry.
The genuine switching cost is your own finance team's time assembling the complete list of legal entities, sites, meters and leases. Almost no group has that written down in one place, and it is the task that most often runs long.
What if our reporting platform changes its pricing or module packaging?
Model it at the site, entity and framework count you expect in three years, because pricing in this category commonly scales with all three. Then add consultant fees for the parts the platform does not cover, which are frequently larger than the subscription.
The more useful question is whether repricing changes anything operationally. If your team already runs the real process in Excel and uses the platform to store the answer, you are paying for storage and a price change is a good moment to say so out loud.
How long does the first release take, and when should we start it?
Twelve to eighteen weeks, and start at least one full reporting cycle before the period you intend to report on so a parallel run is possible. The item that most often extends the schedule is not engineering.
It is assembling the entity, site, meter and lease register, because it is a reconciliation exercise with your finance team rather than a data entry job. Doing that work before kickoff converts the biggest schedule risk into an ordinary accounting task.
Is Workiva enough if our only real problem is the disclosure document?
Yes, and buying is the correct call. Workiva handles document assembly, drafting control and sign off well, and rebuilding that is not a sensible use of capital.
The limit is upstream rather than inside the document. It cannot know which entity owns which meter, which lease bundles utilities into a service charge, or which site controller answers email in a reporting week. When the real process still runs in a spreadsheet beside it, the gap is collection, not drafting.
What does adding a second reporting framework cost?
A mapping layer is $22,000 to $42,000 in the build and $15,000 to $40,000 for each framework added afterwards, provided you modelled each data point once. That is the whole cost argument in this category: collect once, map many.
The expensive alternative is running a separate collection per regime, which multiplies your collection cost by the number of regimes and produces sets of numbers that disagree. A customer questionnaire and a statutory statement should draw from the same store.
What happens to our published numbers when we acquire or divest?
You need an effective dated entity and site register carrying ownership percentage, consolidation approach and operational control over time, so any period can be reported as published or restated on the current perimeter.
Base year recalculation then becomes a rule applied against a threshold rather than a manual reconstruction. Budget $8,000 to $25,000 per acquired business for onboarding new entities, sites and meters and running the recalculation.
Will building reduce our assurance fee?
It reduces the risk of the fee rising, which is the more honest claim. An assurance provider picks a disclosed figure and walks backwards to the source document, the calculation applied and the approvals that let it into the statement.
Engagements expand in scope, and cost, when the first few samples cannot be traced. Confirm expectations with your own provider early, and treat avoided scope expansion as a real saving rather than a soft one.
Who owns the evidence archive if an agency builds this?
You should own the repository, the cloud accounts and the full document archive, written into the contract before kickoff. At Digital Heroes the client owns everything from the first commit.
The archive matters more than the code here. Evidence behind a figure you publish this year may be requested several years later, so it has to outlive your software vendor and probably your current framework. Test a full export during the build, not when you need it.
How long does it take to build a custom BI dashboard?
A working first version usually ships in 4 to 8 weeks, and a full production build with multiple integrations and permissions takes 3 to 6 months. In Digital Heroes delivery experience, schedules slip on data access, meaning credentials, API approvals, and cleanup of source data, far more often than on the dashboard screens themselves. Lining up access to every data source before kickoff routinely saves 2 to 3 weeks.
Can one dashboard pull from QuickBooks, Salesforce, and Google Analytics at the same time?
Yes, and combining sources like that is the main reason to build custom instead of living inside each tool's built-in reports. The standard pattern syncs each source into one warehouse using connectors such as Fivetran or Airbyte, then joins them there, so marketing spend, pipeline, and revenue finally sit in a single view. Each additional source typically adds 1 to 2 weeks to the build, mostly for field mapping and reconciliation.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
We already pay for Microsoft 365. When does building custom actually beat Power BI?
Keep Power BI for internal reporting; at $14 per user per month for Pro it is hard to beat for employee-facing analytics. Custom wins in three cases: you are showing dashboards to customers, since embedded Power BI is priced on capacity and gets expensive fast, you need a fully white-labeled experience inside your own product, or your team keeps fighting the tool to support a specific workflow. Most companies we build for keep Power BI internally even after launching a custom customer-facing dashboard.
Do I need a data warehouse before building a custom dashboard?
Not for a small build; a dashboard reading from 1 or 2 sources can query them directly or use a plain Postgres database as its store. You want a real warehouse like BigQuery or Snowflake once you are joining 3 or more sources, keeping history beyond what source systems retain, or serving many concurrent users. Adding the warehouse costs around 2 to 4 extra weeks and is usually the single best investment in the project's future.
Who can build a custom business intelligence dashboards system?
Digital Heroes builds custom business intelligence dashboards systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other business intelligence dashboards companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Maya.
Office Manager · Sydney · Sydney · 2 posts on the site
Published · Last updated .
