CalWizz Browser Extension — Proposal

TL;DR: A Chrome extension that puts your schedule health score in the toolbar, overlays meeting insights directly onto Google Calendar, and gives you one-click access to your CalWizz analytics without ever leaving your browser. Think of it as CalWizz’s always-on dashboard that lives where you actually work — your calendar.

Last updated: January 2026

1. Concept & Value Prop

The Problem

CalWizz already gives teams deep calendar analytics and the unique Schedule Health Score. But right now, you have to actively go to app.calwizz.com to see any of it. That’s a friction problem:

People don’t check analytics proactively — they check when something already went wrong
Your schedule health score could warn you before you overbook your Wednesday, not after
Google Calendar is where the action is — that’s where meetings get created, accepted, and declined
Flowtrace already has calendar add-ins showing meeting costs inline. We need to be in the same arena

The Solution

CalWizz for Chrome — a lightweight extension that:

Badge icon in the toolbar showing your real-time schedule health score (color-coded: green/yellow/red)
Popup dashboard with today’s stats at a glance — one click, no tab switch
Google Calendar overlay that enriches your calendar page with CalWizz insights (meeting costs, focus blocks, warnings)
Smart notifications — “Your Wednesday is at 31 health score. Consider declining something.”

Why Someone Would Install This

The pitch is simple: “See your schedule health score without leaving Google Calendar.”

For existing CalWizz users, it’s a no-brainer upgrade — the insights they already value, delivered faster. For new users, it’s a low-friction entry point to CalWizz — install the extension, connect your calendar, see your score in 60 seconds. Way easier than signing up on a website first.

The extension also doubles as a marketing channel — it’s listed in the Chrome Web Store, visible to anyone searching for “calendar analytics” or “meeting productivity.”

2. Core Features (MVP / v1)

Keep this tight. Ship fast, learn from usage, iterate.

CalWizz icon in Chrome toolbar
Badge shows today’s health score as a number (0-100)
Background color changes: 🟢 green (70+), 🟡 yellow (40-69), 🔴 red (below 40)
Updates every 15-30 minutes (configurable)
One glance tells you how your day looks

A compact popup (400px × 500px) with:

Today’s Schedule Health Score — big number, front and center, with trend arrow (↑↓→)
Meeting Load — “4 meetings today (3.5 hrs)” with a simple progress bar
Focus Time — “2.5 hrs of uninterrupted time remaining”
Next Meeting — name, time, attendee count, in X minutes
Week Overview — tiny bar chart showing health score per day this week
Quick Link — “Open full dashboard →” to app.calwizz.com

2.3 Google Calendar Page Enhancement (Content Script)

When viewing calendar.google.com, inject CalWizz insights:

Daily health score badge — small colored dot on each day in month/week view
Meeting cost indicator — subtle ”$” icon or dollar amount on meetings (based on estimated attendee cost)
Focus time blocks — light green highlight on detected focus time periods
Overload warning — if a day exceeds healthy meeting thresholds, show a gentle ⚠️

2.4 Authentication

“Sign in with CalWizz” button in popup
Opens app.calwizz.com/auth in a new tab, handles OAuth flow
Extension stores session token securely
If user doesn’t have a CalWizz account, redirect to signup → upsell into the full product

2.5 Basic Notifications

Morning briefing (optional, 8-9 AM): “Today’s schedule health: 62. You have 5 meetings.”
Overload alert: Triggered when today’s score drops below a threshold
Configurable — users can turn off notifications entirely

3. Nice-to-Have Features (v2+)

v2: Deeper Calendar Integration

Inline meeting insights on hover — hover over any meeting in Google Calendar and see CalWizz data (recurring cost, attendance patterns, “this meeting has no agenda” flag)
Quick decline suggestions — “Based on your calendar health, consider declining: [meeting name]” with one-click decline
Meeting cost calculator overlay — real-time cost estimate as you create a new meeting (add attendees → see cost tick up)
Weekly digest notification — summary of the past week’s calendar health + trends

v3: Team Features

Team health dashboard in popup — see your team’s aggregate score (for managers)
Sidebar panel (instead of just popup) — full sidebar within Google Calendar with richer analytics
“Should this meeting exist?” AI nudge — ML-based suggestion for recurring meetings that show low value patterns
Outlook Web support — extend content scripts to outlook.office.com
Slack integration hook — share your daily score to a Slack channel from the extension

v4: Power User Features

Calendar heatmap — month view colored by health score
Focus time auto-block — create focus time blocks directly from the extension
Meeting prep cards — before a meeting starts, show a card with context (last meeting notes, attendee info, agenda)
Export/share — share your schedule health report as a link

4. Technical Architecture

4.1 Extension Structure (Manifest V3)

calwizz-extension/
├── manifest.json              # Extension config, permissions, service worker
├── background/
│   └── service-worker.js      # Badge updates, alarms, API polling, notifications
├── popup/
│   ├── popup.html             # Popup UI shell
│   ├── popup.js               # Popup logic, API calls, rendering
│   └── popup.css              # Styling (CalWizz brand colors)
├── content/
│   ├── calendar-overlay.js    # Injected into calendar.google.com
│   └── calendar-overlay.css   # Overlay styles
├── options/
│   ├── options.html           # Settings page
│   ├── options.js             # Notification prefs, refresh interval, etc.
│   └── options.css
├── lib/
│   ├── api.js                 # CalWizz API client wrapper
│   └── auth.js                # Token management, refresh logic
├── assets/
│   ├── icon-16.png
│   ├── icon-32.png
│   ├── icon-48.png
│   └── icon-128.png
└── _locales/                  # i18n if needed later

4.2 Manifest V3 Config

{
  "manifest_version": 3,
  "name": "CalWizz — Schedule Health Score",
  "version": "1.0.0",
  "description": "See your calendar's health score at a glance. Meeting insights, focus time tracking, and smart alerts.",
  "permissions": [
    "storage",
    "alarms",
    "notifications",
    "activeTab"
  ],
  "host_permissions": [
    "https://app.calwizz.com/*",
    "https://calendar.google.com/*"
  ],
  "background": {
    "service_worker": "background/service-worker.js"
  },
  "action": {
    "default_popup": "popup/popup.html",
    "default_icon": {
      "16": "assets/icon-16.png",
      "32": "assets/icon-32.png",
      "48": "assets/icon-48.png",
      "128": "assets/icon-128.png"
    }
  },
  "content_scripts": [
    {
      "matches": ["https://calendar.google.com/*"],
      "js": ["content/calendar-overlay.js"],
      "css": ["content/calendar-overlay.css"],
      "run_at": "document_idle"
    }
  ],
  "options_page": "options/options.html",
  "icons": {
    "16": "assets/icon-16.png",
    "48": "assets/icon-48.png",
    "128": "assets/icon-128.png"
  }
}

4.3 Permissions Breakdown

Permission	Why	User Trust Impact
`storage`	Store auth token, cached data, user preferences	Low risk — standard
`alarms`	Periodic polling for badge updates (every 15-30 min)	Low risk — standard
`notifications`	Morning briefing, overload alerts	Medium — users can disable
`activeTab`	Read current tab for context (which calendar view)	Low risk — only when clicked
`host_permissions: app.calwizz.com`	API calls to CalWizz backend	Expected — it’s our own API
`host_permissions: calendar.google.com`	Content script injection for overlays	Medium — clearly explained in store listing

What we DON’T need (and should explicitly not request):

tabs (broad) — we don’t need to see all tabs
history — none of our business
cookies — use chrome.storage instead
<all_urls> — absolutely not

Minimal permissions = better Chrome Web Store approval + higher user trust.

4.4 API Communication

The extension talks to the existing CalWizz Flask backend via a dedicated extension API namespace:

GET  /api/ext/v1/health-score          → Today's score + trend
GET  /api/ext/v1/today                 → Today's meeting summary
GET  /api/ext/v1/week                  → Weekly overview (scores per day)
GET  /api/ext/v1/meeting/:id/insights  → Per-meeting data (cost, patterns)
POST /api/ext/v1/auth/token            → Exchange auth code for token
POST /api/ext/v1/auth/refresh          → Refresh expired token

Key design decisions:

Lightweight payloads — extension endpoints return minimal JSON, not the full dashboard data
Aggressive caching — cache health score locally with 15-min TTL; no reason to hammer the API
Auth token in chrome.storage.local — encrypted, not accessible to content scripts directly
Rate limiting — server-side, max 100 requests/hour per user (more than enough for polling)
CORS — backend needs to whitelist the extension’s origin (chrome-extension://<id>)

4.5 Data Flow

                    ┌─────────────────────┐
                    │  CalWizz Backend     │
                    │  (app.calwizz.com)   │
                    │  Flask + PostgreSQL  │
                    └──────────┬──────────┘
                               │
                    REST API (HTTPS)
                               │
              ┌────────────────┼────────────────┐
              │                │                │
     ┌────────▼──────┐  ┌─────▼─────┐  ┌──────▼───────┐
     │ Service Worker │  │  Popup    │  │Content Script │
     │ (background)   │  │  (UI)    │  │(Google Cal)   │
     │                │  │          │  │               │
     │ • Poll API     │  │ • Fetch  │  │ • Receives    │
     │   every 15min  │  │   on     │  │   data via    │
     │ • Update badge │  │   open   │  │   messaging   │
     │ • Send notifs  │  │ • Render │  │ • Inject UI   │
     └───────────────┘  └──────────┘  └───────────────┘

Content scripts can’t make cross-origin requests directly (Manifest V3 restriction), so they message the service worker which handles API calls and passes data back.

5. UI/UX Mockup Descriptions

Color System

Using CalWizz’s existing palette:

Primary Green #2d5a3d — headers, primary buttons, score when healthy
Dark Forest #1a3d2a — backgrounds, deep accents
Sage #8B9D83 — secondary text, borders, subtle elements
Warning Yellow #D4A03C — medium health score
Alert Red #C44536 — low health score, overload warnings
Background #F8F9F7 — off-white with slight green tint
Text #1a1a1a — near-black for readability

┌─────────────────────────────┐
│  [CalWizz Logo]             │
│                             │
│  📊 Your calendar's health  │
│     score, always visible.  │
│                             │
│  ┌───────────────────────┐  │
│  │  Sign in with CalWizz │  │  ← Primary green button
│  └───────────────────────┘  │
│                             │
│  Don't have an account?     │
│  Start free →               │  ← Links to calwizz.com
│                             │
└─────────────────────────────┘

┌─────────────────────────────┐
│  Today          Mon, Jan 27 │
│ ┌──────────────────────────┐│
│ │                          ││
│ │    ╭─────╮               ││
│ │    │ 64  │  ↓ from 71    ││  ← Big score, trend arrow
│ │    ╰─────╯               ││
│ │  Schedule Health Score   ││
│ │                          ││
│ └──────────────────────────┘│
│                             │
│  📅 4 meetings  •  3.5 hrs │
│  ████████████░░░░░  67%    │  ← Meeting load bar
│                             │
│  🎯 Focus time: 2.5 hrs   │
│  ░░░████████░░░░░░░░░░░░  │  ← Focus blocks visualization
│                             │
│  ⏭️ Next: Sprint Planning  │
│     in 45 min  •  8 people │
│                             │
│  ─── This Week ─────────── │
│  M  T  W  T  F             │
│  🟢 🟡 🔴 🟡 🟢            │  ← Dot per day, color = score
│  78 64 31 52 73            │
│                             │
│  Open full dashboard →     │
└─────────────────────────────┘

5.3 Google Calendar Overlay — Week View

On the actual Google Calendar week view page:

Top-right corner: Small CalWizz widget showing today’s score in a circle
Day column headers: Tiny colored dot (green/yellow/red) next to each day name
Meeting blocks: Subtle overlay in bottom-right corner of each event:
- $42 (estimated meeting cost) — small, gray text
- ⚠️ icon if meeting has no agenda or has 8+ attendees
Focus blocks: Light green dashed border around detected focus periods
Daily summary bar: Thin bar at the top of each day column showing meeting-to-focus ratio

Visual style: Non-intrusive. Everything CalWizz adds should feel like a natural extension of Google Calendar, not a popup-ad-style overlay. Use transparency, small fonts, and positioning that doesn’t interfere with calendar interaction.

5.4 Notification — Morning Briefing

┌──────────────────────────────────┐
│ CalWizz                          │
│                                  │
│ Good morning! Today's health: 58 │
│ 5 meetings (4.2 hrs) • 2 back-  │
│ to-back blocks. Consider         │
│ declining the 2pm sync?          │
│                                  │
│ [View Details]  [Dismiss]        │
└──────────────────────────────────┘

5.5 Options Page

Simple settings page:

Refresh interval: 15 min / 30 min / 1 hour
Notifications: Toggle morning briefing, overload alerts, weekly digest
Morning briefing time: Time picker (default 8:30 AM)
Overload threshold: Score below which to alert (default: 40)
Google Calendar overlay: Toggle on/off, toggle individual elements (costs, focus blocks, warnings)
Account: Email shown, “Sign out” button, “Open CalWizz settings →“

6. Integration with Existing CalWizz

What Needs to Change on the Backend

The existing Flask app at app.calwizz.com needs:

New API endpoints (/api/ext/v1/...) — lightweight, extension-optimized responses
CORS configuration — allow requests from the extension’s Chrome origin
Token-based auth for extension — separate from the browser session auth; generate a long-lived API token that the extension stores
Extension-specific rate limiting — prevent abuse without being annoying (100 req/hr is generous for polling every 15 min)

What Doesn’t Change

The core analytics engine stays the same — extension just reads computed data
No new data processing pipeline needed — extension consumes the same scores/insights the web app shows
Google Calendar OAuth flow is unchanged — user has already connected their calendar via the web app
Database schema unchanged — no extension-specific tables needed for v1

Auth Flow

1. User clicks "Sign in with CalWizz" in popup
2. Extension opens app.calwizz.com/auth/extension in new tab
3. User logs in (or is already logged in)
4. Server generates extension API token
5. Redirects to app.calwizz.com/auth/extension/callback?token=xxx
6. Content script on that page sends token to extension via chrome.runtime.sendMessage
7. Extension stores token in chrome.storage.local
8. Popup reloads with authenticated state

This keeps the extension thin — it doesn’t handle OAuth with Google directly, just authenticates with CalWizz’s own backend.

New User Flow (Acquisition Channel)

For users who install the extension before having a CalWizz account:

1. Install extension from Chrome Web Store
2. Click extension icon → sees "Sign in" screen
3. Clicks "Start free" → opens calwizz.com signup
4. Signs up, connects Google Calendar
5. Returns to extension → signs in
6. Immediately sees their health score

The extension becomes a top-of-funnel acquisition channel — people discover it in the Chrome Web Store, install it, and that drives signups to the main product.

7. Distribution & Marketing

Chrome Web Store Listing

Name: CalWizz — Schedule Health Score for Google Calendar Category: Productivity Short description: See your calendar’s health score at a glance. Meeting cost tracking, focus time insights, and overload alerts — right in your browser.

Detailed description highlights:

“Your schedule health score, always one click away”
“Meeting cost calculator built into Google Calendar”
“Get warned before your day becomes a meeting marathon”
“Focus time tracking without opening another tab”

Screenshots: 5 required, show:

Popup dashboard with health score
Google Calendar with overlay (meeting costs, focus blocks)
Toolbar badge (close-up, showing green/yellow/red states)
Morning briefing notification
Week overview with per-day scores

Keywords to target in store SEO:

calendar analytics, meeting analytics, schedule health, meeting cost, focus time, Google Calendar extension, meeting productivity, calendar management

Marketing Angle

Launch tweet thread:

We just shipped CalWizz for Chrome 🚀

Your schedule health score now lives in your toolbar.
No more switching tabs to check if your calendar is healthy.

Here's what it does (thread):
1/ ...

Blog post: “Introducing CalWizz for Chrome — Your Calendar’s Health Score, Always Visible”

Product Hunt: Perfect for a standalone Product Hunt launch (separate from the main app launch). “Chrome Extension” launches perform well on PH.

Cross-promotion:

Prompt existing CalWizz users to install the extension (in-app banner)
Include extension link in the CalWizz welcome email
Mention it in the biweekly newsletter

Reddit:

Share in r/chrome_extensions, r/productivity, r/SaaS
Genuine post: “I built a Chrome extension that shows your calendar’s health score”

Chrome Web Store Considerations

Review time: 1-3 business days for new extensions
Developer fee: One-time $5 registration
Privacy policy required — need a page on calwizz.com/privacy explaining what data the extension accesses
Data disclosure: Chrome Web Store now requires a data practices disclosure. CalWizz extension accesses: calendar data (via backend API), authentication tokens. It does NOT access: browsing history, personal communications, financial data.

8. Effort Estimate

MVP Scope & Timeline

Component	Effort	Notes
Backend: Extension API endpoints	2-3 days	New routes, token auth, CORS setup
Extension: Manifest + project scaffolding	0.5 day	Boilerplate, build tooling
Extension: Auth flow	1-2 days	Token exchange, storage, refresh logic
Extension: Service worker (badge + polling)	1-2 days	Alarms API, badge rendering
Extension: Popup UI	2-3 days	Dashboard layout, data fetching, styling
Extension: Google Calendar content script	3-5 days	DOM manipulation, overlay injection, style matching
Extension: Options page	0.5-1 day	Settings UI, storage sync
Extension: Notifications	1 day	Chrome notifications API
Assets: Icons, screenshots	0.5-1 day	Multiple sizes, store screenshots
Chrome Web Store: Listing + review	0.5 day + wait	Description, privacy policy, submission
Testing & polish	2-3 days	Cross-browser, edge cases, UX polish
Total MVP	~2-3 weeks	One developer, focused sprint

Assumptions

One person building this (Adam or a contractor)
CalWizz backend already computes health scores and meeting analytics (just needs new API surface)
No complex build tooling — vanilla JS for v1 is fine (Vite/React for v2 if popup gets complex)
Testing on Chrome only for v1 (Edge + Brave compatibility is free with Chromium, but not formally tested)

Ongoing Maintenance

~2-4 hours/month — Google Calendar DOM changes occasionally and content scripts may break. This is the main maintenance burden. Monitor and fix.
Chrome Manifest V3 is stable now, so no major migration risk.

9. Competitive Advantage

What Other Calendar Extensions Do

Most calendar-related Chrome extensions fall into two buckets:

Scheduling tools (Calendly, Cal.com) — add scheduling links and booking flows. Zero analytics.
Meeting enhancers (Fellow, Fireflies) — focus on meeting content (notes, transcription). Calendar-level insights are an afterthought.

Flowtrace has Google Calendar and Outlook add-ins that show meeting costs, but they’re calendar add-ins (Google Workspace Marketplace), not browser extensions. Different distribution channel, different install experience.

What Makes CalWizz for Chrome Different

Advantage	Why It Matters
Schedule Health Score in toolbar	No one else puts a calendar health metric in the browser toolbar. It’s a constant, passive awareness tool.
Google Calendar enrichment	Meeting costs, focus blocks, and health indicators overlaid directly on Google Calendar. Not a separate dashboard, not a sidebar — integrated into the page you’re already looking at.
Score-first, not schedule-first	Clockwise/Reclaim extensions manage your schedule. CalWizz evaluates it. Complementary, not competing.
Low-friction CalWizz onboarding	Extension → signup → connected in 2 minutes. Easier acquisition funnel than asking someone to visit a website cold.
Individual AND team context	Personal score + team comparison (v2). Manager installs it and immediately sees both their calendar health and their team’s.

The Moat

The extension itself isn’t hard to build. The moat is CalWizz’s analytics engine and the Schedule Health Score algorithm. The extension is just a delivery mechanism for a unique insight that no other tool generates. Someone could clone the extension UI in a week, but they’d need to build the entire calendar analytics backend to make it useful.

Positioning Statement

CalWizz for Chrome is the only browser extension that gives you a real-time schedule health score. It turns your toolbar into a calendar health monitor and your Google Calendar into an insight-rich dashboard — without leaving the page.

10. Open Questions & Risks

A few things to think about before committing:

Technical Risks

Google Calendar DOM stability — Google changes their Calendar UI periodically. Content scripts that inject into the DOM can break. Mitigation: keep overlay injection simple, use MutationObserver for resilience, and build a monitoring alert for when the overlay stops working.
Manifest V3 service worker lifecycle — service workers in MV3 are ephemeral (they get killed after 30 seconds of inactivity). Badge updates need to use the Alarms API, not setInterval. This is a known pattern — not hard, just different from MV2.

Business Questions

Free or paid? Extension should be free (it’s a delivery mechanism for CalWizz, not a standalone product). Gate it behind CalWizz authentication — free CalWizz tier gets basic extension features, paid tier gets everything.
When to build this? It’s a nice marketing channel and UX improvement, but it’s not critical path. Best timing: after the core CalWizz product is stable and you’re looking for growth levers.
Firefox? Manifest V3 is supported in Firefox now, but the Google Calendar content script is Chrome-specific value. Table Firefox unless there’s demand.
Google Workspace Marketplace add-in (like Flowtrace) vs. Chrome extension? The Chrome extension is easier to build and distribute. A Workspace add-in has deeper integration (sidebar within Google Calendar’s native UI) but requires Google Workspace Marketplace approval, which is slower and more complex. Recommendation: Chrome extension first, Workspace add-in later.

Metrics to Track

Installs — Chrome Web Store downloads
Daily active users — how many people have the extension active
Popup opens per day — are people actually clicking it?
Signup attribution — how many new CalWizz accounts come through the extension flow?
Calendar overlay engagement — are people keeping the overlay on or turning it off?

Summary — Is This Worth Building?

Yes, but with the right timing.

The extension is:

✅ A natural extension (pun intended) of CalWizz’s value prop
✅ A new acquisition channel (Chrome Web Store discovery)
✅ A way to make CalWizz “always on” instead of “sometimes visited”
✅ A competitive response to Flowtrace’s calendar add-ins
✅ Relatively cheap to build (~2-3 weeks for MVP)

It’s NOT:

❌ A replacement for the full CalWizz web app
❌ A standalone product (it depends on the backend)
❌ Urgent — it’s a growth lever, not a survival feature

Recommended timing: Build it after CalWizz has at least 100-200 active users and the core product analytics are solid. The extension amplifies value that needs to exist first.

Estimated cost: 2-3 weeks of dev time for MVP. If hiring a contractor, budget ~$3-5K for a solid Chrome extension developer.

Proposal by Reggie. Ready for Adam’s review and red pen.

🦝 Reggie's Vault

Explorer

calwizz-extension-proposal