Founder and CGO @ Roots & Fruit
RightTime.AI is a great idea. It has a clear "moat" with the fact that no one wants to deal with Calendar APIs, let alone ALL the calendar APIs at the same time.
I build the concept in an afternoon, then tweaked it the rest of that weekend. I'm amazed how much I got done in a short time. But it still needs a lot of love just to get to what I'm considering to be MVP.
I'd love anyone's feedback on this, but this is my MVP list for RightTIme.AI
In One Sentence
Host creates an invite → guests connect their calendars → RightTime computes the best 3 times → host picks one → event is scheduled.
RightTime.ai – MVP Feature Set (v0.0.4)
A deterministic, trust-based scheduling tool that removes polling and manual availability grids. No AI required for matching.
Core Identity & Access
- Google OAuth as host login
- Server-side session (HttpOnly cookie)
- Protected
/app/*routes - Guest access via secure invite token link
- Guest calendar connection via Google OAuth
- Guest timezone required before being marked “ready”
Invite Creation (Host)
- Create one-off meeting invite
- Define:
- Event name
- Description
- Duration (e.g., 30 or 60 minutes)
- Date range (start and end window)
- Host availability:
- Default 08:00–20:00 (local time)
- Host can override their availability window
- Core hours preference:
- Default 10:00–16:00 (soft scoring preference)
Guest Flow
- Receive invite email
- Open invite page via secure token link
- Connect Google Calendar
- Confirm or select timezone (required)
- Guest is marked “ready” only when:
- Calendar is connected
- Timezone is confirmed
Deterministic Matching Engine (No AI)
- Fetch free/busy data from Google (across all connected calendars)
- No calendar event details stored
- Normalize all time to UTC for computation
- Build availability windows per participant:
- Default 08:00–20:00 local time (host override applies to host)
- Subtract merged busy intervals
- Generate candidate slots:
- 15-minute increments
- Must fully fit the meeting duration
- Score slots procedurally:
- Prefer core hours (10:00–16:00 local)
- Penalize early/late edges
- Slight bias toward sooner dates
- Return top 3 ranked options
Host Decision Flow
- Host sees:
- Top 3 recommended times (in host timezone)
- Meeting duration
- Short procedural explanation for each option
- Optional preview of guest local times
- Host selects one time
- System:
- Creates Google Calendar event
- Sends confirmation emails via Resend
- Marks invite as finalized
Reliability & Safety
- No calendar event data stored
- OAuth tokens stored server-side only
- No secrets logged or exposed
- Finalize action is idempotent
- Clear error handling for:
- Guests not yet ready
- No common availability
- Revoked or expired tokens
Explicitly Not in MVP
- AI preference parsing
- Calendar holds
- Recurring meetings
- Poll-style availability grids
- Teams or multi-host accounts
- Microsoft calendar support
- Analytics or tracking
- Advanced scheduling heuristics
This MVP delivers a fully functional, deterministic group scheduling experience focused on trust, simplicity, and correctness.