Step 1/2
project details

Tell us about
the project

Tell us everything! Share your thoughts, ideas, and any specifics about your project. The more details, the better.

Select services
selection
Clear selection
Contact Details

How can we reach you?

Final step! Fill out your contact info, and we’ll be in touch to discuss your project soon.

Dropdown
Thank you for contacting us!

We will be in touch within 48 working hours

Keep your eyes peeled for an email from one of our founders.

Okay, got it!
Oops! Something went wrong while submitting the form.

Last Updated: November 17, 2026

Questions to ask a web designer before you hire them

Six questions worth asking any web studio before you sign, plus how we answer them on our own projects.

Questions to ask a web designer before you hire them
Author
Te Manihera Woods

By Te Manihera Woods

November 3, 2026

November 17, 2026

Te Manihera is a Full Stack Developer at What IF Web, building web apps, portals and integrations in React, TypeScript, Next.js and Strapi. He worked on Carepatron's site migration.

Table of contents

Before starting a website project, it's worth understanding how ownership works and where your domain is registered. Just as important is what happens to everything once the project is complete.

Every studio has its own way of managing website projects. Some transfer ownership once the final invoice has been paid, while others provide access to different accounts throughout the development process. Neither approach is necessarily a problem, provided the arrangement is clear from the beginning.

There are a few things worth clarifying before you sign:

Question A good answer sounds like A red flag sounds like
Who owns the site? We'll outline ownership and access in our agreement. Once the project is paid in full, ownership transfers to you, along with the relevant assets and handover documentation. We'll figure out ownership and access once the project is finished.
Who updates content? You can, through a CMS we'll train you on. We cover any dev updates. You'll need to contact us whenever you want to change something.
Where is it hosted? We'll explain where your site is hosted, how hosting is managed, what it costs and who's responsible for ongoing maintenance and support. We handle everything. You don't need to know where your website is hosted or what happens if something goes wrong.
What's included? Here's the written scope, including deliverables, revisions, integrations and anything that would incur additional costs. It's a full website. We'll work out the details as we go.
How is success measured? We'll agree on what success looks like based on your website's goals and the work included in the project. We'll build the website, launch it and consider the job done.

Who owns the site, the domain and the content when the project ends?

At What IF Web, we retain ownership of the completed website until the project has been paid in full. Once payment is complete, ownership transfers to the client. We also provide a handover document covering the relevant accounts and logins, so clients know exactly where everything lives.

The important thing is to understand these arrangements before work begins, rather than discovering how ownership and access work when you're ready to move on.

Who updates content after launch, and can we do it ourselves?

Most websites need content updates over time, whether that's publishing a new blog post or updating a service page as the business grows. It's worth understanding how much of this you can manage yourself and when you'll need help from your development team.

A good CMS should make everyday content updates easy, without needing to involve a developer every time something changes. For more complex design or development updates, you'll want to understand what support is available and how additional work is priced.

Before signing a contract, there are a few things worth clarifying:

  • Content management: Which parts of the website can you update yourself?
  • CMS training: What guidance will you receive to help you manage the website?
  • Ongoing support: Who can you contact when you need help with something more complex?
  • Additional costs: How are development changes and ongoing support priced?

At What IF Web, we provide clients with recorded Loom walkthroughs and supporting documentation as part of the handover process. These resources show clients how to manage their website and make common content updates themselves.

We particularly like recorded walkthroughs because they become a reusable resource. Rather than relying on remembering everything from a one-off training session, clients can revisit the videos whenever they need a refresher or share them with someone new on their team.

The goal is to give you the confidence and resources to manage your own website, while knowing there's ongoing support available when you need additional help.

Where is the site hosted, who pays the host, and what happens when something breaks?

Every website needs hosting, but how it's managed can vary depending on the platform and the agency you work with. The specifics of your project also affect the setup.

Some studios have clients manage their own hosting accounts, while others manage hosting on their behalf. Both approaches can work well. What's important is knowing where your website lives and what you're paying for. You should also know who's responsible for keeping it running.

Before starting a project, there are a few things worth clarifying:

  • Hosting platform: Where will your website be hosted? Platforms like Webflow and AWS each have different hosting arrangements.
  • Hosting costs: How much does hosting cost, and is it included in your project or ongoing fees?
  • Account management: Will hosting sit under your account or be managed by the agency?
  • Ongoing maintenance: Who handles updates and monitoring? And who looks after backups and technical issues?
  • Support arrangements: What happens if your website goes down, and who do you contact?

At What IF Web, we work with different hosting environments depending on the requirements of each project. The right setup depends on the technology being used and what the website needs to do.

The important thing is that you understand the arrangement before your website goes live. You should know where it's hosted and what it costs. You should also know who's responsible for keeping it running.

What's the timeline, and what happens when it slips?

Website projects involve several stages, starting with discovery and design, then moving through development and launch. Having a clear timeline helps everyone understand what's happening and what's coming next, with the key completion points along the way.

However, a website project isn't entirely controlled by the agency. Content delivery and approvals can affect how quickly a project progresses, along with access to third-party services.

Before committing to a timeline, it's worth understanding:

  • Project stages: What are the main phases of the project, and what happens during each one?
  • Milestones: When should you expect to see designs and development progress? And when does the working website arrive?
  • Client responsibilities: What content and feedback will the agency need from you, and when?
  • Communication: How will progress be shared, and how will changes to the timeline be communicated?
  • Dependencies: Are there integrations or external services that could affect delivery?

At What IF Web, we break projects into stages so clients have a clear understanding of what we're working on and what we need from them. We also recognise that timelines depend on both sides. If we're waiting on content or feedback, that can affect the next stage of development.

A good project timeline isn't just a launch date. It's a shared plan that outlines responsibilities and milestones, giving everyone a clear picture of how the project will get across the line.

When discussing timelines, make sure you understand what's expected from both sides and how any changes will be handled.

What's included in the price, and what counts as extra?

Website quotes can vary considerably, even when two agencies appear to be offering the same thing. That's because the price depends on what's being designed and developed, and what's included in the overall project.

A quote for a five-page brochure website is very different from a custom web application with user accounts and complex integrations. Understanding exactly what's included helps you compare proposals properly and avoid unexpected costs later.

Before signing, make sure you understand:

  • Deliverables: How many pages and templates are included? Which features are part of the scope?
  • Design: Is the website being designed specifically for your business, or is it based on an existing template?
  • Functionality: Which forms and integrations are included? What CMS features or custom functionality are part of the scope?
  • Revisions: How many rounds of design or content revisions are covered?
  • Additional work: What happens if you want to add features or change the agreed scope?
  • Ongoing costs: Are hosting and subscriptions included? Is maintenance and support charged separately?

At What IF Web, we outline the agreed scope before development begins. This gives everyone a shared understanding of what's being delivered and what's included in the price. It also makes clear what would need to be quoted separately.

It's also important to understand that additional requests aren't necessarily a bad thing. Projects evolve, and sometimes new ideas come up once you start seeing the website take shape. The important part is understanding how those changes affect the scope and cost before proceeding.

Ask for a written proposal that clearly outlines the deliverables and associated costs. The more detail you have upfront, the easier it is to make an informed decision. Our marketing websites service page covers what we typically include in a project.

How will we measure whether the site worked?

A website project shouldn't just be about getting something launched. It should be about delivering a website that achieves what you originally set out to build.

However, what success looks like will depend on the purpose of the website and the work included in the project. For some businesses, that might mean making it easier for customers to find information. For others, it could mean improving internal workflows or creating a better content management experience. Sometimes it's about building a platform that supports future growth.

Before starting, it's worth discussing:

  • Project objectives: What are you hoping the new website will achieve?
  • User experience: How should the website make things easier for your customers or users?
  • Functionality: What should visitors be able to do that they couldn't do before?
  • Technical requirements: Are there specific technical improvements the new site needs to make?
  • Measurement: How will you assess whether the agreed objectives have been achieved?

At What IF Web, we look at success in the context of what we've been engaged to deliver. That might include a more intuitive user experience and a faster-loading site, or streamlined content management and a more flexible technical foundation.

It's also worth recognising that some outcomes depend on work beyond the website itself. Traffic and conversion rates can be influenced by marketing and advertising, or by SEO and AI search strategy. Pricing and wider business decisions play a role too. If those aren't part of the engagement, they shouldn't automatically be treated as a measure of the development team's work.

The best approach is to agree on what success looks like before work begins, so everyone understands what the project is intended to achieve and how the finished website will be evaluated.

About What IF Web

What IF Web is a four-person creative studio in Christchurch, New Zealand, and a Webflow Premium Partner. We've been designing and building websites and web applications since 2022, working with businesses from Christchurch to California.

We believe good websites come from asking the right questions and understanding what a business needs, then building something that goes beyond the expected.

That's why we encourage businesses to ask these six questions before choosing a web design or development partner. They're the same things we consider on our own projects, and we're happy to walk clients through our approach and process before work begins.

Good things happen when you don't do normal.

Frequently Asked Questions

How many revisions should be in a web design quote?

Two to three rounds of design revisions on each key page is a sensible benchmark across the industry. Beyond that, revisions should be quoted as separate work, not absorbed indefinitely into the original scope. A quote with "unlimited revisions" usually means the studio has baked a buffer into the price, which you pay for in the quote whether you use the revisions or not.

Should a web designer provide written references?

Yes, and the ones worth having are current clients you can speak to directly, not just read a quote from on a page. A studio with happy clients will have a short list ready when you ask. A studio without one will usually point you at a testimonials page on the website and hope that does the job for them.

What's a fair deposit for a website project?

A deposit of 30 to 50 per cent at project kickoff is standard across the industry. Full payment upfront is a red flag unless the project is small enough that the full amount is also small. No deposit at all is also a flag, because it usually means the studio hasn't scoped the project tightly enough to carry the risk themselves.

Does a web designer need to be local?

Not strictly, because plenty of good studios work remotely with clients across different time zones. What counts more is whether you can get them on a call quickly when something's urgent, and whether they understand the business context you're operating in. If local presence is a priority for you, say that upfront when you're shortlisting.

What's the difference between a web designer and a web developer?

A web designer owns the design decisions. That means the layout and typography, and how the thing feels when a visitor uses it. A web developer writes the code that turns that design into a working site. In small studios the same person often does both jobs. In larger agencies they're separate seats, and you want to know which seat is answering each of your questions during the pitch.

Still Have Questions?

Contact Us

Got a Crazy Idea? We're All Ears

Reach out, share your story, and Isaac or Tom will get back to you, usually same day. Let’s make some magic together.

Four men posing for a photo in a room with concrete walls and floor, three seated on a blue couch and one standing behind. From left to right on the couch are Jacob in a blue sweater and jeans, Te Manihera in an orange t-shirt and dark pants, and Isaac in a black t-shirt with tattoos on his right forearm wearing brown shoes. Standing behind the couch is Tom, smiling broadly in a light-patterned shirt. Each man has his name written above with an arrow pointing to him.