# BitterLeads Public Context

## Summary

BitterLeads is a focused lead database for humans and agents working the same
list. It turns consented signups, replies, referrals, recording links, and
campaign clicks into lead rows that humans and agents can work safely.

It is the operating layer between attention and action: source attribution,
consent, evidence, qualification, follow-up drafts, proposed tags, next
actions, lead events, and receipts without paying suite prices for list
storage.

## Product Loop

```text
SourceEvent -> Consent -> LeadDossier -> Evidence -> Annotation -> Proposal -> NextAction -> ConversationOrConversionReceipt
```

## User And Job

The user is a founder-led seller or operator who needs a cheaper, more useful
lead list than a bloated newsletter suite: source, consent, evidence,
qualification, proposed follow-up, and next action without letting agents
overwrite canonical lead facts.

## Bitter Role

BitterLeads is a constellation satellite for agent-native lead custody. It can
start with BitterClip distribution and founder-led sales, but the product
boundary is broader: consented lead rows and next actions for small software
operators.

## Boundaries

BitterLeads owns consented lead custody, source attribution, lead rows,
evidence, annotations, proposals, next actions, lead events, and MCP-compatible
lead work.

BitterPost owns relay. BitterInbox owns conversations. BitterAnalytics owns
read models. BitterCheckout owns payment handoff. BitterLeads does not replace
a CRM, own support conversations, own analytics interpretation, or let agents
directly overwrite canonical lead facts.

## Public Claims

Source-supported public claims:

- every consented signal can become a structured lead row
- humans keep judgment and relationship context
- agents can research, annotate, classify, draft, and create next actions
- canonical lead facts stay protected from direct agent overwrite
- BitterLeads fits between source attribution and follow-up action
- BitterLeads is a focused lead utility, not a full newsletter suite

Claims to avoid unless separately verified:

- fully automated outbound sales
- CRM replacement
- inbox replacement
- analytics dashboard
- autonomous agent mutation of canonical lead facts
- live production app completion

## Current Deployment Boundary

Status: source-shaped, deployment pending.

The GitHub repository remains private and the live site has not yet verified
the new health, Markdown, or LLM routes. Detailed deployment receipts live in
Factory. Do not call this marketing repo live-done until deployment, edge/TLS,
health route, Markdown/LLM routes, and public visibility are verified.