Snapshots are the thing agencies actually buy

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 automatically and which wait for review, for that team's comfort with 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. An agency serving many clients in a similar trade, roofing companies, law firms, medical spas, 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.

A snapshot captures one client instance's configuration as a single exportable object: its pipeline stages, its cadence structure, its dispositions, its agent policy. That object is applied to a different client instance directly. 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, the structure a new client's instance starts from, instead of a blank pipeline with three default stages nobody has thought about.

This works cleanly because of SalesCrew's single-tenant architecture. Each client instance is its own Supabase project with its own configuration. Applying a snapshot means configuring a new project's structure, a well-defined operation on a project boundary. On a shared multi-tenant database, the equivalent would mean filtering and copying 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.

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, deciding what the stages, cadences, dispositions and agent policy should be, is already done. 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.

The honest caveat is that 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.