Questions to Ask a Website Designer Before Hiring

Hiring guidance updated 15 September 2026. Original publication date retained.

What questions should you ask a website designer before hiring?

Start with the deliverable: are you hiring for editable design files, a working website, or both? Then ask who performs the work, what is excluded, how revisions are handled, what your business will own and who supports the site after launch. The fifteen questions below apply to both an independent designer and an agency; adjust the team questions to the size of the engagement.

If you have not found candidates yet, use our guide to finding a suitable website designer. If budget is unclear, separate the designer’s fee from development and recurring costs before comparing proposals.

Extra checks when hiring an independent designer

Ask whether they personally implement the site or work with a separate developer. If the engagement ends at design handoff, confirm editable source files, mobile layouts, components, interaction states and time for developer questions. If it includes a build, name the person responsible for forms, CMS setup, redirects and testing.

Discuss availability and continuity directly. What happens during illness, leave or another client’s urgent deadline? A freelancer does not need to imitate a large agency, but both sides need realistic delivery and backup arrangements. Confirm how licensed fonts, stock images and third-party templates can be used after handoff.

A focused first-call agenda

Spend five minutes explaining the audience, business goal and main customer journey.
Use ten minutes to review one relevant project and the designer’s exact role.
Use ten minutes to clarify scope, content ownership, implementation and revisions.
Finish by confirming budget fit, availability and what evidence or paid discovery is needed next.

This is a suggested thirty-minute agenda, not a rigid rule. Record each answer as evidenced, unconfirmed or outside scope. Ask for a follow-up document where the call leaves important gaps. Do not treat verbal agreement as a substitute for the written proposal.

What a useful answer sounds like

For scope, look for named templates and deliverables rather than “a modern website.” For quality, ask to see how mobile layouts, keyboard use and forms are reviewed. For handoff, ask the designer to show an example of their documentation. W3C’s preliminary accessibility checks offer concrete starting points, but a short check is not a full accessibility assessment.

A provider can reasonably decline unpaid speculative design. You can still request relevant existing work, a clear delivery process and a scoped paid discovery option. Choose based on evidence of fit and delivery responsibility, not only a confident sales presentation.

Published by Nexcey Editorial Team · Researched & Fact-Checked · Editorial Standards.

Choose the agency whose process you can understand. A portfolio is useful, but it cannot tell you everything about delivery. You need to know what is included, who makes decisions, what you will own and how the team handles problems. Ask comparable questions so you can assess more than presentation style.

1. How will you learn about our business and customers?

Look for a proportionate discovery process using stakeholders, customer evidence, analytics, search data, content, and competitive context—not a generic questionnaire alone.

2. Who will work on the project?

Ask for named roles, relevant experience, availability, subcontracting, and who is accountable for decisions. Meet the people who will lead the work. Ensure candidates understand your business requirements clearly by following our guide on how to write a website brief.

3. What exactly is included?

Clarify strategy, sitemap, wireframes, copy, design, development, migration, SEO, analytics, accessibility, testing, training, launch, and support. Record exclusions.

4. What do you need from our team?

Good agencies make client responsibilities visible: content owners, approvals, product data, legal review, subject experts, access, and response times.

5. How do you plan content?

Ask how page purpose, audience questions, copywriting, migration, images, metadata, and governance will be handled. Design cannot wait for vague placeholder content.

6. How do you approach UX and conversion?

Look for task mapping, information hierarchy, proof, prototypes, usability evidence, and meaningful measurement—not cosmetic trends or manipulative tactics. Evaluate agency proposals against realistic industry pricing using our small-business website cost benchmarks.

7. How will accessibility be addressed?

Request the target standard, design and development practices, testing methods, known limitations, and remediation responsibility.

8. What is your technical and SEO process?

Ask about crawlable links, rendering, metadata, canonicals, structured data, sitemaps, redirects, performance, staging controls, and post-launch monitoring.

The answer should connect requirements, editing, integrations, security, ownership, support, and total cost—not agency habit alone.

10. How will performance and security be maintained?

Ask about hosting, updates, dependencies, backups, monitoring, incidents, third-party scripts, Core Web Vitals, and responsibility after warranty.

11. How are feedback and changes managed?

Clarify milestones, decision-makers, revision rounds, change control, communication channels, and what happens when scope or timing changes.

12. What will we own?

Confirm domain, accounts, data, content, design source files, code, licenses, documentation, analytics, and the right to move providers.

13. How do you test and launch?

Expect device, browser, accessibility, form, integration, analytics, content, redirect, performance, backup, and rollback checks with named owners.

14. What support follows launch?

Ask about warranty, maintenance, response levels, content support, reporting, optimization, training, and costs for typical future changes.

15. Can you explain a relevant project honestly?

Request the initial problem, constraints, decisions, agency contribution, client contribution, result, and what the team would do differently. Avoid case studies that imply unsupported causation.

Practical checklist

Written brief shared with every agency
Required roles and services defined
Comparable scope and assumptions obtained
Relevant references checked
Platform and ownership understood
Accessibility and SEO methods evaluated
Testing and launch process documented
Ongoing costs compared
Risks and exclusions visible
Weighted scorecard completed

Use a proposal scorecard instead of choosing by presentation quality

Good agencies are often good at selling, so a polished proposal is not evidence that the delivery process is equally strong. Score proposals against the things that will matter after the kickoff.

Dimension	What strong evidence looks like
Problem understanding	The proposal reflects your users, business model and constraints rather than repeating your brief.
Relevant proof	Case studies explain the problem, decisions and outcome—not just screenshots.
Scope clarity	Pages, templates, integrations, content responsibilities and exclusions are explicit.
Technical ownership	Hosting, accounts, code, analytics, domains and handover responsibilities are defined.
QA and launch	Testing, redirects, analytics validation, backups and post-launch support are included.
Communication	You know who leads the project, how decisions are recorded and how scope changes are handled.

Questions to ask an agency’s previous client

If the project is important enough, ask for a reference whose engagement resembles yours. Keep the call short and ask questions that are difficult to answer with marketing language:

What surprised you after the project started?
How did the team respond when something went wrong?
Were deadlines missed, and if so, how were they communicated?
Did the final cost differ materially from the proposal?
Could your internal team maintain the site after handover?
Would you hire the same agency again for the same type of project?

Red flags before you pay a deposit

Be cautious when an agency cannot explain what you will own, promises a guaranteed search ranking, avoids naming the platform or hosting arrangement, refuses to document scope, or relies on a proprietary setup that only they can access. Another warning sign is a portfolio with beautiful homepages but no evidence of mobile behavior, content-heavy pages, forms, checkout, accessibility or post-launch outcomes.

Price still matters, but risk matters too. A more expensive agency can be cheaper overall if it reduces rework, missed requirements and operational dependency. Conversely, a large agency is not automatically safer; the best fit is the team whose process and evidence match the complexity of your project.

A 45-minute discovery exercise before contacting agencies

Write one page with five headings: business goal, primary audiences, critical user tasks, required systems, and constraints. Under constraints, include launch deadline, internal approval process, content availability, legal/compliance needs, hosting restrictions and a realistic budget range if you can disclose one.

Then list what you are not buying. Perhaps logo redesign is out of scope, photography will be handled internally, or CRM replacement is a separate project. Agencies can price more accurately when boundaries are visible. This also gives you a common brief so proposals are easier to compare.

Ask to see the boring parts

Portfolio galleries naturally highlight hero sections. Ask candidates to show a content-heavy page, a mobile navigation state, a form with validation, an error or empty state, the CMS editing experience, and—if relevant—a checkout or account flow. These screens reveal whether the team designs systems or only presentation pieces.

Clarify what happens after launch

Who monitors the site during the first days after deployment?
How are launch defects distinguished from new feature requests?
What backup and rollback options exist?
Who owns recurring software licenses?
Will you receive source/design files and administrator access?
Is maintenance mandatory, optional, or handled by your team?

Choose for the project you actually have

A complex ecommerce migration may justify a specialist team with integration and QA depth. A focused brochure site may be better served by a smaller studio with strong senior involvement. Do not pay for organizational complexity you do not need, and do not under-buy expertise when failure would disrupt revenue or operations. Fit is a risk-management decision, not a prestige contest.

Write down why you selected the agency

After choosing, keep a short decision note listing the evidence that mattered: relevant project experience, named delivery team, scope clarity, technical ownership, communication model and accepted trade-offs. This prevents later disagreements from rewriting history and gives the kickoff team context about what was promised. It also makes the next agency selection easier because you can compare what you valued before the project with what actually mattered during delivery.

Frequently asked questions

How many agencies should I contact?

A focused shortlist of three to five qualified candidates usually creates useful comparison without wasting everyone’s time.

Should I choose the cheapest proposal?

Choose the best value and fit for the required outcome, scope, risk, and ownership model. A low total based on missing work is not comparable.

Do I need a budget before contacting agencies?

A range helps agencies recommend a realistic approach. Pair it with priorities and invite options for minimum, recommended, and phased scope.

What is a warning sign?

Vague deliverables, guaranteed rankings, hidden ownership, no discovery, no testing detail, pressure to sign, or refusal to explain recurring costs deserve scrutiny.

Take the next step

Discuss your website project with Nexcey.

Sources & further reading

Ask for evidence without demanding free project work

A relevant walkthrough can show how an agency approached a problem, what its contribution was and what it learned. You do not need a full unpaid design proposal to evaluate that reasoning. Ask for an explanation of a past process and a clear outline of how your project would be scoped.

If a claim matters to the decision, ask what supports it. Clarify whether a result describes the agency’s work alone or a wider business effort. Before signing, resolve ownership, recurring costs, change requests and post-launch support in writing. Friendly communication helps, but it does not replace an agreed scope.

A scorecard for comparing agency proposals

Choose weights before seeing the proposals. This fictional model prioritizes delivery evidence and ownership over presentation polish. Score each criterion from one to five, multiply by its weight and compare the reasons behind the totals; a numeric score is a conversation aid, not an objective guarantee.

Criterion	Example weight
Relevant problem-solving evidence	30%
Scope, testing and launch process	25%
Ownership and maintainability	20%
Communication and responsibilities	15%
Comparable total cost	10%

Continue with a related guide

Have a correction or a question? Get in touch with the team.

Questions to Ask a Website Designer or Agency Before Hiring