# Onboarding MVP Scope Summary

## In-Scope MVP

- Public landing page for CandleCraft Academy
- Public enquiry/contact form
- CAPTCHA or equivalent spam prevention on the contact form
- Secure admin login
- Admin inbox for incoming enquiries
- Admin message detail/review screen
- Message status management for incoming enquiries
- Core validation, security, and acceptance-readiness work

## Out of Scope / Future Backlog

- Booking workflows and payment
- Student portal
- Parent portal
- Teacher/staff tooling beyond message review
- Learning resources and content library
- AI chat, recommendation, or workflow features
- In-system email replies
- File attachments
- Analytics dashboards beyond basic inbox management

## Assumptions

- Onboarding is enquiry-led rather than booking-led.
- Visitor and admin are the only MVP roles.
- Interest area should distinguish pottery, knitting, both, or unsure.
- CAPTCHA provider is flexible.
- Status tracking is useful in MVP.

## Risks

- Business expectations may drift from enquiries to booking capture.
- Missing clarity on admin workflow could under-scope dashboard behavior.
- Security/authentication choices depend on the eventual framework.
- The two-week delivery window requires hard scope control.

## Open Questions

- Is message search required on day one?
- Does admin need internal notes?
- Is one admin account enough operationally, even if multi-admin support is modeled?
- Should subject be required or derived from category?
- Are detailed mobile wireframes needed before implementation?

## Recommended MVP Boundary

Build only what is required to attract interest, capture valid enquiries, prevent spam, and allow the owner/admin to securely review and manage inbound messages. Any feature that does not directly support that flow should be deferred.
