AI consulting and strategy.
I help companies decide where AI actually pays off — and then build it. As an independent AI consultant based in Poland, I don't resell licences or anyone else's platform, so the recommendation is the only thing I have to sell.
The most expensive mistake in AI is not bad technology. It is a well-executed project in the wrong place. Before I build anything, I work out which processes carry a real cost — measured in hours, errors or lost deals — and which of those AI can handle repeatably today.
The output is not a document for the shelf. It is a short list of priorities, each with an estimate of cost and risk, plus a first implementation you can judge on data rather than on claims.
What I do
Process audit and AI opportunity map
I go through your operational processes and identify the ones where AI makes economic sense. I flag the ones where it doesn't just as explicitly — usually the most valuable part of the conversation.
AI strategy and prioritisation
I turn a long list of ideas into a short list of decisions: what we do first, what waits, what we don't do at all. Every priority carries a cost, a risk and a way to tell whether it worked.
Workshop for leadership and teams
A half-day or full-day session after which the team understands what AI can do today, what it cannot, and where the boundary sits inside your process. No marketing, no scare stories.
First use case, delivered
I take the chosen priority to a working production system. That is the moment advisory stops being theory — and the only honest way to verify a recommendation.
Architectural oversight
If you already have a team, I come in as an architect: reviewing the design, model choices, cost and security, and staying available for the decisions that come up.
Who this is for
- Companies that have already tried AI and stalled at a pilot that never reached production.
- Boards that need to decide on an AI budget without an independent source of judgement.
- Public-sector bodies where a deployment has to survive security and procurement requirements.
- Technical teams that need an architect rather than another vendor.
How we work
- 01Free consultation
Thirty minutes. You describe the process, I tell you plainly whether AI is the right tool. Often the answer is “not there, but next to it, yes”.
- 02Analysis and priorities
I go deeper into the process — data, systems, people, legal constraints. The result is a short list of priorities with cost and risk attached.
- 03Implementation
I build the first use case and take it to production, either on your infrastructure or on mine, depending on your requirements.
- 04Maintenance and growth
The system stays with you, documented, with the option to extend it yourselves. I stay involved for as long as I am genuinely needed.
What this is based on
I have advised on World Bank projects and in the public sector — in each case the recommendation ended in a working system or a working prototype.
Two World Bank workstreams in Romania's energy sector — ~100,000 heterogeneous energy certificates (photos, OCR PDFs, spreadsheets) consolidated into one Postgres database with heavy LLM extraction, and the 2021 census turned into accurate heating maps across all 42 counties. Delivered ahead of deadline.
Read the case study~60 AI use cases assessed on impact × feasibility for a Saudi Vision 2030 platform — distilled to 7 prioritised initiatives and a phased roadmap, with a working PoC of an AI photo-inspection assistant built to run inside the Kingdom.
Read the case studyIT and AI architecture advisory for one of Europe's largest thermal-modernisation programmes — bottleneck diagnosis, AI use cases, GDPR and AI Act compliance, implementation roadmap.
Read the case studyCommon questions
- How is your AI advisory different from a traditional consultancy?
- A traditional consultancy stops at the recommendation. Here the recommendation is an intermediate product — I verify it by building. That keeps me from proposing things that cannot be implemented, because I would hit the wall myself a week later.
- Do you work with clients outside Poland?
- Yes. I run projects in English and Polish, remotely. Clients have included companies in France, the US and Romania, a ministry in Saudi Arabia, and World Bank programmes.
- How long does the analysis take before implementation starts?
- Usually from a few days to two weeks, depending on how many processes are in scope and how accessible the data is. The workshop itself is a single day.
- What if it turns out AI isn't needed here?
- Then I say so. Plenty of processes are better fixed with ordinary automation or an organisational change — cheaper and more reliable. I have no incentive to sell a model where a rule will do.