Product documentation (EN) — B2B evidence-led prospecting SaaS (lawful OSINT)

Keep in sync with ../es/README.md: any change here must be reflected in Spanish.

This set defines vision (Apollo/Uplead category: evidenced research + bulk email, send telemetry + AI copy generation; emphasizing signal + traceability over hollow volume), MVP scope, lead model, data sources by phase, compliance, MVP FRs, an architecture sketch, and 09 (stack options proposal). It does not replace legal counsel.

Suggested reading order

1. 01-vision-and-positioning.md — What we build, for whom, and what we do not promise.
2. 02-mvp-scope-and-out-of-scope.md — MVP boundaries and explicit exclusions.
3. 03-use-cases-and-queries.md — Natural-language queries and ICP/signal decomposition.
4. 04-lead-model-and-scoring.md — Lead structure, confidence, scoring, and metrics (defensible precision vs. commercial aspiration).
5. 05-data-sources-by-phase.md — Data tiers, MVP priorities, and per-source risks.
6. 06-compliance-and-risks-us.md — US-oriented compliance sketch and “lawful, documented sources” policy.
7. 07-functional-requirements-mvp.md — Prioritized MVP capabilities.
8. 08-architecture-sketch.md — System flow and conceptual components (no fixed stack).
9. 09-technology-planning.md — Stack options and tradeoffs to implement the MVP (proposal).

Conventions

• Lead (MVP): a candidate organization record (not a patient or end consumer of clinical services). A future lane may cover individuals / B2C under distinct policy and legal review (see 06-compliance-and-risks-us.md).
• Evidence: link, citation, or source reference supporting a field or a “warm” / opportunity tag.
• MVP: minimum version to validate measurable accuracy and human review flow, not national coverage or every vertical.