How Pattern Detection Works

MeetingCost analyses your meeting history and groups meetings by type + day of week + time slot. Any group with 2 or more occurrences is considered a recurring pattern. No manual configuration needed — patterns emerge automatically as you log meetings.

For example, if you have a "client call" every Saturday at the same time, MeetingCost detects that as a recurring pattern and tracks its cost, duration, attendee count, and ROI over time.

💡
Patterns need at least 2 meetings to appear. The more meetings logged, the more accurate the analysis. Set the Meeting Type field consistently for best results — meetings without a type are grouped as "unknown".

My Patterns Tab

The My Patterns tab shows analysis of your own meeting history. It contains four panels:

1. Meeting Frequency

A bar chart showing how many meetings you've had per week over the past 8 weeks, plus three summary stats:

  • Avg / Week — mean meetings per week over the analysis window
  • Avg / Month — mean meetings per month
  • Trend — Increasing, Stable, or Decreasing, based on first half vs. second half of the window

2. Cost Per Attendee

A monthly bar chart of average cost per attendee — total meeting cost divided by number of participants. This metric shows whether your meetings are becoming more or less cost-efficient per person over time. Trends are calculated over a 12-week rolling window.

3. Could Be an Email

Meetings flagged as strong candidates for replacement with an async update (email, Slack message, shared doc). A meeting is flagged if it meets two or more of these criteria:

  • Duration ≤ 20 minutes
  • 4 or fewer attendees
  • AI flagged it as "high" or "medium" async replacement likelihood
  • Not classified as a decision meeting

Each flagged meeting shows the potential saving — the full cost of that meeting, since it could theoretically be eliminated entirely. The panel shows the top 5 candidates by cost, and a total recoverable amount at the top.

4. Recurring Meeting ROI

A list of detected recurring patterns with ROI scores, optimization status, and projected yearly cost. Each row shows:

FieldDescription
Meeting name & dayThe meeting type and day of week it typically occurs.
OccurrencesHow many times this meeting has been logged.
Avg duration & attendeesMean duration and participant count across all occurrences.
ROI Score0–100 score calculated from AI feedback (if available). Weighted: Cost Efficiency 40%, Decision Quality 30%, Action Clarity 30%. Shows "No AI score" until AI feedback is generated for a meeting in this pattern.
Verdict badgeHigh Value (green), On Track (grey), Go Async (amber), Low ROI (red) — automatically assigned based on ROI score and async likelihood.
Async potential %Percentage of meetings in this series flagged as async candidates.
Optimization statusDropdown to mark the meeting as On Track, Optimized, or Needs Review.
Avg cost & projected/yrAverage cost per occurrence and estimated full-year cost assuming weekly recurrence.

Optimization Status Tracking

The status dropdown on each ROI row lets you track your optimization work:

StatusMeaning
On TrackDefault. Meeting is running as expected.
OptimizedYou've made changes to improve this meeting (fewer attendees, shorter duration, moved to async, etc.). When you first set this status, the current average cost is saved as the baseline.
Needs ReviewThis meeting needs attention — high cost, low ROI, or flagged for async replacement.

When a meeting is marked Optimized, MeetingCost records the baseline cost at that point in time. On subsequent refreshes, it compares the current average cost to the baseline and shows a before/after improvement indicator — for example: ↓ $4.78 → $3.20 (-33%) since 2026-05-20.

Optimization status and baseline data are saved to your cloud account (Firestore) so they persist across devices and sessions.

Team Patterns Tab

The Team Patterns tab shows the same four behavioural panels but analysed against your team meeting feed — the meetings logged under your account's team data. This gives you a view of meeting patterns from the organisational perspective rather than just your own calendar.

Team Patterns data comes from your team's shared Firestore feed. It updates each time you click Refresh Team Insights.

👥
Note: Team Patterns currently shows your own collected team meeting data. Cross-team visibility for multiple users is planned for a future release.

Refreshing Insights

Click Refresh Insights (My Patterns) or Refresh Team Insights (Team Patterns) to reanalyse your meeting history. The timestamp next to the button shows when the analysis was last run. Insights are not updated automatically — refresh manually after completing meetings to see updated patterns.