CRM KitsPhotography studios
Every session, shot to delivered.
The shoot is one afternoon. The culling, the editing, the gallery, and the print order are the weeks that follow. Frame is a strictly monochrome studio workspace built around that delivery pipeline, with every visual drawn in code rather than borrowed from a photo library.
The studio wall, one tile per session.
Every session is a large 3:2 tile with an original drawn frame motif, a session type glyph, and a six-step delivery stepper filled through the recorded stage. The recorded date, location label, photographer, package, gallery due date, and print order count sit under it.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Monochrome gallery grid of session tiles with a six-step delivery stepper
- Calendar week list of recorded session dates
- Deliveries register grouped by recorded stage, with overdue rows first
- Print order ledger and package label review
- Studio insights drawn from recorded workspace data
- Black and white Frame application frame with full CRM tools
four pipelines
- Portrait sessions · 7 stages
- Wedding coverage · 8 stages
- Commercial and product · 7 stages
- Print and album orders · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Enquiry response review
- Booking confirmation note
- Pre-session prep review
- Culling reminder
- Editing due check
- Gallery delivered note
- Print order follow-up
- Album approval review
- Anniversary session outreach note
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore ten fictional sessions across all six delivery stages, with eight print order records including one archived row, two overdue galleries, and repeated package labels. Example edits stay in the current page’s memory and reset on navigation or reload; sample sessions are never inserted into your CRM.
No sample customers are added to your CRM.
Setup and source
- Guided setup and compatibility report
- Private rollback receipt
- AI-agent guide for customized installations
- Original editable source, configuration, and tests
How setup works
Full installation guideCheck your Seedly
Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.
Connect the helper
Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.
Make it yours
Set studio name, descriptor, and default pipeline name. Then sign in and check the workflows and permissions your team uses.
Technical details and compatibility
Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original studio helper is required for connected creation, editing, and starter setup. It preserves native account permissions and unrelated custom fields, checks the current record state before saving, and exposes no stage mutation of its own. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
A session is a native contact-linked opportunity with namespaced session type, date and time, location and photographer labels, package label and reference, a six-step delivery stage, gallery due and delivered dates, shot list notes, and print order rows with stable IDs. Package and print amounts are recorded planning references, separate from native opportunity value.
The kit stores no photographs and hosts no gallery: the frame motif and every session type glyph are original inline SVG drawn at render time, and no image file ships with the pack. There is no client proofing, no print lab integration, no online booking, no calendar sync, no contract or e-signature, and no payment. Session dates, photographer labels, and print order statuses are staff-entered records that reserve nothing and assign nobody. The delivery stage is the kit’s own field; the native pipeline stage stays your CRM’s and changes only through its own mutation and its own permission.
Four optional pipeline templates and nine inactive workflow drafts. Ten fictional in-memory sessions and eight recorded print orders.
Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.
Get the Photography Studio Kit
Checking access…
DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 270 website templates for Seedly Sites
- Every class, course, and product we release, added as it ships
- Private calls with Aaron
Already a member? Open your downloads.
Questions
How do I receive the kit?
Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.
Does this include Seedly CRM?
You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.
Is this one connected workspace?
Frame keeps its studio navigation across the original session views and native CRM modules. Full CRM tools remain available within the same signed-in account and application theme. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.
Can I use it with existing customizations?
Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.
Do I have to import all the starter content?
No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.
Can I remove the examples and starter content?
Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.
Can different subaccounts use different kits?
The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.
More hospitality, events & creative kits
Browse all 220 kits
