I am Dominik Pilichowski.
Industrial engineer (M.Sc.) who understands business processes and builds software. I do not sell a platform. I solve process problems.
I analyse processes until the real bottleneck is clear. Only then do I decide whether AI, classic software, automation or integration is the right answer. I connect process understanding with technical delivery. Responsibility does not get stuck between consulting and development.
Because technology moves so fast, I avoid solutions that only work with one vendor. I choose architecture, models and integrations by fit: so you stay able to act two years from now. The goal is not as much AI as possible. The goal is a better process.
Remote · clear · stack-independent
How I got here
Not a straight career line, more a series of decisions against comfort.
-
01
Automation early on
Even as a student I wrote shell scripts to search files or automate transfers. Back then a script often took days. Today a well-formed prompt covers a lot. The wish to automate recurring work has followed me since university. The tools are new, not the motivation.
-
02
Lessons from standard solutions
In the Microsoft ecosystem I learned how standard solutions get rolled out in companies. At the same time it became clear: many challenges are not fixed by another product, but by a better understanding of the process. That is why I work technology-open today.
-
03
Process, architecture and delivery
Today I connect business-process understanding, software development and experience from insurance, logistics and international IT projects. That includes technical ownership of critical applications, documentation-heavy work for audit and operations, and cloud migration. Regulated environments, architecture and AI belong together for me. I work at the intersection of domain and technology: with solutions that are sound on the business side and sustainable on the technical side.
How I work with you
Short and clear. Recommendations by fit, not by commission. The full process is on the Services page.
- Understand the process Clarify bottleneck, data, risks and success criteria before choosing technology.
- Compare options AI, automation, integration or custom software: what actually fits the problem.
- Choose architecture and build Build by fit, test, and document so your team understands the solution.
- Handover and availability Clear handover and reachability from the first conversation through after go-live.
Why I develop the Pilicore-Agent
The Pilicore-Agent is my own reference architecture for AI and automation. I use it to test new technologies in practice and to show how models, knowledge, tools and workflows can work together independently of a single vendor.
The experience from that feeds directly into my client projects. The agent is not a product, but a concrete look at how I work technically.
Independent solution architect for process digitalisation.
Industrial engineering, software development and technology-open architecture: for solutions that work long term. Recommendations by fit, not by licence model. AI is a tool, not the product.
If you need someone who finds the bottleneck and builds the right solution, get in touch.
Describe your process problem
A short note is enough. I usually reply within 1 to 2 business days and say clearly whether and how I can help.