Every seat, every shelf, every firing, as recorded.
A studio front desk for pottery and art studios: the week's class sessions on one grid with seats booked against each seat count, rosters kept as seat counts with a grown-up booker, a kiln queue of work on the shelf, in the kiln and on the pickup shelf, studio memberships with shelves and renewal dates, class and member fees, and instructors and rooms. Leatherhard never stores a young student's name, age or date of birth, or health and allergy details.
See overbooked classes, missing instructors, slow firings and lapsed renewals first.
Classes with seats booked over the recorded seat count, a session within three days with no instructor, work waiting more than 14 days for a firing, fired work left on the pickup shelf more than 30 days and memberships past their renewal date lead. Then the session grid shows today and the next six days, one row per class with each session's time, its number in the class and seats booked, and below it the kiln queue in pieces and memberships at a glance.
Keep every roster as seats with a grown-up booker.
One roster per open class: grown-up booker, seats, booking status, payment and recorded fee, with confirmed, held, waitlisted and cancelled seats in the footer. Then the sessions held in the last 60 days with attendance and seats booked in separate columns.
Follow every board from the shelf to the pickup shelf.
Four lanes: on the shelf, in the kiln, on the pickup shelf and picked up in the last 30 days. Each card carries its ware label, maker or class, bisque or glaze, cone and kiln labels, pieces and days. Then pieces not yet picked up by kiln and firing.
Studio memberships with plan, shelf, start, renewal, monthly fee and status, the active memberships renewing in the next 30 days and each member's work in the kiln queue in pieces.
Open balances with each class's next session, paid bookings on open classes, fees by class and monthly member fees in their own table. Money only, as the studio recorded it.
The next 14 days of scheduled sessions grouped by instructor, then instructors and rooms as ledgers counted in sessions. Instructor and room entries are labels the studio typed.
Records by status, seats booked by audience, bookings by status, sessions by status, the kiln queue by state in pieces and class fees by payment status. Seats, sessions, pieces and dollars are never added together.
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.
Classes and courses · 7 stages
Workshops and private events · 7 stages
Studio memberships · 7 stages
Commissions and wholesale orders · 8 stages
02 / NINE WORKFLOW DRAFTS
Give the next step a shape.
Share the class listing
Check the waitlist
Class wrap-up
New workshop or party inquiry
Quote follow-up
Confirm the seat count
Studio tour
Welcome a new member
Commission pickup
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 12 fictional studio records: nine classes (six courses, two workshops and one private party) and three studio memberships, with 26 sessions, 37 bookings holding 74 seats and 9 kiln queue entries holding 91 pieces. Sample edits stay in memory and reset on navigation or reload.
No sample customers are inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
From the first inquiry to the final handoff.
Editable native forms and document templates give your team a practical starting point.
01 / INTAKE & FOLLOW-UP
Three ready-to-edit forms.
Class signup request
Private event or party inquiry
Studio membership interest
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
02 / WORKING DOCUMENTS
Three reusable templates.
Session roster sheet
Kiln load sheet
Fired work pickup notice
Open each template in Documents and complete it for the actual job or visit.
03 / THE NEXT STEP
Checklists alongside the work.
Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.
Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.
THE KIT, UNPACKED
Your workspace. Your starting point. Your code to edit.
One contact-linked studio record is a class or a membership. A class holds its title, medium, instructor, room, audience, recorded seat count and status, sessions with date, times, status and attendance, bookings with a grown-up booker, seats, status, recorded fee and payment, kiln queue entries with ware, pieces, firing, cone and kiln labels and dates, and an editable checklist. A membership holds the member, plan, shelf, start and renewal dates, monthly fee, status, kiln queue entries and a checklist.
Sessions operating view
Rosters operating view
Kiln queue operating view
Members operating view
Fees operating view
Instructors operating view
Insights operating view
Three native form drafts and three editable document templates
Editable class and membership checklists and preserved row history
Four optional pipeline templates and nine inactive workflow drafts
12 fictional in-memory studio records
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
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 backend helpers are required for connected class and membership creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, refuse access codes, logins, card numbers, young students' names and ages and health details, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Leatherhard records what the studio planned, booked, counted, fired and was paid. It does not run, program, schedule or monitor kilns and makes no kiln-safety, firing, certification or insurance claim; it does not take payments, sign waivers, bill members or check room or instructor overlaps. It is not a student register: young students' names, ages and dates of birth, health and allergy details, card numbers, Social Security numbers, and door, kiln room, locker or gate codes and passwords are refused in recorded text and in the native form drafts, while labels such as Cone 6, Kiln 2, 10 lb clay and Session 4 are kept.
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.
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?+
Leatherhard keeps its porcelain rail with witness cone markers across the kit views and native CRM tools in the same signed-in account. 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.
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
Your privacy, your choice.
We use essential storage to keep the site working. With your permission, we also use analytics and the Whop Pixel to understand visits and advertising results. Optional analytics stay off until you choose.
01 / Sessions
