How we build foundation tools and vendor packs
Programme: Tools and packs for NGOs. This is not Talent Map - that track is for people; this one is reusable tooling.
Playbook
Need → a small foundation MVP → a multi-site pilot → KPIs → optional commercialisation outside the grant territory. The foundation stays a social partner; another NGO keeps its brand.
The stack that is actually running
A static site (Hugo), CI and Pages (GitLab), relative URLs, forms at an external provider, graphics in one visual language (low-poly, no photorealism and no children’s faces on programme cards). Project cards come from a shared source - not from private correspondence.
A vendor pack
For each vendor we want the same set: scope and what is out of scope; an organisation account, not a private one; GDPR/DPA; renewal; an exit (data export, no lock-in). Types: MOU, LOI, licence, pilot, DPA. The website describes types; it does not paste the full contract.
Cloud and model credits
Accelerator programmes (AWS Activate, Microsoft for Startups, Google Cloud credits including Gemini, Claude API, others) are often for companies. The foundation takes the nonprofit path first (TechSoup, GitLab/GitHub Nonprofit, Google for Nonprofits, Cloudflare). Large credits belong to a company or an investor partner - we do not pretend to be YC.
Roles
- someone at an NGO implementing the checklist,
- a vendor with a nonprofit programme,
- a documentation volunteer,
- an ops/web intern.
We publish names only with consent.
How to join
The pack or vendor form or Get involved.