# Partner or volunteer: who should apply When to apply as a nonprofit partner, when as a volunteer, and when both are wrong. Kode Nirlaba filter without fluff. > Reviewed 2026-08-13. Source: https://kodenirlaba.org/en/guides/partner-or-volunteer/ [Kode Nirlaba](/en/) / [Guides](/en/guides/) / Partner or volunteer: who should apply Guides Partner or volunteer — pick the right lane Updated 2026-08-13 · Kaiser Khan Short answer Reviewed 2026-08-13 Should you apply as a partner or as a volunteer? Partner if you represent an Indonesian nonprofit blocked by its systems. Volunteer if you will ship technical or operational work. Do not do both as a tactic “so someone reads it.” Companies, paid-internship hunters, and people who attach beneficiary data to the first email should not apply at all. Who should skip this page Not for agencies placing clients, not for students who need a letter in seven days, not for donors who want a logo. What is the quick test before you open the form? Three questions: is it a nonprofit operating in Indonesia, is the problem a repeated operational one, and can you name the person who will use the system every week. If all three are yes, the partner lane. If you are an individual with skill and time, the volunteer lane. If you want a “brand collaboration,” there is no lane. The eligibility tool asks the same things interactively. The contact form does not replace honesty in that test. When should a partner be declined even if the mission is beautiful? When an off-the-shelf tool already fits, when there is no data owner, when the deadline is next week’s event, or when the board will not use the result. A beautiful mission does not fix a missing workflow. Declining here protects capacity for organisations that are actually blocked. We will write the reason. If the reason is “use a spreadsheet first,” that is not an insult. It is the same verdict as the custom-versus-ready guide. When should a volunteer be declined even with a fancy CV? When they cannot finish a slice of work without daily supervision, when what they want is a speculative rebrand, or when they treat beneficiary data as portfolio material. A CV from a famous company is not proof you can work with a yayasan chair in a chat group. We pick people who finish, not people who are famous. Indonesian-speaking volunteers have an edge in staff training. That is a use test, not a loyalty test. Can one person be both partner and volunteer? Rarely. Conflict appears when the same person ships the work and represents the organisation that uses it without a separation. If you are a yayasan founder who is also an engineer, say so. We may still help, but the decision channel must be written. Do not disguise a personal project as a nonprofit partnership. Conflict transparency matters more than the number of roles. Hide the conflict, and we stop. What happens after you submit the form? We read, sometimes ask, then accept into scoping or decline with a reason. There is no instant support ticket. We aim to reply in several working days. If ten days pass with silence, email again. Do not send someone else’s identity data as “context.” Acceptance into scoping is not a guarantee we will build. Scoping can end with “use an off-the-shelf tool.” That is a valid outcome. How does an independent person use the partner lane, not volunteer? Choose partner or “independent changemaker” on the form if you want us to build a system for your mission. Choose volunteer if you will ship code into this project. Ticking both so “someone reads it” is a bad signal. An individual still has to describe the repeated workflow and who the human backup is after launch. Partner-as-person example: someone running a public-information initiative in Indonesia who copies data into three spreadsheets every week. Volunteer example: an engineer who wants to patch that site after we — or instead of us — refuse to rebuild a tool that already fits. If your initiative has no real users yet, wait. We do not build speculation. Mohsin also looks for changemakers with an operational need, not a deck of ideas. What may and may not be in the first email? Allowed: the mission in six sentences, the repeated workflow, who will use the system every week, and whether you are a person or an organisation. Not allowed: ID cards, beneficiary lists, health data, or a spreadsheet of children. A first email that attaches someone else’s identity fails the filter before we read the mission. That is a test, not cruelty. If the email client does not open from the form, copy the body to hello@kodenirlaba.org. Do not send three times with attachments “so it is complete.” One clean thread is easier to review. Students who need a letter in seven days with no slice of work are still declined, whether as volunteers or as a “campus partner.” Which questions remain after the verdict? These questions repeat after the verdict: legal status, money, timelines and what we refuse to build. Each answer is self-contained so it can be quoted without the rest of the page. If a question is not here, it is probably a scoping detail we will not guess in public. Can students volunteer for course credit? Only if the lecturer and we agree a slice of work that will actually ship. A letter in seven days with no work is not a product we make. What should you read next? Continue with another decision guide, then the matching interactive tool, then apply only if the filter still passes. Do not send beneficiary data with the form. If a free tool already fits, stop here — that is a successful reading of this guide. - [Custom vs off-the-shelf for nonprofits](/en/guides/custom-vs-off-the-shelf/)- [Indonesia PDP law for NGOs](/en/guides/pdp-law-for-ngos/)- [Digitising a yayasan: sequence, not apps](/en/guides/digitising-a-yayasan/) - [Custom or ready tool](/en/tools/custom-or-ready/) - [Partnership check](/en/tools/partnership-check/) - [Request a partnership](/en/contact/)