Competitive Intel

A $40M raise changes their motion — let's map the implications and set up a tracking system.

What $40M means in practice (next 12-18 months):

• Hiring spike: Expect 40-80 new headcount — primarily sales, marketing, and CS. Track their LinkedIn jobs page weekly.
• Pricing aggression: They may drop prices to accelerate land-and-expand. Watch their pricing page for changes.
• Feature velocity: Engineering hiring + capital = faster shipping. Expect 2-3 major feature announcements in 6 months.
• Brand spend: Thought leadership content, conference presence, analyst briefings (Gartner/Forrester outreach)
• Enterprise move: $40M raises typically signal a move upmarket — expect new enterprise features and case studies

Systematic Tracking Setup:

Your strategic options as a bootstrapped competitor:

1. Narrow ICP — pick a segment where their capital doesn't help (regulated industries, specific verticals)
2. Profitability narrative — bootstrap = customer-aligned, no VC pressure; resonates with certain buyers
3. Speed — you can move faster with less bureaucracy; use it before they're fully staffed

What's your current ICP overlap with them — are you going after the same exact buyers?

The Slack-and-forget pattern isn't a process problem — it's a structural one. Intel dies in Slack because there's no owner, no destination, and no cadence. Here's how to build a system that actually changes decisions.

The 4 Intel Sources

1. Public sources Job boards are the most underrated signal. Competitors don't announce strategy, but they hire for it. A cluster of enterprise sales hires signals upmarket move. A wave of ML engineer roles signals a product shift. Check LinkedIn jobs and Greenhouse/Lever directly weekly.

G2 and Capterra reviews (sorted by most recent) surface what actual customers say publicly about competitor weaknesses. These are your best source of objection language that you can use in your own positioning.

Also track: pricing pages, case studies, blog posts, press releases, LinkedIn company updates.

2. Community sources Twitter/X searches for competitor mentions, especially complaints. Reddit threads in your category subreddits — buyers compare tools openly and honestly here. Hacker News "Ask HN" threads about your problem space. These surface organic buyer sentiment you won't find in structured research.

3. Customer sources Win/loss call notes are the most actionable intel you'll ever have — and most companies don't capture them systematically. Every lost deal should produce 3 structured fields in your CRM: primary reason lost, competitor chosen, specific capability cited. Every churned customer conversation should include: what tool did you switch to, and what made you choose it?

4. Partner sources Your integration partners, agencies, and resellers talk to multiple tools in your space. A quarterly call with 3 key partners asking "what are you hearing about [competitor]?" yields more signal than a month of public monitoring.

Lightweight Monitoring Setup

Don't over-engineer this. The goal is consistent signal, not comprehensive coverage.

For teams with budget: Klue, Crayon, or Kompyte automate much of this. Evaluate at $1M+ ARR — before that, manual discipline is faster to start.

The Competitive Wiki Structure

One Notion or Confluence page per major competitor, updated continuously. Each page contains:

• One-line summary: Their positioning statement as they'd describe themselves
• ICP: Who they target (company size, industry, buyer persona)
• Pricing: Current tiers, any known discounts, enterprise pricing signals
• Strengths: Genuine strengths — your team won't trust a biased card
• Weaknesses: G2/customer-sourced, not opinion
• Recent moves: Last 90 days of notable activity (funding, hires, product launches, pricing changes)
• How they sell against us: What they say when they're competing with you directly (from win/loss calls)
• Your counter-narrative: The 3 sentences your reps use when this competitor comes up

Keep it short. A 2-page competitor page that gets read beats a 20-page report that doesn't.

Routing Intel to the Right Team

Intel that goes to everyone goes to no one. Route by signal type:

• Pricing change → Sales leadership same day (reps in deals need this immediately)
• New feature launch → Product manager within 48 hours
• Hiring pattern signal → Strategy/leadership in next weekly review
• New case study targeting your ICP → Marketing for counter-positioning
• Customer complaint on G2 → CSM team for potential win-back opportunity

Assign a Competitive Intel DRI (Directly Responsible Individual). At early stage this is a PM or marketing lead who spends 2 hours per week on it. The job isn't research — it's routing.

The Quarterly Competitive Review

Who attends: Product, Sales, Marketing, CEO/Founder

What gets updated: Every competitor wiki page reviewed, stale info flagged, battle cards refreshed

Output format:

1. Competitive landscape summary (one paragraph per major competitor)
2. Three signal changes from last quarter that matter
3. One strategic recommendation (pricing response, feature acceleration, positioning update)
4. Updated battle cards for Sales

Timebox this meeting to 90 minutes. The output document is distributed before the meeting — the meeting is for decisions, not status updates.

Avoiding Analysis Paralysis

Ship a 80% competitive wiki in week 1, update it weekly. The alternative — waiting until you have complete information — means your reps go into competitive deals with nothing.

Start with your top 3 competitors, the ones that appear in the most deals. Build one page each in the first two weeks. Distribute to sales. Then refine based on what reps actually ask for.

The system only works if it's used. Usage comes from trust. Trust comes from accuracy and timeliness — which means your first priority is speed and relevance, not comprehensiveness.