How to choose a web development agency

Choose a web development agency based on how well it understands your business goals, what past work and case studies it can show, whether it designs from scratch or adapts templates, how it handles the technical build, and who owns the code, design and content once the project is done. It also matters whether it builds in SEO, GEO and AEO during development and what support it offers after launch. Comparing quotes on paper misses what actually decides whether a project succeeds: the process, the expertise and the relationship after signing. Below we cover what to look for on each point, plus a list of questions to ask before you sign.

What a good agency needs to understand before quoting

The first sign of a serious agency is the questions it asks before it quotes. An agency that sends a quote with a page count after a single email is treating you as an order, not a project. A good agency first wants to understand what your website needs to achieve.

Before quoting, it needs to know at least this: who your customers are and how they make decisions, how you get inquiries today and where the process gets stuck, which services or products matter most to you, who will edit the site after launch, and which systems the site needs to connect to, for example a CRM, ERP or booking system. Structure, scope and the technical approach follow from those answers, not the other way around.

At 4tech we usually start a project with an initial conversation and a short document summarizing the goals, target audiences, key pages and technical requirements. You confirm this document before the quote, so both sides know what is being built. For more complex projects, such as a B2B ecommerce portal or a store connected to several systems, it pays to review the structure, goals and technical requirements first, and only then talk about scope.

Past work and case studies

Past work is the easiest evidence to verify. But a gallery of screenshots isn’t enough. The real questions are: do these sites still work, how fast are they, how do they behave on a phone, and were they built for challenges similar to yours?

How to check past work

• Open at least three of the agency’s sites on your phone and try using them as a customer would.
• Check the speed with PageSpeed Insights and see whether the sites pass Core Web Vitals.
• Look at how old the site is. A site that still works well after two years tells you more than one that just launched.
• Ask to speak with one or two clients and find out what working together was like after launch.
• Look for case studies that describe the challenge, the solution and what changed, not just the sentence “we built a website”.

A case study is more reliable evidence than a logo. It shows whether the agency thinks about the business result or only about the deliverable. On the 4tech work page we list the project type, the technologies used and a link to the live site for each project, so you can judge for yourself.

Custom design or a template

Some agencies like to blur this one. For some, “custom design” means a chosen template with the colors and logo swapped. For others, it means a designer starts with a blank canvas and your content. The difference is big, both in the result and in what you can do with the site later.

A template isn’t a bad choice in itself. For a simple brochure site with a few pages, it can be all you need. The trouble starts when the site is part of how you sell and has to stand out from competitors who may be using the same template. Then the template limits structure, speed and recognizability.

Ask the agency directly: will you buy a template or design the site for me? Will I get wireframes and design mockups to approve before development starts? What happens if, a year from now, I want a new type of page the template doesn’t support? The answers show how the agency works. On custom projects we design websites from the ground up and build them on WordPress, because that way the site follows your content and goals most directly.

Technical build and ownership

You can’t see the technical build, but it decides how the site will work three years from now. Ask which system the site will be built on, why that one, how many plugins will be used and who takes care of updating them. With WordPress, the key difference is between a site designed around your process and a template the agency merely adapts.

Many clients ask about ownership too late. At the end of the project you should own the domain and have access to the hosting, administrator access to the system, the theme’s source code and all design files. If the agency builds the site on its own closed platform or on a subscription product where the site goes dark when you part ways, you should know that up front.

At 4tech we build custom sites on WordPress; once the project is paid for, the code, design and logins pass to you, which we set out in the contract. We also make sure another team can take over the site if you ever decide to switch. That isn’t a sign of mistrust. It’s normal practice in a fair working relationship.

What the technical build should cover

• A responsive layout, tested on real devices, not just in a simulation.
• Speed optimization as part of development, not as a fix afterwards.
• Security settings, an SSL/TLS certificate (HTTPS) and automatic backups.
• Accessibility: contrast, keyboard navigation, form labels.
• Integrations with systems you already use, or AI integrations if the project calls for them.
• Documentation and short training on editing content.

SEO, GEO and AEO from the start of development

SEO (search engine optimization) isn’t a service you add after launch. The URL structure, heading hierarchy, speed, structured data and redirects from the old site are all decided during development. If an agency mentions SEO only as a separate line item for after launch, the foundation will be missing.

Today SEO also includes AI search visibility: GEO (generative engine optimization) for AI assistants such as ChatGPT, Gemini and Perplexity, and AEO (answer engine optimization) for direct answers, for example in Google AI Overviews. In our experience, these systems more often cite pages with clear definitions, structured answers and consistently named entities. An agency that understands GEO and AEO will structure content differently from one that only knows classic SEO.

Ask whether the agency will prepare a redirect plan for the redesign so you keep your existing rankings. Ask whether structured data will be part of the build. Ask how the content will be written so AI assistants can understand it. If you don’t have a clear picture of where your current site stands, a good first step is a free SEO, GEO and AEO check, which you can request before you decide anything about a redesign.

Support after launch

Launch isn’t the end of the project. It’s the start of the period when the site has to work. That makes post-launch support one of the most important questions, and the one clients ask least often. You want to know who takes care of system and plugin updates, how quickly the agency responds when something breaks, whether there’s a maintenance agreement and what it covers, and whether you’ll be able to edit content yourself.

Good support also includes monitoring: analytics, Search Console, downtime alerts. If nobody checks after launch whether the forms still work and the site still gets traffic, problems surface months too late. At 4tech, after launch we handle updates, backups and upgrades within a scope and response time agreed in advance and written into the quote. We treat the site as a tool that needs maintaining, not a finished product.

Good signs and warning signs at a glance

Questions to ask before working together

Take this list to the meeting. The answers will tell you more than the quote itself.

1. What information do you need from us before you prepare a quote?
2. Which three past projects are most similar to ours, and why?
3. Will the design be custom or based on a template? What will we approve, and when?
4. Which system will the site be built on, and why is it the right choice for us?
5. How many plugins will be used, and who will update them?
6. Who owns the code, design, content and logins after the project is finished?
7. How will SEO, GEO and AEO be included in development? Will there be a redirect plan?
8. How will tracking be set up: analytics, events, Search Console?
9. Who will write the content, and who will structure it for search engines and AI assistants?
10. What does post-launch support cover, and what is the response time?
11. What happens if, a year from now, we decide to switch agencies?
12. Who will be our contact person during the project and after it?

If you’re planning a new website or a redesign of your current one, tell us about your project. We’re happy to answer every question on this list.