Skip to main content
Wystepek Digital Company
All insights
  • web development
  • small business
  • websites
  • hiring
  • contracts

How to Choose a Web Developer: Questions to Ask Before You Hire

Hiring a web developer is easier when you know what to ask about ownership, hosting, contracts, and support before any money changes hands. Use this plain-English checklist to compare options and spot red flags.

WDWystepek Digital Company · 6 min read

Hiring someone to build or rebuild your website is a bigger decision than picking a design you like. You are trusting that person (or company) with how customers find you, how they contact you, and who controls the asset when the project ends.

You do not need to be technical to hire well. You need clear questions, honest answers in writing, and a willingness to walk away when something feels off. This guide covers ownership, hosting, contracts, support, and common red flags.

Start with what you need, not with who you found first

Before you talk to developers, jot a short brief:

  • What the site has to do (show services, take bookings, sell products, capture leads, and so on).
  • Who it is for (local customers, remote clients, or both).
  • Whether you need to edit content yourself after launch.
  • Rough timeline and budget range you can live with.
  • Whether you already have a domain, hosting, branding, or content ready.

Even a one-page note keeps conversations from drifting into features you do not need.

1. Who will own the website when it is done?

This is the most important question, and it is easy to skip when demos look great.

Ask clearly:

  • Who owns the domain name? Ideally you do, under an account you control (for example at your registrar), with your own login.
  • Who owns the website files, design, and content? You should receive the finished work in a form you can take elsewhere if you change providers later.
  • Who owns accounts tied to the site? That includes hosting, analytics, email forms, booking tools, and any third-party services the site depends on.

If the answer is vague ("we host everything for you" with no path to leave), ask how a clean handoff would work. A reputable developer can explain how you would export or transfer the site without starting over from zero. If they cannot, or if they treat the site as something they permanently control, that is a structural problem, not a pricing detail.

2. Where will it be hosted, and who controls that?

Hosting is where your site lives on the internet. It is separate from design, even when one company handles both.

Ask:

  • Which host will be used, and why?
  • Will the hosting account be in your name, or only in theirs?
  • What does hosting cost after the first year, and who pays the bill?
  • How are backups handled, and how often can you restore from them?
  • What happens if you want to move hosts later?

Some businesses prefer the developer to manage hosting. That can be fine when you still own the account (or have a clear transfer process) and get regular backups. What you want to avoid is a setup where the site only exists inside the developer's private system and leaving means rebuilding.

3. What exactly is in the contract?

A written agreement protects both sides. Before you sign, make sure it covers:

  • Scope: which pages, features, and integrations are included.
  • What is not included: content writing, photography, logo design, ongoing ads, or major redesigns after launch, if those are out of scope.
  • Timeline: milestones and an estimated launch window, plus what happens if either side is delayed.
  • Revisions: how many rounds of changes are included, and how extra changes are priced.
  • Payment schedule: deposits, progress payments, and what is due at launch. Avoid paying 100% up front for a custom build.
  • Ownership and deliverables: a clear statement that you own the finished site and related assets, plus what you receive at the end (access, files, documentation).
  • Support after launch: what is covered for free, for how long, and what ongoing maintenance costs if you want it.

If the proposal is only a price and a start date, ask for the details above in writing. You are not being difficult. You are making sure both of you mean the same thing by "done."

4. How does support work after launch?

A site that launches well still needs care. Forms break, plugins need updates, hours change, and search engines change how they show results. Ask what happens on day 31.

Useful questions:

  • Is there a warranty or bug-fix window after launch, and what does it cover?
  • Do you offer ongoing maintenance, and what is included (updates, backups, uptime checks, small content changes)?
  • How do I request changes, and what is the typical response time?
  • Who do I contact if the site goes down after hours?
  • If I manage content myself, will you train me, and is that included?

You do not have to buy a maintenance plan from the same person who built the site. You do need to know whether walking away after launch leaves you with a site you can maintain, or with a black box you cannot touch.

5. How do they work, and can they show proof?

Ask for a simple picture of the process: discovery, design, build, review, launch, and handoff. Then ask to see work that is similar to yours in scope, not only the prettiest portfolio piece.

Also ask:

  • Who is the main point of contact?
  • Will subcontractors be involved, and who is accountable if something goes wrong?
  • How will we communicate (email, shared board, scheduled calls)?
  • How will content and feedback be collected so the project does not stall?

You are listening for clarity. A good partner can explain their process without hiding behind jargon.

Red flags worth taking seriously

Walk carefully, or walk away, if you hear any of these:

  • You cannot own the domain or site files. Access should not depend forever on one vendor's goodwill.
  • "Trust us" instead of a written scope. Verbal promises fade; contracts do not.
  • Pressure to pay everything up front for a custom project with no milestones.
  • No examples of real work, or only stock mockups with no live sites you can visit.
  • Guarantees of #1 Google rankings. No honest developer can promise a specific search position, because search results depend on many factors outside their control.
  • Refusal to explain hosting, backups, or handoff. Secrecy about the basics is not a feature.
  • One contact who disappears for weeks during the sales process. Responsiveness rarely improves after the deposit clears.
  • A quote that is dramatically lower than others with no clear reason. Cheap can be fine when scope is small. It is a warning when the quote skips ownership, hosting, and post-launch support entirely.

A low price or a freelancer can still be a good fit. These signs just mean you should slow down and get answers in writing.

A short question list you can bring to a call

Copy these into your notes before the next conversation:

  1. Who owns the domain, hosting account, and website files when the project is finished?
  2. How would I take the site elsewhere if I needed to?
  3. What is included in the quoted price, and what is not?
  4. How many revision rounds are included?
  5. What is the payment schedule?
  6. What does support look like for the first 30 to 90 days after launch?
  7. Do you offer ongoing maintenance, and what does it cover?
  8. Can I see two or three live sites similar to what I need?
  9. Who will I work with day to day?
  10. What do you need from me to stay on schedule?

If answers are clear and consistent, you are in a good position to compare proposals. If they are fuzzy, keep looking.

Choosing is about fit, not flash

The right web developer for a small business explains tradeoffs in plain English, puts ownership and scope in writing, and leaves you with a site you can run. Design taste matters. So do accounts in your name, backups you can restore, and a path forward when something breaks.

Ask these questions before you hire. A thorough discovery call beats a fast yes you regret six months later.

We can help

If you are planning a new site or rebuilding an old one and want a clear plan before you commit, we are happy to talk it through. Book a free consultation and we will walk through your goals, ownership, and options in plain English.

0 Comments

No comments yet. Start the conversation.

Leave a comment

Your email address will not be published. Comments appear after moderation.

Never shown publicly.

Comments are moderated. See our Privacy Policy.