GoSeedly Tutoring & Learning Center Kit
A learning center runs on a repeating week. Studyroom puts that week on one white page: students as rows, weekdays as columns, and every recorded session as a coloured subject chip, with the selected student sheet underneath.
YOUR STUDYROOM WEEK
01 — WEEK GRID
Actual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
One connected workspace, with views built around the decisions your team makes each day.
01 / Week gridOne row per student enrollment, seven weekday columns, and a chip for every session your team recorded. Chip colour comes from the recorded subject label, so the week reads as a subject mix without opening anything.
02 / Student sheetSelect a row or a chip and the sheet below fills in: guardian, grade and school labels, the tutor label, the recorded package and what is left of it, the next review date with its band, the reference notes and every recorded progress review.
03 / Enrollment rosterEvery enrollment with its subjects, tutor label, sessions remaining and next review date. An enrollment with no recorded package reads "Not reported" rather than zero, and one past its package reads how far over it is.
04 / Recorded sessionsPick a date and see the sessions recorded for it, grouped under the tutor label on each row, with the subject legend repeated. Record attendance on a booked row without leaving the page.
05 / Progress reviewsRecorded next review dates banded against the selected date: overdue, seven days, thirty days, later, and a separate group for enrollments with no date recorded at all. Every review your team wrote is listed underneath with its next steps.
06 / Tutor labelsEach recorded tutor label with its session count for the selected week, the recorded attendance beside the number of rows that qualified, and the students those sessions belong to. The page says plainly that a label assigns nobody.
07 / Center insightsSessions by palette subject, recorded outcomes, review cadence and package use. Recorded attendance prints its own denominator, and nothing is inferred from a date passing.
YOUR PROCESS, YOUR STARTING POINT
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
Explore twelve fictional student enrollments across one week, with 36 recorded sessions covering all six palette subjects plus one label outside it, a recorded no-show and cancellation, and 11 progress reviews spread across every review band. Example edits stay in the current page’s memory and reset on navigation or reload; no fictional family is ever inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
One student enrollment is a native contact-linked opportunity with namespaced student, grade, school, guardian and tutor labels, up to eight recorded subject labels, a reference package count and price, enrollment start and next review dates, reference notes, session rows and progress review rows. Two enrollments for one student, or two children in one family, stay independent records; unrelated custom fields are preserved.
FROM KIT TO CONNECTED WORKSPACE
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
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.
Edit center name, descriptor, and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
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 enrollment helper is required for connected creation, editing and starter setup. It checks the active account and native permissions, compares both the record timestamp and a server-managed revision, preserves unrelated custom fields and unknown session and review values, and refuses to drop an existing row from a save. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional and install inactive.
Every value on screen is a label, a date, a duration or a short note typed by a member of staff. A session row records a slot the center agreed: it reserves no room, no tutor and no time, creates no native Calendar appointment, detects no conflict and repeats nothing, and an empty cell means only that nobody recorded a session there. A progress review is a staff-written summary with agreed next steps, not a score, a mark, a rubric or a test result, and the grade label is the grade the student is in. Recorded package counts and prices are reference figures: nothing is charged, invoiced, collected, refunded, prorated or recognized as revenue, and no balance is tracked. Subject chip colour comes from an exact match on the recorded label, so a subject your center invents keeps a neutral gray chip instead of borrowing another subject’s colour, and every chip prints its label as text. This is not a learning management system, a curriculum, an assessment or grading system, or a student information system, and it makes no FERPA, COPPA or other compliance claim.
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.
DEVLAUNCH ALL ACCESS
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.
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
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 AccessAlready 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
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.
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.
Studyroom keeps its white top bar and text-tab navigation across the original learning center views and native CRM modules. The permission-filtered All CRM tools drawer keeps the full CRM inside the same signed-in account and 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.
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.
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.
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.
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.
Find a workspace that fits the way you work.
Explore all CRM kitsCustomer experiences / Trustpilot
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
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.
Read our Cookie Policy and Privacy Policy.