The best way to choose a web developer in the Philippines is to ask specific questions before you pay anything: what exactly is included, who owns the domain and code, how long it will take, and what happens after launch. A good developer answers these clearly and in writing. A risky one gets vague, or promises everything for very little.
Here are twelve questions worth asking, why each one matters, and what a good answer sounds like.
Before the questions: know what you want
You will get better answers if you can explain your goal in one or two sentences. For example: “We are a dental clinic in Quezon City. We want patients to find us on Google, see our services and prices, and book an appointment or message us on Viber.” That single paragraph tells a developer more than a long list of design preferences.
The 12 questions
1. Can I see websites you have built that are similar to what I need?
Why it matters: A portfolio shows taste, but relevance matters more. A developer who has built booking sites understands booking problems.
A good answer: Live links you can open on your own phone, plus a short explanation of what the developer did on each one: design, build, content, or all three.
2. What exactly is included in the price?
Why it matters: “Five-page website” can mean very different things. Hosting, domain, content writing, stock photos, business email and SEO setup are often the difference between two quotes.
A good answer: An itemised list. If something is excluded, it says so.
3. Who will own the domain, hosting account and website files?
Why it matters: This is the question most business owners regret not asking. If the domain is registered under the developer’s name and the relationship ends badly, you may lose your web address and email.
A good answer: “The domain is registered to your business, and you get the logins.” If the developer manages hosting for you, you should still be able to request a full backup at any time.
4. Who writes the content and supplies the photos?
Why it matters: Content is where most projects stall. If you are expected to write everything, you need to know that on day one.
A good answer: A clear split: what you provide, what they write or source, and any word limits.
5. How long will it take, and what do you need from me to hit that date?
Why it matters: Timelines depend on both sides. Delays in feedback or content push launch dates back.
A good answer: A timeline broken into stages (for example design, build, review, launch) with the inputs needed from you at each stage.
6. How many revision rounds are included?
Why it matters: Revisions without limits sound generous but often lead to projects that drag on for months.
A good answer: A defined number of rounds at each stage, plus the rate for extra changes.
7. What platform will you build on, and can I update the site myself?
Why it matters: WordPress, Shopify, a custom framework and a website builder each have different costs, flexibility and lock-in. If you want to post updates or change prices without calling the developer, you need an editor you can actually use.
A good answer: A recommendation with a reason tied to your needs, and a short handover or tutorial after launch.
8. Will the site work well on phones and on slow mobile data?
Why it matters: Most of your visitors will arrive on a smartphone, many on prepaid data. A site that looks great on an office monitor but takes ages to load on a mid-range Android phone loses customers.
A good answer: Responsive design as standard, compressed images, and willingness to test on a real phone, not just a desktop browser.
9. What SEO work is included?
Why it matters: A website that nobody finds does not bring inquiries. Basic on-page SEO should be part of any build.
A good answer: Proper page titles and descriptions, sensible headings, clean URLs, a sitemap, Google Search Console and Analytics setup. Be wary of anyone who guarantees a number-one ranking; nobody controls Google’s results.
10. How will you handle security and backups?
Why it matters: Hacked sites, spam injections and lost data are common, especially on unmaintained WordPress sites.
A good answer: HTTPS by default, regular backups stored away from the server, updates to software and plugins, and a clear explanation of who is responsible for each after launch.
11. What happens after launch, and what does support cost?
Why it matters: Websites need updates, and you will want changes. You need to know whether that is a monthly fee, a per-request charge, or included for a period.
A good answer: A written support arrangement: response times, what is covered, and the cost.
12. What are the payment terms, and can I get an official invoice?
Why it matters: Registered businesses usually need proper invoices to record the expense. Milestone payments also protect you on larger projects.
A good answer: Clear terms (for example a down payment and a balance on completion, or milestones for bigger projects), accepted payment methods such as bank transfer, GCash or Maya, and proper documentation.
Red flags to watch for
- Pressure to pay in full immediately with a “promo ends today” message
- No written scope, only a price in a chat message
- Guaranteed first-page Google rankings within weeks
- Refusal to register the domain in your name
- Portfolio links that do not load, or all point to the same template with different logos
- Slow or unclear replies before you have even paid, which rarely improve afterwards
How to compare quotes fairly
Send every developer the same short brief, then put their answers side by side. A simple comparison sheet helps:
| Item | Developer A | Developer B | Developer C |
|---|---|---|---|
| Total price | |||
| Pages and features included | |||
| Content writing included? | |||
| Hosting and domain included? For how long? | |||
| Domain registered in my name? | |||
| Timeline | |||
| Revision rounds | |||
| Post-launch support and cost |
The cheapest line is not always the best value. A quote that includes content, hosting and a year of support can cost less overall than a lower price that leaves you paying for each of those separately. For a breakdown of what drives price, see how much a website costs in the Philippines. If your project also involves an app, the same questions apply, along with a few more covered in our guide to mobile app development costs.
Put ServicioPro to the test
We are happy to answer all twelve questions for your project. You can see what each package includes on the web design page, and send your brief through the contact page, by email to support@serviciopro.ph, or on WhatsApp, Telegram or Viber at +63 929 647 3840.
Frequently asked questions
Should I choose a developer in my own city?
It helps if you want face-to-face meetings, but it is not essential. Many Philippine businesses work with developers in other cities or provinces through video calls and chat. Responsiveness and clear communication matter more than location.
Is it a bad sign if a developer asks for a down payment?
No. A down payment is normal and shows commitment from both sides. What matters is that the payment terms, scope and timeline are written down before you pay.
How many developers should I get quotes from?
Three is usually enough to understand the market without spending weeks on meetings. Give them all the same brief so the quotes are comparable.
What if I already have a website that needs fixing?
Ask the developer to review it first and tell you whether to repair or rebuild. Make sure you still have the logins to your domain and hosting before you start.
