Episode Details

What’s up everyone, today we have the pleasure of sitting down with Rich Waldron, Co-founder and CEO at Tray.ai.

Summary: Marketing ops folks stand at a crossroads where iPaaS platforms and AI agents are colliding in crazy ways. Rich pulls back the curtain on what happens when workflows become agent "skills": Imagine your carefully built automations transformed into autonomous assistants that diagnose tech issues, provision applications, and manage complex Salesforce campaigns without manual intervention. Your marketing stack could suddenly act like a "junior admin" on demand, while you focus on strategy. The explosion of AI features has turned martech leaders into "AI referees" juggling competing vendor tools, yet those who master both fundamentals and experimental curiosity become "10X automation heroes" - the first teammates that are called when problems need solving. As Rich explains, career security comes from momentum, not stability.

About Rich

• After University, Rich spent several years building different projects in the UK which included a web agency, a media company and a mobile app for social gatherings
• Tray was officially founded in 2013, bootstrapped by selling Wellington boots on eBay – the early product idea was email automation but pivoted to enabling less technical people to utilize APIs to integrate their tech stack
• Alongside his 2 co-founders, they spent the better part of 4 years building the product and raising a seed round in 2015. Between 2018 and 2020, Tray grew from $500k to $20M ARR
• Today, Tray processes Billions of transactions across the platform every month and they’ve gone all in on the composable AI integration and automation movement

The Rise iPaaS and AI Orchestration

iPaaS exploded because enterprise suites were too slow to open up their integration capabilities. CDPs made similar mistakes with rigid architectures, birthing today's composable alternatives. Every software system eventually faces the same primal challenge: intercommunication. Rich recounts how this pattern also repeats throughout computing history with startling consistency. Monolithic ERPs dominated early landscapes, where engineers cobbled together custom connections between internal components. These hand-built bridges crumbled easily, leaving teams scrambling for standardized frameworks that could withstand daily operational stress.

As specialized software proliferated around these central systems, integration pressure mounted. "We're still not that far through on adopting the cloud," Rich points out, puncturing the tech bubble many of us live in. While cloud technologies feel omnipresent to industry veterans, countless organizations remain firmly planted on physical servers. This reality created distinct evolutionary phases for iPaaS:

On-premise to on-premise connections (the original integration challenge)
On-premise to cloud bridges (MuleSoft's territory) 
Cloud-to-cloud orchestration (where Tray focused)

Each phase demanded fundamentally different architecture. Cloud applications introduced unique payload structures, execution patterns, and API designs that rendered previous integration approaches obsolete. "Every application now has an API," Rich explains, describing how this technical shift triggered organizational transformation. Marketing departments grew increasingly technical, with marketing ops professionals discovering they could craft custom experiences by tapping into these newly accessible APIs.

> "iPaaS has to evolve because if your iPaaS was built purely for an era when AI wasn't a consideration and your customers are now suddenly saying, 'We're looking at how we infuse AI in these processes,' the requirements have changed again."

You've likely witnessed this evolution in your own organization. Remember when connecting two systems required an IT ticket