fathom-cost-tuning

# Fathom Cost Tuning ## Overview Fathom pricing scales with per-seat licensing for team features, with primary cost drivers being transcript storage volume and recording hours consumed. Every meeting generates a transcript and AI summary that persist in storage. For organizations running dozens of meetings daily, unchecked transcript accumulation and redundant API polling for meeting data create unnecessary spend. Optimizing retrieval patterns and storage lifecycle directly reduces both API costs and plan overhead. ## Cost Breakdown | Component | Cost Driver | Optimization | |-----------|------------|--------------| | Seat licenses | Per-user/month for Team plan | Audit active seats quarterly; remove inactive users | | Transcript storage | Accumulated meeting transcripts | Archive transcripts older than 90 days to local storage | | Recording hours | Meeting duration across all users | Disable recording for standup/informal meetings | | API polling | Repeated list/get calls for meeting data | Use webhooks for push notifications instead of polling | | CRM sync events | Per-meeting sync to Salesforce/HubSpot | Batch CRM writes; skip internal-only meetings | ## API Call Reduction ```typescript class FathomTranscriptCache { private cache = new Map<string, { transcript: string; summary: string }>(); async getTranscript(meetingId: string, apiFn: () => Promise<any>): Promise<any> { // Transcripts are immutable after generation — cache permanently if (this.cache.has...