The spec is the new code, so brush up on your prose, says Kaseya CTO

Software developers will need to get their kicks from becoming code coaches of AI, professors of prompt engineering, and masters of their domain.

So says Pratik Wadher, chief technology officer at Kaseya, who oversaw a team of codesmiths rewriting software across the company’s managed services portfolio, which spans remote monitoring and management, backup and recovery, cybersecurity, and automation.

“The goal is unifying our data, unifying our API, but as we are starting to also look at the product portfolio that we have, we're trying to understand what are the patterns that we can use to consolidate the product workflows,” he tells The Register .

Storage is a good example.

The basic workflows involve reading and writing data to storage arrays, Kaseya's own cloud environment, or the racks run by hyperscalers.

The team re-architected the back end of its storage products so the storage engine reads and writes to any kind of storage from ZFS to S3.

“This is where AI helps,” Wadher claims.

“Fundamentally we have accelerated that piece of re-architecture.” Since joining Kaseya in September 2025, the CTO has been trying to simplify what he admits can be a “confusing” number of individual products.

“The storage layer that we've been writing, we re-architected and wrote it in six weeks.

And that's the actual writing, implementing and testing the code.

There are years of domain expertise behind understanding how we want to write it.” In the process, Kaseya used Anthropic coding agents to help a human write the spec.

The meatbags at Kaseya then iterated on it and peer-reviewed it with critique agents, before the AI generated the code.

Anthropic’s Claude is becoming the “de facto standard” for writing code at Kaseya .

“ When I look at my engineers, it's not how I used to write code.