User Personas

# CalmFalcon User Personas

**Deep dive into who uses CalmFalcon and why**

---

## Overview

CalmFalcon serves 1 primary and 1 secondary user persona across our customer base. Understanding these personas is critical for product decisions - every feature should serve at least one persona's core needs.

---

## Primary Persona: AI Infrastructure / AI Platform PM##

### Goals & Motivations

**Owns inference stack, orchestration, reliability, governance** 
**Makes roadmap and vendor decisions**
**Accountable for cost and platform stability**

### Success metrics
- Time saved 4+ hrs/week
- Enginnering Costs saved in Million by avoiding re-work


### Pain Points & Frustrations

**1. Fast changing AI Ecosystem is crushing the teams**
- Research takes hours to figure out what changed
- Team working nights and weekends
- CFO says "no" to hiring more PMs and engineers
- Burnout risk is high

**2. Inconsistent technology review**
- Quality depends on who reviews
- Missed issues come back as problems later


### Jobs to be Done

* As a platform PM, I want signals updated daily so I can rely on freshness.  
* As an admin, I want ingestion failures logged and retryable.  
* As a user, I want signals categorized so I can filter by domain.  
* As a PM, I want the taxonomy adjustable without code changes.  
* As a PM, I want to see which themes require action this week (ACT) vs which to track over 30 days (WATCH).
* As a user, I want confidence indicators to judge reliability.  
* As an executive, I want 5 themes instead of 50 raw signals.  
* As a technical user, I want to inspect supporting evidence.  
* As a PM, I want to know what changed this week.  
* As a strategy lead, I want to track acceleration patterns.  
* As a director, I want executive-ready summaries.  
* As a user, I want evidence behind each claim.  
* As a PM, I want to filter for ACT-tier themes with Platform Impact only.  
* As a user, I want to save clusters to a watchlist.  
* As an executive, I want a weekly digest of meaningful AI infra shifts.  
* As a PM, I want a brief format for sharing internally.  
* As a user, I want to tune what I see over time.  
* As a product owner, I want ranking to improve without retraining models.

### CalmFalcon Features They Care About

**Must-haves:**
- Dashboard with Signals/Theme Clustering - Instant AI Signal visibility
- Confidence Scoring for each signal/theme
- Signal Tier classification: ACT (act this week) or WATCH (track over 30 days) 

**Nice-to-haves:**
- Week Over Week Deltas
- Email Weekly Briefs
- Bookmark or track particular theme
- Add custom sources
- Social features

**Don't care about:**
- 

### Quotes

*Clear Signals. Faster Decisions.*

---

## Secondary Persona: AI Platform Engineering Lead / Architect##

### Goals & Motivations
**Evaluates OSS frameworks and architecture patterns**
**Needs evidence-backed intelligence**
**Wants to avoid adopting hype**

### Success metrics
- Themes reviewed per week
- Turnaround time
- Issues caught (before they become problems)
- Time saved per week

### Pain Points & Frustrations

**1. Tedious, repetitive work**
- Still need to read every word (might miss something)
- Extracting key information is manual
- A lot of noise - don't know what resource to follow

**2. Inconsistent risk assessment**
- What's "acceptable risk" varies by my mood, workload
- GC wants consistency, but hard to achieve manually
- Junior attorneys escalate too much (or not enough)
- No objective criteria for risk

**3. Context switching**
- Reviewing 5-10 different news/articles/repo types per day
- Each type has different issues to look for
- Mental checklist is exhausting
- Easy to miss things when fatigued

### Jobs to be Done
* As a platform PM, I want signals updated daily so I can rely on freshness.  
* As an admin, I want ingestion failures logged and retryable.  
* As a user, I want signals categorized so I can filter by domain.  
* As a PM, I want the taxonomy adjustable without code changes.  
* As a PM, I want to see which themes require action this week (ACT) vs which to track over 30 days (WATCH).
* As a user, I want confidence indicators to judge reliability.  
* As an executive, I want 5 themes instead of 50 raw signals.  
* As a technical user, I want to inspect supporting evidence.  
* As a PM, I want to know what changed this week.  
* As a strategy lead, I want to track acceleration patterns.  
* As a director, I want executive-ready summaries.  
* As a user, I want evidence behind each claim.  
* As a PM, I want to filter for ACT-tier themes with Platform Impact only.  
* As a user, I want to save clusters to a watchlist.  
* As an executive, I want a weekly digest of meaningful AI infra shifts.  
* As a PM, I want a brief format for sharing internally.  
* As a user, I want to tune what I see over time.  
* As a product owner, I want ranking to improve without retraining models.

### Quotes

*Clear Signals. Faster Decisions.*

---

**Use these personas throughout the course when writing PRDs, conducting user research, and making product decisions. Every decision should consider: "How does this serve our personas?"**