Free during private beta.

Your AI does what you ask — that's not "without approval." Workflows that run on their own follow rules you set up; the Strategist proposes but never acts on its own. Require approval on any specific action (email under your name, archive, delete) by configuring it once.

Yes. Every action is in the event log. Ask your AI: "What did the Strategist propose this week?" "Why is this contact tagged cold?" "Who moved this deal?"

Same as when a teammate does — you see it, fix it, tell the AI what went wrong. Most mistakes are single tool calls, recoverable in seconds. Workflows that cascade can require approval at any step.

No. Relate360 doesn't train on your data. The assistants you connect (Claude, ChatGPT) have their own data policies — turn on no-train in whichever you use.

Yes. Contacts, people, deals, notes, tags, sequences, workflows, full event log. Documented schema. Anytime.

On Cloudflare, with strict tenant isolation — every query carries your tenant ID or it doesn't run. Never co-mingled.

You're the controller; we're the processor. Standard GDPR primitives (consent, right-to-be-forgotten, export) are normal tool calls — your AI can handle the requests. DPA available.

Breeze and Einstein are AI added to a CRM. Relate360 is a CRM built for AI — your assistant calls it directly, you don't log in. The deeper difference is what the system produces: a layer of data only the loop can make — which proposals you approved, which variant won, which patterns predicted churn. None of it comes from an import.

A general-purpose AI handles ~80% — pull contacts from email, summarize calls, draft follow-ups. What it can't do alone is decide when approval is required, when a variant should win, when a tag's meaning has drifted, or keep an audit trail of what your team's AIs did. Those edges need a real system.

They're great at one-off tasks with a fixed dataset. They aren't a CRM — no relationships across time, no triggered workflows, no event stream, no shared team context. Relate360 is the durable system underneath.

Closer to the category than the incumbents, but most still center on a UI you log into — AI added inside their app rather than the other way around. Relate360 makes your AI the primary interface and the dashboard a fallback.

No. Run Relate360 alongside as long as you want. CSV import is there if you want a head start. Most founders start with new contacts and let the old CRM atrophy.

Connection takes under a minute — install the connector, paste an API key, you're in. Workflows wire up organically as you use the system. No half-day configuration session.

Easier, not harder. Tell your AI about a client; it creates the record from the conversation. You build your CRM by using it, not by setting it up.

They need to know how to talk to their AI. If they use Claude or ChatGPT today, they already know. No UI to train on, no field placement to memorize.

Both. Claude was first to support MCP, so it has the most mature experience. ChatGPT uses custom connectors. The CRM doesn't care which assistant is calling.

Gemini's tool-use story differs from MCP — not certified yet. Talk to us if you're Gemini-primary. Any assistant that adopts MCP will work.

Paid pricing with v1.1. Beta participants get advance notice; those who convert lock in a permanent founding rate.

Yes. Export, cancel, walk away. No clawback, no hostage data, no exit interview.

Yes. Built by Chris Lema, San Diego. Runs on Cloudflare. Reach a human at chris@chrislema.com.

Your data is yours, exportable today, in formats off-the-shelf tools can read. The schema is published. Worst case is reading a backup, not chasing files. Exit and data-availability commitments live in our ToS.