Hiring a web designer is easier when you know what to ask before signing a proposal or contract. The right questions reveal what you are actually buying, what you will own, how the project will be managed, what happens after launch, and what it will cost to make changes or leave later.

Just as important, the answers should be documented in the scope of work and agreement. A reassuring sales conversation is not a substitute for clear written commitments.

1. Who owns the website when the project is finished?

You should generally own the website, its original content, its domain, and the custom assets created specifically for your project. The agreement should state exactly when ownership transfers and whether final payment is required first.

Ask who owns the code, design files, copy, photography, domain, and other project assets after payment. Some fonts, stock images, plugins, themes, and platform components may be licensed rather than owned, so any exceptions should also be identified.

2. Is the domain registered in my name?

Yes. Your domain should be registered in your name and in an account you control.

Do not let the most important address for your business live indefinitely in someone else’s registrar account.

3. Who controls the hosting account?

Understand the difference between owning your website and allowing someone else to manage its hosting.

An agency may host your website as a service without owning it. Ask who controls the hosting account, who can access backups, and what files, credentials, and technical information you will receive if you decide to move.

4. Can I leave later?

A good relationship should not depend on technical or contractual lock-in.

Ask what the provider will give you if you move to another developer, host, or platform. Depending on the setup, you should reasonably expect a copy of the website files and database or an available platform export, your credentials, domain and DNS information, and a list of important licenses or dependencies.

The agreement should also explain the handoff timeline, file format, migration fees, and any services or licensed tools that cannot transfer.

5. What exactly is included in the price?

Ask for a written scope of work that lists the page count, templates, features, integrations, content responsibilities, design revisions, testing, training, launch work, timeline, price, payment schedule, and acceptance process.

“Website” is not a useful scope by itself. The document should make it possible for both sides to tell whether the agreed work has been completed.

6. What costs extra?

Ask about common additions and exclusions before the project starts. Also ask how changes will be estimated, approved, and billed after work begins.

Blogging, ecommerce, content migration, booking, multilingual content, gated content, and custom integrations can all change the final price. The scope of work should state what is included, what is excluded, and any allowances or assumptions used to calculate the quote.

7. Who writes the content?

Clarify whether you, the designer, a copywriter, or another specialist is responsible for writing, editing, approving, and entering the content.

Content delays are one of the most common reasons website projects take longer than expected. The scope should include content deadlines and explain what happens if material arrives late.

If you provide the content or pay for original copy and photography, it is reasonable to expect the agreement to state that you own those materials after payment. Third-party stock assets and licensed media may have separate usage restrictions.

8. How much can I edit myself?

Ask to see the editing experience before you commit, preferably using a real page rather than a carefully prepared demo.

You should understand what you can change without calling the developer, what requires development work, which user roles your team will receive, and whether training is included.

9. What platform and technology will you use?

Ask why they chose the platform, how it fits your requirements, and which themes, plugins, apps, frameworks, or external services the site will depend on.

The technology underneath a website affects performance, maintenance, portability, security, and how easily another qualified developer can work on it later.

10. How will the site be maintained?

Ask who handles WordPress core, plugin, theme, security, backup, performance, and hosting maintenance after launch, and how often that work is performed.

A website is software, and software needs ongoing care. If maintenance is optional, understand what responsibilities shift to you when you decline it.

11. What happens after launch?

Know what post-launch support is included, how long it lasts, and what happens when that period ends.

Ask about response times, update schedules, backups, security monitoring, emergency support, training, and how additional development work is requested and billed.

12. What happens if something breaks?

Ask how problems are reported, who decides whether an issue is covered, and how quickly the provider responds at different priority levels.

A maintenance plan should define what is covered, what is excluded, and whether problems caused by third-party services, client changes, or new browser and platform updates are handled separately.

13. How will accessibility and performance be handled?

Ask which accessibility target, performance goals, devices, browsers, and testing methods the developer will use rather than accepting vague promises about a “fast” or “accessible” website.

Look for a combination of automated and manual testing, measurable targets, and a clear explanation of any known limitations before launch.

14. What happens if the site needs to grow?

Ask whether the proposed platform and architecture can handle the amount of content, traffic, integrations, user roles, and functionality you reasonably expect over the next few years.

The least expensive solution today is not necessarily the least expensive over three years. Ask what growth would require routine configuration, additional development, a higher subscription tier, or a full rebuild.

15. Can you show me the contract and terms before I sign?

Read the agreement before committing, especially the sections covering ownership, payment, scope, change requests, hosting, maintenance, warranties, termination, and the project handoff.

It is essential that every commitment you are relying on appears in the signed agreement or an incorporated scope of work. If a price, timeline, feature, ownership right, support promise, or exit term matters to your decision, it should not exist only in a sales conversation.

Red flags

Be cautious if a designer:

• Won’t clearly explain ownership
• Controls your domain without a good reason
• Can’t explain what happens when you leave
• Gives you a vague “website” price without a detailed scope
• Promises everything is included without defining boundaries
• Won’t show you the editing experience
• Treats maintenance as optional but can’t explain the risks of skipping it
• Avoids explaining the technology being used
• Will not put important promises into the agreement or scope of work

Before you sign

You should be able to answer these questions in plain English:

• What am I buying?
• What does it cost?
• What will I own?
• Who controls my domain?
• Where will it be hosted?
• How will I edit it?
• What happens after launch?
• What happens if I leave?

If you cannot answer those questions and point to where the important commitments are documented, you are not ready to sign.