How is SalesCrew different from a sub-account CRM?

SalesCrew gives each client their own Supabase project: a separate Postgres database, storage and edge functions, in a region you pick when the instance is created. No table is shared between two clients, so there's nothing to keep apart with permissions. Every AI action also waits in one approval queue you control.

Can I put my own brand on each client's CRM?

Yes. Branding sets your name, logo and theme in the app for each client instance, and every client signs in on their own subdomain. Your client sees your agency when they log in.

Can I clone a client setup onto the next client?

Yes, with snapshot export and apply. You export a working setup from one instance and apply it to the next, so stages, cadences, segments, ICPs and agent policy arrive ready. Each of those settings also has its own MCP tool if you'd rather script the setup.

What margin can I make reselling SalesCrew?

Your margin is whatever you charge above $1,200 a month per instance, plus any AI top-ups. Seats are unlimited, so adding the client's whole team never raises your cost. Most of the value you sell is the service layer: setup, campaigns, reporting and the person who answers when a sequence misfires.

What happens when a client leaves?

The instance goes read-only and you or the client take a full Postgres dump plus CSVs. Deprovisioning happens after 90 days, and a person triggers it rather than a timer. Because the project holds only that client's data, the handover is the whole database.

A CRM for agency owners, with one database per client

Each client runs on a separate Postgres project, so nothing is shared, everything exports, and seats stay unlimited at $1,200 a month.

Want to see it first? Book a demo

Unlimited seats
A database per client
AI waits for your approval

app.salescrew.io/deals

Pipeline with weighted forecast and stage breakdown

The short answer

SalesCrew is a CRM for agency owners that gives every client their own instance. Each instance is its own Supabase project, with a separate Postgres database, storage and edge functions. Every AI action waits in one approval queue you control, and every action in the app is also an MCP tool.
You brand each instance with your name, logo and theme on a client subdomain, and you clone a working setup onto the next client with snapshot export and apply.
The Agency tier is $1,200 a month per instance with unlimited seats and about 60,000 model calls a month.
Moving a client in brings contacts, companies, deals, notes and tasks across from a CSV export of any CRM. Migration help comes with every tier, and a standard import completes within 7 business days.

One database per client is the whole argument

A shared-tenant CRM stores every customer in one database and keeps them apart with a column and some application logic. That's fine when the vendor is the only party who cares. It stops being fine when you're the middle layer. You carry the risk of a mistake you can't see, and a client who leaves gets an export file instead of their data.

SalesCrew is built the other way round. Each client instance is its own Supabase project, with a separate Postgres database, file storage and edge functions. You pick its region at provisioning. No row is shared between two clients, because there is no shared table. See how that compares across the field in our roundup of CRMs for agencies that keep client data separate.

Single-tenant changes three client conversations at once. Security gets short, because the answer is a project boundary rather than a policy. Data residency gets a real answer, because the region is set per client. The exit stops being a negotiation, because export is a full Postgres dump with every relationship intact. Our guide on keeping client data separate walks through each one.

Agents you can let near a client account

You decide how far each agent goes. Every agent in SalesCrew runs in a mode you choose: off, draft, review or auto. Every external send sits in the approval queue by default until someone on your team reads it. That covers email, LinkedIn messages and marketplace proposals.

Every tool call is written to the audit log with the actor named, whether a person, a token or an agent made it. When a client asks what the AI did on their account last Tuesday, you answer with a record. One kill switch on the Agents page stops every agent in that instance.

Seven jobs an agency runs in SalesCrew

Each one maps to a mechanism in the product.

Onboard a new client

Provision an instance in the region the client needs, connect their mailboxes and calendar, and import their contacts from a CSV. Every step has an MCP tool, so you script it once and rerun it.

Keep client data separate

One Supabase project per client, with its own database, storage and keys. Nothing crosses between two clients because they share no table.

Run outbound for them

Data bank, ICPs, segments with suppression enforced at freeze, multi-step cadences and a sender pool, all inside the client's own instance.

Answer their phones

Phone numbers, two-way SMS, missed-call text-back and outbound calls through Vapi sit in the client's instance, logged beside their pipeline.

Report to them

GA4, Search Console, Bing, Google Ads, Meta Ads and PostHog data lands daily beside the client's leads. Cost per lead by channel becomes a query.

Hand it over on churn

The client's project holds only the client's data. On cancellation it goes read-only, the full dump is ready, and a person decides on deprovisioning after 90 days.

Bill it

You pay the tier price per instance through Stripe Checkout and the Customer Portal. What you charge on top is your service layer.

What white-label covers in SalesCrew

White-label is five separate layers. Here is how SalesCrew handles each one for an agency.

Layer	What it means for your client	How SalesCrew does it
Brand	Your agency's name and logo in the app	Branding sets your name, logo and theme per client instance
Address	The web address the client signs in at	Every client instance runs on its own subdomain
Repeatability	A working setup cloned onto the next client	Snapshot export and apply, plus an MCP tool for every setup step
Tenancy	Where the client's data physically sits	One Supabase project per client, in the region chosen at provisioning
Fleet	Every client instance run from one place	Provisioning, heartbeat checks and daily backups for each instance, from the admin console or MCP

Branding and tenancy are set per instance. Snapshots and fleet actions each have an MCP tool as well as a screen.

Moving a client in from another CRM

A migration brings contacts, companies, deals, notes and tasks across from a CSV export of any CRM. A standard import completes within 7 business days. Migration help is included on every tier, so you don't price it into the first invoice.

You export from the old CRM, then import the CSV into the client's Data Bank. You map the columns, and contacts are matched on email: existing records get filled in, never overwritten. Deals and companies follow through MCP tools. For email, you connect the client's mailbox over IMAP and the first sync backfills the last 90 days of threads. The migration guides walk through the export, and there's a step-by-step for moving a client off GoHighLevel.

Reseller economics start from a published price

Your cost per client is the tier price plus any AI top-ups. The Agency tier is $1,200 a month per instance with unlimited seats and about 60,000 model calls a month. Because the price is on our pricing page, your plan starts from a known number.

Your margin lives in the service layer. You sell the configuration, the campaign work, the reporting, and the person who's accountable when a sequence goes wrong on a Friday. Our answer on how much to charge reselling a CRM works through the numbers.

A client with their own model contract can bring their own Anthropic key for $99 a month. The key goes into the instance's Vault, and their model calls stop counting against the allowance.

Set up, run, report, hand over

The loop you repeat for every client account.

1
Scope the client
Pick the channels they need, the pipeline stages their sales really has, and the agents you want running. Write the knowledge base entries that give replies the client's voice.
2
Provision the instance
A new Supabase project in the region the client needs, branded with your name, logo and theme on its own subdomain.
3
Apply your snapshot
Stages, dispositions, ICPs, segments, cadences, suppression list, agent modes and guardrails arrive from your standard setup. Then connect the client's mailboxes and calendar.
4
Run in review
Turn agents on in review mode. Drafts queue, a person approves, edits or rejects, and the reject reason feeds the next run.
5
Move the safe parts to auto
Research, enrichment, tagging, scoring, reply classification and pausing a cadence on reply run on auto by default. External sends stay in review unless you change the policy.
6
Report and renew
Marketing data sits beside deals in one database. Cost per lead by channel, pipeline by stage and agent activity come out of one client's project.

Where SalesCrew fits an agency best

Built for agencies that

Run sales or outbound as a service and need each client's data provably separate.
Want agents doing real work with a human reading every outbound message first.
Have a team larger than their seat budget: seats are unlimited on every tier.

And for agencies that

Script setup and reporting, because every screen in the app is also an MCP tool.
Hand a client their full database whenever they ask for it.
Report cost per lead by channel from the same database as the deals.

Which tier an agency needs

Prices are per instance, per month. Seats are unlimited on every tier.

Tier	Price	What an agency gets
Core	$299/mo	CRM, inbox, cadences on the mailbox pool, data bank, email, LinkedIn queue and inbound. AI assist with about 5,000 model calls a month, MCP and webhooks. Agents run through your MCP client, or add the agents pack for $199/mo.
Outbound	$699/mo	Core plus the SMS and phone pack, the Instantly send provider, and the Campaign and LinkedIn agents. About 25,000 model calls a month.
Agency	$1,200/mo	Outbound plus the Upwork and Fiverr marketplace module, data sources, the marketing module and every agent. About 60,000 model calls a month.

Add-ons: agents pack on Core +$199/mo · bring your own AI key +$99/mo, and your allowance is not consumed · AI top-up of 1,000 credits for $10 when a cap is hit · point-in-time recovery $120/mo. Trial: 14 days on Outbound entitlements, card required, agents in review only, 2,000-call allowance.

Meter model calls back to the client

Model calls count against each instance's allowance. If you resell at a flat fee, decide the pass-through before the first invoice. Bundle an allowance and bill top-ups, or bill the platform at cost and charge for the service. You get an alert at 80 percent, and the hard stop at 100 percent applies to AI work only, so manual work never stops.

What agency owners ask

How is SalesCrew different from a sub-account CRM?: SalesCrew gives each client their own Supabase project: a separate Postgres database, storage and edge functions, in a region you pick when the instance is created. No table is shared between two clients, so there's nothing to keep apart with permissions. Every AI action also waits in one approval queue you control.
Can I put my own brand on each client's CRM?: Yes. Branding sets your name, logo and theme in the app for each client instance, and every client signs in on their own subdomain. Your client sees your agency when they log in.
Can I clone a client setup onto the next client?: Yes, with snapshot export and apply. You export a working setup from one instance and apply it to the next, so stages, cadences, segments, ICPs and agent policy arrive ready. Each of those settings also has its own MCP tool if you'd rather script the setup.
What margin can I make reselling SalesCrew?: Your margin is whatever you charge above $1,200 a month per instance, plus any AI top-ups. Seats are unlimited, so adding the client's whole team never raises your cost. Most of the value you sell is the service layer: setup, campaigns, reporting and the person who answers when a sequence misfires.
How long does it take to move a client in?: A standard import completes within 7 business days. The migration brings contacts, companies, deals, notes and tasks across from a CSV export of any CRM. Migration help is included on every tier.
What happens when a client leaves?: The instance goes read-only and you or the client take a full Postgres dump plus CSVs. Deprovisioning happens after 90 days, and a person triggers it rather than a timer. Because the project holds only that client's data, the handover is the whole database.
Can a client use their own AI key?: Yes. Bring-your-own-key costs $99 a month, the client's Anthropic key goes into the instance's Vault, and their model calls stop counting against your allowance. The key is never displayed again after it is saved.

Request access for your agency

Fourteen days on Outbound entitlements, unlimited seats, agents in review. Take the full export whenever you want it.