Automation is on everyone’s lips. On LinkedIn, YouTube or in specialist forums, the promise is always the same: “Save 10 hours a week“, “* Automate your business 100%“, “ Replace your employees with robots*“. With “no-code” or “low-code” tools such as n8n and Make, building complex workflows has become child’s play, even without being a developer. Tempting, isn’t it?
Yet a more nuanced reality lies behind this enthusiasm. Many companies rush headlong into building “scenarios” and “AI agents” with no real strategy. The result? They end up with unmanageable systems that are expensive to maintain and, worse still, solve no underlying problem. Automating for the sake of automating becomes a costly trap.
So let us see why technical mastery of n8n or Make is not enough. For an automation to pay off, it must above all answer an unshakeable business logic.
The trap of “cosmetic” automation
It is easy to fall in love with the technology. Watching data flow automatically from a CRM into a Google Sheets file has something magical about it. But be careful not to confuse movement with progress.
The illusion of productivity
The first symptom of this trap is unnecessary complexity. You often see beginners proudly showing sprawling workflows with 50 nodes, nested conditions and three different APIs. It is visually impressive, but is it really effective?
Often, these monsters of complexity are fragile. An API changes, a data format evolves, and everything collapses. And when that happens, nobody knows how to repair the machine, because the underlying logic has been lost or poorly documented. If your automation demands more maintenance time than the time it is supposed to save, you have an ROI (Return on Investment) problem.
Focusing on the tool rather than on the outcome
Companies do not pay for n8n nodes or Make operations. They pay for:
- Increasing their margins.
- Reduce their operating costs.
- Improving customer satisfaction.
- Gaining market share.
If your automation does not directly serve one of these objectives, it is at best a gadget and at worst an expensive distraction. The tool is only a means, never an end in itself.
TO READ: ERP & PIM: how these systems transform (and save) your company culture?
Understanding the business problem: the crucial first step
Before you even open your workflow editor, an analysis phase is essential. That is often where the success of the project is decided. As many software implementation consultants explain, understanding the business problem represents 50% of the work. Selecting and using the tools is only the other half.
Ask the right questions
A pragmatic approach consists of questioning the existing processes:
- Where is the current bottleneck?
- Which repetitive task generates the most human error?
- How much does this process cost today (in person-hours and in Swiss francs, CHF)?
- What would the financial gain be if this problem were solved?
If you cannot quantify the problem, you will not be able to quantify the value of your solution.
The consultant example
Imagine a consultant who spends 2 hours a week copying and pasting leads from LinkedIn into their CRM.
- Cost: 2 hours x CHF 150/hour = CHF 300 a week.
- Annual cost: around CHF 15,000.
If you create an automation that removes this task, you have just created direct value of CHF 15’000 per year. That is the language decision-makers understand, not the number of JSON modules used in your scenario.
ROI-driven solutions: keeping it simple and effective
Contrary to received wisdom, the most profitable automations are often the simplest.
The power of simplicity
You do not need to build a complex architecture to create value. Take a concrete example: a workflow of just 5 nodes on n8n. This workflow detects a specific request in a market niche (for instance, a quote request left unprocessed for 24 hours), sends a Slack notification to the sales team and adds the prospect to an email follow-up sequence.
- Technical complexity: low.
- Set-up time: quick.
- Business impact: immediate (recovering potential revenue).
- ROI: Minimum 300%.
Companies are looking for exactly this kind of “quick win”. They want to see measurable impact fast. A simple solution that runs without a hitch is worth a thousand times more than an ultra-complex AI system that hallucinates every other time.
FURTHER READING: The 15 key AI figures for B2B marketing in Switzerland
Choosing your tools: why does n8n change things?
If business logic comes first, the choice of tool remains strategic for the long-term viability of the solution. This is where n8n often stands apart from Make (formerly Integromat) for organisations concerned about their independence.
The advantage of self-hosting
n8n offers the option of being hosted on your own servers (self-hosted). This has two major advantages for businesses:
- Data confidentiality: your sensitive data does not pass through unknown third-party servers, a crucial point for the finance and healthcare sectors in Switzerland.
- Independence: you do not depend on the sometimes volatile pricing of proprietary SaaS solutions. You avoid the “proprietary purgatory” where migrating your 500 scenarios to another tool becomes a technical and financial nightmare.
That does not mean abandoning Make, which remains excellent for how easy it is to get started. But for critical, confidential processes, the technical sovereignty of n8n is an undeniable business asset.
Positioning: sell solutions, not workflows
If you are a provider or an employee looking to showcase your automation skills, change your pitch. Do not say “I know how to use n8n“. Say “* I know how to cut order processing time by 40%*“.
The importance of business fundamentals
Tools change. Yesterday it was Zapier, today Make and n8n, tomorrow perhaps autonomous AI agents. What does not change are the business fundamentals: margin, efficiency, customer satisfaction.
Beyond the “fluff” and the “hype” around AI, your value comes from your ability to translate an operational problem into a reliable technical solution.
The technical imperative
Be careful, though, not to fall into the opposite excess. This field remains essentially technical. To offer professional, robust solutions, you will have to keep learning: understanding REST APIs, handling JSON, getting to grips with webhooks. The technical side is the foundation your credibility rests on, but it must stay in the service of strategy.
TO READ: Technical debt: why the race for speed can sometimes slow you down?
OBJECTIVE: the balance between technique and strategy
Automation with n8n and Make is therefore a formidable growth lever… Provided you avoid the trap of technology for technology’s sake. For decision-makers and operations experts, the real challenge is not connecting two applications, but connecting automation to the company’s financial objectives.
Always keep this simple equation in mind: Understanding the business problem + a simple technical solution = maximum return potential.
Do not stop at learning the tool. Learn to read a balance sheet, to understand a sales funnel and to identify operational friction. It is at that intersection between code and business that the most lucrative opportunities are found.
