Relevance AI

The buyer Relevance AI addresses is an enterprise revenue, support or operations leader who has already trialled a frontier chat assistant and now wants governed automation with an audit trail. Relevance AI publishes a deployment path in which an embedded team maps candidate use cases in weeks one and two, ships a first team of agents in weeks three to six, and then trains internal experts to scope and build new agents weekly. Customer stories on the Relevance AI site name Qualified, Send Payments and Zembl, with quotes attributed to staff at Autodesk and Canva.

Day-to-day work in Relevance AI happens on a drag-and-drop canvas where agents, tools and human approvals are composed into a flow a non-engineer can read. Relevance AI also offers a build-with-AI route where a plain-language description generates the system prompt, the tools and the eval test cases, and an MCP route so engineers can drive the same Relevance AI platform from Claude Code, Codex or Cursor. Triggers fire from events such as a new HubSpot or Salesforce record landing.

Evals are the mechanic Relevance AI leans on hardest. Relevance AI asks a team to define pass/fail criteria up front, blocks an agent from shipping until the bar is met, samples a slice of live runs, charts the weekly pass rate and flags drift. Those same eval scores feed model routing inside Relevance AI, so the lowest-cost model that clears the bar wins across providers rather than every task defaulting to the most expensive frontier model.

Relevance AI bundles infrastructure that many teams otherwise stitch together, and the Relevance AI site names the equivalents directly: triggers like Zapier, context like Zep, connectors like Composio, model access like OpenRouter, evaluation like Braintrust, a no-code builder like Dust, coordination like CrewAI, durability like Temporal and tracing like Langfuse. Governance in Relevance AI covers SOC 2 Type II, GDPR, multi-region data residency, PII masking, audit logs, RBAC, SSO/SAML, version control with rollback and a stated policy of no training on customer data.

Packaging is the least transparent part of the public Relevance AI story in the pages reviewed. A dedicated Relevance AI pricing page was not retrieved, though the Relevance AI llms.txt points to a pricing page described as including a free tier, and Relevance AI support documentation names four live subscriptions: Free, Pro, Team and Enterprise. Relevance AI publishes first-response SLAs of three business days on Pro, two on Team and one on Enterprise, with no SLA for Free, and states that the former Business plan was sunset with those customers moved automatically to Team.

Billing mechanics in the Relevance AI terms deserve a read before signing. Fees under Relevance AI may combine Subscription Fees, Actions and prepaid Vendor Credits for third-party model usage. Relevance AI states Vendor Credits are charged at cost with no markup, but also that unused Actions and Vendor Credits expire immediately on cancellation, suspension or account deletion, cannot be refunded or transferred, and cannot offset Subscription Fees. Relevance AI additionally reserves the right to charge card surcharges and quotes fees excluding GST.

Compared with category peers, Relevance AI sits between a generic connector platform and a developer agent framework. Where Zapier or Make focus on deterministic step automation and LangGraph or CrewAI expect engineering ownership, Relevance AI targets the business expert who wants an agent with a measured quality bar and enterprise controls attached. Support hours are a practical constraint worth noting: Relevance AI staffs human support from 9am to 5pm Sydney time on weekdays for Free, Pro and Team, with dedicated staff calls reserved for Enterprise customers.