About
Ten years in Prague. Twenty years closing the distance between how systems are built and how operations actually run.
The Short Version
I'm Jarrod Lohoff. I started Vizion AI Advisors to help growing businesses solve the operational problems that appear between people, processes, knowledge, and software.
I work best in the messy middle: the workflow is real, several systems are involved, experienced people are compensating manually, and it is not yet obvious whether the answer should be process change, integration, automation, an internal tool, AI, or something else.
I do not promise transformation. I try to understand the work well enough to recommend the smallest thing that genuinely improves it, including telling you when I do not think you should build anything.
I've spent roughly twenty years around customer service, technical support, hospitality, SaaS support, and practical technology. I'm based in Prague and work with a small number of clients at a time.
The first conversation is always free.
Where This Comes From
I spent several years at Verizon Wireless during the years when smartphones were genuinely new. Most people had never held a computer in their pocket before, and my job, technically sales but practically translation, was to explain what this thing actually was, whether it was worth it, and what it could do for someone like them specifically.
I was good at that. I built a client base that came back not because I'd sold them the most, but because I'd told them the truth. In a system built to do the opposite, with hidden upgrade dates, undisclosed trials, and commission structures that rewarded volume over honesty, that approach had a cost. I was eventually let go for exactly the way I chose to work.
I don't regret it.
What I understood then, and still believe now: people aren't confused by technology because they're not smart enough. They're confused because the people explaining it usually have other priorities.
After Verizon I spent time chasing other things, eventually made it to Europe, and found my way to Prague. That was ten years ago. I came planning to stay a few weeks. I'm still here because this city, more than anywhere I had lived before, felt like a place where you could build something without constantly justifying why you weren't building something bigger.
In the years since I've worked hospitality, managed a bar, and eventually found my way back into technology through a stint at Productboard, and found time and again that I work best when given the room to guide people as an expert, but also as an equal.
Same skill as Verizon, different setting: understand what the person in front of you actually needs to know, and explain it in a way that maps onto what they already understand.
My father ran his own IT consulting business when I was growing up. Building Vizion feels, in some ways, like finishing a conversation we started a long time ago.
Why This,
Why Now
AI has changed what a small technical practice can build, test, and improve. It can make implementation dramatically faster, but access to AI is not the hard part.
The hard part is understanding what should change, which information can be trusted, where the system of record actually is, what requires human judgment, what happens when something fails, and whether the change makes the real work better.
That is where I work: close enough to frontline operations to understand the exceptions and workarounds, and technical enough to build the missing layer when software is actually the right answer.
Practical systems. Real frontline context. No hype.
The Methodology
How I Work
I start by listening.
Before I suggest anything, I want to understand what you're actually dealing with. Not the theoretical version of your problem, but the specific work that cost your team time last week. That's where useful improvements start.
I tell you what isn't worth building.
Sometimes the right answer is an integration. Sometimes it is a process change, better documentation, an existing tool, or another employee. I would rather recommend the smaller correct answer than sell you a larger project you do not need.
I stay honest about the limits.
AI can be extremely useful, but it does not remove the need for reliable information, clear rules, testing, human judgment, and safe failure handling. I would rather give you an accurate picture than an impressive one that does not hold up.
I don't take on more than I can attend to.
The alternative, with more clients, more delegation, and more account management, produces a different kind of consulting practice. One where the thing you were paying for gradually disappears. I'm not interested in building that.
Logistics
I work in English. I'm based in Prague and available for in-person meetings locally. I find the best conversations happen somewhere comfortable, without a timer running.
For clients outside Prague, everything works remotely. I work with a small number of clients at any time. That's intentional.
The first conversation is always free, always 30 to 60 minutes, and there is no pitch at the end of it. If there is a fit, we'll both know. If there isn't, I will tell you that too.
One More Thing
I am genuinely fascinated by what these tools can do. I want to be clear about that, because the skepticism I bring to how AI is being sold can give the wrong impression.
I have built things using AI that I could not have built alone without months of additional learning and practice. I have watched it give people real hours back in their week. The technology, when it is applied honestly to a real problem, is remarkable.
I'm not anti-AI. I'm anti-hype. Those are different positions, and the difference matters for how I work.