Project Brief Speccing Phase July 16, 2026 Maryland

The Summit School
One platform, one login.

Laravel 13+ Tailwindcustom build
Stack — Laravel 13 · Tailwind · fully custom design Source — discovery meeting w/ Nancy (admissions) & Kassie (marketing) Status — spec only, no design or build yet
01 The Problem

Six platforms, five logins, and the most urgent department has nothing at all.

Every vendor they asked — Monday.com, Salesforce, FinalSite — said their school-plus-parallel-program model needs two systems. Meanwhile the Summit Resource Center runs its entire pipeline out of a Google Sheet, follow-ups live in Katie's memory, and 85 summer campers plus 50 waitlisted families receive zero ongoing communication.

PlatformWhat it does todayCost / yrFate
FinalSite — websitePublic site + mass emailWebsite & communications~$7,700Replace
FinalSite — enrollmentex-SchoolAdminInquiry → application → enrollment, parent portal~$7,700Replace
Bloomerang + Qgiv3 modules, separate loginsDonor CRM, fundraising email, event tickets, online auctionest. $5,000+Replace
TutorBirdTutor attendance → in-house billing~$1,200Replace
Google SheetsThe entire SRC "CRM"freeReplace
FACTSTuition management + financial aidunknownSplit
AlmaSIS of recordDemographics, attendance, schedules, report cardsunknownKeep + integrate
Google ClassroomAssignment grading (middle school)freeKeep

FACTS splits: financial aid stays (external reviewers are mandatory — integrate, don't replace); tuition management may move in-house in a later phase. Known spend is already $21k+/yr before Bloomerang's real number.

$21k+/yr
Current platform spend
135
Campers + waitlist, never contacted
150
Max students, new building ~Apr '27
< 1tuition
Target build cost (~$36k anchor)

One custom platform, one login, one database — for less than a single tuition, with hosting and support as the only recurring costs.

The Pitch — as framed in the meeting
02 Build Order

The CRM is the backbone. SRC hurts the most. The website ships with phase one.

Each phase ships usable — departments keep working live while the next division is bolted on. Roles & permissions get a tuning pass at the end of every phase, plus a department walkthrough meeting.

1

CRM core + Summit Resource Center + public website

The backbone: contacts, tags, segments, comms, form builder, automations. SRC pipelines (testing, benchmarking, tutoring, summer camp) with scheduler and payments — Katie goes from a Google Sheet to a real system. Website launches alongside; forms embed or link out either way.

Most urgentCRMSRCWebsiteChatbot
2

School admissions & enrollment portal

Inquiry → applicant → enrolled pipeline, application with uploads and educator questionnaire, acceptance workflow, parent portal with stage-assigned forms, re-enrollment rollover. Retires FinalSite enrollment.

AdmissionsParent portalProgress bar
3

Development, events & fundraising

Donor management, capital campaign tracking, event registration + ticketing (golf, Bash, Bingo, community talks), the annual online auction. Retires Bloomerang/Qgiv. Needs discovery with Tiana first.

DonorsTicketingAuction
4

Later & optional

Tuition management in-house (deposits $3,500/$5,000 by contract date; 1, 2, or 9-payment plans; proration), open-house device check-in, and — only if they ever ask — a scaled-down SIS to replace Alma at ≤150 students.

TuitionCheck-inMaybe never
03 The Modules

Everything is a form. Every person is a contact. Tabs appear as services attach.

Backbone

CRM

  • Student-centric where students exist — kid is the anchor; parents & grandparents link with labeled relationships
  • Standalone contacts too — donors like "Alan" with no student link are first-class records
  • Dynamic profile tabs per assigned service; Overview / Events / Donations for everyone
  • Auto-tagging (tutoring-2026, form submissions) + manual tags; lists drive all email
  • Marketing opt-out, never delete — history must survive staff turnover
Phase 1 focus

Summit Resource Center

  • Four services, four pipelines: testing (~4 meetings + payment), benchmarking, tutoring (match → sessions → in-house billing), summer camp (mini application)
  • Scheduler + payment processing — SRC is a revenue generator
  • Document "file cabinet": psych evals & report cards visible to the assigned tutor
  • Weekly tutor progress form → the "what did I pay for?" answer for parents
Phase 2

Admissions & Enrollment

  • Inquiry → Applicant → Enrolled; staff-only stage moves; declined families stay, suppressed
  • Application: uploads, photo, educator questionnaire emailed to the teacher, $110 fee, PDF export for offline review
  • Portal with stage-assigned forms: signatures, pickup authorization, immunization uploads
  • Applicant progress bar; year-end rollover resets re-enrollment paperwork
  • Per-form recurrence: once-ever (media release) vs. annual (health update)
Platform primitive

Form Builder

  • Signature, checkbox, multiple choice, uploads, read-and-acknowledge fields
  • Staff edit & publish instantly — no developer turnaround for policy tweaks
  • Public shareable link + website embed for every form
  • Per-contact status: clock = pending, green check = done
Phase 3

Development & Events

  • Donor profiles, donation history, capital-campaign tracking
  • Ticketing for golf, Bash, Bingo; free registration for talks & symposium
  • Annual online auction (logistics discovery needed)
  • Shared email templates — build once, another department sends
Ships with Phase 1

Website + AI Chatbot

  • Reposition: prospect-family-focused, plain-language explanations of terms like executive functioning
  • Kill the click-maze: "Schedule a Tour" = one click to a pre-filled mini form
  • Events in chronological order (FinalSite can't); slim non-sticky header
  • Mascot chatbot: conversational forms with live tour dates, stored chat logs as marketing intel, hard guardrails on sensitive topics (financial aid → human)
04 Load-Bearing Decisions

The five choices everything else hangs from.

i.

Contacts are first-class; the student link is optional.

The part every vendor got wrong. Student-anchored families and standalone donors must live in one model — profile tabs attach per service, navigation between linked people works like Ancestry.

ii.

Build the automation system, not the automations.

Staff define trigger → condition → action themselves. The canonical requirement: Katie's Tuesday dashboard says two weeks since you heard from Kassie about testing — call her.

iii.

Never delete — suppress.

A marketing opt-out checkbox (transactional mail still flows) replaces FinalSite's delete-to-silence. I get hit by a bus tomorrow, they reapply in six months — someone needs to know the history.

iv.

Sensitive data is segregated by design.

Immunization records, psych evals, financial-aid PDFs: encrypted, access-logged, stored apart from typed form data. HIPAA named explicitly. No SSNs in form fields, ever. Student names never appear publicly.

v.

Permissions are granular and per-person.

Role presets plus individual toggles; department-scoped visibility; field-level hiding (financial-aid amounts); confirmation warnings on destructive actions — requested by name.

05 Integrations
  • Alma SIS — keep as system of record; sync so nobody re-keys student data. Staff-only; parents don't log in.
  • FACTS — integrate for financial aid (external reviewers mandatory), like the background-check-system precedent.
  • Authorize.net or Stripe — open decision. Auth.net ~3% today; Stripe 2.9% + 30¢ with Terminal hardware for in-person.
  • Square — current in-person events processor; consolidate or keep.
06 Commercial Frame
  • Marketing budget ≈ $80k total, with pre-existing commitments carved out; the board cut it after last year's underspend.
  • CRM + website together may exceed this fiscal year — phasing and payment timing matter.
  • Anchors: current $21k+/yr platform spend; less than one tuition (~$36k).
  • Recurring: hosting + annual support, nothing else.
  • Urgency: growth targets + new building opening ~April 2027.
07 Open Questions

What discovery still owes the spec.

SRC pipeline walkthrough Exact steps, forms, and payment points for testing, benchmarking, tutoring, camp. → Katie
Development inventory Everything Bloomerang actually does — auction logistics, donor letters, campaign reporting. → Tiana
Alma API surface What does it expose, which way does data flow?
FACTS integration Real API or link-out only?
Payment processor Authorize.net vs. Stripe — get the current effective rate and volume.
Form recurrence policy Which forms go once-ever vs. annual (media-release decision pending internally).
Financial aid in-platform? Nancy unsure they even want it inside the system.
Bloomerang's real cost Needed for the proposal's comparison table.
Chatbot v1 scope Public site only or portal too? Which actions?
Auction logistics Item catalog, bidding windows, payment capture — build vs. integrate.
08 Promised Deliverables