Ship buyer documentation with your snapshot
You sell GoHighLevel snapshots. The product is good; the support load is the problem. Every sale creates a buyer who installed a system they've never seen the inside of — and every one of them eventually asks what a workflow does and whether they can change it.
The walkthrough
The steps
- 1
Connect your snapshot's source account with one click with the Chrome app — once per version, not per sale. You're documenting the product; every buyer of that version benefits.
- 2
Patchy writes the docs; you mark what's safe to customize and what's load-bearing logic nobody should touch.
What each piece does, in words a buyer can read. - 3
Put the install steps next to the exact thing they apply to. The assign-a-user-or-nothing-sends kind of detail, sitting right on the workflow it's true of.
- 4
Ship one link in every delivery package — onboarding email, welcome doc, wherever the buyer lands after purchase.
One link in the delivery package — the buyer sees the system, not a black box. - 5
Route questions to the link first. Whatever still gets through tells you what to document next — or what to redesign in the next version.
- 6
New version? Refresh and ship the updated link with the changelog.
Why this changes the economics
A snapshot sale has a hidden second product: the buyer's understanding of what they bought. Ship the snapshot alone and you supply that understanding one support message at a time, forever, multiplied by every unit sold. Ship the understanding in the box and the support load stays flat while sales grow — you answer the genuinely novel questions and stop re-answering the same six.
For agency buyers the link does double duty: it's what they use to onboard their own team onto your snapshot, which makes your product easier to adopt — and easier to adopt is easier to sell. Show the map on the sales page and the snapshot stops being a promise and becomes a visible thing.
The customizable-versus-load-bearing distinction you documented is the same one that determines what you can safely push in version updates — documenting it for buyers and for your own update process is one job, done once.
The takeaway
Ship the understanding in the box. Support stays flat while sales grow — and you go back to answering only the questions nobody has asked before.
FAQ
Won't showing buyers the whole build make it easier to copy?
Anyone who installs your snapshot already has the whole build — it's in their account. The map changes whether the buyer succeeds with what they bought, and successful buyers renew, refer, and buy the next product.
Do buyers need their own PatchyHub accounts to see the documentation?
No — the link opens in a browser. Buyers who want to document their own customizations can set up their own PatchyHub; your deliverable works without it.