Skip to content
View packages
CRM Kits Photography studios

GoSeedly Photography Studio Kit

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.

Checking access…See the interface
One-time purchase · USD · Your Seedly backend · Editable kit source

YOUR FRAME STUDIO WORKSPACE

01 — SESSIONS
Frame studio wall of monochrome session tiles, each with a code-drawn frame mark, a session type glyph and a six-step delivery stepper, using fictional sample data

Actual interface captures with fictional sample data. Open a screenshot for a closer look.

TAKE A CLOSER LOOK

From the booked date to the print order.

One connected workspace, with views built around the decisions your team makes each day.

Sessions in the GoSeedly Photography Studio Kit with fictional sample records01 / Sessions

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.

Session record in the GoSeedly Photography Studio Kit with fictional sample records02 / Session record

One record, opened in place.

Record the session type, date and time, location and photographer labels, package label and reference, delivery stage, gallery due and delivered dates, shot list notes, and print order rows. Currency is chosen once and is immutable afterward.

Calendar week in the GoSeedly Photography Studio Kit with fictional sample records03 / Calendar week

The week, as it was written down.

Recorded session dates and times for the Monday to Sunday of the chosen date, with the client, location label, and photographer label on each entry. Nothing here is booked, held, or synchronized with a calendar.

Deliveries in the GoSeedly Photography Studio Kit with fictional sample records04 / Deliveries

What the studio still owes.

Sessions grouped by their recorded delivery stage, with overdue rows leading each group and the days between the recorded due and delivered dates. The CRM pipeline stage sits beside it and stays your CRM’s to change.

Print orders in the GoSeedly Photography Studio Kit with fictional sample records05 / Print orders

The order ledger.

Every recorded print order row across the loaded sessions: item, quantity, amount reference, ordered date, status, and the session and client it belongs to. Archived rows are preserved and shown on request.

Packages in the GoSeedly Photography Studio Kit with fictional sample records06 / Packages

What the studio actually wrote down.

The package labels in use, how many sessions carry each one, the lowest and highest recorded reference, how many of those sessions recorded a reference at all, and the delivery stages they sit in.

Insights in the GoSeedly Photography Studio Kit with fictional sample records07 / Insights

Read the studio records honestly.

Session counts by delivery stage and type, print order counts and amounts by status, and recorded delivery timing. The on time rate uses only sessions with both dates entered; the rest are excluded rather than counted late.

YOUR PROCESS, YOUR STARTING POINT

Useful structure.
Only what you choose.

4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.

01 / FOUR PIPELINES

Choose your starting structure.

Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.

  1. Portrait sessions · 7 stages
  2. Wedding coverage · 8 stages
  3. Commercial and product · 7 stages
  4. Print and album orders · 7 stages
02 / NINE WORKFLOW DRAFTS

Give the next step a shape.

  • 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

Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.

03 / SAMPLE WORKSPACE

Explore before adding records.

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 inserted into your CRM.

Starter setup checks selected kit additions before removal and preserves edited records and live work.

THE KIT, UNPACKED

Your workspace.
Your starting point.
Your code to edit.

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.

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 optional pipeline templates and nine inactive workflow drafts
Ten fictional in-memory sessions and eight recorded print orders
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Read the installation guide

FROM KIT TO CONNECTED WORKSPACE

Check. Connect.
Make it yours.

01

Check your Seedly project.

Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.

02

Connect the required helper.

Deploy the included helper from your authoritative backend source before connected edits. Build your web app, then choose any optional pipelines and drafts you need.

03

Set up your own team.

Edit studio name, descriptor, and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.

Compatibility and operational details

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.

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.

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.

Checking access…

DEVLAUNCH ALL ACCESS

Every kit.
And everything else.

DevLaunch All Access includes every GoSeedly CRM kit, all 195 available today, along with every class, course, and product we release, and private calls with Aaron.

  • All 195 CRM kits

    Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits

  • Every class, course, and product

    The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.

  • Private calls with Aaron

    Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.

DevLaunch All Access

Want more than one kit? All Access covers the whole CRM kit library and the rest of what we make. See everything it includes on the All Access page.

See DevLaunch All Access

Already a member? Open your downloads.

For your own compatible Seedly CRM. Seedly software, hosting and installation services are separate. Each full-interface kit uses its own web installation.

BEFORE YOU MAKE IT YOURS

Good questions.
Clear answers.

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.

Customer experiences / Trustpilot

What customers say
about DevLaunch.

Read all reviews on Trustpilot ↗

Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.