Web App & SaaS Development
Systems people actually use every day — not a prototype that dies in Figma.
I build web apps and SaaS from scratch: database, auth, billing, dashboard, API — through to live di production. You get the code, the documentation and a system that keeps up as the business changes.
- 3 live production systems
- Built solo, end to end
- The code and documentation are yours
The work
Not a picture portfolio.
Running systems.
Click and try them yourself. Each one has real users, a real database and real hosting costs — not a demo switched off after the pitch.
The Barokah
thebarokah.comAn ecommerce platform: product catalogue, cart, orders and the customer journey in one system.
Visit siteJobHubX
jobhubx.comA two-sided job portal: job search, company profiles and applications in one flow.
Visit siteRahsia Founder
rahsiafounder.myPlatform komuniti founder: content, keahlian and pengurusan ahli berbayar.
Visit siteWhat I built
One system. Not five tools that do not talk to each other.
Most businesses already have WhatsApp, Excel, Google Forms and a bank account. The problem is not data — it is that nothing brings it together in one place.
Multi-tenant SaaS
Every customer gets their own space: separated data, their own subdomain, their own roles and their own billing. One codebase, many tenants — that is what makes SaaS profitable.
Auth & peranan
Sign-up, sign-in, email verification, 2FA and role-based access — admin, staff, customer.
Billing & subscriptions
Stripe, FPX and cards, automatic invoices, monthly/yearly plans, and handling for failed payments.
Dashboard & laporan
The right numbers at the right time: revenue, customers, stock, performance — not a hand-built Excel export.
Integrasi & API
Connect it to a payment gateway, WhatsApp, e-invoicing, your accounting system or your mobile app.
Automasi & cron
Reminders, invoice generation, stock sync and scheduled reports — all running with nobody clicking.
Internal system
Replace Excel and WhatsApp: inventory, quotations, bookings, HR and customer records.
A backend for your mobile app
One API that drives the website, the admin dashboard and the phone app — so the data never contradicts itself across three different systems.
Proses
You see progress every two weeks.
Not after three months.
System projects fail most often not because of technology, but because nobody sees anything until the deadline. This is the workflow I use.
Sesi skop
90 minutes. I ask about the business, not the features. The output: what has to be built first.
System map
Data model, roles, money flow and integrations — documented before a single line of code is written.
Sprint 2 minggu
You get a clickable version every two weeks. Early feedback, not a surprise at the end.
Ujian & live
Real data, backups, error monitoring and a launch without downtime.
After launch
Documentation, training and a support window. The code is handed over to you.
Model kerjasama
Pick by the stage your business is at.
Scope and price are set after the scoping session — not after you pay a deposit. I would rather decline a project that does not fit than take a deposit for something that will never ship.
MVP Sprint
Idea → a version you can test with real users, as fast as possible.
- One core flow, built properly
- Auth, billing, dashboard asas
- Live within weeks
For founders who want to prove the market before burning capital.
Internal System
Replace Excel, WhatsApp and paper notebooks with one system everybody trusts.
- Stock, orders, quotations, HR
- Peranan staf and jejak audit
- Reports nobody has to tally by hand
For a business that is already running and losing hours to manual work.
Skala & Selenggara
An existing system that is slow, fragile or no longer fits the business.
- Audit kod and prestasi
- New features without breaking the old ones
- Backup, pemantauan, and pelan pemulihan
For an owner who no longer knows what is running inside their own system.
The questions we get asked most.
How long does it take?
An MVP is usually 6–10 weeks, an internal system 4–8 weeks, and bigger systems are split into phases. The real dates are set after the scoping session, because promising dates without a clear scope is the fastest way to disappoint both sides.
Adakah saya dapat kod sumber?
Yes. The code, the database and the documentation are handed to you or your company. No vendor lock-in: you can continue with another developer at any time, and I will make sure it runs without me.
Can you connect to a system we already have?
Usually yes, after an audit. If the old system is too fragile to extend, I will say so plainly — including an estimate for rebuilding it, so you can compare that with the cost of patching.
Who manages hosting and domains?
Either way works: I provide and manage it (hosting billed separately and transparently), or install it on your own infrastructure. For systems that hold customer data, business owners usually prefer the second.
What happens after the system goes live?
There is a support window for bugs and small improvements, with documentation and a training session. After that you can carry on yourself, take a monthly maintenance package, or hand it to your in-house team.
If this system could be your competitive edge, we should talk.
Send one paragraph about your business and the problem you want solved. I will answer with an honest opinion — including if the project is not worth building yet.
We usually reply within one business day.