In this episode of the RingStone Podcast, Hazem Abolrous (CEO of Ringstone) and Iain Bishop (CEO of Damilah) discuss the realities of distributed software development—from building trust across borders to the game-changing role of AI. What emerges is a refreshingly honest conversation on what’s working, what’s not, and why a new approach to nearshoring—partner-shoring—is proving to be the way forward.
Partner-shoring is reshaping how companies think about nearshore development. Rather than operating as a supplier at arm’s length, the external team becomes a fully integrated extension of the client’s business—sharing the same vision, ownership, and commitment to outcomes.
“My team feels like they own the product. They’re aligned behind the vision. That’s what makes it work.” – Iain Bishop
It’s not just a resourcing solution—it’s a mindset shift, building mutual accountability and a seamless working relationship across borders.
Access to global talent and flexibility are undeniable advantages—but distributed development only works when teams are structured intentionally. Cross-functional, autonomous teams that are set up to own outcomes perform best.
Blending new distributed hires with existing team members helps transfer knowledge and build rapport. And in-person time—even casually over food or drinks—remains a powerful enabler of team cohesion.
“That’s when they stop being just colleagues and start being a team.” – Iain Bishop
Success in remote environments isn’t about choosing the perfect tool—it’s about creating clarity, structure, and seamless workflows across time zones. Poor processes that might be manageable onshore quickly become blockers in a distributed setup.
“You can’t just copy-paste the same setup you had onshore. You need to rethink it entirely.” – Hazem Abolrous
Rationalising tooling, aligning data flows, and automating routine steps are all part of creating a distributed model that actually works.
No matter where a team sits, leadership remains the key to performance and retention. Respect, psychological safety, shared purpose, and team-based recognition go further than any perks or systems.
“Treat people like adults. Respect their input. Create a culture where people want to stay.” – Iain Bishop
Leaders who lead by example, stay close to their teams, and invest in growth and recognition help foster long-term loyalty.
Scaling distributed teams isn’t just about hiring—it’s about risk management. That means starting with blended teams, understanding cultural dynamics, and ensuring proper onboarding and ownership from day one.
“Don’t make big bets blind. Blend teams. Learn the culture. Then scale.” – Iain Bishop
Scaling should be measured and deliberate, not rushed or spreadsheet-driven. When done right, it unlocks speed and resilience.
AI is already helping development teams get things done faster and better. From writing unit tests to untangling legacy code, the tools are taking care of the repetitive stuff—so engineers can focus on real problem-solving. In internal tests, developers using AI completed tasks up to five times faster, often with higher quality.
“Some people with experience of the AI tools were producing the same applications five times faster and to better quality.” – Iain Bishop
It’s not about replacing developers—it’s about accelerating them. As Hazem put it, the time saved should be reinvested in collaboration because building great software still comes down to people working well together.
Autonomous teams supported by the right AI tools are more agile, more efficient, and better positioned to innovate. AI becomes an enabler, not a replacement, helping teams prototype, analyse, and solve problems faster—without removing the human oversight that ensures quality.
“Good teams are agile. Add AI to the mix, and you have a very powerful recipe. But it takes planning.” – Hazem Abolrous
When AI is paired with team ownership and clarity of purpose, the results compound.
This episode is a must-hear for CTOs, product leaders, and decision-makers navigating the realities of distributed development in an AI-driven world. It’s packed with practical insight—and a refreshing focus on the human side of technology.
Are you ready to learn more about how we can deliver outstanding value for your business? Get in touch with us today to discuss your requirements and discover the difference we make.
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
We therefore ran a controlled experiment, pitting a team of AI-assisted software engineers and quality analysts against a ‘human-powered’ group who were only allowed to use their own brains.
Here’s what we did and what we discovered…
In all, a total of 52 of our people took part in our experiment, over a series of two hackathons.
We split them into two groups:
We gave each group three hours to perform the same task.
For the engineers, the task was:
And for the automation QAs:
The tools used by the AI-assisted team were:
We expected the results of this experiment to be positive in favour of the AI team, but we were still amazed by the difference the AI tools made in terms of enhancing speed and quality.
Here are the overall outcomes we recorded…
On average, when compared to our human-powered team, our AI-assisted engineers were able to:
• Complete the coding nearly 2x (44%) faster
• Conduct the unit tests just over 2x (51%) faster
• Cover nearly twice as many (83%) more edge cases
And when we compared our fastest human-powered engineer with our fastest AI-assisted engineer, the results were even more impressive: the AI-assisted engineer was nearly 5x (78%) faster.
We also compared a human-powered engineer with one who already had experience using AI tools (in this case, GitHub Copilot). We found that:
• For the coding, the AI-powered engineer was 4x (75%) faster
• For the unit tests, the AI-powered engineer was 6x (83%) faster
This demonstrated to us that, as our team of engineers become more experienced with AI tools, our productivity gains will increase even further.
For the QAs, we also saw a significant improvement in the times it took the AI-assisted analysts: the average overall time was just over 2x (54%) faster with AI.
And, as with the engineers, we compared the two fastest times, and found that the first AI-assisted QA to complete the task was 9x (89%) faster.
We also aimed to make some comparisons between the four different AI tools that we used in the experiment, in particular with regard to user experience, productivity gains, and security and IP protection.
For user experience: GitHub Copilot came out on top. Our developers rated it as a robust and mature tool, suited for .NET application development. It offered consistent suggestions and responses as well as strong context management. Cursor and Codium came in joint second place.
For productivity gains: Cursor came out on top, allowing our team to be 3.2x (69%) faster than human-only developers when it came to completing the full task. GitHub Copilot was in second place, making the team 2.7x (62%) faster.
For security and IP protection , we found the following:
• GitHub Copilot transmits code snippets from the integrated development environment (IDE) to GitHub in real time to generate relevant suggestions. Once the suggestion is created, both the prompt and the suggested code snippet are immediately discarded—but note that this is only the case for the Business and Enterprise licence options.
• Cursor provides a Privacy Mode that can be activated during the onboarding process, ensuring that no code is stored on their servers or by their sub-processors.
• Qodo: Paid licence user data is not used to train its AI models. The data is deleted from their storage after 48 hours. Also,
they provide an option for a zero-retention policy, where data is removed immediately if users specifically request.
All three tools are certified for SOC2 compliance.
(Note that we didn’t assess Tabnine as we felt the model wasn’t mature enough and its users struggled to complete the task.)
Our experiment made it clear that AI could offer us some huge benefits in productivity and quality. In every aspect of the tests we conducted, from coding to unit tests to automated test script production, there was a clear time saving – in most cases very significant. It will also enable us to improve the quality of our outputs, as AI-generated code was able to give us broad edge case test coverage.
Furthermore, we expect our efficiency gains to improve further as it is clear that development speed increases with experience when it comes to using AI tools. We found that just a short amount of training significantly accelerates outputs.
As for the future… Our product owner colleagues also ran an experiment to understand how AI can accelerate and improve the product discovery process. We are now looking at how we can use their AI-generated requirements as prompts to build applications – ultimately with the possibility of using AI-assisted processes from an initial description of requirements right through to final outputs.
Meanwhile, right now, we’re already starting to reap the benefits of AI-assisted development with some of our clients, delivering even greater value for them.
If you’d like to find out more about how AI-assisted software development can benefit your business, get in touch now.