Proof from real builds, with the business context still visible.
This page is not a gallery of random screenshots. It is a closer look at what was weak before, what changed in the system, and why the output mattered to the team or the business after launch.
production systems
live demos available
documented case studies
before/after proof points
shipping window
Business context first
Each project is framed around the operational or conversion problem, not just the tech stack.
Before versus after
The strongest proof is not visual polish alone, but the shift in speed, clarity, or workflow friction.
Real usage matters
These are meant to show what changed when the build was actually used in day-to-day work.
A case study worth scanning first
Start here if you want the fastest picture of how nasaq.id frames operational pain, turns it into a system, and then measures the change.
Serat QC — Selisih Berat J&T Express
A clear example of how a repetitive field workflow was turned into a much faster, auditable system.
Challenge
Tim operasional J&T Express harus memverifikasi selisih berat paket setiap hari. Setiap resi membutuhkan 2 foto bukti yang harus di-rename manual satu per satu dengan format tertentu (nomor resi + keterangan). Rata-rata 500 resi dan 1.000 foto per hari.
Waktu per 500 resi
Before
4-5 jam
After
< 30 menit
Rename foto
Before
Manual 1 per 1
After
Otomatis via barcode scan
Total data diproses
Before
Scattered di folder lokal
After
80.187 resi & 160.374 foto terpusat
Browse each case by the kind of problem it solved
Each card below keeps the business problem visible, so the page reads more like proof and less like a portfolio catalog.
If one of these problems feels familiar, the next step is not guessing.
Bring the current bottleneck, the team reality, and the target outcome. The first job is to narrow the right scope, not to sell the largest build by default.