Guides
Decision guides: custom vs off-the-shelf, PDP law, digitising a yayasan, partner or volunteer, donation records. Verdicts that say skip.
Start with custom versus off-the-shelf if you think you need software. Read the PDP-law guide before storing identity data. Use partner-or-volunteer before you apply. Skip the hub if you only wanted a brochure site — none of these guides will recommend one.
Usually not. Start with off-the-shelf tools you already have, and build custom only if staff copy data into three places or sensitive data sits in personal accounts. Kode Nirlaba will refuse to rebuild a spreadsheet, form or inbox that already fits. Skip this guide if you already want a paid consumer app.
Treat beneficiary data as personal data, not as group-chat content. Cut ID-card copies, lock permissions, name the person who answers requests, and do not build a new system if you cannot delete. This is a practical reading of Law No. 27 of 2022, not legal advice. Your lawyer decides compliance.
The order is: organisation domain and email, permissioned folders, one source list, then automation. Custom apps come last, or not at all. Skip this if you want a paid “digital transformation” package. A yayasan without domain email is not ready for custom software.
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.
Often not. What you need is a record that matches the bank, a thank-you that does not spray data, and a board report that was not copied overnight. A custom payment gateway is almost always the wrong first step. Skip this if you want a “crowdfunding platform” to resell. We are not a money intermediary.