For me, the big thing is that Octopus lets each team work the way it actually works, without forcing everyone into one mould.<br><br>Our TV desk still lives in the rundown. That’s how a show gets to air, and nobody wanted to give that up. Our digital and radio teams think in stories, though. In Octopus, each team can stay story-centric or rundown-centric, but underneath it’s still the same story. A reporter writes it once, and it flows to the bulletin, the website, social and radio from there. We used to have five copies of every story, which meant five places for a name or a number to be wrong. Now a correction gets made once and shows up everywhere. That’s where most of the time savings came from, and where most of the mistakes stopped.<br><br>It holds up when things get messy, too. When breaking news drops ten minutes before air, the producer uses Element Skipping to drop what no longer fits, and the rest of the rundown adjusts around it. Nobody has to rebuild the timing by hand, and the show keeps its shape. Reporters in the field file into the same story from the Octopus Web Client, so the desk sees changes as they happen instead of waiting for a phone call. When it really counts, it’s fast: we react in seconds instead of scrambling. On our heaviest nights, with the whole newsroom in the same rundowns and wires pouring in, it still keeps up, which makes sense, since national networks and news agencies with much bigger teams than ours run the same system.<br><br>Then there’s the AI. Our legal team would never have let us paste scripts into a public chatbot. With Octopus, the models run on our own servers, so nothing leaves the newsroom. Any headline, summary or translation the AI suggests comes through as a suggestion: we can see where it came from, and the journalist can edit it or throw it out. It also handles transcription and tagging so people don’t have to, but the editorial call is still ours.<br><br>What got it approved, though, is that we didn’t have to start over. It connected to the graphics, playout and MAM we already had through MOS, so the equipment we’d paid for stayed in place. We moved over in phases, without a big-bang switch where you just hope you don’t go off air.<br><br>That’s also where the money made sense. We could choose between a subscription and a one-off licence, so we picked what fit our budget cycle. And it’s the same platform the big networks run, not a cut-down version for smaller stations. The return didn’t show up as one big number; it came from three things: we kept the equipment we already owned, nobody retypes a story for every platform anymore, and we can change our own workflows without paying a developer every time.<br><br>Getting people on board was easier than I expected. Journalists work in a browser-based web client, so we didn’t need a big install on every desk. The first time we needed a new approval step, one of our editors built it in the No-Code Workflow Designer while we watched. Normally, that would have been an IT ticket. And for support, with offices in Prague, New York and Bangkok, there’s always someone working in our time zone. We never felt like a small account.<br><br>To me, that’s what modernising a newsroom should feel like.