The phrase good AI gets used by everyone who wants the credit without the work. We would rather show what it means in a build than argue about the words.
The phrase belongs to a UN platform.
AI for good is a movement run by a UN agency. The International Telecommunication Union, a United Nations agency, has run the AI for Good platform since 2017, with dozens of UN agencies and tens of thousands of contributors behind it. We are a small Australian studio and do not speak for that. What we do instead is build the actual software a specific organisation uses to do a specific piece of environmental work.
So this is not a claim on the phrase. It is a position on the practice. Here is what we think good AI looks like in working software.
It is built with the people it serves.
The fastest way to build bad software for a cause is to build it from the outside, guessing at the need. Good AI starts from the specific thing the people need. A conservation collective needs the count of trees to be accurate. A volunteer treasurer needs the dues to arrive without a developer. You find that thing first, with the people who need it, and build from there.
This is why the credit on every client property we build reads built with Ecodia, not by. With makes the organisation the maker and us the partner, which is what the relationship actually is. The word choice is small and deliberate.
It is honest about what it cannot do.
Generic AI asserts. It fills a confident paragraph whether or not the number underneath is true. Our posture is the opposite: every figure we publish is cited to the database it came from, and where an outcome is not yet quantified we say so plainly rather than round it up. The impact page carries the source note on every tile for exactly this reason, and the way we measure impact is built so a number cannot be published unless it is true.
Every number we publish can be checked against the source it came from.
It asks before it acts.
An AI that can do things in the world has to answer to the person it works for. In Friend, our AI companion, an approval gate sits in front of anything consequential: the companion explains what it is about to do, in plain language, and waits for a yes. Consent is not a hidden setting. Every consequential action goes through that gate.
The AI is built in from the start.
There is a clear difference between software built AI-native from the first commit and a chatbot bolted onto a product that was finished before AI existed. One is load-bearing; the other is a widget. We only build the first kind, and we wrote down why the distinction matters.
None of this is a manifesto for later. It describes how the work already gets made. To see it rather than read about it, the case studies are the proof.