Skip to content
View packages

CRM KitsPrivate and independent school admissions offices

Every entering grade. Every open seat.

An admissions funnel for independent day schools: entering grades as rows, inquiry, tour, applied, visit day, decision and enrolled as columns, with each grade's open seats against the offers made. Inkwell follows the admissions year from fall tours to spring re-enrollment and a quiet summer, keeps students as a first name and last initial with an entering grade, ticks application items as they come in and never holds what they say.

Funnel in the GoSeedly Private School Admissions Kit with fictional sample records

See every entering grade from inquiry to enrolled.

The needs-attention strip, then every entering grade as a row and the six steps as columns, each number the students who reached that step, with the grade's seats beside the offers made and a strip of seat boxes for enrolled, awaiting a reply and open. Beside it: replies due, visits in the next 14 days and files still open. In spring the same home view becomes the re-enrollment board, and in summer a quiet board of next fall by grade.

Actual interface captures with fictional sample data. Open a screenshot to see it full size.

What’s in the kit

Screens

  • Admissions funnel by entering grade with seats against offers
  • Spring re-enrollment board and a summer board
  • Inquiries operating view
  • Tours and open houses operating view
  • Applications operating view with item checkboxes
  • Decisions and waitlist operating view
  • Re-enrollment operating view
  • Families and Insights operating views
  • Three native form drafts and three editable document templates
  • Editable family checklists and preserved row history

four pipelines

  • New student admissions · 8 stages
  • Waitlist · 7 stages
  • Re-enrollment · 7 stages
  • Feeder schools and partners · 7 stages

Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.

nine workflow drafts

  • Answer the admissions inquiry
  • Tour confirmation
  • Application file follow-up
  • Visit day confirmation
  • Decision letter check
  • Reply-by follow-up
  • Waitlist seat review
  • Intent form follow-up
  • Contract follow-up

Inactive until you review and publish them. None send customer messages.

Forms and documents

  • Admissions inquiry
  • Tour or open house request
  • Re-enrollment intent
  • Family admissions summary
  • Visit day sheet
  • Re-enrollment status by grade

Editable native forms and document templates. Forms collect information for staff review.

Sample workspace

Explore 20 fictional families for one admissions year: 15 new students applying to entering grades from PK3 to Grade 7 (one withdraws) and 9 current students re-enrolling, with open houses, tours, visit days, application items, decisions, replies, deposits and re-enrollment contracts on real calendar dates. The home view follows today's date: the funnel in fall and winter, the re-enrollment board from mid-March and a quiet board in summer. Sample edits stay in memory and reset on navigation or reload.

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
Read the installation guide
  1. Check your Seedly

    Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.

  2. Connect the helper

    Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.

  3. Make it yours

    Set school name, descriptor, default pipeline name, the admissions calendar (file deadline, decision and reply dates, intent and contract due dates, when the spring and summer boards begin) and the entering grades with their open seats. 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 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 student names, children's details, access codes, logins, card, bank, passport, license and ID numbers in recorded text and in family and parent labels, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.

One contact-linked family holds its parent contact, how it heard about the school, the admissions year, the first contact date and tuition assistance as a label, plus each student applying as a first name and last initial with an entering grade, file status, decision, reply-by date, reply and deposit as recorded, each current student with the intent and contract dates, every tour, open house, visit day and interview, each application item as a checkbox, and an editable checklist.

Inkwell records what the admissions office typed. It makes no accreditation, admissions outcome, financial aid or enrollment statement, and it does not decide, rank or offer anything, run an application portal or testing, hold transcripts, take payments, bill tuition, send contracts, collect signatures or send messages. Students are minors, so a guard against accidental entry refuses the common ways these details get typed: full student names, dates of birth, ages written with a name, test scores and academic grades, learning support, diagnoses, behavior, custody and medical details, along with door, gate and carpool codes, passes, passwords and logins, card, bank, routing, Social Security, passport, driver license and student ID numbers, in recorded text and in the native form drafts. Form answers are capped at 250 characters, names at 80, and phone answers take a phone number only. It is a guard, not a guarantee. A matching Seedly school website template is available separately.

Four optional pipeline templates and nine inactive workflow drafts. 20 fictional in-memory families.

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 Private School Admissions Kit

Checking access…

DevLaunch All Access

Every kit and every template.

See DevLaunch All Access

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?

Inkwell keeps its framed canvas and boxed view tabs 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.

Browse all 220 kits

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.