What exactly does a snapshot capture?

A client instance's setup, exported as a single object. That covers pipeline stages, cadence steps, dispositions and agent policy. You apply it to a different client instance instead of rebuilding it by hand.

Does applying a snapshot copy the client's actual data too?

No. A snapshot captures configuration, the shape of the pipeline and the automation policy. It does not capture the contacts, deals or messages inside a client's database. Applying it to a new instance sets up that instance's structure. It does not move one client's data into another's project.

Can a snapshot be edited before it is applied to a new client?

Yes, and it should be. A snapshot's value is as a starting point close to what worked before, not a rigid copy. An agency configuring a new client from a snapshot still adjusts it for that client's specifics.

Snapshots are the thing agencies actually buy

A good feature helps one client a little. A setup that works, exported and applied to the next client, makes reselling a CRM a business.

app.salescrew.io/today

The short answer

A SalesCrew snapshot takes one client's setup (stages, cadence steps, dispositions and agent policy) and exports it as one object you apply to another instance.
Because SalesCrew is single-tenant, one Supabase project per client, applying a snapshot configures a new project's structure. It does not filter rows in a database every client shares.
A snapshot captures configuration, not data. Contacts, deals and messages stay inside each client's own instance. Applying a snapshot never moves another client's records.
If you run several client instances, a proven snapshot turns one well-set-up client into a starting point for the next. No client starts from a blank state.

What actually takes time when setting up a client instance

Configuring a CRM well for a specific business is real work. Deciding what stages a deal moves through and what each one means. Building the cadence steps a cold or warm contact moves through. Defining the dispositions a rep logs against a call. Setting the agent policy: which actions run on their own and which wait for review, to suit how much that team trusts automation. None of that is a quick default. It is judgment applied to a specific business's process, and getting it right for one client takes real hours.

An agency serving one client pays that cost once and spreads it over the relationship. Now take an agency serving many clients in one trade, such as roofers, law firms or med spas. It pays the full setup cost again for every new client. That is the expensive, repetitive part of the business. It does not get cheaper because the agency has done it before, unless the previous work is captured as something reusable.

What a snapshot actually is, and why the architecture makes it possible

A snapshot captures one client instance's setup as a single object you can export. It holds the pipeline stages, cadence structure, dispositions and agent policy. You apply that object straight to a different client instance. It is not a data export. A client's contacts, deals and messages stay inside that client's own database. What moves is the shape of the setup. A new client's instance starts from it, instead of from a blank pipeline with three default stages nobody has thought about.

Snapshot export and apply work cleanly because of SalesCrew's single-tenant architecture. Each client instance is its own Supabase project with its own configuration. Applying a snapshot means setting up a new project's structure, a clean step with a clear edge. On a shared multi-tenant database, you'd have to filter and copy specific rows out of a table every client shares. That is messier, with a much higher chance of a copy touching something it should not.

Why this is the part that compounds for an agency

A single well-built feature helps every client using it a little. A snapshot helps the next client in the same trade a lot, once an agency has proven a configuration works for one client there. The hardest part of onboarding is already done: deciding what the stages, cadences, dispositions and agent policy should be. It needs adjusting, not inventing. That is a different kind of value than any one feature. It turns "we configured one client well" into "we configured this trade well, once, and every future client in it starts from that". That is closer to what an agency is actually selling when it resells a configured CRM to a series of similar clients.

One caveat: a snapshot is a starting point, not a finished product for the next client. Every business has its own specifics, even within one trade. Treating a snapshot as untouchable defeats the purpose. The value is in not starting from zero, not in never having to think about the new client at all.

Questions

What exactly does a snapshot capture?: A client instance's setup, exported as a single object. That covers pipeline stages, cadence steps, dispositions and agent policy. You apply it to a different client instance instead of rebuilding it by hand.
Does applying a snapshot copy the client's actual data too?: No. A snapshot captures configuration, the shape of the pipeline and the automation policy. It does not capture the contacts, deals or messages inside a client's database. Applying it to a new instance sets up that instance's structure. It does not move one client's data into another's project.
Can a snapshot be edited before it is applied to a new client?: Yes, and it should be. A snapshot's value is as a starting point close to what worked before, not a rigid copy. An agency configuring a new client from a snapshot still adjusts it for that client's specifics.