Effort × Automation = Freedom. Not a philosophy — an equation I recalculate every day.
It was sometime around two in the morning when I stared at my inbox and realized: I had spent the entire day answering emails. Not building. Not selling. Not thinking. Just answering. Two hours in the morning, one after lunch, two in the evening, and then again right before falling asleep — "briefly," so another 40 minutes. That wasn't a bad day. That was my standard.
And it wasn't just the inbox. Between emails there was calendar Tetris, formatting proposals, replying to LinkedIn messages, screening applications, googling competitors. Individually, all tasks that look harmless — but together they devoured my entire day. I once tracked it for a whole week. The result: 26 hours a week went into tasks that require no judgment at all. 26 hours in which I wasn't working on my product.
I'm a founder. I started this company because I believed AI agents could take real work off people's hands. But in that moment, I was the best proof that belief alone isn't enough. So I stopped talking about agents — and started building them for myself.
What I do
I run strategy calls with founders, CTOs, and managing directors from the DACH Mittelstand. Most arrive with the same pattern: too much operational work, too little strategic thinking. An inbox that overflows. Outreach that doesn't scale. Applications piling up. Support tickets stacking up. I listen, ask questions — and translate these pain points into an architecture of autonomous agents.
No ChatGPT wrappers. No demos on stage. Real pipelines with cost tracking, runtime logs, and persistent context. My own setup is also my showroom: a multi-agent stack that triages email, prepares meetings, handles research in advance, and summarizes contracts. While I sleep, the inbox manager keeps running. While I'm in a meeting, the research agent works through the next round of prep.
This system wasn't born from marketing slides, but from a concrete problem: too many hours, too little lifetime. A shared memory layer, persistent context, all GDPR-compliant and hosted in Germany. What I build, I use myself — every day. I'm not the consultant who shows you a slide and moves on. I'm the founder who checks his own logs in the morning before opening the client's logs.
The numbers from my own setup
I don't like talking about features. I'd rather talk about numbers, because numbers don't negotiate.
My inbox agent over a 30-day test: €0.34 cost per session. 38 hours of lifetime back per month. 14 of 200 emails already pre-answered on the table each morning, before I even open my laptop. No prompt-engineering course required — just a clearly defined workflow that runs without me.
Recruiter agent over the same period: €47 total cost, 80 applications pre-qualified, 6 meetings booked straight into the calendar. It used to be half a day a week. Now it's a Monday-morning review.
Research agent: 12 competitor profiles a week, each with sources, figures, and a pricing comparison. It used to be two days of manual work, now it's a lunch-break review. I read, evaluate, decide — the agent does the groundwork.
When I extrapolate that, I arrive at the numbers I bring into every strategy call: 26 hours a week. 1,352 hours a year. 281 days of life over five years. That's not a marketing claim. That's a spreadsheet with real data — and every client gets access to the same math.
What I honestly can't do
I'm no magician. And I'm not a consultant with a pitch deck telling you AI solves everything. There are situations where I tell a founder: You don't need an agent. You first need a better process description.
Agents automate workflows. If your workflow is unclear, an agent just scales the chaos. I've experienced this myself — my first mail agent replied beautifully, just unfortunately to the wrong emails. Because I hadn't clearly defined what should be escalated and what shouldn't. Clarity first, then automation. I no longer make that mistake with clients, because I already made it with myself.
I also can't build you an agent that runs your company strategically. Agents don't replace decisions — they give you back the hours in which you can make decisions. That distinction matters. Anyone who thinks AI takes over the thinking hasn't understood the problem.
And there are companies that don't need an agent at all. If you get five emails a day and have a clear eight-hour day, an agent is overkill. If your problem is a missing employee, not a missing process, automation won't help much. I say that openly — even when it doesn't grow my business. My reputation rests on being honest, not on selling to everyone.
How getting started with me works
A strategy call takes 30 minutes. Free. No obligation. I ask three questions:
- Which task repeats itself in your day, every day?
- How many hours does it eat up per week?
- What would you do if you got those hours back?
The answers become a roadmap — not a tool stack, but a concrete plan for which workflows get automated first and how many hours per week that brings back. No lock-in. No hidden follow-up costs.
Once the roadmap is set, it typically takes 14 days to a productive agent. EU hosting, GDPR-compliant, operated in Germany. You get the same code path I use myself — not a stripped-down version of it. The agent runs, you see the logs, you decide whether it keeps going or whether we adjust it.
After setup, I stay involved for the first two weeks. Not because the agent is shaky, but because you need to learn to trust it. Most founders still intervene in the first few days, because they're used to doing everything themselves. After a week, they let go. After two weeks, they're asking which workflow is next.
And if it turns out during the call that an agent doesn't make sense for you, I'll say so. Before we start, not after.
281 days
I've written this number down often enough that it sometimes feels abstract. Then I trace it back: 281 days is nine months. Nine months of life over five years that you either burn on repetitive work — or get back. For your product. For your team. For the hours between the end of the workday and falling asleep that should belong to you.
That's not magic. Just math. And a founder who decided at two in the morning that he wanted his nights back.
Since then, I've met at least one founder every week with the same problem. The difference between those who solve it and those still sitting in their inbox at two in the morning isn't budget. It's the decision to start.
If you want to know where your hours are going — I'll show you.