Services
Ways to work with me
System integration, IoT builds, and AI workflows when something needs building. Talks and mentoring when something needs explaining.
Full-Stack Web & Product Development
A product that runs end to end, not a demo with a database attached.
I build the whole thing: Next.js on the front, Laravel or Node underneath, Postgres or MySQL holding the data, deployed and monitored so it keeps running after launch day instead of needing you on call.
System Integration
Five tools that finally behave like one system.
Most stacks do not fail at the parts, they fail in between them. I build the layer that holds them together: authenticated APIs, data flow you can actually observe, and infrastructure another engineer can pick up without calling you.
IoT & Hardware Builds
Hardware that keeps reporting after you walk away.
ESP32 sensor networks over MQTT, feeding telemetry and control dashboards. Built for sites where power cuts and signal drops, so reconnecting is the firmware’s job and not your 2am problem.
Automation Workflows
The morning routine nobody should still be doing by hand.
Every process has a step someone repeats manually before the day starts. I move those into n8n and Python pipelines with retries and alerting, so no news is genuinely good news.
AI Integration
An assistant that cites your data instead of inventing it.
Wrapping a model API is the easy part. The work is retrieval that surfaces the right document, answers that stay inside what you actually know, and behaviour that holds up under real questions.
Six stages, no surprises
From first message to handover. You know the scope and the price before the building starts, and you never wait until the end to see it.
Tell me what you need
Day oneNot the stack you think you need. What breaks, what is slow, what keeps landing back on your desk.
- You bring
- A rough description, plus whatever already exists.
- You get
- Questions that narrow it down to the real constraint.
Agree on the shape
A day or twoScope, price, and timeline written down before anything starts. If it is outside my lane, you hear that here instead of three weeks in.
- You bring
- Your deadline and whatever budget shape you have.
- You get
- A written scope with milestones and a fixed price.
I build in the open
Milestone by milestoneWork lands in milestones you can actually run, not a black box that opens at the end. Progress is visible whether or not you ask.
- You bring
- Access to whatever the system needs to talk to.
- You get
- Working software at every milestone, not screenshots.
You try it for real
Each milestoneYou use it the way your users will, on your own data. Anything that feels wrong gets written down rather than politely ignored.
- You bring
- An honest run-through and the edge cases you know about.
- You get
- A demo, a changelog, and a list of what is still open.
We fix what the review found
Before sign-offRevisions inside the agreed scope are part of the price, not a change request. Anything genuinely new gets quoted honestly instead of absorbed quietly.
- You bring
- Priorities, when there is more to fix than time to fix it.
- You get
- The agreed fixes done, and a straight answer on the rest.
It goes live and stays yours
HandoverDeployed, documented, and handed over so your team can run it without me. No lock-in, no undocumented magic, no calls required.
- You bring
- Where it should live and who needs access.
- You get
- Source, deploy setup, docs, and a short support window.
Explaining the system
Some of the work is not building it, it is making sure other people can.
Speaking
Talks built from systems that shipped, not slides that circulate.
Sessions on automation, IoT, and AI systems for campus and community audiences. The failures stay in the deck, because that is usually the part people learn from.
More on my backgroundMentoring
A shortcut past the mistakes I already paid for.
One-on-one or small groups for students building their first real system: code review, architecture direction, and a straight answer on what to learn next instead of everything at once.
More on my backgroundDifferent shapes, same standard
Pick whichever matches how you need to bring someone in. The engineering does not change with the contract type.
Working details
- Based in
- Depok, Indonesia
- Timezone
- GMT+7, async friendly
- Reply time
- Within a day, usually
- Languages
- English, Bahasa Indonesia
Freelance
Project-based
A scoped build with one clear deliverable. Best when the problem has an edge to it.
Contract
3-6 months
Ongoing engineering capacity, delivered in milestones you can review as they land.
Full-time
Hiring
Open to teams where systems, automation, and AI work actually sit next to each other.
Remote
GMT+7
Based in Depok, Indonesia. Comfortable with async work and written handoffs.
Speaking engagement
Events
Campus and community sessions on automation, IoT, and AI systems.
Mentoring
Students
One-on-one or small groups, aimed at getting a first real system finished.
Want the full background? Read the story
Need the CV file? Download it here
Have something in mind?
One message with the problem in it is enough. You get back a straight read on scope, effort, and where I would start.