How to choose a web design company: 12 questions to ask before you sign anything

Choose a web design company based on fit, proof, process and ownership—not the prettiest homepage or the lowest quote.

Reviewing portfolios, prices, testimonials and experience is sensible, but not enough. A polished portfolio cannot tell you who writes the copy, what happens when scope changes, whether old URLs will be redirected or whether you can take the site elsewhere.

You do not need to become a web expert. You need clear answers about what will be delivered, how you will judge it and who is accountable when something changes.

Before you contact anyone

Write one sentence describing the site’s job. Not “look modern.” Use a verb and an outcome: “help homeowners request an estimate,” “let patients choose the right service and book,” or “reduce calls about order status.”

Then note:

the two or three audiences the site must serve;
the most important action for each audience;
what is wrong with the current site, if one exists;
required functions such as booking, payments, logins or integrations;
who can supply copy, photography, product data and approvals;
a realistic budget range and a date that matters;
what success could be measured: qualified enquiries, bookings, sales or fewer support calls.

This is a starting brief, not a solution. A good provider should challenge it. If you are deciding between a builder and a bespoke build, read Template or custom?. For budget context, see what a small-business website should cost.

Which kind of provider might fit?

Provider	Often fits when	Check before choosing
Freelancer	The scope is contained and one person’s skills cover most of it	Availability, backup cover, specialist gaps and support after launch
Small studio	You want direct access to the people doing the work and the project needs a few disciplines	Capacity, named responsibilities and what is handled by partners
Agency	The site is a major channel with many stakeholders, integrations or parallel workstreams	Who is actually assigned, management overhead and continuity after launch
Hosted builder	The site is a straightforward brochure or shop and speed, cost and self-service matter most	Platform limits, recurring fees, export options and how much customization you truly need

None is automatically safer or better. A freelancer may excel on a focused site; an agency may earn its overhead when coordination is the hard part. WordPress may suit a publishing team; a hosted template may suit a five-page site. The provider should explain why its shape fits your job.

12 questions to ask a web design company

1. What do you think this website needs to accomplish?

Why it matters: This tests whether the provider understood the business before prescribing pages or software. Google gives similar advice when hiring an SEO: look for someone interested in what makes the business different, its customers and how search can help—not someone leading with a standard package (Google Search Central).

A strong answer sounds like: “The primary job is to turn service-area visitors into qualified estimate requests. We should make the service boundaries and minimum job size clear before the form.” It names an audience, action and constraint.

Follow up if you hear: “We will make it modern, responsive and SEO-friendly.” Those are baseline qualities, not a business objective. Ask what the homepage must help a visitor understand or do.

2. What are you proposing, and why is it the right level of solution?

Why it matters: A five-page brochure, a content-heavy site and a customer portal are different purchases. The platform should follow the job. It should not be chosen solely because it is the only tool the provider sells.

A strong answer sounds like: “A hosted builder will cover these requirements and let your team update it. Custom development would add cost without removing a real constraint.” The reverse can also be strong when the provider can name the workflow, integration or content structure that a template would fight.

Follow up if you hear: “We only build custom,” “WordPress is always best,” or “templates are bad for SEO.” Ask which requirement rules the alternatives out and what trade-off you are accepting.

3. Can you walk me through a relevant live project?

Why it matters: A screenshot proves visual taste at one viewport. It does not show whether the provider understood the problem or whether the finished site works.

Open the live site on your phone. Find the offer and next step without coaching. Enlarge the text, use the menu and try keyboard navigation on desktop. Test representative pages with PageSpeed Insights. Google’s LCP guidance defines a good result as 2.5 seconds or less for at least 75% of visits, but one lab test is only a clue (web.dev).

A strong answer sounds like: “Customers could not tell which service they needed. We reorganized the content around three situations and measured completed booking starts.” It separates the business problem, the design decision and any measured outcome.

Follow up if you hear: only awards, adjectives or screenshots. Ask what the provider personally did, what constraints shaped the work and whether claimed results were actually measured.

4. What is included, excluded and assumed in the price?

Why it matters: Two identical totals may cover different projects. Count page types, not just pages. Confirm discovery, copy, design, development, integrations, content entry, testing, migration, launch, training and support. List third-party costs such as hosting, plugins, imagery and payment fees.

A strong answer sounds like: a written scope with deliverables, exclusions, client responsibilities, recurring costs and acceptance criteria. It says whether the price is fixed, capped or hourly and when payments are due.

Follow up if you hear: “Everything you need is included.” Ask for the exclusions and assumptions in writing. For a more detailed view of cost drivers, compare the proposal with CMT Web’s pricing guide.

5. Who is responsible for content and approvals?

Why it matters: Copy, photography and data often become the real schedule. “Client provides content” might mean you owe fifty finished pages before design begins. “Copy included” might mean light editing, not interviews and original writing.

A strong answer sounds like: a content list with an owner and due date for every item. It explains who interviews subject-matter experts, writes, fact-checks, sources images, handles licenses, enters content and gives final approval.

Follow up if you hear: “We will sort content later.” Ask to see the content workflow and what happens to the schedule if an asset is late.

6. What happens between kickoff and launch?

Why it matters: A process should expose misunderstandings while they are cheap to fix. Know the milestones, what you review, who decides and how progress is shown.

A strong answer sounds like: discovery produces an approved brief and sitemap; design uses real content; a working staging site appears before launch; testing has a named owner; and each approval has a date. Communication has a cadence and one accountable contact.

Follow up if you hear: a long silent build followed by a reveal. Ask when you will first see the structure, content, mobile design and working site—and who you contact when the usual contact is unavailable.

7. How do revisions, new requests and delays change the plan?

Why it matters: “Unlimited revisions” sounds generous but does not explain how decisions end. Change control is not a trap when it is visible; it is how both sides distinguish correcting agreed work from adding new work.

A strong answer sounds like: a named number of feedback rounds, a definition of a revision, one consolidated feedback owner, and written approval of any added cost or time before work begins. The timeline shows client dependencies and what happens if either side misses a date.

Follow up if you hear: “We are flexible” without a mechanism. Ask for a hypothetical: “If we add a second location and booking integration after design approval, what happens next?”

8. How will you protect our existing search visibility during the redesign?

Why it matters: A redesign can change URLs, content, internal links and metadata. Google recommends mapping old URLs to their new destinations, using permanent server-side redirects where possible, testing them, submitting the new sitemap and monitoring both sites in Search Console (Google Search Central).

A strong answer sounds like: “We will export current URLs and search data, preserve valuable content, create a page-to-page redirect map, remove staging blocks, verify canonicals, submit the sitemap and monitor indexing after launch.” It also states what ongoing SEO is—and is not—included.

Follow up if you hear: a guaranteed ranking, “SEO plugin installed,” or no migration plan. Google explicitly warns that nobody can guarantee a number-one ranking and recommends asking providers to explain every change they make (Google Search Central).

9. How will you test performance, accessibility and security?

Why it matters: These are practices, not badges. Automated checks catch only part of the job. WCAG 2.2 provides testable accessibility criteria and notes that conformance testing combines automation with human evaluation (W3C).

A strong answer sounds like: testing on real phones and browsers; keyboard and screen-reader checks; labeled forms, visible focus and adequate contrast; image and script performance budgets; HTTPS; spam controls; least-privilege access; software updates; backups and a restore procedure. CISA’s basic security guidance includes multifactor authentication and prompt software updates (CISA).

Follow up if you hear: “The platform handles all of that” or a perfect automated score offered as proof. Ask which manual tests are run, who fixes failures and whether any accessibility standard is named in the contract.

10. What will we own and control?

Why it matters: Confirm control of the domain, hosting, code, repository, CMS, data, content, design files, analytics, Search Console and third-party licenses. Copyright, account access, usage rights and the practical ability to move are not the same.

A strong answer sounds like: the domain is registered to your business in an account you control; your organization is the owner or primary administrator of critical services; handover includes current source and credentials; and any non-transferable licenses are listed. ICANN defines the registrant as the person or entity contracting with the registrar and managing the domain settings (ICANN).

Follow up if you hear: the provider must remain the domain registrant, account owner or sole administrator. Ask for the exact export, transfer process, fee and timeframe.

Discuss ownership and exit before launch. That is when both sides have leverage and goodwill, and when accounts can still be created correctly. At launch, a missing registrar login or non-transferable plugin is no longer contract language; it is an operational dependency.

11. What do hosting, maintenance and support cover?

Why it matters: Hosting, maintenance and support are different. Maintenance may include updates, monitoring and backups; support may cover content changes or only incidents.

A strong answer sounds like: separate prices and service boundaries; backup frequency and retention; restore responsibility; monitoring and response targets; update policy; included change time; renewal terms; cancellation notice; and a plain description of what happens after an urgent report.

Follow up if you hear: “managed hosting” without specifics or twelve months of vague maintenance hidden in the build price. Ask what a normal request costs, what an emergency looks like and how you leave. CMT Web describes its own boundaries on the services page; use that level of specificity as the test, whoever you hire.

12. What will be measured at launch, and what does handover include?

Why it matters: Page views do not tell you whether the site does its job. Google Analytics lets important actions be marked as key events, so the measurement plan should name actions such as form completions, calls, bookings or purchases (Google Analytics Help).

A strong answer sounds like: a launch checklist covering forms, redirects, analytics consent, key events, Search Console, backups and rollback; then training, documentation, account access and a review after real traffic arrives. Baseline data and post-launch results are kept separate.

Follow up if you hear: “Analytics is installed.” Ask which decisions the reporting will support, who validates each event and what will be reviewed after 30 or 60 days.

How to compare two proposals that do not describe the same thing

Do not compare the totals yet. Normalize the work first.

Create rows for discovery, page templates, copywriting, CMS setup, integrations, content entry, redirects, accessibility testing, analytics, training, warranty, hosting and maintenance. Mark each included, excluded, allowance, client responsibility or unclear.

Then price the gaps. If Proposal A includes copy for ten pages while Proposal B says “content supplied by client,” the difference is a second project assigned to you. If one includes a redirect map and the other does not, ask for it before comparing.

Finally, compare risk allocation:

Is the price fixed, estimated or hourly?
What assumptions can reopen it?
What counts as acceptance?
Who carries the cost of rework when an agreed requirement is missed?
What recurring fees begin at launch?
What does cancellation require, and what do you receive on exit?

The better proposal is the one you can explain without the salesperson in the room.

Copyable web design provider scorecard

Score each item 0 (missing), 1 (partial or unclear) or 2 (specific and written). Add notes before adding the total.

Criterion	Score (0–2)	Evidence or concern
Understands the site’s business job
Recommends an appropriate solution
Shows relevant live work and explains decisions
Defines scope, exclusions and recurring costs
Assigns content and approval responsibilities
Names milestones, people and communication rhythm
Explains revisions, changes and delays
Provides SEO migration and launch checks
Defines accessibility, performance and security testing
Gives you account control, handover and workable exit terms

Treat the total as a conversation aid, not a machine for choosing. A score below 14/20 means too much material risk is still unclear. A high score does not rescue poor fit, weak work or communication you already distrust.

How to choose a web design company with confidence

The right provider is not necessarily the biggest, cheapest or most technically elaborate. It is the one whose proposed solution fits the job, whose live work survives inspection, whose process makes responsibility visible and whose terms leave you in control.

That is how to choose a web design company without pretending you can predict every design decision in advance: make the important risks discussable before you sign.

You can review CMT Web’s work, how the studio operates and what it offers. If you want a read on your brief or proposals, send them over. You will get a straight answer—including if a freelancer, agency or template is the better fit.