Sales settings

Sales settings is the owner / admin setup page for the sales-loop agents: Prospect Research and Outreach Writer. The values on this page are the input the agents read every time they run — change them here and the next research run or outreach draft will use the new config.

Until you fill this page out and pick at least one approved sender domain, the Outreach Writer will refuse to draft emails.

Layout

The page has four tabs and a global Save button. A metadata strip shows the current version, the source (pack-default or saved override), the config hash, and the last-saved timestamp.

ICP — who you sell to.
Positioning — how you describe yourself.
Offer — what you sell and which claims are safe to make.
Cohorts — tagging defaults plus the approved sender-domain allowlist.

You can edit any tab in any order. Save commits all four tabs in one versioned write.

ICP

ICP summary — one sentence describing your ideal customer. The Prospect Research agent reads this as the top-line fit criterion.
ICP criteria — one criterion per line, pipe-separated: Label | Description | required, preferred, or disqualifier. Example: Headcount | 20–200 employees | required. Use disqualifier for hard nos — Prospect Research will mark matching accounts as poor-fit even if other criteria pass.

Positioning

Primary audience — the value proposition the Outreach Writer anchors on.
Differentiators — one per line. The writer is allowed to claim these.
Proof points — one per line. Concrete evidence the writer can cite (customer names, metrics, certifications). Only put things here that are honestly true and externally verifiable.

Offer

Offer name — the primary thing you're pitching.
Offers — one per line. Additional offers the writer can rotate through.
Forbidden tokens — one per line. Phrases the writer must never emit (regulated claims, competitor names you can't reference, etc.).
Required tokens — one per line. Phrases that must appear in every draft (e.g. a compliance disclaimer).
Allowed claim themes — one per line. Topical claims the writer may make.
Unsupported claim themes — one per line. Topics the writer must hedge or omit because they aren't backed by proof points.

If a draft trips the forbidden / unsupported guardrails, the Outreach Writer fails the safety check and refuses to produce that draft. That failure is logged on the agent run and surfaced in the Inbox.

Cohorts

Default tags — one per line. Tags applied automatically to new accounts as research is approved.
Priority cohorts — one per line. Cohorts that bump research and outreach to the front of the queue.
Disqualifier tags — one per line. Accounts with any of these tags are blocked from outreach.
Sender-domain allowlist — the domains Outreach Writer is allowed to send from. The list is populated from your connected email accounts in Email accounts — click a domain to approve it. Outreach Writer requires at least one intersection between connected and approved domains before it will draft emails.

Where the agents read this

Prospect Research reads ICP, Positioning, Offer, and the cohort tag taxonomy. It writes back account mutations, cohort tags, and a reviewer-facing research document.
Outreach Writer reads Positioning, Offer (including all four guardrail lists), and the sender-domain allowlist. It refuses unsafe or low-fit cases.

Both agents are governed: their output goes to human review in the Inbox before any send happens. Sales settings is the input contract to that governance — the more honest the inputs, the more honest the drafts.

Tips

Treat Proof points as a legal/compliance surface. If you wouldn't put a claim on your website, don't put it here either.
Forbidden tokens is a blunt instrument. If you want a phrase blocked across all writers (e.g. "guaranteed ROI"), add it here.
Sender-domain allowlist is a two-step gate. Connecting a mailbox is not the same as approving its domain — both are required before Outreach Writer becomes eligible.
The metadata strip's Hash changes only when content changes. Use it as a quick diff signal across environments.

Permissions

Edit and save require the admin / owner role. The page is read-blocked for members.