Two constraints shape almost every web design project made for this market, and neither of them is aesthetic. The first is that a visitor sees a consent dialogue before they see the brand. The second is that the language is longer, denser and more literal than the one most layout systems were tuned on. A studio that treats both as legal chores will hand you something that photographs well in a case study and feels awkward in use.
Why a web design brief in Berlin starts with the first screen
The consent layer is the real first impression. It arrives before the hero image, it covers whatever was underneath it, and its wording, contrast and button hierarchy are web design decisions with consequences. Treating it as a plugin nobody owns produces the familiar result: a grey box that clashes with everything around it and a rejection path hidden two clicks deep.
Ask during procurement who designs that layer, whether it is styled to the identity, and how the page behaves for a visitor who declines. Sites built around embedded video, mapped locations and third party fonts often degrade badly in that state, leaving holes where content should be. Decide what the declining visitor sees, because in practice a substantial share of your audience will be that visitor, and the fallback layout deserves as much attention as the default one.
German copy will break a layout tuned to English
Compound nouns are long, and they do not hyphenate politely. A navigation item that fits comfortably in one language wraps to two lines in the other, a button label overflows its pill, and a card grid that looked orderly in the mockup develops uneven heights the moment real text arrives. This is the most predictable failure in the category and it is entirely avoidable.
The defence is procedural. Insist that the design is reviewed with genuine copy rather than filler, that the longest plausible label is tested rather than the average one, and that components are built to grow rather than to a fixed height. If the site will carry both languages, ask to see the same template in both and check where the rhythm falls apart. A web design team that has done this before will volunteer the problem; one that has not will discover it during build and bill you for the fix.
Formal or informal address is an interface decision
Choosing between formal and informal address is usually filed under tone of voice and then forgotten. It is not a copy detail, it is a structural one. The formal register produces longer, more careful sentences and a calmer, more spacious interface; the informal register supports short labels, direct calls to action and a denser layout. Switching halfway through, which happens often when marketing writes the homepage and somebody else writes the forms, reads as carelessness.
Settle it in the brief, apply it to error messages, form hints, confirmation screens and the cookie layer, and make it part of what you sign off. These are the surfaces where inconsistency is most visible and least excusable.
Studios here argue about content, and that is worth paying for
The local web design market has an unusually strong craft culture and a habit of pushing back. A good studio will question the page structure, tell you that half the service list is duplicated, and refuse to design a homepage carousel because you asked for one. Buyers occasionally read this as difficulty. It is the opposite: a supplier that accepts every instruction without argument is protecting its margin, not your outcome.
What follows from that is a practical test during the pitch. Give each studio a genuinely awkward part of your content, a service nobody can describe in one sentence or a product range with inconsistent naming, and see who engages with it. The one that comes back with questions rather than a mood board is the one that will save you money later.
Legal and information pages belong in the scope
Imprint, privacy and terms pages are mandatory, heavily read and almost always designed last by whoever has time. They also sit outside most web design scopes by accident, and they are where a careful brand loses its composure: a wall of unstyled text in the wrong typeface, tables that break on a phone, headings that do not match the rest of the site.
Put them in the page inventory as named templates with their own review. The same applies to the contact and location pages, which in this market carry more weight than most buyers expect, and to any page where a visitor is asked to hand over data. Consistency across these unglamorous surfaces is a large part of what makes a site feel professional.
Accessibility is a design input, not a final audit
Contrast ratios, focus states, heading order and target sizes are decided when the visual language is decided. Discovering them after the interface is approved means either rework or a quiet decision to ship something that excludes people. Ask which conformance level the web design team works to as standard, whether keyboard navigation is part of their own review, and who checks it before launch. WCAG 2.1 is the reference most teams use, and a studio that cannot name what it targets is telling you something.
Turning a Berlin shortlist into a decision
Proposals in this market vary widely in how much thinking they include before a price appears, so compare the shape of the engagement rather than the total. Ask for the page inventory as a list of templates, the number and placement of review rounds, who writes the copy, whether translation is included, and what you receive on final payment: source files, the component library, font licences held in your name.
Then ask who will actually work on it. Small senior teams and larger studios with a junior layer both produce good work, but they produce it differently, and you should know which you are buying. The fastest way to get comparable answers is to set the requirement out once and collect proposals against it rather than running the same conversation five times.
Two adjacent purchases are worth separating deliberately. If the identity itself is unresolved, the logo, the palette, the typographic rules, that work sits with studios handling identity and visual systems and should be settled before the pages are drawn. If the requirement is really an application with an interface attached, product flows, account areas, complex forms, start instead with interface and product design specialists or with firms that build and maintain web applications. For the wider view of how this category is organised across markets, begin at the overview of website design agencies.