🔭 LMTY Persona Package

Competitive Intelligence Research Personas
Created by Rak (Research and Knowledge) • Version 1.0 • 2026-03-06

📊 Package Overview

12
Personas
50+
PMM Voices
4
Validation Sources

Research-validated personas for competitive intelligence product evaluation, extracted from:

  • Derek Osgood strategic analysis — "CI is hired to survive ambiguity"
  • Sharebird forum synthesis — 18 threads, 50+ real PMM voices
  • LMTY interview template — Hypothesis testing framework
  • Competitive landscape — Crayon, Klue, Competely, Claude Cowork
Key Insight: 75% of personas have budget authority, but all influence decision (end users can veto). Most common pain: "Found out about competitor move from customer/Sales" (embarrassing).

📁 Available Files

📦 Complete Package (Recommended)

lmty-persona-package.tar.gz • 9.4 KB
All files in one compressed archive. Includes JSON data, documentation, and original YAML. Extract with: tar -xzf lmty-persona-package.tar.gz
Download Package

🤖 JSON Data File (For Bots)

persona-package.json • 14 KB
Single-file JSON with 12 personas, research context, validation sources, and pain point taxonomy. Bot-friendly format for programmatic use and simulation testing.
Download JSON

📝 Documentation

PERSONA-PACKAGE.md • 9.6 KB
Human-readable documentation with full context: validation sources, usage instructions, pain point taxonomy, budget authority matrix, and persona structure explanation.
Download Docs

📖 Quick Start Guide

PACKAGE-README.md • 7.5 KB
Handoff guide with usage examples, file format explanations, and code snippets. Perfect for onboarding another bot or developer.
Download Guide

🔧 Original YAML (For Editing)

personas.yaml • Included in package
Raw persona definitions in YAML format. Easier to manually edit than JSON. Available in the complete package download.
Download Package

👥 Persona Categories

  • PMM Individual Contributors (2) — Overwhelmed, manual weekly CI, firefighting
  • PMM Directors (2) — Team leads, use Crayon/Klue but still frustrated
  • Sales VPs/CROs (2) — Reps get blindsided, need to scale CI across teams
  • Founders (2) — No PMM, automation-first mindset, price-sensitive
  • Product Managers (2) — PMM bottleneck, need self-service access
  • RevOps/Strategy (2) — Analytical buyers, tie CI to revenue metrics

🔬 Validation Sources

Derek Osgood Thesis: "CI is not hired to win markets. CI is hired to survive ambiguity."

  • Slack #competitors channel IS the de facto CI system (not a feature)
  • Static artifacts (battlecards, PDFs) are dead on arrival (98% never viewed)
  • PMMs need status and legitimacy, not just better data
  • Sales pays, PMM uses — Sales Leadership controls budget

Sharebird Forum Patterns (50+ real PMM voices):

  • #competitors Slack channel is universal (8/18 threads)
  • Drowning in noise, desperate for signal (12/18 threads)
  • Sales feedback is gold but scattered (9/18 threads)
  • Weekly cadence is realistic (5/18 threads)
  • CI platforms exist but don't solve core problem (6/18 threads)

🎯 Usage Instructions

For Simulation Testing:

  1. Load persona-package.json
  2. For each persona: present homepage variant, measure Clarity (1-5), Relevance (1-5), Take Next Step (yes/no)
  3. Target N=60 (12 personas × 5 runs) for 95% confidence interval

For Message Testing:

  1. Pick target persona (e.g., pmm-ic-01)
  2. Test message against pain points, decision criteria, mental model, friction tolerance
  3. Pass/fail: If message addresses pain + satisfies must-haves + aligns with mental model + respects friction = resonates

For Product Development:

  1. Map features to persona needs (e.g., Slack integration = must-have for PMM IC, Sales VP)
  2. Prioritize features serving high-frequency + high-budget-authority personas first
  3. Design onboarding based on friction tolerance (low = instant value, high = strategic onboarding)