A snapshot is a product, not a backup
A snapshot is the packaged version of a working account: pipelines, calendars, forms, and the follow-up that belongs to one kind of business. It is what an agency sells again. It is not a dump of every test workflow that happened to be left on.
Each snapshot in the library is built for one buyer. Marketing agencies, real estate teams, med spas and wellness, home services, and coaches and consultants do not share a pipeline. Forcing them into one template is how a resale falls apart on the onboarding call.
What is inside
A library snapshot includes the pipeline stages that match how that business actually closes work, a calendar and form that feed the first stage, and the follow-up that runs after a lead or a missed call. The names are plain. A new user should not need a legend.
Documentation sits with the snapshot: what each stage means, what the client is expected to do, and what the agency still does for them. Without that page, the snapshot is a login with extra steps.
What stays out
Test contacts, one-off campaigns, and automations that only made sense for a single client do not go into the library. If a step needs a human to explain it every time, it is not ready to be copied.
The library grows as each industry package is finished and deployed, not as a list of ideas. If a snapshot is not in the library yet, it is because it has not been run on a live account.
How a snapshot is handed over
We load the snapshot, then we stay on the call while the first lead path is tested. The client watches a form submission become an opportunity and a booking. That is the difference between a file and a working system.
If you resell accounts, the library is the thing you repeat. If you run one business, it is the starting configuration for that industry, adjusted on the same call.
