Account Intelligence

AEs and SDRs have no living view of funding, leadership, hiring, stack, or news across assigned accounts — so outreach stays generic.

Signals get missed. Monitoring does not become an action.

Without this: Reps refresh the same feeds. Territory mapping and outreach stay disconnected.

Primary: Single rep, personal feed (v1 is not a multi-rep admin console)

Secondary: Future: Nooks/Outreach as a handoff, not a live v1 integration

Job: See assigned-account signals and draft outreach that cites the specific event.

Companion to Channel Territory Mapping. Private repo account-signal-engine. Assignments arrive via webhook from secretsafari, or manually. Own copy of accounts — no shared database — so either app can stay up if the other is down.

Goals

• Classify signals: funding, leadership_change, hiring_surge, tech_change, news_mention.
• Mark read/dismissed.
• Draft copyable outreach from a signal (Claude API) — payload shaped for a later Nooks/Outreach push.

Non-goals

• Live Nooks/Outreach API, multi-rep admin, Salesforce IDs in v1.

Synced assignment appears in the feed; signals classified and tied to the account; a usable draft from a signal.

Question the MVP tests: Does a personal signal feed change outreach from generic to triggered?

1. Sync or enter assignment
2. →Poll Sumble / Exa
3. →Classify signal
4. →Feed (chrono or by account)
5. →Draft outreach

Plain language

1. Assignments
2. →Signal poll
3. →Classification
4. →Feed
5. →Draft

Technical

1. Next.js App Router
2. →Supabase (own instance)
3. →Sumble + Exa
4. →Claude API for drafts
5. →Webhook from secretsafari

• accounts
• rep_assignments
• signals
• signal_feed_reads
• outreach_drafts

Operational

• Sync without manual re-entry
• Correct signal type and account

Behavioral

• Drafts generated from signals
• Read/dismiss usage

Business

• Hypothesis: triggered outreach improves reply quality vs. generic sequences

If reps see account-specific events and can draft from them, outreach relevance should improve. No fake pipeline numbers.

• Independent deploy vs. a shared database.
• Copyable drafts vs. live sequencer push.
• Personal feed vs. team admin.

PRD. Private repo account-signal-engine. Whitespace accounts synced from territory mapping should show existing signals immediately, not wait for the next poll.

Intended value

• Fewer missed account events
• Outreach tied to a real trigger
• Territory mapping connected to action

• Live sequencer push
• Multi-rep view
• Salesforce IDs when available