How GRADIENT BUILDERS works: from a community need to deployment
We explain the model: why we do not hand out money for other people’s projects but assemble teams around a specific task.
We published the statute and internal policies in their entirety, not as extracts. Why do this before the first grant.
We published the statute and five internal policies in full. Not as extracts, not "available on request", not a two-page scan.
The usual sequence runs the other way: an organisation receives money first, then a donor asks to see the policies, and they are written in a week to match that specific requirement. Such documents describe not how the organisation works, but what the donor wanted to read.
We did the reverse. The rules were written before the money existed, so they were not tailored to anyone. It also means anybody can hold us to our own documents.
The statute was approved by the General Meeting in a new edition. The policies are approved by the Board and reviewed at least once a year, or earlier if legislation or donor requirements change.
The policies apply to everyone acting on behalf of the organisation: members of the Meeting and the Board, the Supervisory Board, staff, team members, mentors, volunteers and contractors. For contractors the obligations are written into the contract rather than left as a declaration on the website.
All of them are on the Policies page.
We explain the model: why we do not hand out money for other people’s projects but assemble teams around a specific task.
Before building technology for veterans, we want to hear the people we are building for. The survey is anonymous.
The statute and five policies are published in full — not as extracts and not on request.