How to choose a web agency? 7 questions you must ask

A beautiful portfolio isn't enough. Before signing with a web agency, ask these 7 questions — they'll save you from wasting money and time.

Key takeaways

Why isn't a beautiful portfolio enough to choose an agency?

A portfolio is a starting point, not a decision. Every agency shows its best 10% of projects, while the difficult ones stay hidden. You never see the build that ran three months late, or the client who paid a premium and got a site loading in eight seconds.

In my experience the portfolio answers one question only: can they design something that looks good? It says nothing about deadlines, code ownership, support costs or whether the finished site actually ranks and converts. Those are the things that decide whether the project earns its money back.

So treat the portfolio as a filter for taste, then dig into the operational reality. The seven questions below each expose a specific risk that costs you money or time after the contract is signed. Ask them before you pay a deposit, not after.

Do I actually own the code and accounts?

Yes, you should own everything: code, database, domain and hosting accounts. Some agencies keep your site on "their" hosting or a proprietary CMS, so the day you leave, you lose the lot, or you pay an exit fee to get it.

Before signing, demand four things in writing:

• HTML/CSS/JS files delivered to a server you control
• Your database, owned by you
• No exit fees to take the project elsewhere
• Admin access to hosting and domain accounts

This is the single most important question, because everything else depends on it. If you don't own the code, you can't switch agencies, you can't shop hosting, and you can't get a second opinion. At NoStressStudio 100% of the code is yours from day one: code, domain, hosting and content, with zero vendor lock-in.

Who will actually build my project?

Ask exactly who sits on your project and whether you can talk to them before signing. Larger agencies often sell you senior talent at the pitch, then hand the build to a junior you never meet. The gap between who you were sold and who delivers is where quality and deadlines slip.

The fix is simple: get names, and get a conversation. A studio that won't let you speak to the person writing your code is hiding something. In a small studio of two to five people you usually talk to the same person who builds the site, which removes middlemen and shortens every feedback loop.

Faster communication is not a soft benefit, it directly speeds delivery. When the builder hears your feedback first-hand, fewer details get lost in translation, and fewer revisions are needed. Ask for a direct line to the maker, in writing, as part of the deal.

What is actually included in post-launch support?

Get the support scope and per-task prices in writing before you sign. The common pattern is 30 to 90 days of free fixes, after which a paid subscription begins. The real question is what each task costs once that window closes.

Ask for concrete numbers: is a plugin update closer to 10 EUR or 100 EUR? Is a new subpage 50 EUR or 500 EUR? Vague answers here usually mean expensive surprises later. A clear price list lets you forecast the true running cost.

There's a deeper point too: the best site is one that barely needs monthly care. A static site with no CMS has no plugins to update and no security patches to chase. Hosting on a platform like Cloudflare Pages is free, and SSL renews automatically. That architecture quietly removes most of the "support" line item that other builds depend on.

What does the site really cost after a year (TCO)?

Compare the total cost of ownership over twelve months, not the headline build price. A "700 EUR" site can quietly become the more expensive option once a monthly care fee, hosting and domain are added. The example below shows how two builds compare across year one.

In year two the gap widens: the no-subscription site costs just 15 EUR for the domain. Always run this calculation before deciding. More detail in our article on website costs in 2026.

Will my site actually be indexed by Google?

Ask the agency directly about Core Web Vitals and the SEO basics, because a slow or badly structured site won't rank no matter how it looks. A frequent problem is WordPress builds stacked with dozens of plugins that push load times past six seconds, which Google penalises.

The basics you should hear without hesitation are meta titles and descriptions, schema.org structured data, a sitemap, clean headings and fast mobile loading. These are covered in our guide to SEO for small business.

Use one simple test during the sales call: ask what Core Web Vitals are and how they'd hit good scores on your site. If the answer is vague, or the person doesn't recognise the term, keep looking. An agency that can't explain how Google measures speed and stability is unlikely to deliver a site that ranks, which means you'll pay again later to fix it.

How will communication and deadlines work?

Pin down the communication process before signing, because chaos here is what causes missed deadlines and budget overruns. You want clear answers on a few points: do you get a single point of contact, what's the expected email response time, how often do you receive status updates, and which tool tracks the work.

A defined rhythm, for example a weekly status update and a named project owner, keeps everyone honest and surfaces problems early. Without it, small misunderstandings compound into delays nobody flagged until launch week.

Watch for one clear red flag during the sales process itself: an agency that takes three or more days to reply while it's still trying to win your business. If they're slow when they want your money, they'll be slower once they have it. The way an agency communicates before the contract is the most honest preview you'll get of how the project will actually run.

What references can you share from my industry?

Ask for two or three client references in a similar industry, then actually call them. References from your sector tell you far more than a generic testimonial, because they reveal how the agency handles your specific constraints, audience and expectations.

When you reach those clients, ask four direct questions: would you recommend them, was the deadline met, how was post-launch support, and does the site generate real leads or sales? The answers cut through the polish of any sales pitch.

There's also a strong negative signal to watch for. An agency that refuses to share any client contacts at all is telling you something, and it's rarely good. Established studios have happy clients who are willing to vouch for them. If nobody will pick up the phone for them, ask yourself why, and treat it as a reason to look elsewhere. Looking for a studio that meets all seven points? Check NoStressStudio: sites ready in 5 to 14 days, full code ownership, zero subscription.