Patsy knowledge base
Start with the question in front of you.
You do not need to read everything before using Patsy. Begin with the first two guides, then return when you are ready to publish, deliver galleries, accept appointments, sell prints, request reviews, migrate, or ask for human support.
Start
Getting started with Patsy
Go from a real photography-business question to useful guidance, then decide whether to create a Founding 100 account.
Read the guide ›Available nowGiving Patsy useful context
Help Patsy understand the business without learning prompt engineering or inventing a lengthy creative brief.
Read the guide ›Website
Reviewing and approving Patsy's work
Use Patsy as a prepared-work layer while keeping the photographer responsible for facts, taste, promises, and final approval.
Read the guide ›Founding releasePublishing and connecting a domain
Understand the difference between a public conversation, an activated trial workspace, and a paid website on the studio's own domain.
Read the guide ›Studio
Client galleries, favorites, and downloads
Deliver client photographs privately while keeping access, downloads, storage, and backup responsibilities explicit.
Read the guide ›Founding releasePrint ordering with Prodigi
Plan a print-on-demand offer without confusing Patsy's subscription, payment processing, production cost, shipping, taxes, and photographer markup.
Read the guide ›Founding releaseInquiries, bookings, deposits, and reminders
Design a calm client path from first inquiry to confirmed session without pretending every conversation can be automated.
Read the guide ›Growth
Help and ownership
Calling in human help
Know when to keep working with Patsy, when to use direct controls, and when a person should take over.
Read the guide ›In developmentOwnership, exports, retention, and leaving
Separate what belongs to the photographer from what the platform hosts, generates, retains, or can export.
Read the guide ›Planning a move from another platform?
Migration guides cover platform-specific inventories, backups, public-site cutover, active client protection, and the limits of automated imports.
