WC Check — Toilet Inspection System
Production toilet inspection system: 3.293 inspeksi, 53 users, 49 lokasi. Client bayar 12-month subscription — revenue locked in. QR code + real-time analytics.
Context
A monitoring system built to replace paper-based inspection and make reporting visible in real time.
Project at a glance
Sistem monitoring kebersihan toilet berbasis web untuk Proservice Indonesia. Problem: inspeksi toilet manual pakai form kertas — hilang/rusak, tidak ada data historis, tidak bisa monitor real-time. Solution: QR-code scanning per lokasi, 11-component checklist, photo documentation, dan real-time dashboard. 3.293 inspeksi tercatat, 53 users (14 aktif mingguan), 49 lokasi. Client locked in 12-month subscription.
What this case helps prove
The challenge
Inspeksi kebersihan toilet dilakukan manual dengan form kertas, tidak ada monitoring real-time
The response
Web-based inspection system dengan QR code, photo documentation, dan real-time dashboard
Why it mattered
12-month subscription locked in — client retention 100%
Before and after, in clearer terms
The point of this section is not decoration. It is to show the operational shift in terms the client team can immediately recognize.
Inspeksi per hari
Before
5-10 inspeksi (form kertas)
After
20-30 inspeksi (scan QR + checklist)
Laporan
Before
Manual kumpulkan form, input ke Excel
After
Auto-generate dashboard real-time
Data historis
Before
Tidak ada (form hilang/rusak)
After
3.293 inspeksi tercatat, searchable
“Sekarang tinggal scan QR, checklist, foto, selesai. Laporan langsung masuk dashboard.”
Koordinator Lapangan
Tim Inspeksi
Key highlights of the build
3.293 Inspections
Total inspeksi tercatat di production — terus bertambah harian
53 Users & 49 Lokasi
14 active users mingguan mengelola 49 titik inspeksi
QR Code + Real-time
Scan QR per lokasi, dashboard analytics langsung update
Impact that stayed visible
What the system includes
Technology stack
Frontend
Backend & Database
Services & Tools
If this kind of operational shift is what you need, start from the problem.
The fastest useful next step is not asking for a random feature list. It is clarifying what feels weak today, what friction the team still carries, and what a cleaner first version should solve.