# EdYou Japan — scope & payment discussion draft

Prepared after reviewing Khushi’s transcript and five screenshots. Review the clickable HTML first; this proposal is not an accepted contract or invoice.

## Delivered visual prototype
A self-contained offline HTML demonstration of student records; four-factor quotations (student residence, degree, package, agreement month); editable discounts; explicit Khushi approval; simulated quotation email; parent acceptance; two-day reminders; Japan/India/Global payment instructions; manual payment confirmation; family onboarding-folder preview; status tracking and activity history. Fictional data and sample prices only. Reloading resets the session.

The styling follows the Career Doctor screenshot’s pale background, navy typography, gold divider, rounded table and restrained red accents. The parent form replaces PDF comments with structured fields. The current workflow begins after consultation and covers steps 6–11; superseded screening steps are excluded.

## Proposed implementation, subject to written approval
- Secure admin access, persistent student records and an approved pricing matrix with quote version history.
- Approved email templates and sender configuration; delivery monitoring, retries and duplicate-send protection.
- Parent acceptance tied to a quote version, approved terms and an auditable date/signature record.
- Scheduled acceptance reminders every two days, stopped on acceptance or withdrawal; agree expiry, escalation and payment follow-up rules.
- Approved Japan bank, India bank and Global Wise instructions, with payer route confirmed separately where needed.
- Khushi’s manual payment verification, followed by a restricted individual Drive folder and student welcome email with parent CC.
- Deployment, acceptance testing, operational documentation and handover, to an agreed extent.

No consultation/screening or NeetoCal integration, post-onboarding counselling, automated bank reconciliation or live payment collection is included in this proposed scope unless added in writing.

## US$600 — definition required before payment
The supplied transcript mentions a requested 50% advance but does not establish what US$600 covers or confirm acceptance of that arrangement. Both parties must select and document one interpretation: prototype only, a listed implementation deliverable, or an initial phase/deposit toward a separately priced project. Explicitly state whether this supplied prototype is included, complimentary or separately billable.

If both parties agree US$600 is the total implementation fee, a proposed split is US$300 after written scope approval and US$300 after agreed acceptance checks and handover. This split is conditional; no payment is requested by the demo.

The signed scope should itemize included deliverables, revision rounds, ownership/source handover, taxes/transfer fees, third-party subscriptions, hosting, maintenance, warranty/support duration, response times and change-request rates. Maintenance and external costs are not assumed to be included or excluded: record the actual agreement.

## Decisions needed from Khushi
1. Approve visual direction and the demonstrated journey.
2. Supply approved prices, currencies, package inclusions, discount permissions, monthly rules and missing degree combinations. The June/August and December boundaries overlap in the transcript; the demo uses provisional non-overlapping rules.
3. Approve service terms, acceptance method, sender, recipients, payment instructions and folder access rules. Confirm treatment of adult students and parent CC.
4. Confirm student record source, migration responsibility, failure handling and retention/privacy requirements.
5. Agree milestones: design sign-off → pricing/template confirmation → implementation → user acceptance testing → handover. Confirm the year and date of the requested February/March target; no delivery date is promised here.
6. Sign the exact scope, fee coverage and payment schedule before implementation or advance payment.

## Proposed acceptance checks
Verify all approved pricing combinations and missing-price blocks; edited quotes require fresh approval; parent acceptance preserves the accepted quote; reminders recur at 48-hour intervals and stop correctly; regional instructions match the approved route and amount; no onboarding occurs before verified payment; welcome emails contain the correct student-specific folder and parent CC; separate family accounts cannot access each other’s files; failed deliveries surface for retry without duplicates.

## Prototype limitations
No authentication, real emails, scheduler, bank connection, PDF generation, database or Drive permission enforcement. Demo prices and typed signatures do not establish live service terms. The local folder preview demonstrates intent, not actual security. Production requires real access-control and integration testing.

## Additional Drive review
The supplied Drive folder contains three quotation PDFs (Japan Bachelor discount, Global Bachelor, Global Master), Email Templates, source spreadsheets and an onboarding template. The email examples quote Global premium Bachelor at USD1,250 and Japan at JPY110,000 including 10% tax. The India email also shows JPY110,000 alongside Indian bank instructions, so India settlement currency and conversion require explicit confirmation. These examples do not establish the full approved matrix. This prototype intentionally retains clearly marked sample prices and placeholder bank details. Its onboarding preview now mirrors the source structure: University Tracker/Checklist, School Documents, Personal Identification and Extracurriculars. Real families must receive individual copies with restricted access, rather than the shared template link.