Cases
Client systems run on this in production today. Two of them are described below — an e-commerce brand in Lithuania and a food-delivery business in Poland. Full cases publish after the client has signed off on every number in them, which is why this page is deliberately short.
Counted from the live database on 5 September 2026 — an order came through the system that same day. Client revenue is not published here: that is theirs to share, not ours.
Written from what runs, not from what was planned.
case 01 · e-commerce · Lithuania
WooCommerce orders in one system, a weekly letter of what changed and why, meeting transcripts turned into assigned tasks, and a voice assistant for a founder who prefers to stay out of dashboards entirely.
Full case — publishing after client sign-off.
case 02 · food delivery · Poland
A production store where a silent checkout failure was quietly costing orders — order fields were being written one way and read another, so orders arrived without a city. Fixed, then wired: a Telegram bot per pickup point with a catch-all for anything that cannot be routed, and ads reconnected to revenue so spend is judged by returns rather than clicks.
Full case — publishing after client sign-off.
Client names and client figures appear on this site only after the client has read the sentence they are in and said yes. That rule has already cost us a nice-looking number: “6,776 orders of a live client in Poland” turned out, on checking, to be the demo tenant. It came down the same day, and the counters above are now computed from the live database rather than typed by hand.
One step
The audit is free and ends with a map of where your business leaks time and money — whether we work together or not.
Thirty minutes, no slides. You show the process; we say what moves onto a system.