Salesprompter

Docs that map the app, CLI, and extension as one system.

Public documentation for the Salesprompter contracts, workflows, and runtime behavior. This deployment is generated directly from the docs source in the CLI repository.

Source repository

Salesprompter has three product surfaces that should behave like one system:

  • The app owns identity and backend auth flows.
  • The CLI runs deterministic lead and domain workflows as JSON-first artifacts.
  • The Chrome extension should operate as a browser-side companion, not a separate product silo.

This repository currently contains the CLI implementation and the contracts the rest of the universe must honor. That means some pages in this docs set are implementation docs for code in this repo, while others are contract docs for the app and extension that integrate with it.

Pick your path

Start here

  • Read Quickstart if you want to run the CLI or preview the docs locally.
  • Read Architecture if you want the system model first.
  • Read CLI for the command surface and runtime behavior.
  • Read App for the backend auth contract the CLI expects.
  • Read Chrome Extension for the browser-side contract the extension should follow.

What this repo is the source of truth for

Today, this repository is the strongest source of truth for:

  • The CLI command surface in src/cli.ts
  • The JSON contracts in src/domain.ts
  • The auth handshake the app must satisfy in src/auth.ts
  • The BigQuery and domain-finder workflows in src/bigquery.ts, src/domainfinder.ts, and related modules
  • The Instantly sync behavior in src/instantly.ts

Documentation map

Platform

  • App: the backend and identity contract shared by the whole product.
  • CLI: command groups, auth behavior, exit codes, and runtime conventions.
  • Chrome Extension: how the extension should share identity, contracts, and provenance with the rest of the stack.

Workflows

  • ICP and Leads: define an ICP, generate or look up leads, enrich them, score them, and sync them.
  • BigQuery Lookup: build and execute warehouse queries safely.
  • Domain Finder: backlog analysis, candidate fetch, selection, audit, writeback, and repair.

Integrations and Reference

  • Auth Backend: device flow, token flow, session storage, and environment variables.
  • BigQuery: table contracts, field mapping, and bq execution behavior.
  • Instantly: dry-run semantics, dedupe behavior, and payload mapping.
  • Agent Resources: the AI-facing entry points for LLM and agent consumption.
  • CLI Reference: grouped command reference.
  • Environment Variables: the full runtime configuration surface.
  • JSON Contracts: ICP, lead, scoring, and domain-finder artifact shapes.

Operations and Development

Product posture

Salesprompter is not trying to hide business logic in opaque automations. The design choice in this repo is the opposite:

  • every important step emits JSON
  • provider boundaries are explicit
  • fallback behavior is labeled as fallback
  • warehouse-facing mutations are separated from audits and dry runs

That posture should stay true across the app, CLI, and extension.