In This Article
Buy an ESG platform or build your own tools? Who should absorb each kind of change, when a hybrid wins, and how to test the choice before you sign.
Last updated
Build or buy sustainability software? When each one wins
The rules that sustainability software is built to follow moved fast in the past year. The EU's amendments to the CSRD, in force since 18 March 2026, cut the number of companies required to report by about 85%, and the Commission adopted revised reporting standards that July. California moved its first SB 253 reporting deadline from August 10 to November 10, 2026. The GHG Protocol is rewriting its 2015 Scope 2 Guidance after a consultation that drew nearly 1,100 responses from 56 countries.
Buy a sustainability platform for work that must follow a published standard and keep pace with its changes. Build custom tools for work that encodes your own judgment, serves people outside your organization or has no product that fits. Most organizations with a distinctive program end up with both: buy the ledger, build the edge.
We sit on both sides of this decision. Council Fire advises companies, NGOs, foundations and public agencies, and has been a certified B Corp since 2010. Through Council Fire Labs we also build software, including the free tools on this site and two platforms: Aptation for climate resilience and Trovance for AI search visibility. Building our own has made us more careful about recommending custom builds, not less.
Our free tools taught us the lesson in both directions. In September 2026 we found that every free tool we had embedded on this site from a third-party widget service had stopped loading. We retired most of them and rebuilt the few worth keeping, among them the Climate Risk Lookup and the Stakeholder Engagement Scorecard, on our own code with published, sourced data. Anything public that carries your name should run on something you control, and most tools are not worth maintaining at all.
What are you really deciding when you build or buy?
You are deciding who absorbs change. A sustainability tool faces two kinds. Standards change on someone else's schedule, whether the rulebook is written in Brussels or Sacramento. Your program changes whenever your strategy, your partners or your board do.
A vendor spreads the cost of the first kind across every customer it has. Nobody outside your organization will prioritize the second. That asymmetry, more than features or price, should decide which parts you buy and which you build.
Launch is the cheap part either way. The U.S. federal government spends more than $100 billion a year on IT, and agencies report spending about 80% of it operating and maintaining systems they already have. Your ratio will differ, but the shape holds: a custom tool is a maintenance commitment that starts the day it ships, and a platform is a subscription that never stops.
Custom builds also carry more risk than their budgets admit. In a peer-reviewed analysis of 5,392 IT projects, cost overruns followed a power law: most projects overran a little, and a smaller number overran to an extreme. Scope small and ship early.
Layer of the work | Examples | Usually | Who this is for | Risk to avoid |
|---|---|---|---|---|
The ledger: numbers bound to a published standard | A GHG inventory, ESRS datapoints, an SB 253 report | Buy | Companies in scope of the CSRD, SB 253 or ISSB-based rules | Building an engine you must re-map every time the standard moves |
The network: data exchanged with outside parties | Supplier questionnaires, CDP responses | Buy, or join the network | Companies with large supplier bases | A portal your suppliers will not log in to |
The logic: your own judgment | Supplier or grantee scorecards, materiality weights, project rankings | Build, or configure in the open | Teams whose method is their edge | Buying a score that encodes someone else's method |
The edge: tools people outside your staff use | Public calculators, grantee portals, partner dashboards | Build or own | NGOs, foundations and brands with public tools | Licenses priced for staff, paid for occasional outside users |
The glue: moving data between systems | Scheduled exports, imports, reconciliations | Build small | Any team with two systems that disagree | A platform-wide integration project to fix one feed |
Who this is for: sustainability leads and program directors who already know which decision the tool supports. If you do not yet, start with our guide to choosing sustainability software, which compares buying, configuring, building and changing the process.
When should you buy a sustainability platform?
Buy when the work is bound to a standard, runs through a network or has no owner on your team. Each of those is a reason to let a vendor carry the weight.
When the work must match a published standard
For companies in scope, that describes most of corporate disclosure. The amended CSRD now reaches EU companies with more than 1,000 employees and over €450 million in net turnover, and California's SB 253 covers U.S. companies with more than $1 billion in revenue that do business in the state, with Scope 3 reporting due from 2027. Further afield, more than 45 jurisdictions are using ISSB Standards, and companies in 18 jurisdictions will be issuing reports by 2027.
These rules change, and a well-maintained platform absorbs each change once, for every customer. Companies that first reported under the ESRS in 2025 now face revised standards the Commission adopted in July 2026, written to remove the least important datapoints and to separate mandatory datapoints from voluntary ones. On a custom data model, that remapping is your project. On a platform it should be the vendor's next release, so ask to see the release notes for the last rule change before you sign.
When the work runs through a network
Companies reporting to CDP put their supply chain emissions at 26 times their operational emissions on average, and almost 45,000 suppliers were asked to disclose through its supply chain program in 2025. Your suppliers already answer requests in the formats those networks use, and a custom portal asks them to learn one more. Our Scope 3 measurement guide covers the data work that no portal does for you.
When nobody on your team can own a system
A platform with a named administrator beats a custom tool with no owner almost every time. If the person who would run a custom build is also the person writing the sustainability report, buy.
Who this is for: corporate sustainability leads facing a mandatory, assured disclosure or a large supplier base. If that is you, buy the ledger and put your effort into the ESG data management behind it and the assurance your auditor will ask for. Our explainer on the CSRD and CSDDD after the omnibus and our ISSB implementation guide cover the rules themselves.
When does a custom build win?
Build when the logic, the users or the workflow are yours alone. Those are the places where no vendor will follow your changes as fast as you need.
When the logic is your judgment
Scores and ratings are methods, and methods disagree. In a peer-reviewed comparison of six major ESG rating agencies, correlations between their ratings ranged from 0.38 to 0.71, and differences in measurement explained 56% of the divergence. A score you buy is a method you adopt. When the method is your edge, as with a supplier scorecard or a project ranking, own the logic and publish the weights.
When the users are outside your organization
Grantees, residents, suppliers and partners use a tool a few times a year and will not learn a platform to do it. A narrow tool built for their one task does better. Our Stakeholder Engagement Scorecard is an example: it takes about five minutes and ends with your three biggest gaps, scored against 12 statements built on AA1000SES and the IAP2 Spectrum.
When no product fits the workflow
That is how Aptation began. On the Annapolis Maritime Resilience Initiative, where Council Fire was an implementation and stakeholder engagement partner, the Resilience Authority of Annapolis and Anne Arundel County needed one record to carry projects from community-chosen criteria through funding to a public portfolio. CF Labs built that record with the Authority, and the platform is now ready to adapt for other jurisdictions.
When the job is small and stable
A calculator or a single review queue can reach working software in weeks and be handed to the people who run it. A platform replacement cannot. And a custom tool that nobody owns after launch is worse than the spreadsheet it replaced.
Who this is for: NGO and foundation program leads, and corporate teams whose program is distinctive enough that no vendor would put it on a roadmap.
What does a hybrid look like in practice?
For most organizations with a real program, the answer is both: buy the ledger, build the edge. The platform holds the standard-bound numbers and the audit trail. Small tools you own sit at the edges, where your judgment and your stakeholders are.
Four patterns cover most of what we see:
- A platform plus a custom intake. The platform keeps the inventory; a short form collects facility or project data in the shape your people actually have it and feeds the platform on a schedule.
- A platform plus a decision layer. The platform reports what happened. A scorecard or ranking tool, with weights your leadership signed off, decides what to do next.
- A prototype, then a purchase. A few weeks of working software on your own data shows what you need before you write the RFP. Sometimes the prototype becomes the tool; more often it becomes a far better requirements document.
- A public tool on your own code. Anything stakeholders use with your name on it should run on something you control, even when everything behind it is bought.
The hinge in every hybrid is data access. Before you sign, ask the vendor to show a scheduled, documented export or API your own tools can read, and put the exit terms in writing. Our one-workflow build brief and custom software budget worksheet cover the custom side of that agreement.
Be clear about what neither route fixes. Since 2016 Council Fire has led the Net Gains Alliance, an effort to modernize the data systems behind fisheries management, where the usual obstacles are legacy systems, missing data standards, manual collection and resistance from the people asked to collect more. Choosing between building and buying solves none of those.
Who this is for: organizations that need a defensible ledger and a distinctive program at the same time, which describes many companies with a public climate commitment.
How should NGOs and foundations decide?
The same logic applies, with one difference: the people most affected by your software usually do not work for you.
Foundations: buy the grants system, build the learning layer
Grants management is a mature category. In the Technology Association of Grantmakers' 2024 survey of 355 foundations, just 3% used a custom grants management system, a share that has kept falling. Unless your grantmaking is unusual, a custom grants platform is a cost without a reason.
The learning layer is different. The questions a foundation asks about outcomes, partnerships and its theory of change are specific to its strategy, and tools built for grants administration are rarely designed around them. That is where a custom dashboard or a light data pipeline, fed by the grants system, earns its keep; our guide to metrics, monitoring and verification for foundations covers the method behind it.
Mind the grantee's side of the screen. In the Center for Effective Philanthropy's study of 61 funders, grantees reported a median of 15 hours on a funder's proposal process and six hours a year on its required reporting and evaluation, down from 20 and eight before the pandemic. Every field a new portal adds lands on that clock, so before you build one, audit which reporting questions you can stop asking.
NGOs: one view of impact for every funder
NGOs face the mirror image: several funders asking for the same outcomes in different formats. Buy the accounting system and the CRM, and build the one view of impact that your board and each funder can read, instead of rebuilding the same report for every one of them.
Who this is for: foundation program and operations leads weighing a grantee portal or an impact dashboard, and NGO leaders who report the same results to several funders. Council Fire works with foundations and nonprofits on the measurement design before anyone writes code.
How do you test the decision before you commit?
Put the decision on your own data before you put it in a contract. Five questions settle most cases:
- Which standard or rule must this work match, and who updates the tool when it changes?
- Whose judgment does the logic encode, and can you see and change the weights?
- Who uses it, and how often: staff every day, or partners twice a year?
- Can you get all your data out on a schedule, in a documented format, without a services contract?
- Who owns it in year three, and what will that cost?
Then run the cheapest real test. Ask each shortlisted vendor to work through one representative task on your records, including a missing value and a correction. If you are leaning toward a build, commission a short prototype on the same task and compare. Either way you will learn more in a few weeks than in a quarter of demos.
If AI is part of the proposal, test it the same way, with a named reviewer and a source trail for every output. Our AI sustainability reporting pilot checklist sets out the acceptance tests.
Frequently asked questions
01Should we build or buy sustainability software?
Buy sustainability software for work bound to a published standard, such as a greenhouse gas inventory or a CSRD disclosure, because a vendor absorbs rule changes for every customer; the amended CSRD took effect on 18 March 2026. Build for work that encodes your own judgment or serves outside users. Most organizations need both.
02Is it cheaper to build custom sustainability tools than to buy a platform?
Rarely over the life of the tool. Most software cost arrives after launch: U.S. federal agencies report spending about 80% of their IT budgets operating and maintaining existing systems. A narrow custom tool can cost less than an enterprise license, but only if you budget for hosting, fixes and changes; our budget worksheet lists them.
03What is a hybrid approach to sustainability software?
A hybrid buys a platform for standard-bound records, such as emissions inventories and disclosures, and builds small tools around it for intake, scoring, partner dashboards or public calculators. It works only if the platform exports your data on a schedule, so test the export before signing. Our one-workflow build brief scopes the custom piece.
04When does a custom tool make sense for a nonprofit or foundation?
When it serves your strategy rather than administration: an outcomes dashboard, a grantee scorecard or a public calculator. Buy the grants management system instead; only 3% of foundations in TAG's 2024 survey used a custom one. Then build the learning layer the grants system feeds, after a grant reporting audit.
05How do changing regulations affect the build or buy decision?
They favor buying your sustainability software's calculation layer. In 2026 the EU cut the companies in CSRD scope by about 85% and revised its reporting standards, and California moved its first SB 253 deadline to November 10, 2026. A vendor updates once for every customer; a custom engine makes you the maintainer. Our omnibus explainer covers the EU side.
06Can AI replace a sustainability software platform?
Not for standard-bound reporting. AI can draft and summarize, but a disclosure still needs traceable sources, a method that matches the standard and a person who signs off. Use AI inside a tool with a review step: in Aptation, our resilience platform, AI drafts scores and staff confirm every one. Our AI pilot checklist shows how to test it.
07Who should own a custom sustainability tool after launch?
A named business owner who decides what the tool's outputs mean, plus a technical operator, inside your team or contracted, who keeps it running. Without both, buy sustainability software rather than build it. Council Fire Labs either hosts what it builds or hands it over with documentation and training, and that choice belongs in the contract from the start.
Related Resources
Choosing and scoping software
- How to choose sustainability software: buy, configure or build?: the decision matrix to use before this one.
- Before you commission sustainability software: write a one-workflow build brief: scope the custom piece of a hybrid.
- What drives the cost of custom sustainability software?: a budget worksheet for buyers.
- Custom sustainability software development: what Council Fire Labs builds, and how a build starts.
- Build or buy climate resilience planning tools?: the same decision for local governments' resilience portfolios.
- AI sustainability reporting: a pilot acceptance checklist: the review discipline AI features need.
- Sustainability data and technology guides: the library's data and tooling guides.
The rules the ledger must follow
- CSRD & CSDDD after the omnibus: 2026 rules: what changed in Europe.
- California SB 253 guide: the U.S. emissions disclosure law most companies watch.
- GHG Protocol guide: the accounting standard behind most emissions engines.
- ISSB implementation guide: the global baseline many jurisdictions are adopting.
- ESG Data Management Guide: owners, sources and controls behind any platform.
Programs, grantees and proof
- Grant reporting: which questions can you stop asking?: cut the burden before you build a portal.
- Stakeholder Engagement Scorecard: a free tool we rebuilt on our own code.
- Climate Risk Lookup: FEMA risk ratings and plan status for any county.
- Net Gains Alliance: our work modernizing fisheries data systems.
- Council Fire Labs: the software and AI practice that builds our tools.
Bring one workflow, leave with a direction
Bring us the workflow you are weighing, whether a disclosure, a scorecard or a grantee portal, and the systems it touches. We will tell you what to buy, what to build and where the line between them sits, including when the answer is a product we do not make. If a build wins, Council Fire Labs' fixed-price Tool Sprint puts a working prototype on your own data in two to three weeks for $12,500. To start, talk to us on our contact page and choose Software & AI (CF Labs).
About the Author
George Chmael II is Council Fire's Founder & CEO. He has led the firm since its founding and through its B Corp certification in 2010. Council Fire's sustainable business practice helps companies, NGOs and foundations build sustainability programs that hold up, and Council Fire Labs builds the software that puts them to work.
FAQ