About · Prom · Bangkok
You talk to the person who builds it.
I'm Prom (พรหม), a digital studio of one based in Bangkok. I design and build the websites, booking apps, and internal tools that businesses run on every day.
There's no account manager between us, no junior I quietly hand the real work to. You brief one senior person, that same person ships it, and that same person hands you the keys at the end. The whole point of working with one operator is that nothing gets lost in translation.
The standard I hold
What I will not ship without.
Range is only trustworthy if the bar stays fixed. The same standard applies whether I'm building a gym booking app, a clinic site, or an internal tool: these three things are non-negotiable.
- 01
It ships, and it works.
Finished means in your hands and running in the real world, not a demo that breaks the first time a real customer touches it. I scope to a date and I hit it. If something slips, you hear it from me early, with a plan, not on the deadline.
- 02
You own everything.
Code, hosting, domain, and accounts go in your name with a plain-language runbook so your next person (or your future self) can pick it up. No lock-in, no holding your own software hostage. If we ever part ways, you walk away with the keys.
- 03
The scope is honest.
You get a proposal-grade scope before any money changes hands: what's in, what's out, what it costs, and when it's done. No surprise invoices, no "that's a phase two" once you're already committed. If I'm not the right person for the job, I'll tell you that too.
How I work
One senior brain, zero handoffs.
Most of the speed (and most of the honesty) comes from one fact: the person who scopes the work is the person who builds it. Decisions don't wait in a queue. Nothing gets re-explained three times.
Every project runs through the same named process, so breadth never means improvisation. See The Build.
We map it before we build it.
I start by getting the actual problem out of your head and onto paper: who it's for, what "done" looks like, and the one or two decisions that will make or break it. A fuzzy brief becomes a scope you can read and sign.
I make the call, then I tell you why.
Hundreds of small decisions go into shipped software. I make them with a senior bias toward what's simple, durable, and cheap for you to run, then I explain the trade-offs in plain language so you stay in control.
Built for how Thailand actually works.
PromptPay checkout, LINE reminders, LIFF mini-apps, Thai-first UX. I build for the way your customers really pay and message, not a template imported from somewhere else.
I prove it, then I hand it over.
Before launch I test it the way a real user would, not the way a developer hopes. Then I hand off code, accounts, and a runbook so the thing keeps running long after I've stepped away.
The human part
I'm a builder before I'm a salesperson. I'd rather tell you the honest version of what something takes than win the work and disappoint you later. Calm, specific, and on the record is how I prefer to operate.
I work first-person, in writing, and I keep promises small enough to actually keep. If you want a partner who treats your budget like their own and your deadline like a fact, that's the whole pitch.
Availability, honestly
I take on a small number of builds at a time, so each one gets a senior brain from start to finish. Message me and I'll tell you my current lead time before I can start.
If the standard sounds like what you've been missing, let's talk.
Tell me the problem in plain language. If it can be built, I'll scope it fixed: clear price, clear date. I reply within one business day.