Green Goods
A reporting and funding platform for regenerative communities turning local work into trusted evidence and capital
Problem
Regenerative work is not only planting trees. It can mean keeping a solar hub running, tracking waste recovery, restoring agroforestry systems, or teaching people how to steward a shared space. The evidence for that work is usually scattered across phones, chats, spreadsheets, and memory. At the same time, many impact reporting tools keep records inside isolated platforms that are hard for local teams to access and hard for funders to verify. The result is a gap between people doing credible work and the capital that could support them. Green Goods connects evidence, review, reporting, direct support, and local endowments so communities can prove progress and funders can allocate with more context and confidence.
Architecture
Green Goods has three main product surfaces: a public web app for discovery, evidence, and funding; an installed client PWA for field submissions; and an admin dashboard for operator review, assessments, roles, action catalogs, and capital flows. Those surfaces run on Arbitrum, a layer two network on Ethereum, where attestations record work, approvals, and assessments, while smart contracts manage garden accounts, permissions, actions, and funding modules. Indexers turn that protocol activity back into usable app data. On the capital side, gardens can receive direct support or endowment deposits, giving funders a withdrawable position while routed yield supports operations, contributor compensation, and future community work.
Development
Green Goods is being developed as both a product and a methodology system. The work is not just building screens or contracts; it is translating solar, agroforestry, waste, and education projects into evidence flows that people can use in the field and funders can understand. My role spans product leadership and core engineering across the client PWA, public web app, admin workflows, documentation, onboarding, and support. A lot of the work is turning community research and operator feedback into action definitions, review patterns, funding pathways, and guidance that are practical enough for real teams to keep using. The hard part is that each context needs different evidence: solar teams may need uptime and maintenance records, waste teams may need kilograms diverted, agroforestry teams may need planting and survival checks, and education teams may need attendance, curriculum, and learning signals.
Green Goods is one of the main products I steward through the Greenpill ecosystem, so the technical work and community work feed into each other.
Learnings
Building from the ground up with a distributed, grant funded team has taught me how much product work is coordination work. Funding is uneven, contributors are global, and many people put in hours that are not fully compensated, so the architecture has to respect human capacity as much as technical correctness. The lesson is to keep the stack practical, keep the methodology close to communities, and build proof systems that people can actually understand, operate, and sustain.