MeetingMeter - Meeting Cost Calculator

Model: z-ai/glm-4.7
Status: Completed
Cost: $0.442
Tokens: 335,146
Started: 2026-01-04 22:05

Section 06: MVP Roadmap & Feature Prioritization

MeetingMeter - Strategic Execution Plan

1 MVP Definition & Core Value

The MVP in One Sentence

A Google Calendar integration that automatically calculates and displays the real-time labor cost of meetings based on role-based salary estimates.

Core Problem Lack of visibility into the largest hidden operational expense: unproductive meeting time.
Must-Haves Google Auth, Event Sync, Role-Based Cost Engine, Personal Dashboard
NOT in MVP Outlook/Zoom Sync, Team Budgets, Calendar Nudges, Slack Integration

MVP Success Criteria

  • 100 Active Users (Beta)
  • 30% Weekly Retention
  • 10% Conversion to Paid Waitlist
  • Validation: "Shock Value" (Users share cost screenshot)

2 Feature Inventory

Feature Description User Val Biz Val Effort Category
Google Calendar Auth OAuth2 connection to read events High High Low CORE MVP
Role-Based Cost Input User selects salary band (e.g., "Eng Manager") High High Low CORE MVP
Cost Calculation Engine Logic: (Salary / Hours) * Attendees * Duration High High Med CORE MVP
Personal Dashboard View weekly/monthly meeting spend High Med Med CORE MVP
Weekly Email Report "You spent $4,200 in meetings this week" High High Low QUICK WIN
CSV Export Download raw data for analysis Med High Low QUICK WIN
Outlook/MS365 Sync Expand beyond Google Workspace High High High MAJOR
Calendar Nudges "This meeting costs $X" in event description High High High MAJOR
Team Budgets Set limits on meeting spend per team Med High High MAJOR
Slack Bot Daily meeting cost summary in channel Med Med High NICE-TO-HAVE
Mobile App Native iOS/Android experience Low Low High NICE-TO-HAVE

*Table abbreviated for top 10 features. Full inventory includes 30+ items.

3 Value vs. Effort Matrix

VALUE
EFFORT →
PHASE 1

Quick Wins (MVP)

  • Google Auth
  • Role-Based Input
  • Cost Engine
  • Weekly Email
  • CSV Export
PHASE 2

Major Initiatives

  • Outlook Sync
  • Calendar Nudges
  • Team Budgets
  • Advanced Analytics

Opportunistic

  • Profile Settings
  • Basic Help Docs
  • Invite Teammate
BACKLOG

Don't Build Yet

  • Mobile App
  • Slack Bot
  • Custom Branding
  • API Access

4 Phased Development Roadmap

Phase 1: Core MVP (Weeks 1-8)

Month 1-2

Objective: Prove the "Shock Value" hypothesis. Deliver an immediate "aha moment" when a user sees their personal meeting spend in dollars. Focus solely on Google Calendar users to minimize integration complexity.

Feature Effort Timeline
Google OAuth & Data Sync 3 Days Week 1
Cost Calculation Engine 5 Days Week 2-3
Role-Based Salary Input 2 Days Week 3
Personal Dashboard UI 7 Days Week 4-6
Success Criteria: 100 Beta Users, >60% Weekly Active Rate, No critical data leaks.

Phase 2: Product-Market Fit (Weeks 9-16)

Month 3-4

Objective: Transition from individual utility to team value. Introduce monetization and expand platform support to Outlook to capture the enterprise market. Validate if teams will pay to manage this data.

Feature Effort Timeline
Stripe Payments Integration 4 Days Week 9
Outlook / MS365 Sync 10 Days Week 10-12
Weekly Email Reports 3 Days Week 13
Optimization Insights (Basic) 5 Days Week 14-15
Success Criteria: 100 Paying Teams, $15K MRR, 30-Day Retention >35%.

Phase 3: Growth & Scale (Weeks 17-24)

Month 5-6

Objective: Drive behavioral change. Move from passive reporting to active intervention via nudges. Increase retention by becoming part of the scheduling workflow.

Feature Effort Timeline
Calendar Nudge System 10 Days Week 17-19
Team Budgets & Limits 8 Days Week 20-22
Zoom/Teams Attendee Sync 7 Days Week 23-24
Success Criteria: 250 Teams, $50K MRR, Viral Coefficient >0.3.

5 Prioritization Scoring Model

Priority Score = (User Value × 0.4) + (Business Value × 0.3) + (Ease of Build × 0.3)
Rank Feature User Val (10) Biz Val (10) Ease (10) Score Phase
1 Google Calendar Auth 10 10 9 9.7 MVP
2 Cost Calculation Engine 10 10 7 9.1 MVP
3 Weekly Email Report 8 9 9 8.6 MVP+
4 Role-Based Salary Input 8 8 9 8.3 MVP
5 Personal Dashboard 9 7 6 7.5 MVP
6 Outlook Sync 10 10 2 7.6 Phase 2

6 Technical Strategy

Low-Code Accelerators

  • Auth: Clerk.com (Saves 5 days)
  • DB: Supabase (Postgres + Auth) (Saves 4 days)
  • Hosting: Vercel (Saves 2 days)
  • Payments: Stripe Checkout (Saves 3 days)
  • Email: Resend (Saves 2 days)
Total Time Savings ~16 Days

MVP achievable in 6 weeks vs 10 weeks

Cost Estimates (Per 100 Users)

Hosting (Vercel)$20
Database (Supabase)$25
Auth (Clerk)$25
Email (Resend)$10
Total$80/mo

7 Development Timeline

Week 1 Week 12 Week 24
MVP Build
PMF & Monetization
Scale & Nudges
Week 8: Beta Launch (100 Users)
Week 16: First Paying Customers ($15k MRR)
Week 24: Scale Ready ($50k MRR)

8 Risk Management

Privacy Perception

Users fear salary surveillance.

Mitigation: Default to industry averages/role-bands. Never ask for exact salary. Individual data is private by default.

API Rate Limits

Google Calendar API throttling.

Mitigation: Efficient incremental sync. Queue system for background processing.

"Big Brother" Backlash

Employees resisting tracking.

Mitigation: Position as "Productivity Tool" for the user, not just a "Cost Cutter" for the boss.

9 Launch Strategy

Pre-Launch (Weeks 6-7)

  • Landing page with "Meeting Cost Calculator" widget.
  • Content: "The $400 Meeting You Didn't Need".
  • Waitlist: Target 500 emails.

Beta Launch (Week 8)

  • Staged rollout to waitlist (50 users).
  • Direct feedback interviews.
  • Monitor API costs closely.

Public Launch (Week 10)

  • Product Hunt (Focus on "Productivity").
  • HackerNews / IndieHackers.
  • LinkedIn outreach to Ops Managers.