Seven questions to ask before you pay anyone to build your website

Hiring someone to build your website is a lot like hiring a contractor. Most are honest and good at their jobs. But you are handing over something your business depends on, and the time to find out how they work is before you sign.

Here are seven questions to ask any web developer, freelancer or agency, including us. For each one, we've written what a good answer sounds like. A hesitant or vague answer isn't proof of bad intentions, but it is a reason to ask again.

1. Who will own the domain and the accounts?

Your domain name (yourbusiness.com), your hosting account and your Google Business Profile should be registered in your name, with your email, so you can always get in.

A good answer: "You own all of it. We'll be added as users, and you'll have the logins." If they say they'll register the domain in their own name "to keep things simple," ask them to put it in yours instead. If you ever part ways, the domain is the hardest thing to get back.

2. What will it cost each month after launch, and for what?

Many sites have ongoing costs: hosting, a domain renewal, a booking or form tool, a maintenance plan. None of these is a scandal. The problem is finding out later.

A good answer: a written list. Each item names what it is, who is paid, and how often. Ask which costs go to a third party and which go to the developer, so you can see what you're actually paying for.

3. Can I change the text myself?

Think about how often your hours, your menu, a holiday closure or a staff photo change. If every edit needs an email to the developer and a few days' wait, that gets old fast.

A good answer: "Yes, here is how, and we'll show you." Some sites are built so owners can edit text directly. Others are built so changes go through the developer, and that can be perfectly fine if the process is quick and part of the deal. Just know which one you're buying.

4. How will it look and load on a phone?

Most of your customers will find you on a phone, often with a weak signal, often in a hurry. Ask to see the site on a real phone, not a laptop screen resized to look small.

A good answer: they show you examples on their own phone, and they talk about keeping pages light: fewer giant photos, no heavy features you don't need. You can also try it yourself. Open one of their past sites on your phone on mobile data and see how long it takes before you can read something.

5. Is it built to be usable with a keyboard and a screen reader?

Some visitors never touch a mouse. Some listen to the page instead of looking at it. A site that works for them is usually clearer for everyone.

A good answer: they know what you mean, and can say how they check. Listen for mention of WCAG, the common technical standard for web accessibility, and for actually testing with a keyboard and a screen reader, not just running an automated scan. Be wary of any promise that a site will be "fully accessible" or "compliant" with no mention of testing. Nobody can promise a legal outcome, and this is not legal advice.

6. What happens if we part ways?

Maybe you outgrow them. Maybe they retire. Maybe you simply want to switch. It is awkward to raise this before you've started, which is exactly why it matters.

A good answer: "You get the files, the content, and the logins, and we'll help hand it off." Ask whether the site is built on common tools another developer could pick up, or on something only they can maintain. Ask whether there is any cancellation fee or notice period, and get that in writing.

7. Is the price fixed, in writing?

A quote that says "around" or "starting at" is fine as an estimate. Before work begins, you want a number.

A good answer: a written scope that lists what's included, how many pages, how many rounds of changes, and what counts as extra. Ask what happens if you want something added midway. Good developers can answer that easily, because they've been through it before.

A note on comparing quotes

Don't pick the cheapest or the fanciest. Pick the one whose answers you understood. If you've asked all seven questions and one provider explained things in plain language while another got defensive, that tells you something about the next year of working together.

It also helps to ask each provider the same questions in the same order, so you can lay the answers side by side.

Where Mobius fits

Two of these answers are written into how we sell. Every project gets a fixed price in writing before work starts, and our monthly plans are month-to-month with no long-term contract. You can see the details on our packages page, and you are welcome to ask us the other five questions too.

If you already have a website and aren't sure it would pass these questions, our Free Tech Checkup will give you a written look at it, whether or not you ever hire us.