Founders and early sales teams using SalesOS waste critical opportunities by reaching out cold. Today, outreach timing is guesswork based on stale data, causing 72% of outbound emails to be ignored (source: Q2 SalesOS engagement report, n=1.4M sends). Prospects actively signal readiness through job changes (17% higher response rate), funding rounds (32% higher), or competitor complaints (41% higher) — but these signals are buried across 8+ sources and manually tracked in spreadsheets costing 6.1 hours/week per seller (source: user survey, n=58 SMB sales teams).
Business case: 9,200 active SalesOS users × 12.2 prospect signals/month × $84.50 avg deal size × 8% conversion lift from timely outreach = $922K/year incremental revenue (source: user count from BI dashboard, signal frequency from Apollo.io benchmark, conversion lift from Gong.io study). If adoption reaches only 40% of users: $369K/year. This excludes saved labor from manual tracking ($1.2M/year recoverable).
This feature is real-time AI detection of 5 high-intent signals with tailored outreach prompts. It is not a replacement for CRM integration, lead scoring, or email automation — it feeds warm prospects into existing workflows.
Competitors solve partial aspects:
| Capability | Apollo.io | HubSpot | 6sense | SalesOS (this) |
|---|---|---|---|---|
| Real-time job change alerts | ✅ | ❌ | ✅ | ✅ |
| Funding round detection | ❌ | ❌ | ✅ | ✅ |
| Competitor complaint monitoring | ❌ | ❌ | ❌ | ✅ (unique) |
| AI-generated outreach angles | ❌ | ❌ | ✅ | ✅ (context-specific) |
| WHERE WE LOSE | Price (50% cheaper) | Ecosystem integration | Signal depth | ❌ vs ✅ |
Our wedge is hyper-relevant outreach angles because we synthesize signal context (e.g., "Congrats on Series B! Here’s how we helped [similar startup] scale support") while others send generic templates.
##SECTION:solution_design``` ┌───────────────────────────────┐ │ Prospect Signals Dashboard │ ├───────────────────────────────┤ │ Acme Inc ⚡ NEW SIGNAL │ │ - CEO changed 2h ago │ │ - Suggested angle: │ │ "Congrats on new leadership│ │ role! When [prior company]│ │ onboarded us during..." │ │ │ │ [View Prospect] [Draft Email] │ └───────────────────────────────┘
┌───────────────────────────────┐ │ Signal Settings │ ├───────────────────────────────┤ │ [✓] Job title changes │ │ [✓] New funding rounds │ │ [✓] Competitor complaints │ │ [ ] Leadership team growth │ │ │ │ Sources: LinkedIn, Crunchbase,│ │ Reddit, X, Angellist │ └───────────────────────────────┘
**Flow:**
1. User saves prospect list in SalesOS
2. AI engine scans 5 sources every 15 mins
3. Alert appears in dashboard with 1-click email draft
4. Outreach angle uses signal context + prospect history
**Key decisions:**
- **Excluded news mentions** (low intent) to reduce noise
- **Pre-written angle templates** validated by top SDRs (not generative AI)
- **No auto-send** — user must review before outreach
WHO / JTBD: When a founder or sales rep at an early-stage startup plans outbound, they need to know the exact moment a prospect is most receptive — so they can send relevant messaging that sparks conversations instead of generic cold emails.
FAILURE MODE:
Aggregate: $92.2K/year/seller in lost efficiency and revenue (source: comp bands + conversion benchmarks).
JTBD statement: "When my prospect shows buying intent through specific public events, I want to be alerted immediately with a tailored outreach angle so I can strike while the iron is hot."
Phase 1 — MVP (6 weeks)
US#1 — Signal detection
US#2 — Alert surfacing
Out of Scope (Phase 1):
| Feature | Why Not Phase 1 |
|---|---|
| Auto-send emails | Legal review required for spam compliance |
| Leadership growth signals | Requires org chart parsing (high complexity) |
| Slack/email alerts | Notification system overhaul needed |
Phase 1.1 (3 weeks post-MVP):
Primary Metrics:
| Metric | Baseline | Target (D90) | Kill Threshold | Method |
|---|---|---|---|---|
| Signal-to-conversion rate | 6.8% | ≥10% | <7.5% | SalesOS deal tracking |
| Time to first outreach | 48hrs | ≤4hrs | >24hrs | Activity log timestamps |
| Saved tracking time | 0 | ≥4 hrs/week | <2 hrs/week | User survey (n=100) |
Guardrail Metrics:
| Metric | Threshold | Action |
|---|---|---|
| False positive rate | <5% | Pause detection for review |
| Unsubscribe rate | ≤0.1% | Disable auto-drafts |
What We Are NOT Measuring:
Risk: False positives annoy prospects
Probability: Medium | Impact: High
Mitigation: Human review of all angles pre-launch (SDR team owner; due 8/15)
Risk: Delayed Crunchbase data
Probability: High | Impact: Medium
Mitigation: Fallback to SEC filings for funding (Eng owner; sprint 2)
Risk: Non-compliance with GDPR
Probability: Low | Impact: Critical
Mitigation: Exclude EU prospects by default + legal signoff (Compliance owner; due 7/30)
If blocked: Feature disabled in EU until approval
Risk: Alert overload for large lists
Probability: High | Impact: Medium
Mitigation: Max 5 alerts/day/prospect + customizable thresholds (PM owner; launch day)
Kill Criteria (90 days):
0.15% email unsubscribe spike
| Question | Owner | Deadline |
|---|---|---|
| Max prospects/list for real-time scanning? | Eng | 7/15 |
| Process for user-reported false positives? | Support | 8/1 |
| Angle template refresh cadence? | Product | 7/30 |
Decision: Data source prioritization
Choice: LinkedIn/Crunchbase/Reddit/X/Angellist only
Rationale: Cover 92% of high-intent signals (source: user survey) vs. adding 4 low-yield sources (+3mo dev).
Decision: Outreach automation level
Choice: Draft generation with manual send
Rationale: Avoids spam risk from AI auto-sending; preserves human review.
Decision: Signal types in MVP
Choice: Job changes/funding/complaints only
Rationale: Leadership growth detection requires complex org chart parsing (deferred to Phase 1.1).
Decision: Alert delivery
Choice: In-app only (no email/Slack)
Rationale: Reduces implementation complexity; 74% of users check app daily (source: usage data).
Before: Alex (founder at B2B startup) misses that "Acme Inc" posted complaints about Salesforce on Reddit. He sends a generic cold email 3 days later — ignored. He spends 30 mins daily checking prospect social feeds.
After: SalesOS detects Acme’s Reddit post instantly. Alex sees: "Acme: Complaints about Salesforce! Suggested angle: ‘We helped [similar co] cut support tickets by 40% without Salesforce’s complexity.’" He sends a reply within 1 hour — books a meeting.
Pre-Mortem:
It is 6 months post-launch and this feature failed because:
Success looks like:
Users say: "I stopped stalking prospects on LinkedIn." Sales teams report 30% shorter sales cycles. The CEO notes: "This turned SalesOS from a contact tool to an intelligence layer."