01
Integration Systems that do not agree with each other
ERP, WMS, OMS, supplier feeds, ecommerce platforms, custom apps. Each one is internally logical. Together they become a personality test.
Integrations & operations · Krakow
I connect systems that were never meant to understand each other.
ERP meets ecommerce. Supplier feeds meet inventory reality. Warehouse software meets whatever accounting decided in 2014. That kind of work.
I've spent 15 years building custom operational software through AgileVision and turning repeatable pain into product through Runtara.
Worked with teams across 15+ countries. The problem is rarely a lack of tools — it's that they were bought at different moments, for different reasons, and now someone has to make the whole thing behave like one system.
AWS partner via AgileVision
✦Manufacturing ✦Logistics ✦Wholesale distribution ✦Ecommerce operations
What I usually get pulled into
The business already works. Just not the way the diagram says.
By the time I show up, it's running on spreadsheets, workarounds, and a few heroic people who know the real process.
02
Operations Fixes that should have happened a year ago
Order routing, inventory sync, reconciliation, approvals, reporting, exception handling. The unglamorous bits that quietly decide whether a business scales or stalls.
03
Strategy The build vs. buy question
Sometimes the answer is custom software. Sometimes it's buying a decent tool and integrating it properly. A surprising amount of value comes from choosing the boring option on purpose.
Custom work when the process actually matters
This is where I build and implement the bespoke stuff: cloud migrations, integrations across ERP/WMS/OMS stacks, IoT-heavy workflows, and systems that need to fit the business instead of forcing the business to fit the software.
Visit AgileVisionProductized automation for recurring pain
Runtara came out of seeing the same operational problems over and over again. Orders, invoices, documents, and approvals get read, checked against your rules, and entered into your systems — your team only handles the exceptions. Results in days instead of another six-month side quest.
Visit Runtara
A little about me
I prefer fixing the system to presenting a theory of it.
I write about integrations because they are never as tidy as the architecture sketch. One week it's serverless design. The next it's discovering that someone else's definition of "out of stock" can ruin your month.
Most of my work lands in manufacturing, logistics, wholesale distribution, and ecommerce operations. Those industries accumulate weird edge cases faster than slide decks can describe them, which is probably why I keep ending up there.
If you want the unvarnished version of how this work actually goes, the blog is where I write about the mistakes too.
Let's talk
One heroic spreadsheet and three people who know the real process? We should talk.
We can figure out what to fix first, what to automate, and what should stay human.
European afternoons or US mornings work best.