Discover · Field system
Competitive Intelligence Engine
Competitive knowledge becomes stale quickly and is difficult to operationalize.
Career signal: Competitive Strategy, Market Intelligence, Product GTM
All projects1. Problem
Competitive knowledge becomes stale quickly and is difficult to operationalize.
Deals and product decisions need a living view of where we win, where we do not, and what changed.
Without this: Objection handling lives in Slack. Every deal reinvented the brief.
2. Users
Primary: AEs and SAs in live cycles
Secondary: Product and PMM using field signal for messaging and roadmap
Job: Walk into a competitive conversation with a current, teachable brief.
3. Evidence
Across Forcepoint, Rapid7, and Truffle, competitive noise showed up differently in every deal. Playbooks and battlecards worked when they were a system, not a one-off deck.
4. Goals and non-goals
Goals
- Repeatable briefs: category, win conditions, gaps, and how to teach it in the room.
- A path from competitor change → field recommendation.
Non-goals
- Scraping the entire internet.
- Automated public attack content.
5. MVP
Structured battlecards and briefs the field can run without the author in the room.
Question the MVP tests: Does a shared competitive system change win strategy more than hero decks?
6. Workflow
- Competitor sources
- Snapshots
- Change detection
- Classification
- Impact analysis
- Recommendations
- Alerts / history
7. System design
Plain language
- Sources
- Monitoring
- Change detection
- Impact
- Recommendation
- History
Technical
- Scheduled source checks (next)
- Snapshot store
- Classification
- Application API
- Field UI / CRM notes
8. Data model
- Competitor
- Claim
- Change
- Impact
- Recommendation
- Deal context
9. Metrics
Operational
- Faster awareness
- Less duplicated research
Behavioral
- Brief usage in deals
Business
- Hypothesis: more consistent competitive execution and better messaging feedback into Product
10. Business impact hypothesis
If competitive changes are classified and turned into recommendations, deal strategy and product messaging should stay current. Field briefs are the current proof; monitoring is next.
11. Tradeoffs
- Human-authored win/loss over unreviewed model summaries.
- Depth on a few competitors over shallow coverage of everyone.
12. Prototype
Field system: battlecards and briefs. Monitoring, snapshots, and alerts are designed, not built.
Intended value
- Faster awareness
- Better deal strategy
- Improved messaging
- Stronger product feedback
- More consistent competitive execution
13. What I would build next
- Scheduled source snapshots.
- Change detection with human review.
- Closed loop into product feedback.