Product Owner and Thesis Project Lead, Digital Touchpoint for KSP Arthaguna
Grobogan (Purwodadi), Central Java – 2024

KSP Arthaguna: a thesis project built around a real member-service problem

KSP Arthaguna is a savings and loan cooperative, a Koperasi Simpan Pinjam, serving members around Grobogan, Central Java. This project started as an undergraduate thesis at Universitas Gadjah Mada. It centered on one question: how does a cooperative like this extend its member service beyond the branch counter? The goal was to do that without losing the relationship-based support members already relied on.

Rather than treat the answer as a single app, the KSP Arthaguna project got scoped as a full digital touchpoint system. It included a member-facing mobile app, a public information layer, and a backoffice layer for staff. A shared data model connected all three. So did an omnichannel flow, one that always assumed a member might still walk into a branch or call a relationship manager.

What the KSP Arthaguna work involved

• Mobile touchpoint design: Planned and designed a member-facing mobile app. It covered service information, profile context, service routing, and a loyalty or points layer members could track.
• Public information layer: Defined a website and public information layer. It covered the institution’s profile, product information, and a clear contact and support route for members.
• Backoffice and data model: Designed a backoffice layer for staff, covering record handling, member support visibility, and service status. A structured data model backed all of it, for members, products, services, and activity.
• Omnichannel service strategy: Mapped the full path a member might take. It started with social or web discovery, moved into the app, continued through support contact, and often ended back at an offline branch or relationship manager when a human conversation was still the better answer.
• Thesis documentation and testing: Backed the product work with implementation notes, testing evidence, and documentation. A thesis committee at UGM needed all of it to evaluate the KSP Arthaguna project on its own terms.

Why the offline branch never left the plan

It would have been easy to design this as a pure app-first product and treat the branch as legacy. That was never the brief. A cooperative like this runs on relationships between members and the staff who already know them. Consequently, a mobile touchpoint that ignored those relationships would have solved the wrong problem. Instead, the harder, more useful version of this KSP Arthaguna project built a digital layer that made the branch and the relationship manager easier to reach, not a replacement for either.

This KSP Arthaguna project sits alongside other product and systems work built around real operational problems rather than polished briefs. Therefore, reach out anytime via the contact page to talk through the thesis, the product thinking behind it, or what a similar touchpoint system could look like elsewhere.