Bangkok has no shortage of app developers. Freelancers, small studios, large agencies and offshore teams all compete for the same projects, and their quotes for the same idea can be very far apart. Price alone won't tell you who will deliver.
The questions below are the ones we suggest every business owner asks, including when talking to us. A good developer will answer all ten clearly and in writing. If someone avoids a question, that tells you something too.
This is the most important question and the one most often skipped. You should own the source code, the domain, the hosting account, the Apple and Google developer accounts, and all customer data. Put it in the contract.
Some developers publish your app under their own store account, or keep the code on their servers "for maintenance". That works until you want to change developer. Then you discover that moving the app means starting again.
Hourly billing can make sense for open-ended work, but for a defined first version you should get a written fixed-price quote with a clear scope. Ask what happens if the project runs over time. With a fixed price, that is the developer's risk, not yours.
Also ask how changes are handled. A fair process is simple: small changes are absorbed, bigger new features are quoted separately before any work starts.
The apps that launch on time usually start with one job done well: taking orders, confirming bookings, or giving staff a checklist. Ask the developer to list the features in version one and, just as important, what is not included.
If the proposal says "full app with all features", ask for the list. Vague scope is where budgets break.
You should not wait three months to see your app. Ask for a weekly demo or a live preview link you can open on your own phone. Regular check-ins catch misunderstandings while they are still cheap to fix.
There are three common routes:
A good developer will recommend the cheapest route that does the job, and explain why. Be careful if every client is told they need the most expensive option.
For a business in Bangkok, ask directly about:
Store review can delay a launch by days or weeks if the listing, privacy policy or screenshots are not right. Ask whether the developer prepares the store listings and handles review, and make sure the app is published under your developer accounts.
Every app needs fixes after real users arrive. Ask:
At Qlooto, bug fixes and small tweaks are free for 30 days after launch, and we reply within one business day. Whoever you choose, get these terms in writing.
Screenshots are easy to fake. Ask for live apps or websites you can open yourself, ideally in a business similar to yours. Look at speed, how it works on your phone, and whether the business still uses it.
Bangkok projects often involve Thai staff, foreign owners and a development team in more than one city. Agree up front on the channel (LINE, WhatsApp, email), the language of documents, and the working hours.
A note on where teams sit: many good teams work across several cities. Our own team is in Noida, India, and works with Thai clients in Thai business hours. What matters is not where the team sits, but whether they are honest about it and reachable when you need them.
Put each proposal in a table with the same columns: fixed price, scope of version one, timeline, who owns what, support terms, and live examples. The cheapest quote often moves to the middle once you compare like for like.
If you'd like a second opinion on a quote you already have, send it to us. We'll tell you honestly whether it looks fair.
Book a free 30-minute call. We'll help you scope the first version and send a written fixed-price quote.
Start the Conversation →