How to choose a web developer: 10 questions to ask before signing

Why the wrong developer costs more than the website itself

A website isn't a digital flyer you print once and forget. It's a business tool that should generate leads, build credibility, and work for you every day. When it's done poorly, it doesn't just fail to deliver results — it actively drives away customers who might have found you online.

If you want a clear picture of what websites actually cost, I've written a complete guide to website pricing with real figures for every type of project.

The three risks nobody warns you about

You lose time. The developer disappears for weeks, deadlines slip, and the site launches months late. Meanwhile, your business stays invisible online.

You lose money. The site gets delivered, but it's slow, doesn't rank on Google, and brings zero leads. A year later, you're starting over — and paying twice.

You lose control. The domain is registered under the developer's name, the code is proprietary, the hosting is tied to them. When you try to switch providers, you discover the website isn't yours.

These problems don't happen by accident. They happen because the client didn't know what to ask. The questions below are designed to prevent all three scenarios.

Freelancer, agency, or DIY platform — which one fits your business

Before choosing who will build your site, figure out what type of professional you need. The three main options have different strengths and trade-offs.

Side-by-side comparison for small businesses

If you want to dig deeper into the DIY route, I'm preparing an article on DIY website builders: are they really worth it? covering the pros, cons, and hidden costs.

When a freelancer is the smartest choice

A skilled freelancer is often the best fit for a small business or independent professional who needs a brochure site, a business blog, or a small online store. The advantages over an agency: direct communication without intermediaries, lower costs, and a leaner process.

The trade-off is verification. With an established agency, reputation is easier to check. With a freelancer, you need to do more homework to determine reliability. That's exactly why the questions in the next section matter even more.

10 questions to ask your next web developer

These questions work whether you're talking to a freelancer or an agency. Print them, bring them to your meeting, and note the answers. How the developer responds matters as much as what they say.

1. "Can I see live websites you've built?"

Screenshots and PDF mockups aren't enough. Ask for links to real, live, working websites. Then check:

• Open them on your phone. Does the site adapt well? Are buttons easy to tap without zooming?

• Test the speed. Go to Google PageSpeed Insights and enter the address. A mobile score below 60 is a warning sign.

• See if they look different from each other. If every site in the portfolio looks the same, they're probably reusing the same template for every client.

A serious developer will be happy you're doing these checks. One who gets defensive has something to hide.

2. "What technology will you use — and can I switch providers later?"

You don't need to become a coding expert, but you need to understand one thing: the technology chosen determines how easy (or impossible) it will be to modify the site in the future and how dependent you'll be on that developer.

Ask in plain language: "If I wanted to switch to a different provider someday, would another professional be able to work on my site?"

If the answer is "yes, I use standard, open-source technology," that's a good sign. If the answer is vague or evasive, be careful. For a deeper comparison of technology options, check out the article WordPress vs custom website.

3. "Will I own the domain, hosting, and code?"

This is the most important question of all — and the one most clients forget to ask.

Domain: your web address (e.g., yourbusiness.com) must be registered in your name. You can verify ownership through ICANN WHOIS lookup. If the domain is registered under the developer's name, you're trapped.

Hosting: the server space where your site lives. You should know where it is, have the login credentials, and be able to migrate elsewhere.

Source code: at the end of the project, the website's code should belong to you. Ask for this to be explicitly stated in the contract.

4. "What's included in the quote — and what isn't?"

A clear quote is the first sign of professionalism. Here's what it should contain:

• Number of pages and/or sections

• Design (how many design concepts? how many revision rounds?)

• Technical development (which platform?)

• Content (who writes the copy? you or the developer?)

• Basic SEO setup

• Responsive design (mobile optimization)

• Training on using the content management system

• Timeline with estimated dates

For a more detailed breakdown, the article how to read a website quote covers this topic in depth.

Watch for missing items: annual hosting, maintenance, security updates, costs for future modifications. If they're not in the quote, it doesn't mean they're free — ask about them.

5. "How do you handle basic SEO?"

A beautiful site that's invisible on Google is useless. You don't need a full SEO specialist at this stage, but the developer should at minimum:

• Set up title tags and meta descriptions for every page

• Create clean, readable URLs

• Ensure load times under 3 seconds

• Use heading tags (H1, H2, H3) correctly

• Optimize images for the web

If you get a vague answer like "we'll deal with that later" or "SEO is all about social media," that's a negative sign. If your current site isn't delivering results, the causes might be those I describe in your website isn't bringing clients: here's why.

6. "What happens after launch?"

Launching a website isn't the finish line — it's the starting point. A site needs regular updates, security patches, and performance monitoring. Ask:

• Do you offer maintenance plans? What do they cost?

• How often do you update the system (CMS, plugins, components)?

• How are backups handled?

• What's your response time for emergencies?

A developer who delivers the site and vanishes will leave you alone when something breaks — and it's only a matter of time.

7. "What's a realistic timeline?"

A 5-8 page brochure site typically takes 4 to 8 weeks in my experience. An e-commerce store can take 12 weeks or more. Be skeptical of anyone who promises "your site in one week" (a sign of a pre-built template) or anyone who can't give you a clear timeline.

Ask for a simple schedule with at least these milestones:

1. Information gathering and brief

2. Design concept (first draft)

3. Revisions and design approval

4. Technical development

5. Testing and bug fixes

6. Launch and training

8. "Can I update content on my own?"

After launch, you should be able to update text, images, and prices without paying the developer every time. Ask for a demonstration of the content management system (CMS) and judge whether it's manageable for you.

A well-configured CMS makes you self-sufficient for daily operations. If the developer says "for every change, you go through me," you're signing up for a lifetime subscription.

9. "Will the site meet accessibility standards?"

Since June 28, 2025, the European Accessibility Act has extended digital accessibility requirements to many businesses. Even if your business isn't directly covered, building an accessible site improves the experience for all users — and Google tends to reward it.

Ask the developer if they're familiar with WCAG guidelines and whether they account for them during development. They don't need to be a certified accessibility expert, but they should know about color contrast, image alt text, and keyboard navigation.

10. "Can I talk to a past client?"

A developer who's confident in their work will have no problem giving you a reference from one or two past clients. If they refuse, ask yourself why.

When you reach out, ask: Did they meet the deadlines? Were they easy to reach? Did the site deliver results? Would you hire them again?

5 red flags that should make you walk away

Not all warning signs are obvious. Some hide behind phrases that sound professional.

1. "I'll get you to page one of Google within a month." SEO takes months of consistent work. Anyone promising instant, guaranteed results is lying.

2. "The price? Let's discuss that after we start." No serious professional begins work without a written, approved quote.

3. "I'll register the domain for you — it's easier that way." Easier for them, risky for you. The domain must be in your name, always.

4. "You don't need SEO — just use social media." Social media is useful, but it doesn't replace search engine visibility. They're different channels with different goals.

5. "The site is built on my proprietary platform." Translation: if you want to leave, you start from scratch. Portability is your right.

You can also check the developer's own site with PageSpeed Insights: if their site is slow or not optimized for mobile, they're unlikely to do better with yours.

Evaluation checklist — print this and bring it to your next meeting

Use this table for every developer or agency you're evaluating. Fill in one column per candidate and compare.

The highest score doesn't automatically mean the best choice — personal fit and communication matter too — but it's the candidate with the strongest foundation.

How to read a website quote without getting lost

Website quotes aren't standardized: every professional structures theirs differently. Here's how to navigate them.

The line items that matter

A complete quote should include at least these sections:

Project scope: number of pages, features, who produces the content (copy and photos).

Technology: which platform the site will be built on, which hosting is included.

Design: how many design concepts, how many revision rounds, whether the design is custom or template-based.

Recurring costs: annual hosting, maintenance, cost for future changes outside the original scope.

Timeline: estimated dates for the main project milestones.

Ownership: a line confirming that domain, hosting, and source code belong to you.

If even one of these items is missing, request an addendum before signing.

What I do when a new client reaches out

I'm not telling you what to ask a developer so I can position myself as the only answer. These questions apply to any professional, including me. But I think showing you how I work can give you a useful benchmark.

My 5-step process

1. Listen. Before talking about technology or pricing, I understand what your business does, who your customers are, and what you expect from the site. If I don't understand your business, I can't build a tool that works for you.

2. Written proposal. You receive a detailed quote with every line item I described above, including recurring costs. No surprises.

3. Design and feedback. I create a first design concept and we review it together. Your feedback drives the revisions — the site should represent your business, not my personal taste.

4. Development and testing. I build the site, test it across devices, optimize it for speed and basic SEO. You see the result before it goes live.

5. Handoff and training. I deliver the site with all credentials (domain, hosting, CMS). I teach you how to make basic updates. And I'm available for ongoing maintenance if you want it.

If this approach sounds right for you, you can see my services or get in touch to discuss your project.

Frequently asked questions

How much does a freelance web developer charge? In my experience, a professional brochure site from a competent freelancer starts at $2,000-3,000 and can reach $6,000 for more complex projects. An e-commerce site starts at $4,000-5,000 and up. Key price factors are the number of pages, required features, and design complexity. I've written a detailed guide on how much a website costs with real examples for every price range.

Is a web developer the same as a web designer? No. A web designer handles the visual side (graphics, colors, layout). A web developer handles the technical side (code, functionality, performance). A full-stack developer like me does both. When evaluating a professional, clarify upfront whether the price includes both design and development.

How long does it take to build a website? For a 5-8 page brochure site, expect 4 to 8 weeks from project confirmation. An e-commerce store typically takes 8-16 weeks. Timelines also depend on how quickly you provide content (copy, photos, logo).

Can I request changes after delivery? It depends on the contract. Most developers include a set number of revisions in the initial price. After delivery, small changes (text, images) should be something you can handle through the CMS. For structural changes, verify the rates for additional work in advance.

How do I know if my website is truly mine? Check three things: domain registration (verifiable through ICANN WHOIS), hosting credentials (you should have them), and source code ownership (should be stated in the contract).

What to do next

If you're evaluating several professionals for your next website, print the evaluation checklist above and use it as a guide during your meetings. The right questions protect you more than any contract clause.

If you'd rather talk to me directly about your project, you can get in touch here. I respond personally within 24 hours, and we can figure out together whether the project makes sense.