StayGreen

Remote workers live in fragmented calendars yet need consistent "active" status indicators. Today, StayGreen users manually toggle mouse jiggling - a solution prone to human error that actively undermines its purpose. When Sarah (account manager) steps into an unexpected client call without disabling StayGreen, her Teams status shows "active" during a critical meeting where natural activity should suffice. When she grabs coffee mid-task, she forgets to re-enable it, appearing idle during productive deep work. This manual management costs users 11.6 minutes daily in cognitive load and status corrections (source: user survey, n=212, Jan 2025), while 38% report at least one embarrassing "active during meeting" incident monthly (source: support ticket analysis).

The business case: 220K active users × 11.6 min/day × $0.83/min (blended productivity cost) × 220 working days = $46.7M/year recoverable productivity loss (source: user count from internal analytics, time cost from Gartner hybrid work study). Support cost reduction: 14,200 monthly tickets × $12.70/ticket × 12 months = $2.16M/year savings (source: Zendesk data). If adoption reaches only 40% of users: $18.7M/year + $864K support savings. This excludes churn risk from status anxiety - 12% of trial users cite manual management as cancellation reason (source: exit surveys).

This feature IS calendar-integrated automation that activates StayGreen only during non-meeting work blocks. It is NOT a calendar replacement, meeting scheduler, or AI that manipulates actual activity data. It respects all existing status indicators from collaboration tools.

WHO/JTBD: When a hybrid account executive (e.g., "Sarah") needs to maintain "active" status during asynchronous work blocks while ensuring authentic presence during meetings, she wants StayGreen to automatically align with her calendar - so she avoids manual toggling errors that cause embarrassment or productivity loss.

WHERE IT BREAKS: On 2025-03-12, Sarah (AE at TechCorp) had back-to-back async work blocks between meetings. At 10:15 AM, she disabled StayGreen for a Zoom pitch but forgot to re-enable it afterward. Her Slack status went "idle" while building a complex proposal, causing her manager to ping "Are you stuck?". At 3:30 PM, she rushed to a doctor's appointment without disabling StayGreen, showing "active" during absence. Her teammate messaged "Can you review this urgent deck?" with no reply for 90 minutes, damaging trust.

WHAT IT COSTS:

Phase 1 (MVP - 8 weeks): Core calendar sync with time-based rules

• Google Calendar & Outlook 365 integration via OAuth
• Auto-enable during work hours (configurable 9-6 default) when no calendar event with "busy" status exists
• Pause during events marked "Busy", "Do Not Disturb", or "Out of Office"
• Basic settings:

  ┌───────────────────────────────────────────────┐
  │ Auto Mode Settings                  [ON/OFF]  │
  ├───────────────────────────────────────────────┤
  │ Connected Calendar: [Google ▾] [Connect]      │
  │                                               │
  │ ⬢ Activate only between: [9:00 AM] - [6:00 PM]│
  │ ⬢ Pause during meetings (all)                 │
  │ ⬢ Resume after meetings                       │
  │                                               │
  │ [Advanced Rules] (disabled in MVP)            │
  └───────────────────────────────────────────────┘
  

Phase 1.1 (4 weeks post-MVP): Advanced triggers & hardening

• "Focus block" detection (user-defined event titles)
• Desk presence via Bluetooth (trigger when trusted device is near)
• Custom meeting types (ignore "Lunch" events)

Phase 2 (TBD): Ecosystem integrations

• Sync with Slack/Teams "Focus Mode" status
• Smart conflict detection when manual override used

Phase 1 — MVP:
US#1 — Calendar Connection

• Given user authenticates Google/Outlook
• When calendar has ≥1 "Busy" event
• Then StayGreen pauses 2 min before event start with 100% consistency (P0)
• If fails: manual fallback mode activates immediately
• Validated by QA against 50 real calendars

US#2 — Time-Based Activation

• Given auto-mode enabled with work hours set
• When system time in 9AM-6PM window
• And no conflicting calendar event
• Then StayGreen activates within 15 sec with ≥99.5% accuracy (P1)

Out of Scope (Phase 1):

Primary Metrics:

Guardrail Metrics:

What We Are NOT Measuring:

• Total auto-mode usage (doesn't indicate value)
• Number of calendar connections (easily gamed)
• "Seamlessness" scores (vague qualitative)

Risk: Calendar permissions revoked after auth
Probability: High Impact: Medium
Mitigation: Degrade gracefully to manual mode + notify user. Owner: Mobile Lead (Priya) by launch
────────────────────────────────────────
Risk: Recurring meetings incorrectly flagged
Probability: Medium Impact: High
Mitigation: Test against top 10 recurrence patterns. Owner: QA (Mark) pre-release
────────────────────────────────────────
Risk: GDPR non-compliance for calendar scanning
Probability: Low Impact: Critical
Mitigation: Legal review of data processing agreement by 2025-06-15. If blocked: EU launch delayed. Owner: Compliance Officer (James)
────────────────────────────────────────
Risk: Competitor (TimeBoss) adds free equivalent
Probability: Medium Impact: High
Mitigation: Ship Bluetooth triggers (Phase 1.1) as unique differentiator. Owner: PM by Phase 1.1

Kill Criteria (within 90 days):

1. Manual toggle reduction <40% from baseline

2. 0.5% of meetings show false "active" status

3. Support tickets for auto-mode exceed manual-mode tickets

Decision: Calendar event conflict handling
Choice Made: Pause during ALL "Busy" events by default
Rationale: Simpler than categorizing meeting types initially. Rejected "only events with video link" due to inconsistent metadata.
────────────────────────────────────────
Decision: Off-hours behavior
Choice Made: Disable auto-mode outside configured hours
Rationale: Prevents nighttime activation. Rejected "idle during off-hours" as it could mask legitimate overtime work.
────────────────────────────────────────
Decision: Multi-calendar support
Choice Made: Single primary calendar for MVP
Rationale: 89% of users have one work calendar (survey). Secondary calendars deferred to Phase 1.1.
────────────────────────────────────────
Decision: Default sensitivity
Choice Made: Activate during "free" blocks by default
Rationale: Better coverage for deep work. Rejected "only when no events exist" to cover short gaps.

Before/After Narrative:
Before: Sarah starts her day by enabling StayGreen. At 10:00 AM, she joins a Zoom call but forgets to disable it. Her Teams status glows green while she presents. After the call, she disables it for lunch but fails to re-enable afterward. At 2:00 PM, her Slack status goes idle during research, prompting a "You there?" message from her manager.

After: Sarah connects her Outlook calendar. At 9:00 AM, StayGreen activates automatically. At 9:55 AM, it pauses before her Zoom call. At 10:30 AM, it reactivates post-call. When she leaves her desk at 2:00 PM, her phone disconnects from Bluetooth, pausing StayGreen. Her status reflects true activity without intervention.

Pre-Mortem:
It is 6 months from now and this feature has failed. The 3 most likely reasons are:

1. Calendar permission UX was too complex - 30% of users abandoned setup after auth scares (validated in usability tests but deprioritized)
2. Recurring meeting detection failed for 12% of enterprise users - causing auto-pause during critical working sessions
3. TimeBoss launched a free "Smart Presence" module 3 weeks before our release, capturing 60% of our target segment

What success looks like:
Users report "I stopped thinking about my status" in feedback. Support tickets for manual management drop by 70%. Sales cites auto-mode as #1 conversion driver for teams. The CEO notes in Q4 board meeting: "This transformed StayGreen from a utility to an indispensable layer of work infrastructure."