VAWM
EmailIndependent Product Builder · Business Systems Analyst
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
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 have been at Aptaworks since February 2023, where I now lead application development and build full-stack products. Along the way, Aptaworks assigned me to its Pertamina EP engagement as a business analyst (May 2024 – April 2025). Earlier, I was 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
Feb 2023 — Present
Application Development Team Lead & Full-Stack Developer
Aptaworks
May 2024 — Apr 2025
Business Analyst — assigned by Aptaworks
Pertamina EP (client)
Sep 2020 — Feb 2023
Backend Developer
OKEJOB
2018 — 2019
Technology Consultant · booking-system work
Bukit Vista
02 — Approach
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.
Interviews and lightweight system analysis to separate the real problem from its symptoms — written down, so we agree on what “done” means.
Requirements become a scoped plan: data model, workflows, and the smallest release that answers your riskiest question first.
Working software in short, reviewable increments — backend-first where reliability matters, with the boring parts done properly.
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
Invented case studies are worse than none. The engagement below is published only as far as the facts allow; the remaining two slots stay placeholders until real work can be documented the same way.
Internal system · Pertamina EP engagement via Aptaworks
An internal application for calculating and tracking forecast versus realization across Regional 2 Investment projects.
My role: Business Analyst · System Analyst · Project Manager / Developer Team Lead
Role focused on analysis and delivery leadership; I did not write production code.
Case study · Coming soon
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.
Case study · Coming soon
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.
04 — Credential
05 — Contact
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.