
A new recruitment platform for OTTO Work Force
Cloudflight built OTTO Work Force a recruitment platform on Pimcore DXP, with a mobile-first design, automated translations and a new SEO foundation.




WHAT WE DO DIFFERENTLY
Known from








































OUR SERVICES
Technology Advisory decides where AI pays off. Tailored Innovation builds what no product covers, in your stack. Accelerators start your build from a proven core, not from zero.
Cloudflight understood immediately what we need. They convinced us right away with their fast and future-oriented solution.

Florian Haslehner
Head of Digital Solutions (Rosenbauer International AG)

REFERENCES

Cloudflight built OTTO Work Force a recruitment platform on Pimcore DXP, with a mobile-first design, automated translations and a new SEO foundation.


KWB's energy management worked. Customers just couldn't see it. Discover what changed when Cloudflight built an app on top of it, why KWB tested the…


Austria’s Parliament is modernizing its digital foundations and rethinking how public services are delivered— putting people, collaboration, and lasting…


When Austria's top parts distributor needed to sell beyond the catalog, Cloudflight built the platform to do it.


The platform offers tools such as a sheet metal bending simulation, a 3D model viewer, and engineering file converters, all accessible for free through the…


Up to 90% of cases are now prepared with AI support, significantly relieving the staff and minimizing manual preprocessing.

EVENTS
Take this opportunity to get directly in touch with us.
On-siteFrontier Transformation Day brings together Austria’s leading decision-makers, innovators, and technology leaders to bring this very future to life. It represents the crucial next step: from inspiration to implementation.
On-site & remoteThe Cloudflight Coding Contest is one of the biggest coding contests in the world with more than 9,000 coders per edition. Join our 43rd edition and challenge yourself in level-based coding games.
INSIGHTS
Most enterprise AI conversations I’ve had this year eventually arrived at the same question: which model should we use? In almost every single case, it’s the wrong one to ask. It’s understandable why you’d be asking this; everyone’s buzzing about the latest versions of their model of choice and comparing them endlessly. But in the enterprise setting, it’s a question with a boring answer. The leading models are close enough in capability that the difference rarely determines if your project succeeds. If you swap one for another, most enterprise workloads perform within a margin that nobody outside the team would notice. The difference that does determine success is what the model knows about you when it starts working, because intelligence without memory is just fluency. Consider what you’re actually asking for when you ask an agent to handle a customer escalation. You want it to know, for example: this customer’s history. the commitments your sales team made two quarters ago. the reason this product line has a different SLA. the fact that this particular complaint pattern preceded a churn event last year. You won’t find any of that in the model itself. All of it is in your organization, scattered across different systems and documents (the brilliant minds of your specialists could count for both) . You could compare a model without that context to a very articulate new hire on…
Gernot Molin, Chief Technology Officer
November 20, 2026
There’s a conversation happening in European boardrooms this year that goes roughly like this: “We invested in artificial intelligence and ran the pilots. The pilots worked, but very little reached production. What went wrong?” The answers on offer are almost all technical: “The models weren’t good enough.” “The data wasn’t ready.” “The talent wasn’t available.” “The infrastructure wasn’t in place.” Some of that is true, but none of it is the root cause. The actual issue is that most organizations delegated a leadership question to an engineering department. Then they’re surprised when engineering returned an engineering answer. What’s actually being asked When a board approves an AI program, they believe they’re approving a technology investment. They aren’t. In reality, they’re approving a change in who—or what—makes certain decisions inside the company and under what accountability. This is a serious governance decision, and it belongs to the people who own governance, not technology. Consider what an agent actually is once it’s in production. At the essence, it’s an entity that makes consequential judgements at volume, without a named human doing so each time. It follows that, at first, someone must decide which judgements an agent may make. Someone must decide what happens when it’s wrong, because at times it will be. Someone must be accountable to a customer or an…
André Holhozinskyj, CEO
November 18, 2026
In June 2026, Gartner predicted that by 2028, AI coding costs will overtake the average developer’s salary. The drivers are rising token consumption and the shift from seat-based to consumption-based pricing. For me, the more important point in that announcement is a different one. According to Gartner, token discipline won’t emerge from developers’ own choices, because developers optimize for speed and convenience rather than cost. I agree, and not because developers are careless. In most setups, nobody can see what the work actually costs. So the useful question isn’t “how much AI budget do we need?” It’s “can we see and steer what we spend?” We’ve spent the past year building our answer to the second question. This article walks through the four building blocks we use today and the decision behind each one that every organization has to make for itself. Why a budget number alone won’t help If you have no data at all, you need a starting point. Mine is around €200 per developer per month. We calculated it a year ago, and as top models have become more expensive, it drifts upward rather than down. It sits at the lower end of what the market reports: Gartner Peer Insights found that 23% of tech leaders already spend $200 to $500 per developer per month on tokens for coding agents, and Anthropic puts enterprise Claude Code usage at $150 to $250 per month . But the number is the…
Vincenzo Sessa, Vice President Technical Strategy
November 2, 2026
Most people starting to use AI for building software use Claude Code the way they used Google ten years ago. Type a question, get an answer. It works, but only to some degree. This approach stops being enough once the project gets large enough to matter. Between the basic, Google-like functionality and an agent team that ships work while you review decisions, we identified seven distinct levels. Level 7 is where everything comes together, so it will also collapse the moment you jump there without having built the levels underneath it reliably. This model is built around Claude Code, and every path, command and example below refers to it. That said, it’s applicable to other agents like Copilot or Codex with small adaptations. Treat the levels as seven levers, not a checklist to rush. The 7 levels at a glance Direct prompting: you get answers. CLAUDE.md: Claude gets context. MCPs: Claude gets eyes and hands. Skills: Claude gets resuable shortcuts. Agents: Claude gets focus. Hooks: Claude gets guardrails. Agent orchestration: Claude gets a team. Each level solves a problem the previous one leaves open. That is why every section below points out a limitation. This limitation is the reason the next level exists. Level 1: Direct prompting, where most people stop Simply put, a prompt goes in, code goes out. You ask questions about your codebase, fix bugs, or write functions, with…
Hannes Brandstätter, Senior Technical Architect
October 12, 2026

Most enterprise AI conversations I’ve had this year eventually arrived at the same question: which model should we use? In almost every single case, it’s the wrong one to ask. It’s understandable why you’d be asking this; everyone’s buzzing about the latest versions of their model of choice and comparing them endlessly. But in the enterprise setting, it’s a question with a boring answer. The leading models are close enough in capability that the difference rarely determines if your project succeeds. If you swap one for another, most enterprise workloads perform within a margin that nobody outside the team would notice. The difference that does determine success is what the model knows about you when it starts working, because intelligence without memory is just fluency. Consider what you’re actually asking for when you ask an agent to handle a customer escalation. You want it to know, for example: this customer’s history. the commitments your sales team made two quarters ago. the reason this product line has a different SLA. the fact that this particular complaint pattern preceded a churn event last year. You won’t find any of that in the model itself. All of it is in your organization, scattered across different systems and documents (the brilliant minds of your specialists could count for both) . You could compare a model without that context to a very articulate new hire on…
Gernot Molin, Chief Technology Officer
November 20, 2026

There’s a conversation happening in European boardrooms this year that goes roughly like this: “We invested in artificial intelligence and ran the pilots. The pilots worked, but very little reached production. What went wrong?” The answers on offer are almost all technical: “The models weren’t good enough.” “The data wasn’t ready.” “The talent wasn’t available.” “The infrastructure wasn’t in place.” Some of that is true, but none of it is the root cause. The actual issue is that most organizations delegated a leadership question to an engineering department. Then they’re surprised when engineering returned an engineering answer. What’s actually being asked When a board approves an AI program, they believe they’re approving a technology investment. They aren’t. In reality, they’re approving a change in who—or what—makes certain decisions inside the company and under what accountability. This is a serious governance decision, and it belongs to the people who own governance, not technology. Consider what an agent actually is once it’s in production. At the essence, it’s an entity that makes consequential judgements at volume, without a named human doing so each time. It follows that, at first, someone must decide which judgements an agent may make. Someone must decide what happens when it’s wrong, because at times it will be. Someone must be accountable to a customer or an…
André Holhozinskyj, CEO
November 18, 2026
In June 2026, Gartner predicted that by 2028, AI coding costs will overtake the average developer’s salary. The drivers are rising token consumption and the shift from seat-based to consumption-based pricing. For me, the more important point in that announcement is a different one. According to Gartner, token discipline won’t emerge from developers’ own choices, because developers optimize for speed and convenience rather than cost. I agree, and not because developers are careless. In most setups, nobody can see what the work actually costs. So the useful question isn’t “how much AI budget do we need?” It’s “can we see and steer what we spend?” We’ve spent the past year building our answer to the second question. This article walks through the four building blocks we use today and the decision behind each one that every organization has to make for itself. Why a budget number alone won’t help If you have no data at all, you need a starting point. Mine is around €200 per developer per month. We calculated it a year ago, and as top models have become more expensive, it drifts upward rather than down. It sits at the lower end of what the market reports: Gartner Peer Insights found that 23% of tech leaders already spend $200 to $500 per developer per month on tokens for coding agents, and Anthropic puts enterprise Claude Code usage at $150 to $250 per month . But the number is the…
Vincenzo Sessa, Vice President Technical Strategy
November 2, 2026
Most people starting to use AI for building software use Claude Code the way they used Google ten years ago. Type a question, get an answer. It works, but only to some degree. This approach stops being enough once the project gets large enough to matter. Between the basic, Google-like functionality and an agent team that ships work while you review decisions, we identified seven distinct levels. Level 7 is where everything comes together, so it will also collapse the moment you jump there without having built the levels underneath it reliably. This model is built around Claude Code, and every path, command and example below refers to it. That said, it’s applicable to other agents like Copilot or Codex with small adaptations. Treat the levels as seven levers, not a checklist to rush. The 7 levels at a glance Direct prompting: you get answers. CLAUDE.md: Claude gets context. MCPs: Claude gets eyes and hands. Skills: Claude gets resuable shortcuts. Agents: Claude gets focus. Hooks: Claude gets guardrails. Agent orchestration: Claude gets a team. Each level solves a problem the previous one leaves open. That is why every section below points out a limitation. This limitation is the reason the next level exists. Level 1: Direct prompting, where most people stop Simply put, a prompt goes in, code goes out. You ask questions about your codebase, fix bugs, or write functions, with…
Hannes Brandstätter, Senior Technical Architect
October 12, 2026


