Skip to content
NagentNagent
Log inSign upHire your AI team
Atlas/Relevance AI
Vendor dossier / Horizontal AI

Relevance AI

AI workforce platform for building and operating agents, with strong go-to-market templates.

REVIEWED 29 SEPTEMBER 2026Marketing / Sales / CXNO HANDS-ON BENCHMARK

What it is

Official-source notesHorizontal AIscaling

The reviewed enterprise offer lists unlimited agents, tools, users and workforces, with custom action and vendor-credit allocations. It also lists agent evaluations, A/B testing, SSO, RBAC and audit logs. [V1] [V2]

Documented means the statement is present in the cited material. Capability effectiveness, customer outcomes and security assurances have not been independently audited here.

Promoted use cases

  • Build coordinated sales agents
  • Automate support and operations
  • Run marketing research and repeatable tool workflows

Horizontal platforms compete on how people connect company knowledge, delegate work and keep control across tools. The central question is whether a reusable workspace can become an operating process, with a named owner and a reliable path from request to approved action. A visually appealing agent builder is only one part of that decision.

Pricing and buying model

Published commercial evidence

Custom enterprise pricing

Current pricing page lists Enterprise; actions and vendor credits require a quote.

Check current commercial source ↗

Budget for implementation, model and tool usage, data, human review and ongoing support. Credit units and outcome definitions differ between vendors. A missing numeric rate is marked unverified rather than replaced with an old third-party estimate.

Collaboration and governance

Access controls and audit features are listed in the enterprise offer. Confirm where approvals are enforced, what traces contain and which costs fall outside actions.

The relevant unit of control is permission to update the CRM and release approved follow-up. Inspect who can propose, approve, execute, interrupt and audit that action. Shared seats, shared content and a shared live agent session are different capabilities; require a demonstration of the one your process needs.

Evaluate memory correction, permission revocation and release control for updated instructions. An improvement loop should preserve the original evidence, proposed change, test results and named approver. A safety or security badge alone cannot establish those workflow properties.

Review and customer evidence

G2 exposes mixed individual experiences. A March 2026 invited review by Leopoldo E. is enthusiastic about custom-agent creation but describes an early learning journey. An organic November 2025 review by Griffin S. raises refund and billing concerns. Neither establishes typical production outcomes. Validate cancellation terms and production usefulness in your own pilot.

Before relying on a testimonial, confirm the exact product, version, package, workload and baseline. Ask a relevant customer about setup effort, failed cases, ongoing manual work and support after launch. This dossier does not convert customer logos or vendor-hosted awards into independent proof.

Focused feature documentation

Focused documentation check · Sep 2026

Workforce connections: approval modes and an explicit limit

The Workforce Edge Settings documentation distinguishes an agent-selected connection from a mandatory next step. For an agent-selected handoff, the builder can choose automatic execution, approval before completion or a mode in which the agent asks when it lacks context or confidence. A custom maximum for automatic runs triggers a later approval request.

The same page says connections in its Workforce Builder currently communicate in one direction. Parallel handoffs require separate task instances and the parallel tool-call feature is labelled beta. Its current product page also advertises a shared context layer, persistent project/user memory, per-tool and conditional approvals, cost-based pauses, eval thresholds, pinned versions and production sampling. Those are vendor-published capabilities, whose edition and enforcement still need testing. The page labels native scheduled deployments and webhooks beta, even while describing broader orchestration as generally available. Do not describe all autonomy and trigger options as equally mature; test a failed step, retry, approval, shared context correction and version rollback in the quoted plan.

Primary sources: Official Edge Settings documentation ↗ · Official current product and availability claims ↗

Published documentation and public illustrations; account behaviour was not independently tested.

Visual source

Public Relevance AI source page captured 22 September 2026
Relevance AI · Public page captured 22 Sept 2026. Vendor presentation, not an authenticated product test. Open source ↗

Fit, limitations and proof requests

Editorial assessment

Relevance is close to the custom-agent-team thesis, particularly where buyers want to assemble their own workforce. The procurement question is who owns design, evaluation and maintenance after the initial build.

Priority question: Demonstrate a human approval gate that survives a retry, a handoff between agents and an external tool failure.

The evaluation owner should be a growth operations lead. Use accepted work completed across tools as the business target. Judge the solution in its own stack role: a cloud runtime, a specialist production tool and a managed AI team can be complementary purchases.

Use-case evaluation plan

Account research to approved follow-up

Give the team an account record, a current product brief and a small set of approved customer references. Ask it to identify a relevant problem, distinguish observed facts from inferred needs, and prepare a follow-up for review. Then change one source and require a second person to correct the draft without restarting the research.

Measure: source accuracy, reviewer minutes, approved follow-ups and CRM consistency.

Campaign brief to coordinated delivery

Start with one campaign objective, audience, budget constraint and brand guide. Require research, a brief, assets and a release checklist with distinct human owners. Introduce an unresolved claim midway through the process. The system should retain useful work while preventing that claim from silently propagating into every asset.

Measure: accepted assets, revision burden, approval latency and missing handoffs.

Customer insight to shared learning

Provide anonymized support themes and sales objections. Ask for a synthesized insight, a proposed campaign adjustment and a knowledge update. A marketing owner and a CX owner should review the same underlying evidence. The exercise tests cross-functional context and accountability, not merely summarization quality.

Measure: evidence coverage, disagreement resolution and reuse of approved learning.

Detailed comparison

Read the detailed Nagent vs Relevance AI guide for operating models, shared context, governance, cost, evidence gaps and a staged pilot.

Nagent vs Relevance AI

Sources and evidence register

Nagent · Multiplayer AI for growth teamsResearch: 21–29 September 2026 · Public-source analysis, no hands-on benchmark · Sources & method