Independent consultant / Poland
Independent technology consulting for organizations modernizing infrastructure, cloud environments and technical workflows.
Services
Most engagements start in one of these areas and drift into the others as the picture gets clearer. They can be scoped as a short assessment, a defined project, or ongoing support.
SVC.CLD
I help teams choose an architecture they can actually run: one that fits the workload, the budget, and the number of people who will maintain it after I leave. Usually that means Azure, AWS or Google Cloud, and often some combination of them.
SVC.MIG
Migrations rarely fail on the main path. They fail on DNS, certificates, data volumes, and the one service nobody documented. I plan the route, run the cutover with your team, and stay through the weeks afterwards, which is when the real problems tend to show up.
SVC.DEV
The goal is a release nobody has to plan their week around. I work on the pipeline and the process together, because a fast pipeline bolted onto a fragile process helps no one.
SVC.AUT
Most teams already know which tasks eat their week. Fewer have had a spare afternoon to work out which of them are worth automating. I start with the ones that are risky to do by hand, not the ones that are easiest to script.
SVC.AI
AI is worth adopting in specific places and a distraction in others. I look at where it fits the work you already do, connect tools that are proven rather than promising, and hand back a process your team can run without me.
AI enablement
Most organizations do not need a model of their own. They need proven AI services connected to the systems that already hold their data, with the access rules, the running costs and the failure behaviour worked out before any of it reaches production.
AI.INT
Connecting AI services to the systems and data you already run, without opening holes in either.
AI.IMP
Getting from a demo that worked once to something people can rely on every day.
AI.SYS
Designing systems where AI is one component among several, with explicit limits on what it decides.
Expertise
Platform recommendations follow the workload. Each of the major clouds fits some requirements better than others, and part of an estate is often best left where it already runs.
Regions worked in most often
Approach
Infrastructure work has an order to it. Skipping the early phases is what produces migrations that stall halfway and automation nobody trusts.
Engagement start
Phase 1
Work out what is running today, what constrains it, and what the business actually needs it to do, including what it currently costs.
Phase 2
Define the architecture, migration strategy and technical processes. Decisions get written down so they can be reviewed by people who were not in the room.
Phase 3
Hands-on work alongside your team: infrastructure changes, migration execution, automation and deployment processes.
Phase 4
Resolve the issues that surface after a change lands, and improve reliability and efficiency once the system is under real load.
Phase 5
Introduce automation and AI-supported workflows where they provide measurable value, and hand over processes the team can run without you.
Ongoing operation
About
I'm Filip Szczepanski. I work as an independent consultant on infrastructure, cloud environments, DevOps practice, and the practical side of adopting AI.
You work with me directly. There is no account manager in between, no rotating project team, and no handover between the person who scoped the work and the person who does it.
Most of what I take on starts with an IT department that has the context but not the spare capacity: a migration with a date already promised to the business, a deployment process that has outgrown the way it was first set up, or a question about whether AI is worth the budget before anyone commits to it.
I am based in Poland and work with organizations across Europe, usually from inside an existing team and its processes rather than alongside them.
Contact
Tell me what you are running now, what needs to change, and any dates that are already fixed. That is usually enough for me to say whether I can help and how I would go about it.