Craig Harman

Relay.app has become a core part of how we run Product and Operations.

We use it to support a range of workflows, including research, hiring, project updates, competitor analysis, and delivery monitoring. The standout for us is how readable and intentional the workflows are. As automation becomes embedded into day-to-day operations, that clarity is what allows teams to trust, adopt, and evolve it over time.

From a product perspective, Relay strikes a rare balance. It’s quick to get started with, but structured enough to support real operating models as they scale. It doesn’t feel like you’re fighting the tool or reverse-engineering logic months later.

Jacob’s content and webinars also do a great job of clearly explaining both the space and the product, and that product thinking shows through in the experience. We’re actively expanding usage and expect to scale to around 20 agents by the end of March.

This is for most AI tools currently. Supporting logged-in, in-browser interactions would be a big win. Some tools don’t expose everything via APIs, and being able to securely work within those environments directly would unlock additional use cases.

We chose Relay.app for its clarity and ease of ongoing ownership. Compared to alternatives, it’s quicker to get started with and far easier to understand, trust, and maintain as workflows scale.

We’ve used both Zapier and Make. They’re powerful, but Relay stands out on clarity and ease of ongoing ownership. It feels designed to help teams build and maintain workflows collaboratively, not just stitch together automations that become brittle over time.