Skip to main content
Lavanchy Automation

About Loïc Lavanchy

Who's behind this

I connect business teams and IT. My focus is on solutions that make sense, work in daily use, and grow with the business step by step.

Loïc Lavanchy

Loïc Lavanchy

From requirement engineering to self-employment

As a project lead and requirement engineer, I've spent the last nine years bringing business teams and IT together. I worked at Switzerland's federal institute for intellectual property and at a Swiss software company.

My job was to understand what business teams actually needed and turn that into solutions that genuinely work in daily use. I spent four of those years with a particular focus on processes.

Among other things, I digitized and automated a paper-based procedure handling around 7,000 cases a year. The result was roughly 90% less manual effort per case and more than 40% more cases processed within a year.

I want to understand how things work. When I come across a workflow, I first want to understand why it grew the way it did. Usually there's a good reason behind it. And often, on a closer look, part of it could work more simply.

In 2020, I came across Camunda for the first time, a process automation platform. The approach both convinced and disappointed me: for smaller projects, the tool was simply too heavy. I couldn't use it myself.

With n8n, that changed. What would previously have required an entire project was suddenly done in a few days. That's exactly why I went self-employed.

Today I help SMEs and freelancers cut down on admin work and win back more time for tasks that create real value.

In short

My roots are in Lausanne, I grew up in Baden, studied in Olten and worked in Bern. That makes most of Switzerland feel like home.

  • Location: St-Sulpice VD, Switzerland
  • Languages: German and French, English
  • Experience: More than nine years in requirement engineering and IT project leadership, four of them focused on processes
  • Motivation: Giving my clients and myself more flexibility and more time for tasks that create real value

Outside of work

Travelling is one of my passions. What matters to me is broadening my horizon: new places, new people, new perspectives.

To unwind, I read, go hiking or do watersports. Clive Cussler novels are a particular favourite. The curiosity that drives me on the road is the same curiosity that makes me ask, with any process, how it could be made simpler.

Listening, understanding, and moving forward together

Before I build anything, I want to understand how you work today and what really occupies you. That listening stays with me throughout the whole process.

Your feedback continuously shapes the solution. Technical decisions are explained clearly and discussed together.

A pragmatic approach matters to me. The goal is a solution that delivers real value quickly and isn't unnecessarily complicated.

Anyone who spends less time on tasks that feel like a chore and drain a lot of energy can focus more on tasks that are enjoyable and create value. That's more motivating for individuals and a real win for businesses.

1

Use what already exists

Your tools aren't replaced — they're sensibly connected with each other.

2

Understand the needs

The solution should fit the daily work and the people using it.

3

Explain clearly

You should understand what's being built and why.

4

Iterate together

The solution keeps evolving based on your feedback.

Building pragmatically, testing carefully

The technical implementation follows a clear process:

  1. 1

    Draft a pragmatic concept

    I develop a solution that fits how you work today.

  2. 2

    Build with AI support

    I build the automation with n8n and use AI tools where they genuinely support the implementation.

  3. 3

    Test the result

    The automation is checked before it goes live.

  4. 4

    Discuss the result and adjust

    We discuss the result and adjust the solution until it works in daily use.

  5. 5

    Automated tests and error handling

    Where it makes sense, automated tests and error handling are built in. This improves maintainability and traceability.

  6. 6

    Go live process by process

    Implementation happens process by process. The next process is only tackled once the previous one is live, so the automation grows with you step by step.

You can see at any time what's running automatically and how the process is built. That means no black box — a traceable solution instead.

What others say about working together

„I found working with Loïc across various cross-functional projects to be very pleasant. He always took the time to fully understand the requirements and needs of the business teams before implementing solutions. His openness to feedback and his commitment to developing practical solutions made the collaboration much easier.“

Xenia Abdin, ClientTranslated from German.

„Loïc was always a pragmatic project lead and business analyst. He listened to his clients and colleagues to understand everyone's needs and find the best compromises. People are at the center of his approach.“

Elie Jeannerat, Software EngineerTranslated from French.

„I can highly recommend Loïc's work. I especially value his ability to approach people and proactively address problems in projects. His willingness to get involved is outstanding.“

Patrick Andreas Näf, Former managerTranslated from German.

„Working with Loïc was a great experience. His contribution within the requirement engineering team was key to delivering digital solutions our department could put to productive use. I especially valued his constructive and pragmatic approach.“

Mihail Leontescu, Digital Services Operations

The full recommendations can be viewed on LinkedIn. To LinkedIn →

Ready to simplify your processes?

In a free intro call, we'll take a look at one of your workflows together. No obligation, in German, French or English.

Book a free intro call