How to Choose a Web Agency — 7 Criteria

How to understand what you actually need

Before requesting a quote, describe what needs to change in your business. For a company website, this could mean more high-quality enquiries. For an online store — accurate stock levels, card or cash-on-delivery payments and automatic waybill creation. For a B2B company — a catalogue, quote request form and transfer of leads to the CRM.

Also write down the constraints: languages, deadline, content, payments, inventory, invoicing, internal systems and who will maintain the website. If you do not know all the answers, a good agency will help you clarify them. It will not send you the same package whether you sell services, products or work with field teams.

What are the seven criteria for choosing a web agency?

Does it have real projects similar to yours?

A portfolio is valuable only if you can verify what is behind it. Open several websites on a phone and a computer. Submit a form, search for a product, explore the filters and check whether the main pages load properly. Also see how the website looks on Google, not just on its homepage.

Look for similar complexity, not necessarily the same industry. A service website with a contact form is a different project from a store with a catalogue, filters, courier delivery, inventory and cash on delivery. For a store, look specifically at what is included in online store development.

Ask to see a project that involved a difficult integration or an unclear process. Ask what was dropped from the original plan and how changes were managed. This conversation reveals more than a gallery of attractive homepages.

Does it offer the right technology, rather than its favourite technology?

WordPress, a ready-made template, a custom web system and Next.js are not inherently good or bad. The question is which option makes sense for your team, way of working and future changes. A company that publishes news frequently and has standard needs may work well with WordPress. A business with roles, inventory, invoices, ERP, CRM and API integrations will probably need a specialised system.

Ask who will own the code, where it will be stored, how backups are made and whether another developer can take over the project. If the agency offers every client the same platform without asking about their processes, that is a sign of a template-driven approach.

For a more complex project, ask for a diagram showing the connections between the website, payment system, courier, ERP, CRM, telephony and notifications. This will show whether the agency understands how data moves, rather than just the visual side.

Is there a clear process with approvals at each stage?

A standard project goes through requirements clarification, structure, design, development, testing and launch. At every stage, you should know what you are approving and what comes next. Verifiable results matter more than words such as “milestone” or “agile”.

Ask how changes are managed. If you add a new language, catalogue or ERP connection, is that additional work? How is it documented? How do the deadline and price change? These questions should be answered before the contract is signed.

Do they understand SEO and enquiry tracking?

SEO is not a plugin installed at the end. The structure should already determine which services and categories will have their own pages, how they will be linked to one another and what your customers are searching for.

The technical foundation includes a mobile version, clear URLs, redirects, headings, speed, structured data and tracking. Contact forms, phone calls and store orders should be visible in analytics. Otherwise, you will know how many visits you get, but not which channels generate business.

If SEO is important, ask for a specific scope: structure, technical tasks, content and measurement. Compare what SEO optimisation includes instead of accepting a promise of “the first page” with no conditions.

How does the agency communicate and who is responsible?

Ask who leads the project, who makes the technical decisions and who you should contact when there is a problem. Having one contact is convenient, but one person should not be selling, designing, programming and maintaining everything without a clear team behind them.

Clarify where tasks and feedback are kept. Email may be enough for a small website. A store or custom system needs documented tasks, priorities, deadlines and a history of changes. Do not leave decisions about deadlines and prices only to phone conversations.

Ask to speak to the person who will be involved after the sale. If responses are quick before the contract is signed, but nobody can explain who will work on the project afterwards, the risk is real.

What does post-launch support include?

After launch, there are still updates, backups, security checks, content changes and sometimes urgent issues with payments, forms or integrations. Clarify who is responsible for the hosting, domain, SSL certificate and access credentials.

Ask what “support” means. Are minor text changes included? Is there a limit? What is the response time for a blocked store and for a routine request? If you already have a website from another company, check the terms for support for an existing website.

For a website with critical operations, ask for written service levels. For a small company website, lighter monthly support may be enough. Do not pay for a contract whose services nobody can describe in concrete actions.

Is the proposal transparent, and do the assets remain yours?

A useful proposal separates what is required from what is recommended. It should clearly list the pages, features, integrations, content, migration, testing, hosting and support. It should also be clear what is not included.

The domain, hosting, analytics, advertising accounts and data should be under your company’s control. The terms covering the code, design and content should be set out in the contract, including how you will receive access credentials when the engagement ends.

Don’t compare only the final price. Compare the scope, analysis, testing approach, acceptance process and post-launch terms.

How much does a web agency cost?

The price depends on the scope, how ready the content is, the number of language versions, the design and the integrations. An estimate is meaningful only when you are comparing like-for-like requirements.

If the content and product data are ready, the work is more predictable. If the agency needs to clarify processes, migrate a catalogue or connect several legacy systems, these activities should be listed separately in the proposal.

How can you compare two proposals without making the wrong choice?

1. 01
   Describe the process and the outcome

   Map out how a customer reaches an enquiry or places an order, and what needs to happen inside your company afterwards.

2. 02
   Send the same requirements to everyone

   Give all agencies the same information: pages, features, integrations, languages, deadline and the person responsible for approval.

3. 03
   Ask the same questions

   Ask about the technology, ownership of the code, SEO, measurement, support and charges for changes.

4. 04
   Check live projects

   Open the websites on a phone, use their main function and ask for an explanation of a project with similar complexity.

5. 05
   Compare the risks

   Note what is unclear, who makes the decisions and what will happen if there is a delay or a change in requirements.

6. 06
   Document the agreed scope

   Describe the features, deadlines, payments, access credentials, acceptance and support in the contract.

What signs show that you should continue your search?

• You receive a final price with no description of the features.
• They promise first place on Google or a specific number of sales without any analysis.
• They cannot show live projects or explain their role in them.
• No one asks about your processes, products, inventory or sales method.
• It is unclear who owns the domain, code, advertising accounts and data.
• Support is described only as a “guarantee”, without deadlines or specific actions.
• They start development before the content and acceptance criteria have been agreed.

When is an agency a better choice than a freelancer or a website builder?

A freelancer may be a sensible choice for a small website with a clearly defined scope and one type of work. A website builder can also do the job when you want to test an idea quickly and do not need specific integrations.

An agency makes sense when the project involves design, development, SEO, content, advertising or support from several specialists. Do not choose based on the “agency” label. Choose the team that can take on the risk that matters to your business — accurate inventory, courier integration, quality enquiries, CRM integration or a secure internal system.

What should you ask at the first meeting?

• Which parts of the project do you consider the riskiest, and why?
• How will we know that the website is ready to go live?
• Who will write the content, and who will add the products?
• How will we track calls, forms and orders?
• What happens to access and data if we stop working together?
• What costs remain after launch?
• Can you show us a similar project and explain what you did for it?