Ofert wzięte pod lupę

Finding a web agency isn't the problem. The problem starts when you try to tell a good offer apart from well-packaged mediocrity.

The market is full of agencies that know how to make great PDFs. Polished presentations, five-step processes, a values section, glowing testimonials. Everything looks professional. Everything looks identical.

And that's exactly the trap: the quality of a sales proposal has absolutely no relationship to the quality of the product you'll actually receive.

If you're ordering a website for the first time — or for the second time after the first one ended in disappointment — this article is for you. I'll show you how to evaluate a website offer before you sign the contract and before the money leaves your account.

Why most offers look good

Web agencies have learned one thing very well: how to sell. Not how to build websites — how to sell the project of building a website. Those are two completely different skill sets.

A beautiful Canva deck, a five-step process, a technology section (React! Figma! Agile!), a portfolio of pretty screenshots — all of this is part of the sales process, not evidence of competence.

A client who isn't a specialist has no tools to evaluate this. They can't tell whether the described "discovery process" is a real methodology or a marketing label for a single kick-off call. They can't tell whether "custom design" means a bespoke solution or a Themeforest template with swapped colours.

Sales language is engineered to sound convincing without actually saying anything concrete. "We build websites that convert" — what does that mean? How do you measure it? What data do you have? Silence.

A good offer isn't the one that looks the best. A good offer is the one that answers your questions before you even ask them.

1 / 1
abstract diagram of converting webiste principles

Click to zoom

What to really look at before choosing a web developer

When you're figuring out how to choose a web agency or how to choose a web developer, forget the proposal for a moment. Start with the signals an agency sends before they even send you a quote.

Tech stack = way of thinking

Ask the agency what they build on. If the answer is always "WordPress" — regardless of whether you need an e-commerce store, a SaaS app, a content portal, or a simple brochure site — that's a warning sign.

It's not that WordPress is bad. WordPress is a great tool — for the right projects. The problem is when an agency uses it for everything because it's the only thing they know. Or because it's the fastest and cheapest to produce — for them, not for you.

The WordPress vs custom website debate has no single answer. But a good agency can justify the answer for your specific case. "We're building this on WordPress because your team will manage content themselves and you don't need anything custom" — that's a justification. "We build everything on WordPress" — that's not.

Technology isn't a technical detail. It's an architectural decision that will cost you — or save you — for years to come.
I explained it a bit in the post “WordPress Is Not Cheap. It's Expensive — Just Differently”

SEO spam as a quality signal

Go to the agency's website and look at its structure. If you see pages like "web design London", "web design Manchester", "web design Birmingham", "web design Leeds" — and each one looks identical, differing only in the city name — you've just found an agency that does SEO spam. And guess what… the process is the same in London and Manchaster.

This isn't accidental. It's a deliberate choice: instead of building real value and genuine case studies, they generate dozens of pages with duplicated content to catch long-tail traffic. Effective? Sometimes. Ethical and valuable to users? Absolutely not.

If an agency does SEO spam for themselves, they'll do it for you too. It's not a question of bad intentions — it's a question of how they think about quality.

A good agency has a handful of solid case studies with real results. A bad agency has thirty city-name landing pages and one portfolio of pretty screenshots with zero context.

Portfolio — what it really shows

Most clients evaluate portfolios aesthetically. "Nice websites" — and that's it. That's a mistake.

When you browse an agency's portfolio, look for something else. Do the projects look like they were made by the same person using the same template? Does every site have an identical layout — big hero image, three icon columns, testimonials section, contact form? Is there any evidence of thinking about UX, user journeys, conversion?

A lack of diversity in the portfolio signals that the agency doesn't adapt solutions to client problems. They adapt clients to their solutions.

1 / 1
Cloned websites

Click to zoom

Ask about results too. Not how the site looks — but what changed after it launched. Did organic traffic grow? Did conversion improve? Did load time drop? If the agency has no data, either they didn't measure, or the results were bad. Both are concerning.

The problem isn't aesthetics. The problem is the absence of any thinking about why the website exists in the first place.

How the agency talks about the project

This is one of the most important signals, and most clients ignore it entirely.

A good agency asks about your business in the first meeting. Who are your customers? What's the primary goal of the site — lead generation, sales, brand building? What does your current sales funnel look like? What isn't working on your existing site? What resources do you have for managing content after launch?

A bad agency immediately talks about features. "We'll build you a homepage slider, a project gallery, a contact form, and a Google Maps integration." Sounds specific. But it's a list of deliverables, not a solution to a problem.

An agency that doesn't understand your business cannot build a website that supports it. They can build a pretty website. That's not the same thing.

Also notice whether the agency can say "I don't know" or "that doesn't make sense for your case". An agency that agrees with everything and never challenges your ideas isn't a partner — it's a vendor. Sometimes you need someone who'll tell you that a homepage slider is a bad idea.

What a bad offer looks like — even if it looks good

When you're thinking about what's included in a website quote and how to evaluate a website offer, it helps to know what to look for on the other side — the signals that should make you pause.

1 / 1
Two faces of web agencies

Click to zoom

Here's a list of things that should raise a red flag — regardless of how polished the presentation is:

  • WordPress as the default answer for everything. No questions about your needs, no justification, no alternatives offered.
  • SEO pages for every city in the country. Dozens of identical pages with different city names — that's not an SEO strategy, that's spam.
  • A one-template portfolio. Every project looks like a clone of the last — different logo, same layout.
  • Zero questions about your business. The quote arrived 24 hours after your first email, with no conversation. How do they know what you need?
  • Offer focused on deliverables, not outcomes. "5 pages, contact form, mobile-responsive" — but not a word about what the site is supposed to achieve.
  • No information about who will actually do the work. An agency with ten people on the about page, but your project is handled by one junior developer and a freelancer from Upwork.
  • Guaranteed Google rankings with no details. Nobody can guarantee rankings. If someone promises them, they're either lying or they don't understand how SEO works.

Any one of these signals on its own isn't necessarily a dealbreaker. Several of them together — that's a clear pattern.

Price — the biggest chaos on the market

How much does a website cost? It's the question every client asks. And it's the question with no single good answer — because the market is completely disorganised.

For £300 you'll get a pseudo-site on a free template, hosted on shared hosting, with AI-generated content and no thought given to SEO or UX. It technically exists. Practically — it does nothing.

For £30,000 you'll get... often the same thing, just better packaged. WordPress, a premium theme, nice design, maybe some customisation. Website pricing doesn't correlate with value the way you'd expect.

What a website costs depends on dozens of variables the client usually can't see: the complexity of the UX design, the number of third-party integrations, the quality of the code (will it be maintainable in a year?), the team's experience, the time spent on research and strategy, the approach to testing and post-launch optimisation.

The client sees the final price. They don't see how long the design took, how many iterations the layout went through, whether the code is written for the future or just to work right now.

That's why comparing offers purely on price is a mistake. You can only compare prices when you know you're comparing the same thing. With websites — you almost never are.

The web agency vs freelancer question has no simple price answer either. A great freelancer can be more expensive than an average agency and worth every penny. A large agency can be cheaper than a small one and deliver a worse product. Size and price are not quality indicators.

The price of a website tells you nothing about its value. It only tells you how much someone wants to earn.
I touched this topic in the post “How Much Does a Modern Website Cost in 2026?”

What a good agency looks like

Since I've spent so much time on what to avoid, let's look at the other side. What does an agency worth trusting actually look like?

A good agency matches technology to the problem, not the problem to the technology. If your project doesn't need WordPress — they'll tell you and suggest something else. If WordPress is the right choice — they'll explain why, rather than just defaulting to it.

A good agency explains trade-offs. "We can do this faster and cheaper, but you'll have limited room to scale in a year. We can do it more robustly, but it'll take two months longer. What matters more to you?" — that's a partner conversation, not a sales pitch.

A good agency understands business — not just technology. They ask about your customers, your sales funnel, how you measure success. They design the site with business goals in mind, not their own portfolio.

A good agency isn't afraid to say "this doesn't make sense". If you want a feature that won't help you reach your goal — they'll tell you. Even if they could charge you for it.

A good agency has case studies with results, not just pretty screenshots. "We built a site for X, organic traffic grew 40% in six months, conversion went from 1.2% to 2.8%" — that's a case study. "We built a beautiful site for X" — that's a screenshot in a portfolio.

A good agency is transparent about process and team. You know who will work on your project. You know how communication works. You know what happens if something goes wrong.

And finally — a good agency thinks about what happens after launch. Who will manage the content? What does support look like? What happens when you want to add a new feature in a year? A website isn't a one-off product — it's a system that will live and evolve.

Summary

The web agency market is full of companies that know how to make a good impression. Far fewer know how to make a good product.

When you evaluate an offer, don't look at the PDF. Look at the agency's own website — how their SEO looks, what their portfolio shows, how they talk about projects. Those are the real quality signals.

Ask about technology and demand a justification. Ask about results, not just looks. Ask who will do the work and how communication is handled. Ask what happens after launch.

And keep one thing in mind long after you've finished reading this:

The most expensive project isn't the one that costs £30,000. The most expensive project is the one you have to do a second time.

A bad choice of developer costs you more than just the project fee. It costs you the time you lost. It costs you the revenue you didn't earn because the site didn't work. It costs you the energy you poured into a project that had to be thrown away.

That's why it's worth taking the time to properly evaluate an offer — before you sign the contract, not after.

Not sure if the offer makes sense?

If you're at the stage of choosing a developer and you have a few offers in front of you but don't know how to evaluate them — I can help.

I'll review the offer, flag the risks that might not be obvious at first glance, and help you make a decision with full awareness of what you're committing to.

FAQ

Frequently asked questions

Ignore the PDF and look at the signals the agency sends before they even send a quote. Check their own website: how's their SEO, does their portfolio show real variety, do their case studies include actual results? In the first meeting, a good agency asks about your business — not about features and deliverables. If a detailed proposal arrived within 24 hours of your first email and no one asked you a single question, someone just filled in a template.

The market is completely disorganized: you can pay $500 and get a template with no strategy, or pay $30,000 and get essentially the same thing in a nicer wrapper. Price depends on UX complexity, integrations, code quality, and team experience — none of which are visible in most proposals. Comparing offers purely on price is a mistake, because you're almost never comparing the same thing. Instead of asking "how much does it cost," ask "what exactly do I get and how do you measure success."

There's no universal answer, but there is one good test: can the agency justify their technology choice for your specific situation? "We're using WordPress because your team will manage content and you don't need anything custom" is a real answer. "We use WordPress" with no further explanation is a red flag. WordPress is an excellent tool for the right projects — the problem is agencies that use it for everything because it's the only thing they know. Technology is an architectural decision that will cost or save you money for years.

Don't evaluate aesthetics — that's the mistake most clients make. Look for variety: does every project look like a clone of the last one with a different logo, or is there evidence of real UX thinking and user journey design? Ask about outcomes: what changed after launch — did organic traffic grow, did conversion rates improve, did page speed increase? If the agency has no data, they either didn't measure or the results were bad. Both are concerning.

Watch for these warning signs: WordPress recommended as the default without asking about your needs, dozens of identical city-name landing pages on their own site (SEO spam), a portfolio where every project looks the same, a proposal sent within 24 hours of first contact with no discovery call, a list of deliverables with no mention of business goals, and no clarity on who will actually build your project. Any one of these alone isn't a dealbreaker — several together is a clear pattern. And if anyone guarantees you a Google ranking, they're either lying or don't understand how SEO works.

There's no simple answer based on price or size. A great freelancer can cost more than an average agency and be worth every penny — and the reverse is equally true. Agencies typically offer a larger team and project continuity, but you might get sold by a senior and built by a junior. A freelancer gives you direct access to the person actually doing the work, but can become a bottleneck on larger projects. Instead of asking about the format, ask about the specific people involved, their experience, and how communication works throughout the project.