Nikola Kolevski
Founder & Digital Transformation Consultant based in Luzern. Around twenty years of practice — from the workshop floor through aviation and the electrical engineering industry to managing a software company. What I took from it: digitalisation is not a project you finish once, but a craft you get good at.
How I got here
My route into consulting did not run through a strategy department but through the workshop. Around ten years at a car dealership — first as a mechanic, later in the warehouse and in technical customer service — teaches you how businesses actually work: that processes depend on the person carrying them out, and that any rule which gets in the way of daily work will be worked around.
Then came industry. As a production engineer in aviation the work was about production ramp-ups, manufacturing processes and the question of how to describe a specification so that it is understood identically at every workstation — part of it while setting up a site in the United States. Five years at an international electrical engineering company followed: first as a supply chain business analyst, then responsible for SAP applications in Switzerland — including the migration to S/4HANA and the introduction of electronic invoice processing — and finally as head of the Swiss project management office.
Since 2025 I have been managing a Swiss software company that builds SME software for trades and services. That means I know both sides of the table: the business that has to adopt a solution, and the vendor selling it. Alongside that I have been lecturing part-time at a Swiss technical college since 2019 — which forces you to explain complicated things in a way that actually lands.
Nikolevski Consulting grew out of all of that: a consultancy that deliberately goes through to implementation. Not because strategy is unimportant, but because implementation is where you find out whether it was any good.
What I believe
First: the process comes before the tool. Digitalising a disordered workflow gives you a disordered workflow with higher licence costs. So the first question is always how the work actually runs — not how it looks on the org chart.
Second: being understandable is not optional. If an explanation only works in the meeting room and not in the workshop, it has failed. Jargon is shorthand between specialists, not a mark of quality.
Third: independence has to be worth paying for. Vendor commissions would be good business. But they make it impossible to say that the existing solution is fine — and that statement is often the most valuable one a client can hear.
Fourth: small steps win. An undertaking that delivers something visible after six weeks survives daily business. One that delivers only after twelve months rarely survives the third crisis in operations.
An honest assessment, even when it argues against my own mandate. A quote with a fixed ceiling before any work starts. And a solution your team can operate itself — without anyone outside keeping the key.
The short version
Around twenty years of practice — from hand tools to ERP projects.
Where I work
Four areas that overlap in practice — and a fifth that sits above them all: whether a solution actually gets used in the business.
Artificial intelligence
Assess use cases, select models and tools, settle data protection under revFADP, enable employees.
Automation
Capture workflows, close the seams between systems, set up error handling and logging.
Software & strategy
Gather requirements properly, review the market neutrally, make offers and contracts comparable.
Web & visibility
Fast websites, technical SEO and preparation for AI answer systems.
What it is like to work with me
Few slides, many questions. I would rather sit for an hour next to the person who runs the workflow every day than spend three hours in a meeting room talking about them.
- Direct. One point of contact from intro call to production — no handover after the sale.
- Concrete. Examples from your own business instead of generic reference slides.
- Without jargon. Explanations that hold up without an IT background.
- Reliable. Agreed dates and deliverables are met or renegotiated early.
- Confidential. With an NDA before the first detailed conversation if you prefer.
About the person and the approach
What is your background?
Around twenty years of hands-on experience in manufacturing and service businesses. The starting point was a trade role in the automotive sector, followed by years as a production engineer in aviation and five years at an international electrical engineering company — first as a supply chain business analyst, then responsible for SAP applications in Switzerland including the migration to S/4HANA, and finally as head of the Swiss project management office. Since 2025 that is complemented by managing a Swiss software company, and since 2019 by a part-time lecturing role at a technical college. On the education side: a higher technical college qualification, a university of applied sciences degree, and further training in project management.
Do I work with you or with a team?
With me. Nikola Kolevski carries out analysis, selection and implementation personally; there is no handover to junior consultants after the sales conversation. Where specialist knowledge is required — tax, legal or security questions — a network of specialists is brought in, transparently and in agreement with you.
What sets you apart from a classic consultancy?
Two things. First, implementation: automations, configurations and interfaces are built, not merely recommended — a recommendation nobody can implement is worthless. Second, independence: no commissions flow from software vendors, which is what makes the recommendation "your existing solution is fine, it is just configured wrongly" possible in the first place.
What do you explicitly not do?
No pure strategy presentation without implementation. No recommendation for products I earn from. No large projects with an open end and an open budget. And no promises of results whose preconditions are missing in the business — if the data is not there, even the best tool will not help.
Which languages do you work in?
German and English, written and spoken. Documentation and training material are produced in the language your team actually works in.
The fastest way to find out is a conversation.
30 minutes, free, without sales pressure. You describe your situation, I tell you where I would start — and whether I am the right person for it.