logo
business

Agency, freelancer or in-house team: who should build your SaaS?

7 min read
Agency, freelancer or in-house team: who should build your SaaS?

You have a SaaS idea. Maybe you already have mockups, a waiting list, a first customer who cannot wait to get started. And now you are stuck on a question that sounds trivial but will decide everything: agency or freelancer to build a SaaS?

Let me be straight with you. Most articles on this topic are written to sell you an answer that was already decided. An agency will tell you to pick an agency. A freelancer will tell you that agencies are billing factories. I am an independent developer based in French-speaking Switzerland, so I have a bias too. But I will try to give you the comparison I wish I had read before I got started.


The real question is not "agency or freelancer"

People talk a lot about the structure. Agency, freelancer, in-house team, offshore. As if the word on the invoice changed the quality of the code.

It does not change it.

The only question that truly matters is this one: if the person coding your SaaS disappears tomorrow, does your project die with them?

It is called the bus factor. How many people need to get hit by a bus for your product to become impossible to maintain. If the answer is "just one", you have a problem, no matter whether that person is called "agency" or "freelancer". Keep this question in mind, we come back to it with every option.


The four options, no filter

The classic agency

The real advantage of an agency is continuity. There are several people, a process, a contract, an entity that will still exist next year. Your bus factor is better.

The downsides are just as real. You pay a lot, often two to three times the rate of an independent, because you are funding salespeople, project managers, offices. And above all, you almost never talk to the person who codes. Your need goes through a salesperson, then a project manager, then a junior dev, then comes back distorted. Velocity takes a hit and quality depends entirely on who they assign you internally, which you do not control.

The freelancer / the independent

The huge advantage of a freelancer is direct access. You talk to the expert who writes the code, not to a middleman. Your decisions move fast, context is not lost, and you pay for the actual work, not the structure around it. On velocity and communication, nobody beats a good independent.

The downside, you already know it: the bus factor is one. The freelancer gets sick, changes their life, lands a permanent job, and your project is stuck. That is the real risk, and it is a legitimate risk. That is exactly why many founders choose an agency when they would rather have an independent.

The in-house team

Hiring one or two developers in-house means full control and product knowledge that stays with you. It is the right choice when the software IS your business over the long run.

But to launch, it is heavy. In Switzerland, a good full-stack dev easily costs you 120k and up per year, including social charges, without counting the months of recruitment. And a single employee is still a bus factor of one, with the added risk that they leave with all the knowledge in their head. You do not hire to test an idea, you hire once it is validated.

Offshore

The rate is unbeatable, that is the only argument, and it is true. But you pay elsewhere: time zone gap, language barrier, asynchronous communication that turns a five-minute back-and-forth into two lost days. Quality exists, but it is very uneven and hard to assess from a distance. And the question of code ownership, of GDPR, of the confidentiality of your Swiss data becomes a real issue. For a throwaway MVP, why not. For the product that has to carry your business, I am cautious.


The table, in one picture

  • Price: offshore, then freelancer, then agency, then in-house (cheapest to most expensive).
  • Direct access to whoever codes: freelancer in the lead, agency last.
  • Velocity and communication: freelancer and in-house up front, offshore behind.
  • Continuity and bus factor: agency up front, freelancer and in-house behind, offshore variable.
  • Ownership and code sovereignty: in-house and a Swiss technical partner up front, offshore to watch closely.

You see the trap? Each option wins on one axis and loses on another. The freelancer gives you everything you want, except safety. The agency gives you safety, but cuts you off from the expert. It is frustrating, and for a long time I believed you had to choose your poison.


What I decided to fix at AsuOs

I am an independent expert. Seen from the outside, an independent and a small structure look alike. I am not going to sell you the word "studio" as if it were a magical category superior to freelancing. That would be hollow, and you would feel it.

What I sell you is concrete. I kept the direct access of the freelancer and I removed the risk of the freelancer. Here is how, precisely.

The AsuOs brand. This is not cosmetic. It is an entity, a continuity, documented processes, versioned and clean code that you fully own. Your project does not live in a folder on my desktop, it lives inside a structure.

And above all, a partnership with Wavemind, a Swiss agency. This is my direct answer to the bus factor. If I disappear tomorrow, Wavemind can take over your project. This is not an empty promise, it is a concrete relay, an established team that knows how I work and can pick up where I left off on code built to be handed over. The freelancer, without the risk of the freelancer.

So when you ask me agency or freelancer to build your SaaS, my honest answer is: you do not have to choose between the two. You take the direct access of an independent, you talk to me, the one who codes, and you keep the continuity of an agency thanks to the brand and the Wavemind relay.


How to choose, concretely

Whatever option you lean toward, ask these questions to anyone before you sign.

"If you disappear, what happens?" A good answer is precise and concrete. A bad answer is vague or offended.

"Do I talk to the person who codes?" If the answer goes through three middlemen, know that your context will get lost along the way.

"Who owns the code?" The only good answer is: you, fully, from day one, on your repository. If they hesitate, run.

"Show me code you have written." Not a pretty portfolio of screenshots, real code. On this topic, I wrote a whole article: what your developer does not tell you. Read it before your next meeting, it can save you months of trouble.

Price, honestly, comes after. The cheapest option that delivers code nobody can take over is not a saving, it is a debt.


For your project

If you are building a SaaS in French-speaking Switzerland and you want direct access to the expert who codes, without betting your business on a single person, that is exactly what I offer with my custom SaaS in Switzerland service. You talk to me, from the first call to production, and continuity is already handled behind the scenes.

The best way to know if we are made to work together is to talk about it openly, no commitment. Tell me your idea, and I will honestly tell you which option makes the most sense for you, even if it is not me.

Send an email
Toni Dias

Toni Dias

Software engineer and technical partner · AsuOs

Ready to transform your digital business?

Toni Dias supports you in your digital strategy with tailored solutions.