When it comes to bringing Besyncly’s integration platform to life, few people know the product better than Ricky, one of the core developers driving its progress. From joining Eureka Solutions straight out of university to helping shape the product’s most advanced features, Ricky has been part of Besyncly’s journey since its early days.
We sat down with him to talk about his path into software development, his view on Besyncly’s mission and what’s coming next for the platform.

From graduate to Besyncly advocate
“I came to Eureka Solutions (the developers of Besyncly) fresh from graduating in Computer Science at Strathclyde University,” Ricky explains. “From the start, I was involved in solving interesting and complex problems, specifically within the Besyncly application. I’ve been hooked ever since – there’s something addictive about seeing how integrations can remove pain points for customers and transform how they manage data.”
Ricky says it was the innovative culture and product’s potential that drew him in. “Besyncly isn’t just another integration tool. It’s a forward-thinking platform built around flexibility and user empowerment, and the team encourages us to keep pushing those boundaries. That combination of technical challenge and creative freedom is what keeps me motivated.”
A day in the life
A typical day for Ricky blends deep technical work with collaboration. “Most days involve feature development: gathering requirements, designing solutions and implementing new functionality,” he says.
“Every feature we build starts with the customer. We’re constantly aligning our work with real business needs, whether that’s streamlining workflows, improving API handling or making the user experience more intuitive. I also work on the operational side – those background tasks that keep things running smoothly. They might not be flashy but they’re vital for platform health.”
Finding the balance between flexibility and simplicity
From a product perspective, Ricky believes Besyncly stands apart because of its approach to complexity.
“Data integration isn’t a new problem,” he says, “but traditional solutions tend to sit at two extremes – either too rigid to fit into a modern API ecosystem, or too complex for everyday users to adopt easily. Besyncly’s mission is to strike the perfect balance between power and simplicity.”
“That’s what makes our platform unique and so exciting to work on. We’re creating a platform that’s genuinely customer focused and adaptable, giving our customers the flexibility they need without the technical overhead.”
Innovation through customer feedback
Although the development roadmap is guided by overall strategy, Ricky sees innovation and customer needs as deeply intertwined. “I don’t always choose the priorities directly, but in practice, customer requests often spark innovation. A small feature request might open up a new way to automate or visualise data, which then benefits the wider platform. We’re always learning from how people use Besyncly in the real world and we’ve been getting some great suggestions via our new Feature Request tool so far.”
Keeping an eye on the future: AI and MCP
When asked about the trends shaping the integration landscape, Ricky points straight to artificial intelligence.
“I’m really interested in the use of generative AI with the Model Context Protocol (MCP). It’s an open-source standard that lets AI models interact directly with external systems, like APIs. It’s still early days, but it’s the kind of technology that could make integrations smarter and more autonomous – which aligns perfectly with where Besyncly is headed.”
“Aside from these broader technological advances, we’ll be continuing to develop connectors for even more of the platforms our customers use to run their organisations. 2025 has seen us make great strides into helping non-profits better integrate their systems, with connectors for Raiser’s Edge, Access Charity CRM, Donorfy and JustGiving. And the roadmap for 2026 is already shaping up to be good for even more online sellers, with a strengthened ecommerce offering.
Tackling technical challenges head-on
Building and maintaining integrations isn’t without its hurdles. For Ricky, the biggest technical challenges include scalability, data quality and managing APIs that evolve constantly.
“APIs change all the time – new versions, new rules and sometimes even the removal of features need to be adapted to. Our goal is to make sure Besyncly handles that and most of the time our customers are completely unaware of the changes”, he explains. “We design our solutions with scalability and resilience in mind, so our users don’t have to worry about what’s going on behind the scenes.”
Proud moments: smarter control for users
One of Ricky’s proudest recent achievements is a feature that gives users more control over how integrations handle failure.
“We recently added functionality that allows users to define custom conditional retry behaviour,” he says. “Things fail sometimes – maybe the data isn’t valid, or the API is temporarily down. This feature lets users decide what should happen in those scenarios. It’s a milestone because it empowers customers to fine-tune integrations to their needs, instead of relying on one-size-fits-all logic.”
What’s next: AI-assisted transformation
Looking ahead, Ricky is particularly excited about the team’s work in applying AI to enhance Besyncly’s usability.
“I’m currently developing a feature that uses generative AI to assist with building complex data transformations,” he reveals. “It’s a huge step towards that balance between flexibility and usability – making the platform smarter and even more accessible.”
Staying ahead of the curve
So where does Ricky see Besyncly – and integration technology – heading next?
“I think we’ll see generative AI used much more heavily to connect systems through technologies like MCP,” he predicts. “The key for us is to stay curious and keep asking: how can this technology empower our users to build better, faster and more resilient integrations? That’s how we’ll keep Besyncly ahead of the curve.”





















Comments are closed.