Software developers can make huge productivity gains through the adoption of AI tools – sometimes with speed increases of up to 20x. That was the outstanding conclusion of our recent CTO Roundtable, Exploring AI-Driven Productivity in Software Development, hosted by Iain Bishop and Aleksandar Karavasilev, CEO and CTO of Damilah Technology.
Kicking off the event, they presented the findings from a series of controlled experiments they had conducted at Damilah, which demonstrated that time savings of up to 2x are quickly and easily achievable by using AI tools, in particular for tasks such as:
Furthermore, when engineers already experienced in using AI performed the set tasks, they were able to operate 4x to 6x faster.
While Iain and Aleksandar highlighted these impressive gains, the discussion revealed even greater possibilities. A start-up founder explained how combining a series of AI tools for different stages of development enabled him to deliver productivity improvements of up to 20x. To do this, he used:
This illustrated how companies willing to fully embrace AI across the development lifecycle can potentially achieve extraordinary results – for example, by enabling them to rapidly put new product ideas in front of users as basic MVPs. As a result, this founder now plans to launch at least three start-ups within a year.
This kind of accelerated development cycle can usher in a whole new era of dynamism in the market, it was concluded—the main points being:
But even companies who take a steadier or more cautious approach to AI-adoption, it was agreed, can still make immediate productivity gains. This could be, for example, by starting with ChatGPT, then progressing to more sophisticated tools such as GitHub Copilot or Cursor.
The conversation also turned to barriers to AI adoption. Several of those present described a certain amount of reluctance or resistance among larger enterprises, often due to concerns relating to company policies and regulatory matters.
However, it was noted that simply banning the use of AI tools can lead to “shadow AI”, where developers, in particular, will find workarounds in a constant pursuit of innovative ways of working.
Several attendees agreed that the solution to this is not to block, but rather to encourage the use of specified AI tools with some strict guardrails in place to ensure certain boundaries are not crossed, particularly with regard to security, privacy and IP protection
Questions were also raised about whether developers should be allowed to use AI during the hiring process, as often this could mask an applicant’s true capabilities when it comes to coding and testing. However, as one participant pointed out, companies should be looking to hire employees who are adept at using AI, as having an AI-proficient workforce will be necessary to maintain competitive advantage in the future.
Another attendee recommended a solution to the hiring problem: they deliberately asked applicants to use an AI tool which they knew would produce a certain bug in its code. They were then able to check whether the applicants had detected the bug, and therefore whether they were capable of testing and fixing code without the use of AI.
Furthermore, as one participant noted from their own experiences, many developers will decline to work for a company that denies them the opportunity to use AI tools to enhance and accelerate their work.
One recommendation to encourage those more hesitant about AI, alongside formal training, was to hold informal “brown bag” sessions. The participants from Damilah talked about their own experiences of this – holding the sessions once a fortnight, and inviting anyone from their own company or their client base to share their experiences and knowledge of AI tools.
The importance of keeping on top of rapid changes in the quality of AI tools also emerged. Several participants pointed out that some, which didn’t perform well a few months ago, are now proving to be highly valuable – software-testing tool CodeRabbit being a good example of this.
Participants also discussed optimal approaches to handling bugs in AI-generated code – as, they generally agreed, no AI tool is capable of producing perfect code.
In particular, “code bloat” was highlighted as a major issue. In other words, as AI operates so rapidly, it’s easy to generate huge amounts of code – and inevitably the more code that exists, the more bugs there will be.
Because of this, there was a consensus that:
The roundtable also discussed the challenges related to measuring the gains achieved by AI. The key points raised were:
Our roundtable participants agreed that keeping up with the lightning pace of change in AI is almost impossible. It therefore requires individuals and companies to work together to share knowledge and experiences for the advantage of all.

In traditional IT outsourcing, the product owner role tends to shrink to one task: backlog management. Requirements come in, user stories go out. That model is starting to show its limits. There is growing recognition that product owners in outsourced teams need more than backlog management skills and that the role itself needs to evolve.

When tech ecosystems are shaped by outsourcing and staff augmentation, software development teams risk becoming expert executors. But, especially in the age of AI, what they need is a strong product culture: a mindset that focuses on user outcomes, not just shipped features.

AI maturity starts with rethinking how software is built, how teams are structured, and what the “senior” title really means in an AI era. Organisations that move beyond experimentation are willing to question their operating model, not just layer AI onto the way they’ve always worked.
eBook