AI readiness and use-case selection
Where AI realistically helps in your stack, where it would just be expensive theatre, what GDPR and the EU AI Act mean for it, which architecture you actually want to operate.
/ AI · tool, not religion
Between hype, reality, and actual value
/ AI services
Yes, I am critical of AI hype. At the same time, I integrate exactly the systems that genuinely make sense for many businesses. Pragmatic, GDPR-aware, operable.
Common path: a discovery workshop (90 min), then a 1-2 day AI readiness audit, followed by either a concrete integration or an honest verdict that the timing is not right yet.
Where AI realistically helps in your stack, where it would just be expensive theatre, what GDPR and the EU AI Act mean for it, which architecture you actually want to operate.
Local LLMs (Ollama, llama.cpp, vLLM), vector databases, embedding pipelines, on-prem inference for data that cannot leave: public sector, tax, healthcare.
Self-hosted n8n pipelines, Model Context Protocol servers, tool bridges to existing systems (Excel, SQL, ERP). AI as a tool between your systems, not as magic.
Retrieval-augmented generation for internal knowledge bases, contract review, inbox classification. Sources traceable, answers citable, hallucinations controllable.
How a small team puts Claude Code or Cursor to productive use, which guardrails matter, what code review looks like when half the code comes from agents.
Data protection impact assessment, processing agreements with model vendors, EU AI Act classification of your use case, logging, audit trails, accountability. So a demo becomes operations.
/ Architecture · sample
A user question hits a local embedding model, queries a vector DB, and is sent with the relevant internal-document context to a local LLM. The answer comes back with citations, fully auditable, nothing leaves the building.
/ Architecture · stack
Triggers via webhook, cron, email, or an Excel button. n8n orchestrates the pipeline, MCP servers bridge to your real systems (Excel, SQL Server, ERP, filesystem). Inference local, logging and retry built in, no cloud egress.
AI is neither the salvation of humanity nor the end of every profession. And no, a Claude Code prompt alone usually does not replace stable software, a thought-through process, or years of experience with real systems.
But anyone who completely ignores what AI can do today will run into problems before long.
That is why I take a pragmatic view of AI. Where it is sensible, economical, and technically defensible, it can be extremely helpful:
Automation, data analysis, reporting, data prep, and ETL-style work.
Knowledge bases, internal search, internal tools, and structured workflows.
Routine tasks, structuring, code support, and documentation.
But that is often where the real work only begins.
"It works on my machine" is not yet a productive business process.
Today Claude Code, ChatGPT, or Cursor can, in remarkably little time, build small tools, analyze data, create workflows, write scripts, build automations, connect APIs, and even generate complete mini systems.
And honestly: that is impressive.
But after the first wow moment, the questions that follow are usually far less viral on LinkedIn:
And suddenly you notice: the prompt was the easy part.
I am not into panic. But I am also not into "AI will replace all developers tomorrow". Reality sits somewhere in between.
AI is a tool. An extremely powerful tool. But a tool is only as good as the person who uses it well.
An AI agent working unchecked on production data is not innovation. It is often just a new failure mode with better marketing.
It depends. There is no single best answer for every case.
Many small teams underestimate how much infrastructure suddenly sits behind we host it locally.
That is where AI is often far harder than in YouTube demos. Topics like these suddenly matter:
Data protection impact assessment, GDPR, EU AI Act, internal policies, and documentation duties.
Hosting location, network separation, VPN, logging, and audit-grade records.
Role models, permissions, and works councils when it comes to rollout and use.
And that is appropriate. A flashy tool is not automatically sensible or permitted in every environment.
Not everywhere. But often where repetitive work piles up. Typical areas:
Reporting, data preparation, ETL-style processes, and SQL support.
Knowledge systems, internal search, support knowledge bases, and sensible summaries.
Office automation, structured workflows, and small internal tools.
Intelligent assistants embedded in existing processes.
Combined with real processes, AI can save a lot of time. But only if:
No magical fully automated companies.
No AI replaces every employee.
No miracle fixes after two prompts.
No agent systems that supposedly do everything alone.
Because reality usually looks different.
I treat AI as a tool, not a religion. Where it really helps, can be integrated sensibly, and delivers a real economic upside, I am glad to support ideas, evaluation, automation, on-prem AI setups, reporting, workflows, data analysis, internal tools, and office or process automation.
Briefly describe the scenario, data context, and constraints (cloud, on-prem, public sector). I will reply with an honest view.