Freelancer or web agency in Switzerland: what is the difference, and how to choose?

Every founder and SME owner asks it when launching a site, an application or a product: agency or freelancer? It gets treated as a price trade-off. It is not one. The two do not sell the same thing, and the right answer depends on the size of the project, on what must survive one person leaving, and on who, concretely, will write the code.

This article compares the two models on ten dimensions, says when each is the right choice, then describes a third profile — the independent product engineer — and, in full transparency, the model I practise myself.

The difference in one sentence

An agency sells a structure: several people, separate roles (sales, project management, design, development), capacity that survives absences, a contractual guarantee. A freelancer sells a person: their skill, their time, their availability — and nothing else. Everything else follows from that.

Ten dimensions, without propaganda

When the agency is the right choice

• The project needs more than one full-time person from the start — several interfaces, several platforms, a volume of content or design a developer cannot absorb.
• Your organisation requires a referenced supplier, insurance, an SLA or a formal procurement process.
• You need guaranteed continuity over several years, without depending on an individual.
• The subject is broad and shallow: identity, brochure site, campaigns, content — coordinating disciplines matters more than technical depth.

When the freelancer is the right choice

• The project fits in one person’s hands and you want to talk directly to the one who builds it.
• Speed of decision matters more than structure: a founder who has to show something to a customer or an investor.
• The budget is that of an SME or a first product, and every franc must go into the software, not into coordination.
• You can verify the level on real products — not only on a presentation.

The third profile: the independent product engineer

Between “freelancer” and “agency”, the vocabulary hides a more useful distinction: who carries the product, not only the code. An integrator assembling a template and an engineer designing a data model, a rules engine, payments and operations are both “freelancers”. The second is a product engineer: they turn an operational problem — rules, workflows, money moving — into a system that holds in production, and they carry its architecture as well as its consequences.

This profile fits when the project is a product, not a site: a SaaS, business software, a product with dense logic. It does not fit when a team of several people is needed from day one, nor when the organisation needs a supplier with an agency’s structure. Its structural weakness is the same as any independent’s — redundancy — and is offset by what it leaves behind: a repo in your name, a documented architecture, a hand-off another engineer can pick up.

How to decide in three questions

• Who, by name, will write my code — and will I be able to talk to them directly?
• What happens if that person disappears for three months: do I have the repo, the accounts, documentation, readable code?
• Does the project fit in the hands of one senior person for four to eight weeks — or does it need several disciplines in parallel?

If the answer to the first is an identifiable, senior person, to the second “yes, contractually”, and to the third “one person”, the independent is rational. If the project overflows one person or your organisation requires the structure, the agency is.

My model, in full transparency

I am an independent product engineer in Zürich. I build alone, at a fixed fee — one price, agreed before starting, no hourly billing — production v1s between CHF 20’000 and 45’000 in 4 to 6 weeks, automation systems and growth infrastructure from CHF 20’000 — the minimum engagement — and architecture audits when building right away would be premature. I take one to two projects per quarter; I do not subcontract; the repo and the accounts are in your name from day one, with thirty days of replies within 24h after delivery. What this model does not do: hourly staffing, staff augmentation, projects that need a team from the start. The proof of the level is not this article but the products I operate — Atamatax, Horvera, Wabiro, SponsorsMetrics — with their case studies.

In one line

The right criterion is not “agency or freelancer”: it is the size of the project, what must survive one person leaving, and the level of the one who codes. For a website, an application or a SaaS v1 that fits in one senior person’s hands, the fixed-fee independent is the rational choice; beyond that, or under procurement constraints, the agency. The project-fit check tells you in six questions which case you are in.