Focused DMA or full enterprise suite?

Only if you need all of what it covers. Enterprise ESG suites price the full bundle — DMA + carbon + reporting + supply chain + climate risk — even if you only use part of it. Organisations that already have carbon accounting in a dedicated tool (e.g. Sweep, Persefoni, Plan A, Normative), or that outsource iXBRL tagging to their auditor, end up paying for capabilities they don’t use.

Modularity matters: being able to choose a focused DMA platform and integrate it with carbon accounting from another vendor is often both cheaper and better, because best-of-breed tools tend to outperform bundled modules.

Genuine use cases: (1) you need end-to-end automation from activity-data ingestion through iXBRL-tagged ESEF output as a single workflow; (2) you have the budget and governance to support a six- or seven-figure annual contract; (3) your organisation benefits from a single sustainability-reporting vendor for procurement or vendor-risk reasons; (4) you have no existing carbon accounting infrastructure and want one vendor to solve everything.

If most of these apply, an enterprise suite is genuinely the right tool. For the many organisations where only one or two apply, a focused DMA platform plus best-of-breed tools for carbon / supply chain is the more efficient architecture.

Yes. A common pattern: the enterprise suite handles carbon accounting, supply chain and reporting automation; the DMA sits in our platform because of workflow depth, auditor collaboration features and cost. Data export via CSV or JSON supports integration either direction. No lock-in either way.

Deliberate scope decision. Carbon accounting is a separate discipline — activity data ingestion, emission factor libraries, verification methodology — and best-of-breed dedicated tools already exist for it. Building a thin carbon module into a DMA platform would dilute both. We’d rather do DMA deeply and integrate cleanly with dedicated carbon tools than build a shallow imitation of both.

If your organisation needs a single-vendor solution, an enterprise suite is the right answer. If you can run best-of-breed across categories, the DMA platform + a dedicated carbon tool is almost always the better architecture.

We support CSV and JSON import from standard DMA data structures. The practical friction is usually contractual, not technical — enterprise contracts often have multi-year commitments. Many organisations start by running the GIG platform as a parallel workspace for year 1’s DMA while the enterprise contract runs out, then consolidate onto the cheaper, more focused tool in year 2.