FOR NGOS & PUBLIC-SECTOR ORGS

We build for organizations that markets ignore.

Your organization serves people no SaaS company will build for. You have a bottleneck AI could fix. Tell us. We scope, build, and ship for free.

Who we work with

We work with NGOs, public-sector teams, and social enterprises in Malaysia and Southeast Asia. We have shipped for Pocket of Pink and are scoping work with food banks, refugee legal aid clinics, and government translation teams.

We prioritize partners who

+

Serve communities the private market does not — B40 households, refugees, undocumented workers, smallholder farmers, people with disabilities, linguistic minorities.

+

Have a real operational bottleneck — not a “we want a chatbot” hunch.

+

Are willing to work in the open: the tool we build for you will be MIT-licensed, so the next NGO with a similar problem can fork it.

+

Can commit one staff member to scope and test the build with us. We do not do drive-by software charity. The tool only works if your team co-owns it.

What good problems look like

The projects that work have a specific shape: a recurring cost, a clear scope, and a codebase another NGO can reuse.

Examples we would say yes to

Our team spends 12 hours a week manually translating intake forms.

Our intake forms are English-only but our beneficiaries speak five languages.

We have ten years of case files in PDFs and we cannot search them.

We need to track every food bank in the country and there is no central registry.

Examples we would say no to

Build us a full CRM

Too broad, already exists — buy don't build.

We want to fundraise using AI

Not our remit; talk to a fundraising consultant.

We need a one-off marketing video

Not what builders are for.

How it works

Five steps. No surprises.

01

You tell us about the problem.

A 20-minute scoping call, no commitment. We will tell you honestly if a build is the right fix or if you should buy something instead.

02

We co-scope a v1.

Together, in writing. We define what shipping looks like, what the smallest useful version is, and who from your team will work with us.

03

A team forms.

From our volunteer community. Typically 2–4 builders, with a named lead engineer responsible for delivery.

04

We ship in 4–8 weeks.

With your team testing and giving feedback throughout. The codebase is yours; we co-own the README.

05

We hand it over.

Documentation, deployment, a training session for your team. Open source on GitHub under our org. Maintenance falls to you, but we stay reachable for fixes and v2 conversations.

What we have shipped

Real partners, real outcomes.

NGO WE HELPED

Pocket of Pink

Visit Website →

Youth education nonprofit — we helped ship their website in a single day using AI.

OPEN DATA PROJECT

AI Adoption by Country

Live API →

Interactive visualization + open data API tracking AI adoption across 16 countries. From UAE at 64% to Nigeria at 7%. Data sourced from Microsoft, Stanford HAI, OECD, and 11 other authoritative sources.

More in active scoping.

If you want to see in-progress work, ask.

Get in touch

Tell us briefly:

1.

What your organization does and who you serve.

2.

The specific problem — one paragraph is enough.

3.

How much staff time it currently costs per week.

4.

Whether you have someone who could work with us for 4–8 weeks.

We respond within a week. If we cannot take on the build ourselves, we will try to refer you to someone who can.