Best web design agencies in Switzerland: a buyer's guide without the beauty contest

The pitch is not the skill you are being sold

A confident pitch and a well-delivered project draw on two different skills, and most Swiss buyers only ever test the first one. An agency can present a polished deck, quote a fair-sounding price and answer every question fluently in the room — and still be the wrong choice, because none of that predicts what happens after the invoice is paid. The evidence that actually predicts a project's outcome shows up in four specific moments most buyers skip past entirely: what the agency asks on the first call, what the written proposal commits to on paper, what an independent reference confirms once you are no longer in the room, and what a contract clause says when nobody reads it aloud.

A disclosure before anything else: Weissmann AI builds websites and has a direct commercial interest in how you answer this question. That is precisely why this guide does not attempt to rank named competing agencies — without verifiable, current data on specific providers, any such ranking would be invented rather than researched. Instead, you get four due-diligence stages you can run against any proposal already on your desk, including one from Weissmann.

Four moments, not one first impression

Each of the four stages below tests something a portfolio cannot. Read them in order and, by the end, you will have a repeatable method for working through two or three real proposals — specific questions with specific right and wrong answers, not a list of adjectives to compare. Write down what you actually find at each stage for the two or three agencies you are weighing, in the order the due diligence itself unfolds rather than as a single scored table.

• Initial call — tests whether the agency is diagnosing your business or reciting a script it uses on every caller
• Written proposal — tests whether its commitments are specific enough to hold anyone to later
• Reference check — tests whether the outcomes it claims are verifiable independently of its own account
• Contract review — tests what actually happens once the relationship ends, whether that is well or badly

Stage 1: the initial call

A competent agency spends the first call asking about your audience, your offer, your competitors and what is actually wrong with your current site or process — before it shows you a single visual concept. That sequencing is not politeness; it is the only way the resulting website ends up built around your business rather than around a template the agency already had on hand. Weissmann's own published process states the same expectation of itself: structure, audience and conversion goals come before a line of code is written. That is not a special claim about Weissmann — it is the minimum you should expect any agency to describe unprompted, and worth noticing immediately if it cannot.

Three signs are worth noting on the call itself. First, the agency opens with a mockup or moves straight to visual style before asking a single question about your business — a sign it is selling a template, not designing a solution. Second, it cannot describe, even loosely, how it will know whether the project worked, whether that is enquiries, bookings, rankings or load time, because a team that cannot define success in advance is unlikely to build toward it. Third, it becomes vague or changes the subject when you ask, this early, who will own the code, the domain and the hosting account once the project ends.

Stage 2: the written proposal

A proposal is the first document that has to survive contact with reality, and it should already answer questions you have not thought to ask yet. Look for an itemised list of what 'SEO included' actually means technically — page structure, metadata, a sitemap, structured data — rather than the phrase sitting on its own. Look for ownership terms stated in writing: source code, CMS admin access, domain registrar control and hosting login, not just the assumption that of course it will all be yours. Look for a defined number of revision rounds, a stated consequence if your own content arrives late, and an explicit list of what is excluded and billed separately, so nothing appears as a surprise later.

Weissmann's own published packages list, in writing, what is not included — copywriting, additional language versions, paid third-party licences — rather than folding these in silently as a later add-on; that is the standard of itemisation worth expecting from any proposal, not only this one. Its public process description also mentions a 'handover' after launch without itemising, on the public page itself, exactly which accounts and access that handover transfers. That gap is not an accusation — it is exactly the kind of detail this stage exists to surface. Ask for the specifics directly, from any agency, including Weissmann, before you sign anything.

Stage 3: the independent reference check

A reference is only useful if you can verify it without relying on the agency's own account of itself. Ask for two or three clients you can contact directly, and confirm they are findable independently — a real company, a real person, a phone number that is not the agency's own. Then ask a sharper question than 'were you happy?': ask what happened when they needed a small change made six months after launch, how long it took, and what it cost. That single question exposes more about support and ownership than an hour of polished testimonials ever will.

When an agency does have a live, comparable site to share, do not take its word on load time — run the URL through a free tool such as Google PageSpeed Insights yourself and read the number, not the adjective. When it states a specific technical approach, that claim is testable too: Weissmann, for instance, describes its own stack as pre-rendered pages built with Astro and served through Netlify, and you can check that description directly by running weissmann.ai itself through the same free tool rather than accepting it on faith. On evidence specifically, Weissmann currently has no published customer case studies to offer as independent references — an honest 'not yet' from a young company, which should be judged on candour rather than treated as automatically disqualifying, for Weissmann or for any other young agency you are evaluating.

Stage 4: the contract review

This is the clause nobody reads aloud, and it is where a friendly verbal promise about ownership either holds up or quietly does not. Confirm, in the contract itself rather than in an email, exactly which accounts transfer at project end and to whose name: domain registrar, hosting account, CMS admin login, source repository. Check the notice period for cancellation, whether the agreement renews automatically, and whether there is an exit fee attached to releasing your own domain or files. If the agency will keep processing visitor data after launch through its own accounts — form submissions, analytics — a written data-processing agreement under the revised Swiss FADP belongs in this conversation too.

One structural detail is worth checking early, because it changes what can go wrong later: is the agency billing once, or is this a recurring subscription that renews unless you actively cancel it? Weissmann's own website packages are billed once rather than as a subscription, which removes the classic automatic-renewal trap by design. That is a fact about billing structure, not a substitute for confirming the ownership clause itself — a one-time invoice and a clear, written transfer of code, domain and hosting access are two different things, and this stage asks you to verify both, for any agency you are considering.

Questions worth asking at each stage

The following twelve questions map directly onto the four stages above. Ask them in this order, write down the actual answer rather than your impression of it, and compare notes only once every stage is complete.

• Initial call — What do you need to know about my business before you can design anything?
• Initial call — How will we know, in measurable terms, whether this project worked?
• Initial call — Who owns the code, the domain and the hosting account once the project is finished?
• Proposal — What, specifically, does 'SEO included' cover on this project?
• Proposal — What exactly is excluded from this price, and what would trigger an extra charge?
• Proposal — What happens to the timeline and the price if my content arrives later than planned?
• Reference check — Can I contact two or three clients directly, without you present on the call?
• Reference check — What is a live, comparable site I can test myself with a free page-speed tool?
• Reference check — What happened the last time a client needed a small change months after launch?
• Contract — Which specific accounts transfer to my name, and when?
• Contract — Is this a one-time invoice or a recurring contract, and how do I cancel it?
• Contract — Is there a written response-time commitment for support after launch, or only a verbal one?

What can go wrong: the single point of contact who disappears

Here is a realistic, constructed scenario, not a specific client's story: a small company hires a one-person, freelancer-style operation because the price is good and the portfolio looks sharp. Work begins well. Then, in week eight of a twelve-week build, that single point of contact becomes unavailable — illness, a new job, a family emergency, the cause does not matter — and no one else at the 'agency' has access to the half-finished files, the staging environment, or even a record of what has been decided so far. The client is not just delayed; they own nothing they can hand to someone else to finish.

This risk is not a reason to avoid solo operators, who are often excellent and often cheaper for a reason that has nothing to do with quality. It is a reason to ask, at the initial call, what happens if the person you are speaking to becomes unavailable mid-project, and to confirm, at the contract stage, that working files and staging access are shared with you as the project proceeds rather than promised only for the end. A single transferred credential during the build is worth more than a paragraph of reassurance about what will happen later.

When this framework will not help you

This framework assumes you already believe an agency is the right route and are now choosing between two or three real candidates. If you have not made that earlier decision yet — agency, freelancer, a website builder, or an internal hire — a four-stage due-diligence framework is the wrong tool for a question you have not asked yourself yet. And if you already have a long, trusted relationship with one agency or an internal team and are not seriously comparing alternatives, running a formal comparison across candidates you were never going to choose between is paperwork, not a decision.

Where to start

The decision is not made by reading this guide; it is made by applying it to the proposals already sitting in your inbox. Take the two or three you are actually weighing, work through all four stages for each, and write down the actual answers rather than your overall impression of the meeting. A choice checked stage by stage on paper is cheaper than one corrected after the accounts have already been paid for.