> ## Content Index > Fetch the complete content index at: https://blog.durst-group.com/llms.txt > Use this file to discover other available public pages before exploring further. # Three days, two questions. - URL: https://blog.durst-group.com/three-days-two-questions/ - Published: 2026-10-15T10:02:52.000Z - Updated: 2026-10-15T10:02:52.000Z - Description: What customers and partners asked us at PRINTING United, and what it set in motion back in Brixen. - Author: Michael Deflorian - Tags: #kyveris, #chapters 01Las Vegas ## The bottleneck is not always the press. Three days in Las Vegas. Most visitors came for our software offering: OSI, our [Open Software Initiative](https://www.durst-group.com/en/landing-page/open-software-initiative?ref=blog.durst-group.com), and the ecosystem around it, with Lift, Prepare, Produce and eCommerce. Their question was practical: where does software make a print business more efficient today? The answers we heard pointed away from the press. The bottleneck sits more often before and after printing: in how jobs arrive and are prepared, and in what happens once the print is done. The press itself is only one station on that route. | The route of a print job | | | --------------------------------- | ---------------------------------------------------------- | | 01 | Job intakeHow jobs arrive. | | 02 | PrepressHow files are checked and prepared. | | 03 | PressThe station everyone looks at first. | | 04 | Finishing and shippingWhat happens once the print is done. | | The press is one station of four. | | Take prepress as one example. It shows how far apart our customers start. Some prepress departments still open every file by hand in Illustrator. A whole small team spends its day on routine that automation could take over, so that these people can focus on what adds value for the customer. Others run prepress almost fully automated. Same industry, very different starting points. ![Illuminated stand columns for the OSI modules callas, Lift ERP, Prepare and Produce at PRINTING United Expo 2026.](https://storage.ghost.io/c/40/2a/402a9f14-9897-4467-a646-8b861051f542/content/images/2026/10/durst_printing-united---114-_1.jpg) The OSI modules at the stand: callas, Lift ERP, Prepare and Produce. Each one a station on the route of a print job. Kyveris was a smaller part of the conversations. It came up as the question behind the practical one: what does production look like when machines, workflow and data become a learning system? OSI is the vendor-neutral integration layer of Kyveris, so the order made sense. First things have to connect, then they can learn. 02The questions ## Two questions that kept coming back. They came up at the stand, and again in the talks. The words differed, the questions did not. ### How do I benefit from AI without spending hours teaching it what I need? Think of a new colleague on their first day. Smart, willing, and knowing nothing about your presses, your substrates or the way your shop runs. You can onboard them for weeks. Most print shops don’t have those weeks. Generic AI starts from zero and learns from whatever you give it, so the time goes into teaching instead of printing. ### How do I protect the know-how that sets my business apart? Every print shop has its version of a recipe: how a difficult job is run, which settings hold on which substrate, what the experienced operator does without thinking. That is what differentiates a business. Nobody wants to hand it over and wonder where it ends up. 03The consequence ## What this asks of us. In [*Building, in Beta*](https://blog.durst-group.com/building-in-beta/), we wrote: problem first. Always. Both are problems, said out loud by the people who will use what we build. We read them as two requirements: | Two requirements | | | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 01 | Start informedAn industrial intelligence system should begin with what is already known about machines, color, substrates and processes, so the printer doesn’t have to teach it the basics. | | 02 | Stay yoursA printer’s own know-how should remain with the printer. | These are requirements, not features we claim today. They are the standard we hold the beta work to, together with [the three questions](https://blog.durst-group.com/building-in-beta/#one-word-building) from the same post: does it work, can someone who didn’t build it use it, are the results good enough to act on. 04Brixen ## Back home, straight into the workshop. Back in Brixen, we started processing the feedback right away, in the Kyveris architecture workshop. The question we worked on: how do we build an open system that complements the software a customer already runs, creates transparency, enables automation and leads to a learning system? ![The Kyveris team at a long dinner table in Brixen after the architecture workshop.](https://storage.ghost.io/c/40/2a/402a9f14-9897-4467-a646-8b861051f542/content/images/2026/10/CECEE93E-42CE-43C7-8D29-8A7BC236838E_1_105_c.jpeg) After the architecture workshop in Brixen, the Kyveris team at dinner. Guided by what the industry needs. We build on [the blocks we showed at PRINTING United](https://blog.durst-group.com/building-in-beta/), and we build for the industry, not only for Durst. How that looks technically deserves its own post. 05Together ## Shaping the industry’s future with the people in it. Nobody has to be told that print is changing. What matters is who shapes the change. We would rather do it with customers than for them. That is why we are at the stands, on the print floors and in the talks: to hear where customers lose time, what they need and what they want to protect. Then we bring it back into what we build. If you want to shape this with us, the Kyveris Beta Program is open. [Join the Kyveris Beta Program →](mailto:Tomio.Kiyose@durst-group.com?subject=Kyveris%20Beta%20Program) *— Michael Deflorian, October 2026*