Case study · Coming soon
Founder MVP delivery
What this slot will hold: the initial brief, the scope agreed, what shipped, and what it changed — end to end, from first conversation to deployed product.
Independent Product Builder · Business Systems Analyst
From messy requirements to a working product.
I help founders and small product teams turn ambiguous business needs into practical systems and usable MVPs — requirements analysis, delivery leadership, and hands-on backend engineering, in one pair of hands.
01 — About
An editor’s answer to “what do you actually do?”
I work where business analysis meets software delivery: clarifying what a product must do, designing the system behind it, and building the backend that keeps it running.
I currently lead application development and build full-stack products at Aptaworks. Before that, I worked as a business analyst at Pertamina EP, a backend developer at OKEJOB, and a technology consultant on booking systems at Bukit Vista. Across those roles the constant has been the same: take a fuzzy, half-spoken need and return something people can actually use.
Working depth: Requirements analysis · Database design · Backend systems · Go · PHP / Laravel · Vue.js
Background
Jun 2024 — Present
Application Development Team Lead & Full-Stack Developer
Aptaworks
May 2024 — Apr 2025
Business Analyst
Pertamina EP
Sep 2020 — Feb 2023
Backend Developer
OKEJOB
2018 — 2019
Technology Consultant · booking-system work
Bukit Vista
02 — Approach
One line from unclear problem to working system.
Every engagement follows the same four stages — the point of the line below is that they stay connected. Work done in one stage is never wasted in the next.
Clarify
Interviews and lightweight system analysis to separate the real problem from its symptoms — written down, so we agree on what “done” means.
Shape
Requirements become a scoped plan: data model, workflows, and the smallest release that answers your riskiest question first.
Build
Working software in short, reviewable increments — backend-first where reliability matters, with the boring parts done properly.
Refine
Watch how it behaves in real use, tighten what’s slow or unclear, and hand over a system your team can run and extend.
On speed: I use AI-assisted development — “vibe coding” — as an approach for drafting and iterating faster. It is a working method, not a credential: requirements, architecture, and accountability stay human.
03 — Selected work
Three honest placeholders.
Invented case studies are worse than none. These slots stay marked as placeholders until real engagements can be documented with outcomes and the client’s permission.
Case study · Coming soon
Operational system design
What this slot will hold: a business process replaced by a real system — the analysis, the data model, and how the work actually runs after handover.
Case study · Coming soon
Decision-ready portfolio tooling
What this slot will hold: tooling that turned scattered operational data into decisions — what was measured, and what the owner agreed to publish.
04 — Credential
Verified, not decorative.
05 — Contact
Have a problem worth clarifying?
The fastest way to find out whether this fits is a short email — describe the mess, and you’ll get a straight answer about what I’d do with it.