What SalesCrew is, in plain words

An AI-native CRM that your agents can operate and your clients can own. Every action in the app is also an MCP tool, every AI action waits for your approval, and every client gets their own database.

Unlimited seats on every tier
One database per client
A person approves every AI action

app.salescrew.io/deals

Pipeline with weighted forecast and stage breakdown

The short answer

SalesCrew is a CRM first: pipeline, contacts, companies, tasks, meetings and a unified inbox. The AI layer sits on top of the same data model, not beside it.
Every screen action has a matching MCP tool with the same effect, so Claude, ChatGPT, Cursor or any MCP client can run the CRM the way a person would.
Each client instance is its own Supabase project. Data isolation is structural, export is complete, and a client who leaves takes their own database.
The product is new. No customers, case studies, certifications or reviews are claimed anywhere on this site, and none will be until they exist.

Five things the product is built around

Agent-operable by design. Every UI action is also an MCP tool with identical effect. Nothing is UI-only, so an agent can do anything a rep can, and nothing a rep cannot.

A person in the loop, as a control plane. Each agent has a mode: off, draft, review or auto. Drafts and reviews land in one approval queue. Guardrails set limits, an audit log records every tool call, and the kill switch belongs to the customer.

Your own database. One Supabase project per client instance. Data residency follows the project region. Bring your own AI key if you want the model bill in your own name.

Outbound-complete and allowed. A data bank, suppression enforced when an audience is frozen, multi-step cadences, a sender pool, a deliverability loop and a unified inbox sit beside a real pipeline and inbound. Consent and the law stay the customer's responsibility; the product enforces suppression and opt-out.

The whole funnel in one database. Ad spend, organic search data and product analytics are stored next to leads and deals, so cost per lead by channel is a query, not a spreadsheet.

What it runs on

Supabase

Postgres, storage, auth and edge functions, one project per client instance. This is where your data lives.

Vercel

Serves the app and this site. Each client instance gets its own hostname.

Anthropic

Claude models for AI actions on the managed plan. Bring your own Anthropic key to keep the model bill and data agreement in your name.

What this site does not claim

No certifications, no uptime numbers, no customer logos, no testimonials, no case studies. Where a fact about SalesCrew is not published, the page leaves the section out rather than hedging. Competitor facts are checked on the vendor's own site and dated.

Questions

Who is SalesCrew for?: Agencies that run sales for clients and want each client on its own database, and small B2B teams that want AI to do the work while a person approves it. It is not built for enterprise procurement or for teams that need a marketing page builder.
Is SalesCrew a bot that sells for me?: No. Agents draft, research, score and queue; every action waits in an approval queue unless you switch a specific agent to auto. The audit log records every tool call with the actor named.
What does SalesCrew run on?: One Supabase project (Postgres, storage, edge functions) per client instance, the app served by Vercel, and Anthropic models for AI actions unless you bring your own key. Those three are the only subprocessors.
Does SalesCrew have customers and reviews yet?: It is a new product. There are no published customer names, case studies or third-party reviews yet, and the site does not claim any. New accounts are approved by hand.
How do I talk to a person?: Use the Request access form. Someone reads it, replies by email, and sets up your workspace. There is no sales sequence.

Request access

New accounts are approved by hand. Tell us what you are fixing and you get an email when your workspace is ready.