GoSeedly Summer Camp Kit
An enrollment board for day and overnight summer camps: every camper by week under their sessions, with the cabin or day group the office assigned, the waitlist and its offers, which camp forms came back and the tuition lines. Bunkline follows the camp year from fall planning to summer wrap-up, keeps campers as a first name and last initial, and records whether a form came back, never what it says.
YOUR BUNKLINE WORKSPACE
01 — CAMP WEEKS
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 / Camp weeksThe needs-attention strip, then every camper as a row and the eight camp weeks as columns under their four sessions, the current week marked. Each cell shows the cabin or day group, or a waitlist place or an offer with its reply-by date, and each row ends with how many camp forms are back. Beside it: forms still out, tuition due and the waitlist.
02 / CabinsEvery cabin and day group as a row and every week as a column, with the campers in it and a count against the places set in the kit config. Group places count toward a cabin separately from named campers, and held weeks with no cabin yet sit in their own row.
03 / FamiliesEvery family with its campers, weeks held and waiting, camp forms back and tuition still due, families with an alert first.
04 / FormsEach camper against the registration, health history, pickup authorization and photo permission forms, with the date each went out or came back. Bunkline records whether a form came back, never what is on it.
05 / TuitionEvery tuition line with its kind, amount, due date and status, past due lines first. Money is totalled per status and currency only.
06 / WaitlistEvery camper waiting for a full week and every place offered, with the date they joined the waitlist and the reply-by date. An offer past its reply-by date leads, in red with the words Offer reply overdue.
07 / InsightsFilter buttons for each alert, then weeks by status with campers and group places in their own columns, camp forms by kind, tuition by status and families by how they heard about camp.
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 13 fictional families for one camp year: 15 campers and one scout troop, 44 weeks across day groups and overnight cabins by May, a waitlist with five campers waiting or offered in late June, 62 camp form rows and 117 checklist steps. Registrations, forms back and paid lines follow today's date, so the board shows next summer's families in the off season and a full grid in summer. Sample edits stay in memory and reset on navigation or reload.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
Editable native forms and document templates give your team a practical starting point.
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Open each template in Documents and complete it for the actual job or visit.
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
One contact-linked family holds its guardian label, how it heard about camp, the camp year and the date it registered, plus each camper as a first name and last initial with an age band (or a group label with its places), every week with its program, cabin or day group and status, every camp form with its sent and received dates, every tuition line with its amount, due date and status, and an editable checklist.
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 camp name, descriptor, default pipeline name, the camp calendar (first week, number of weeks, weeks per session) and the cabins and day groups with their places. 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 backend helpers are required for connected family creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, refuse full camper names, children's health and custody details, access codes, logins, card numbers and Social Security numbers, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Bunkline records what the camp office typed. It makes no licensing, accreditation, safety, medical or insurance statement, and it does not collect or hold camp forms, health or pickup details, run registration, take deposits or payments, invoice, assign beds, check ratios or send messages. Campers are minors: full names, dates of birth, exact ages and health, allergy, medication, dietary and custody details are refused, as are gate, cabin, office and Knox box codes, passes, passwords and logins, payment card numbers and Social Security numbers, in recorded text and in the native form drafts.
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.
Bunkline keeps its white side rail and lichen lanyard edge 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.
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.