How to choose a web design company: 12 questions

Choosing a web design company should begin with your business goal, not with a comparison of colours in agency portfolios. A capable partner needs to understand who you sell to, what the website should achieve and how its results will be measured.

Price still matters, but it becomes comparable only when each proposal describes the same scope. One quote may include custom design, content support, analytics and post-launch care. Another may cover only the setup of a ready-made theme. The totals can sit next to each other in a spreadsheet while representing very different products.

Define what the new website must achieve

Before contacting potential partners, write down the website's primary goal. It might be generating enquiries, selling online, accepting bookings, presenting projects or supporting sales conversations that begin through referrals.

Also clarify:

1. who will use the website,
2. which action visitors should take,
3. which materials are already available,
4. who will update the content,
5. which timeline and budget are realistic.

You do not need a complete technical specification. A clear starting point is enough to see whether a potential partner asks useful questions. If your materials are not ready yet, start with our guide to preparing content for a business website.

12 questions to ask a web design company

1. Which business goal will the project support?

A company should not begin with the number of pages or a preferred technology. It should first ask about your offer, customers, competitors and traffic sources. Without that context, you may receive an attractive website that does not guide visitors towards a clear decision.

2. Can you show relevant live projects?

Ask for working URLs rather than screenshots alone. Open the websites on a phone and check their speed, text readability, forms and routes to contact. Experience in your sector can help, but the ability to solve different problems is more important than repeatedly using one layout.

Check whether each case explains the actual scope. A polished image does not reveal who handled the strategy, content, design, development and optimisation. You can review examples of our work in the AMCompany portfolio.

3. What exactly does the proposal include?

The quote should define the number and type of views, design scope, responsive implementation, forms, CMS, integrations, analytics, SEO foundations, testing and launch. Ask which items are optional and which changes may increase the price during delivery.

If you are comparing budgets, see how much a business website costs. A number without a defined scope tells you very little.

4. Who is responsible for structure and content?

A website should not be designed around random placeholder copy. Its layout depends on the offer, sales arguments, customer questions and visual materials. Establish whether the company plans the information architecture, edits your copy, provides copywriting or expects finished content from you.

5. Why are you recommending this technology?

WordPress, Next.js, Shopify and WooCommerce address different needs. The recommendation should be connected to functionality, content editing, maintenance costs and future development. Be cautious when the only explanation is that the company uses the same platform for every project.

Our comparison of Next.js and WordPress explains the practical differences.

6. Will the design be custom?

A ready-made theme can be a sensible choice for a limited budget when this is stated clearly. The problem begins when a template is sold as a fully custom project. Ask which elements will be created specifically for your brand and what limitations come with the chosen foundation.

7. What does SEO preparation include?

The phrase “SEO-friendly website” is too broad. Ask whether the scope covers heading structure, metadata, URLs, internal links, indexation, an XML sitemap, redirects from the old website and structured data. Clarify whether keyword research and content creation are separate services.

No company can honestly guarantee a specific Google ranking. It can provide sound technical foundations, a useful structure and a plan for continued improvement.

8. How will mobile usability, performance and accessibility be tested?

Ask how the team tests different screen sizes and browsers. Before launch, forms, keyboard navigation, colour contrast, alternative text and key performance indicators should all be reviewed.

Do not focus only on one score from one testing tool. Layout stability, readability and the ease of completing the primary action matter as well.

9. How will the website's results be measured?

If the goal is lead generation, you need to know where enquiries came from and which pages contributed to the decision. Agree on analytics, form events, phone link tracking, consent settings and connections with advertising platforms.

Traffic alone does not show whether a website supports sales.

10. What is the process for feedback and revisions?

Understand the project stages, responsibilities, method of sharing materials and number of revision rounds. A clear process prevents a situation in which the client sees the complete website only shortly before launch.

Ask what happens if materials arrive late or the scope changes during the project.

11. What happens after launch?

Clarify the warranty period for defects, update policy, backups, monitoring and the cost of future changes. If the website uses paid tools or plugins, check renewal dates and licence ownership.

Support does not always require a monthly retainer. The important point is to define post-launch responsibility before the website goes live.

12. Who owns the domain, accounts and finished project?

The domain, hosting, analytics, Search Console and other accounts should be registered to the client or transferred at project completion. The agreement should also cover rights to the design, code, images, fonts and paid licences.

Request a list of credentials and assets that you will receive. This prevents a future change of supplier from disrupting your business.

A simple way to compare proposals

Instead of choosing on price alone, score every proposal in five areas:

1. understanding of the business goal,
2. clarity of scope and costs,
3. quality of process and communication,
4. technical quality and testing approach,
5. ownership and post-launch support.

Give each area a score from 1 to 5 and add a one-sentence explanation. This simple table often reveals that a low quote is cheaper because it leaves out important work.

Warning signs before you sign

Take extra care when a supplier:

• gives a final price without understanding the scope,
• guarantees the first position in Google,
• cannot explain its technology choice,
• shows mock-ups but no working websites,
• does not define ownership of the project and accounts,
• avoids questions about testing, security or post-launch care.

One missing answer does not automatically end the conversation. It should, however, be resolved before you pay a deposit.

Agency or freelancer?

A freelancer may offer direct communication, flexibility and a lower cost. An agency can often combine strategy, design, development, content and marketing more easily. Neither label guarantees better work.

Choose the model that fits the project's complexity and the level of responsibility you need. What matters is who will actually deliver the work, how risks are communicated and whether the scope supports your goal.

A good partner helps you make the right decision

A reliable web design company should not push you towards the largest possible project. It should explain what is needed now, what can be added later and what each decision means for cost and maintenance.

If you are planning a website or an online store, review AMCompany's services. You can also tell us about your project. We will first clarify the goal, required functions and realistic scope before preparing a detailed proposal.