Real estate · MY
AlKath Property
Problem — Listings lived in chat threads and leads went cold before anyone followed up.
Shipped — A property platform with listing management and lead capture — every inquiry lands in one pipeline with a name on it.
← All work
Studio work · 2022–present · Updated July 2026
Client engagements
Every engagement here started as a business bottleneck, not a feature request. These are the problems clients brought, what shipped, and why they trusted a remote solo developer across three markets to fix them.
Next.jsSupabaseFlutterModern PHPVPSAI integration
[01] — The problems
Different industries. The same leak.
A property firm generating leads it couldn't track. A vocational school processing enrollments by hand. Brands with revenue but no platform of their own. In every case the business had outgrown its tooling — and the cost showed up daily as lost leads, wasted hours, and missed sales.
Education · ID
LPK Training Center
Problem — Enrollment ran on paper forms and phone calls; staff hours went to admin, not teaching.
Shipped — A platform for programs, registration, and administration — sign-ups process themselves, staff review instead of retype.
Commerce · ID / MY / US
Independent brands
Problem — Selling on rented marketplace land: rising fees, no customer data, no control.
Shipped — Custom storefronts and company platforms the brands own outright — with AI and automation where it removes real cost.
[02] — How the work runs
Why clients in three markets trust a remote solo dev.
Not because of the portfolio — because of the process. Every project gets a written proposal with exact scope and what's excluded, milestone-based payment (50/30/20) so nobody pays for unapproved work, staging previews from the first weeks, and documentation the client owns. One person carries the project from proposal to production, so nothing is lost in handoffs — and for B2B clients I've drafted the technical architecture and the outreach strategy in the same engagement.
[03] — Why this stack
Chosen for the client's balance sheet, not my résumé.
A solo studio serving three markets can't afford exotic infrastructure — and neither can the clients. The toolkit is deliberately boring where it should be and intelligent where it pays.
Next.js + Supabase
One well-supported stack across projects means faster delivery and cheaper maintenance — clients pay for their platform, not for me re-learning tools.
Modern PHP
When a client's existing hosting and team know PHP, meeting them there beats a rewrite — the pragmatic choice is sometimes the boring one.
Flutter
One codebase for Android and iOS — a mobile app at half the build-and-maintain cost of two native teams.
AI where it pays
Chatbots, recommendation engines, and internal agents go in when they remove a real cost center — never as a checkbox on a proposal.
Docker + VPS
Flat hosting bills a small business can budget for, and no platform lock-in if we part ways — clients keep the keys.
Documentation & handover
Code, API integrations, and workflow guides transfer with ownership on final payment — no hostage-taking, which is exactly why they come back.
[04] — The results
Shipped, adopted, and still running.
Platforms delivered across IDR, MYR, and USD markets since 2022 — remotely, milestone by milestone. The strongest metric a solo practice has: clients who return for the next build and hand your name to someone else.