Guide

Web design: the most common mistakes and how to avoid them

Projects involving web design rarely fail because of technology. The patterns repeat themselves — and can be prevented in advance.

Quote upon request3 to 5 weeksStatus 2026
In short

The most common mistake in web design is to start with the technology instead of the actual bottleneck. A project that no one in the business actually maintains will deliver less in the long run than a smaller one that is actually used.

01 — Mistakes

The most common mistakes

  • Starting too big. Projects where nobody can use anything for months fail more often than average. A small, usable first step is almost always the better way.
  • Not involving the people who work with it. Requirements that only come from management rarely match the actual work.
  • Not defining a success measure. Without a metric defined in advance, you can't say afterwards whether it delivered anything — and the next decision will be made on gut feeling again.
  • Overlooking operating costs. The project price is only part of it. What operation costs over three years belongs in the same calculation.
  • Creating dependency. If you don't get access, documentation and source code, you're locked in. That needs to be clarified before commissioning, not after.

02 — Warning signs

When to be skeptical

  • Guaranteed results. Anyone promising top Google ranking or a specific revenue increase is selling something they can't deliver.
  • No pushback. A provider who thinks every project is a good idea has either not listened or is only selling.
  • Time pressure. Limited-time discounts on project prices are a sales tool, not an offer.
  • Unclear ownership. Anyone who won't clearly say who owns data and access doesn't have your interests at heart.
  • No contact with technical expertise. If only sales sits in the first meeting, that's where misunderstandings arise.

03 — Bottlenecks

What typically causes delays

  • Content and deliveries. By far the most common cause of delay. Text, images, price lists, access credentials — what's missing blocks progress.
  • Decisions. When it's unclear who approves, the project waits. A named contact person with decision-making authority noticeably shortens the timeline.
  • Access to third-party systems. Getting access to inventory management, phone systems, or CRM regularly takes longer than the integration itself.
  • Endless review rounds. Two correction rounds are normal, five are a sign that the goal wasn't clear at the start.

04 — Questions

Frequently asked questions

Do we even need custom design?

Not necessarily. If you need a site with five pages and no brand ambitions, a well-adapted standard system is the more sensible choice. Custom design pays off when you need to stand out from competitors or manage many pages.

Who owns the files?

You do. You get the source files and the documentation. If you work with someone else later, they can continue with them.

What if we don't like any of the directions?

Then we go back to the discovery phase — usually that means something important about the business hasn't been understood yet. It rarely happens, but better to start fresh than to force a design.

What about accessibility in design?

We check contrast, font sizes, focus presentation, and click areas against WCAG 2.1 AA. That's significantly cheaper in design than later in implementation.

Do you also provide image material?

No, that's not part of the design system. But we specify exactly what kind of images are needed and recommend suitable sources or a photographer if required.

Do we get several drafts?

Two to three directions on one page type. Ten variations help no one — they just shift the decision to the client instead of making it.

Will this look good on mobile too?

We design the narrow view first, because that's where the majority of visitors arrive. The wide view is the easier case, not the other way around.

05 — Decision

How to move forward

The most affordable next step is a conversation, not a quote. Twenty minutes is usually enough to clarify whether a project makes sense, what scope it involves, and whether we're the right fit.

If we're not, we'll say so. An honest no costs less than a project you abandon after three months — for both sides.

Next step

We'll look at your starting position.

Tell us what's eating up time today. That becomes an assessment with effort and benefit — and only then an offer.