Agent-first GTM workspace
Optic watches SEC filings, newsrooms and the news for the moments your buyers care about, scores each one against a brain you write for every product, and drafts a note that opens with your product's own read on their news. Nothing sends until you approve it.
any new kumkuat signals above 0.7?
optic-kumkuat · list_signals(workspace="kumkuat", min_score=0.7)
Two above 0.7. Halvard has a new comms lead in their first 90 days, which matches yourexec-change play. Corvane’s is an 8-K, so the source is the filing itself.
How it works
Five steps, one engine. Every step is a service function, so Claude, webhooks and the coming web UI all run the same code.
The full walkthrough →Optic watches SEC filings, news search, company newsrooms and investor-relations pages for the accounts you care about, every hour.
8-K items 2.02, 2.01, 5.02 · GDELT news · RSS/Atom · IR pages
A YAML brain per product sets the ICP, personas, voice, offers, signal weights and pace. Every score keeps its reasons.
score = weight × account fit × persona fit × freshness
The play runs your own product on their news and puts the result in the first line. The hook is the product working, not a merge field.
analyze → draft { offer, max_words }
Drafts wait in the approval inbox with the person, the company and the signal that triggered them. You approve, edit or reject from Claude.
list_approvals built · approve / reject next
Approved messages go out inside the brain's send window and daily caps, from a sending domain that belongs to one workspace.
one vendor first: Instantly or Smartlead
MCP-first
Optic is an MCP server first. Ask Claude what you owe replies on, which signals fired overnight, or what's waiting for approval. The agent works through the same functions a UI would, with your key's permissions and nothing more.
# add Optic to Claude Code
claude mcp add --transport http optic \
https://api.optic.to/mcp \
--header "Authorization: Bearer opt_…"Tools you can call today
list_workspacesWorkspaces you can act in, with your roledigestReplies you owe, conversations gone cold, tasks and deal next steps duelist_approvalsDrafts waiting for approval, with the person, company and triggering signallist_signalsThe signal feed, best score first, with the reasons behind each scoredismiss_signalMark a signal as not worth acting onBuilding next approve, reject, search next.All tools
Multi-product
We built Optic to run GTM for our own products, and each one is a workspace with its own brain, voice, pace, plays and sending domain. Two very different markets, one engine.
Enterprise comms
Sells to corporate communications teams at large companies. A small market, so every send is approved and the pace is slow.
Developer tool
Sells to B2B SaaS teams that ship weekly. Developer-to-developer voice: short, concrete, one link, one ask.
Your next product
Start from brains/_template.yaml. Set the ICP, voice, offers and signal weights, then optic push validates the brain and every play before anything runs.
auto plays where the brain requires approval.Rules in the database
These hold for every caller: the API, the agents, the workers, and someone editing rows in a SQL client. An agent can't talk its way around a trigger.
Row-level security limits each user and API key to its workspaces. Composite foreign keys stop a row from pointing at another workspace's record, even from the backend.
When someone replies, their play ends, queued automated drafts are canceled and they're marked engaged. Drafts you wrote by hand stay.
A suppressed address or domain can't be approved, scheduled or sent to. A hard bounce adds one. They survive deleting and re-importing the lead.
A person can be in one running play at a time, so two plays never email the same lead.
A sending domain belongs to one workspace, so one product's campaign can't hurt another product's sender reputation.
Every signal, email, reply, meeting and stage change is an event that can't be edited. Webhook deliveries are queued in the same transaction.
Guides
Approval-first outreach puts a human on every send. How to make reviewing drafts fast, which guardrails belong in the database, and when a play can run alone.
MCP for GTM: why a sales and marketing system should expose its actions as Model Context Protocol tools before it builds a UI, and how to design them safely.
Signal-based outbound for corporate communications buyers: which signals matter, how to score them, and how to pace a market of a few hundred accounts.
It isn't for sale yet. If you'd run it for your product, tell us what you sell and which signals matter, and we'll talk when drafting and sending are done.