Operations redesigned as production systems — not decks, not pilots. When the spreadsheets, hand-offs and swivel-chair work finally break, this is who gets called.
Your best people spend their days re-typing data between tools that were never introduced to each other. That's not a staffing problem — it's a missing system.
Order in one screen, status in a second, invoice in a third. Every swivel is a delay, an error budget, and a person who can never take a holiday.
The AI demo impressed everyone eight months ago. It still isn't in production, because demos are easy and systems are not.
Two weeks inside your operation. Where the hours go, where the errors breed, what the real constraint is — which is never what the brief said.
The target system on one page: components, flows, owners, failure modes. Boring technology chosen on purpose. Decisions documented with their reasoning.
Shipped in slices, each one live in production before the next begins. Your team operates slice one while slice two is built. No big-bang cutover, ever.
Monitored, maintained, evolved. The system earns its keep quarter after quarter — or you'll see exactly why in the numbers, because everything is measured.
A growing e-commerce company serving multiple European markets had disconnected systems — NetSuite ERP, PrestaShop webshop, invoicing, payment gateways — each drifting apart daily. I architected the end-to-end event-driven sync, built the finance core, and run the production infrastructure.
READ THE CASE STUDY →Print and packaging companies worldwide need automated PDF preflight, correction, and production tracking. Deep callas pdfToolbox integrations eliminated manual prepress work across 900+ installations — years of reliable operation without spec-level regressions.
READ THE CASE STUDY →A hardware company needed a complete smart access platform: video doorbell with sub-second calling, NFC-based access, and a management dashboard. Outdoor, all-weather, patent-pending. One engineer owning the full stack — firmware to cloud to apps.
READ THE CASE STUDY →A tag above the doorbell that a visitor taps with their phone. The call reaches the household wherever they are — video, audio or chat. No camera on the wall, no wiring, and nothing for the visitor to install. I lead the architecture, backend and infrastructure, and the team that builds it.
READ THE CASE STUDY →A shipping BLE parking product was running on two ageing native apps — Android in Java, iOS in Swift — against third-party backends nobody controlled. I reverse-engineered the beacon protocol from the legacy source, recovered its encryption key, and rebuilt the product as one React Native codebase on an API we own.
READ THE CASE STUDY →Also in the archive: Blndr — real-time green screen & Kinect.
I've spent twenty-five years inside other people's operations — print floors, warehouses, hardware labs, e-commerce back offices. A hundred and thirty systems shipped to production across sixteen industries. The pattern never changes: the company isn't short on software, it's short on design.
I work alone, with your team. No account managers, no juniors learning on your budget. The person who diagnoses your operation is the person who architects the system, writes the code, and answers the phone when something breaks.
Two weeks inside your operation. You get a written, quantified verdict on where the hours and errors actually go — and what to build first.
The full method: diagnose, architect, build. A production system shipped in slices, documented, and handed over to your team.
Your systems, monitored and evolved. Telemetry reviewed monthly, improvements shipped quarterly, one phone number when it matters.
Tell me about your operation. If it's a fit, we book the two-week diagnostic. If it isn't, I'll tell you that in the first email — and usually point you somewhere better.
Three sentences about your operation and what's breaking. No forms longer than that deserve to exist.
Within two working days: fit or no fit, and why. No "let's hop on a call to explore synergies."
Two weeks, fixed price, written findings. Everything after that is your decision, made with real information.