Hyper-Local Parents-Helpers Marketplace Build

Account creation & verification
• Search & filter
• Public profiles
• Booking & payments (Stripe Connect)
• Messaging
• Reviews & ratings
• Availability calendars
• Admin back office
• Trust & safety (background check workflow)
• Notifications & analytics

Designed so Phase 1 (Landing) becomes part of V1, not throwaway.

⸻

1) High-Level Scope (Modules)
1. Public Marketing

• Home, How it Works, Districts Served, FAQ, Contact, Privacy, Terms, Blog.
• SEO, schema, fast performance.

2. Auth & Accounts

• Email/password + magic link (optional).
• Roles: Parent, Helper, Admin (RBAC).
• Email verification; password reset.

3. Profiles

• Helper public profile: bio, skills, district familiarity, rate, languages, sports, certifications, background-check badge, reviews, gallery (optional).
• Parent profile: household basics (not public), preferred districts, communication preferences.

4. Search & Discovery

• Filters: district(s), subject(s), sport(s), grade level, language, price range, availability window, verification (background checked).
• Sort: relevance, price, rating, new.

5. Availability & Scheduling

• Helper calendar (recurring availability + blackout dates).
• Parent request flow → propose times (1–3 slots).
• Booking confirmation & calendar invites (iCal attachments).

6. Booking & Payments

• Stripe Connect:
• Standard or Express accounts for Helpers.
• Card payments from Parents.
• Platform commission + optional booking fee.
• Payouts to Helpers (weekly default).
• Refunds/partial refunds; cancellation windows & fees.
• Taxes: collect helper W-9 details; year-end 1099-K (Stripe handles thresholds).

7. Messaging

• In-platform, session-scoped messaging (Parent–Helper).
• File sharing (small docs/screenshots), safe word filters.
• Email push for unread messages.

8. Reviews & Ratings

• Post-session review by Parents (1–5 stars + short text).
• Display aggregate rating; report/flag abusive content.

9. Background Checks (workflow)

• Integrate Checkr (recommended) or manual upload:
• Helper clicks “Start Check”.
• Status: pending → cleared → badge displayed.
• Admin override / revoke badge.

10. Notifications

• Email (SendGrid/Postmark): sign-up, booking events, reminders, receipts, review prompts.
• Optional SMS (Twilio) for reminders (helper opt-in).

11. Admin Back Office

• Dashboards: sign-ups, active users, bookings, revenue, disputes.
• CRUD: users, profiles, reviews (moderation), districts, subjects, sports.
• Trust & Safety: verify/revoke background badges; handle reports.
• Finance: payouts overview, fees, refunds, export CSV.
• CMS: FAQs/blog posts.

12. Analytics & Observability

• GA4 + event tracking; privacy-friendly analytics optional (Plausible).
• Error monitoring (Sentry), logging (structured logs).
• Funnel: visit → sign-up → profile complete → booking.

13. Legal/Compliance

• Terms, Privacy (GDPR/CCPA-aware).
• Minor safety: Parent contact is primary; COPPA-sensitive flows avoided.
• Data retention policy; consent logs; DSR workflow.

⸻

2) Data Model (Core Entities)
• User {id, role, email, phone, status, created_at}
• ParentProfile {user_id, name, city, zip, districts[], children_grades[], languages[], preferences}
• HelperProfile {user_id, name, bio, rate_min, rate_max, districts[], subjects[], sports[], grades[], languages[], certifications[], bg_check_status, media[]}
• AvailabilitySlot {helper_id, day_of_week, start_time, end_time, recurrence, blackout_dates[]}
• Listing/SearchIndex (denormalized helper fields for fast filters)
• Booking {id, parent_id, helper_id, start_at, end_at, status: requested/confirmed/cancelled/completed, price, fee_breakdown}
• Payment {booking_id, stripe_payment_intent_id, amount_gross, platform_fee, processing_fee, net_to_helper, payout_status}
• Message {booking_id (or thread_id), sender_id, body, attachments[], created_at}
• Review {booking_id, parent_id, helper_id, rating, text, public}
• BackgroundCheck {helper_id, provider, status, initiated_at, result_at}
• District {id, name, zip_ranges}
• Subject/Sport {id, label, tags}
• Audit/Consent {user_id, doc_type, ip, timestamp, version}

⸻

3) User Flows (Happy Paths)

Parent
1. Browse → Filter by district/need → Open Helper profile.
2. Choose a time → Request booking (or propose 2–3 times).
3. Pay to reserve (Stripe PI) → Confirmation email + calendar invite.
4. Session happens → Auto prompt for review → Receipt.

Helper
1. Sign up → Complete profile → Connect Stripe account → (Optional) Start background check.
2. Set availability → Receive requests → Accept/decline.
3. After session → Auto mark completed → Payout queued.

Admin
1. Review new helper profiles; verify background check status.
2. Handle disputes/refunds; moderate reviews; export finance.

⸻

4) Integrations
• Stripe Connect (payments/payouts, fees, refunds).
• Checkr (background checks) or manual upload in early weeks.
• SendGrid/Postmark (transactional email).
• Twilio (optional SMS reminders).
• Sentry (error monitoring).
• GA4 (analytics) + server events for bookings.

⸻

5) Non-Functional Requirements
• Performance: TTFB < 200ms (cached pages), Lighthouse ≥ 85/95/90 (Perf/A11y/SEO).
• Security: HTTPS, CSP, rate limiting, throttled auth, encrypted secrets, RBAC; file virus scan.
• Privacy: PII minimization; consent logging; right to delete/export; no child accounts.
• Reliability: 99.9% uptime target; DB daily backups; disaster recovery runbook.
• Scalability: Search via indexed queries; pagination; background jobs for emails/payouts.