Concepts

The mental model behind Sales as Code. Read this once and the rest of the docs make sense without backtracking.

The portfolio

Sales as Code is a portfolio of products, one per sales role, sold as separate yearly subscriptions but built on one shared model: agents run the role's day on a schedule, in Claude Cowork, and never send or write anything without your yes.

• gtmcron (Founder / GTM operator) — Your go-to-market, on cron.
• salescron (Enterprise account executive) — Your sales day, on cron.
• leadercron (Sales leader) — Your sales org, on cron.
• secronjob (Sales engineer) — The SE’s day, on cron.
• partnercron (Partner / channel manager) — Your partner motion, on cron.
• bdrcron (BDR / inside sales rep) — Your pipeline day, on cron.
• crocronjob (Chief revenue officer) — The revenue org, on cron.
• cscron (Customer success manager) — Your post-sale motion, on cron.

One account licenses whichever products you own — a sales leader can run leadercron for themselves and add product seats for their AEs and SEs through Team on Cron without juggling separate logins. Founder, AE, Leader, and SE are the company-level personas the live portfolio is built around (partner managers, BDRs, CROs, and customer success managers join when their products launch); don't confuse them with gtmcron's own internal plugin roles below — those are one product's roles, not the portfolio's.

The two planes

Sales as Code is split across two places, on purpose:

• Claude Cowork — the work surface. The plugins run here. They read your tools through Cowork's connectors, do the actual work (draft outreach, research a market, prep a meeting, write a post), and never send anything without you.
• salesascode.com — the control plane. This site. It licenses the plugins, holds the one API key Cowork authenticates with, receives run telemetry + brain state, and shows you a read-only rollup. It does not do the work and does not hold your third-party access tokens.

gtmcron's plugins — one company, as roles

gtmcron — the founder / GTM-operator product — ships as eight Cowork plugins rather than one bundle. Each plugin is a company function an agent can run; together they play the roles of a one-person company. This is gtmcron's own internal role system (Operator, Closer, Writer, Researcher, Event) — a different, narrower axis than the portfolio personas above (one per product — Founder, AE, Leader, SE, BDR, CRO, CSM, Partner), which describe which product you need, not which role inside gtmcron a plugin plays. You license the gtmcron plugins you need; Company OS Core is required because every other plugin reads your company, offer, ICP, and voice from it.

• Company OS Core (Operator) — the front door. Scaffolds your Company OS, decision log, role map, and weekly operating review. Required by all others.
• GTM Engine (Closer) — trigger-driven prospecting, daily standup, a self-tuning funnel, and deal-closing help. Drafts only; never sends on its own.
• Content Engine (Writer) — the 10-agent Content Studio: research, draft in your voice, publish across channels, measure signups.
• Founder Chief-of-Staff (Operator) — morning brief, meeting prep, monthly investor/board update from your calendar, inbox, and business.
• Launch Readiness Audit (Operator) — a complete pre-launch audit of your repo and site (code, payments, security, SEO/GEO/AEO, ops) with a prioritized fix list and a remediation prompt. Read-only.
• Inbound & Lifecycle (Closer) — triage replies, route hot interest, nurture signups through lifecycle stages. Pairs with GTM Engine.
• Market Intelligence (Researcher) — weekly competitive sweep, daily community scan, drafted replies where it helps.
• Launch Kit (Event) — launch prep and launch-day ops (assets, positioning, timeline, comment templates).

Browse them at /plugins; each has its own feature doc, and the full set is listed together on the gtmcron product page. The other products — salescron, leadercron, secronjob, and the rest of the portfolio — each license as one product, not a per-plugin picker.

Plans & entitlements

salescron, leadercron, and secronjob are each a single yearly product subscription (see the portfolio for pricing). gtmcron is the exception: alongside its own $150/yr product subscription, it also sells per-plugin — this section covers that per-plugin picture. What you buy grants an entitlement — a per-plugin (or per-product) permission the skills check before they run.

• Pick gtmcron plugins — one-time purchases from $39 to $299. Buy a bundle (Core + a role) at a discount.
• Full Suite — all eight gtmcron plugins, one-time $599.
• All-Access — membership at $19/mo or $149/yr: every gtmcron plugin, updates, priority support.

Two rules worth knowing: Company OS Core is added to your cart automatically if you buy any gtmcron plugin without it; and every skill calls check_entitlement first, so an installed-but-unlicensed plugin or product stops and points you at /pricing rather than half-running. Choose a plan at /pricing.

The control-plane contract (MCP)

The plugins talk to this site through one MCP server at /api/v1/mcp, authenticated with your API key. Every skill follows the same shape: verify + entitle first, report last.

• verify_session — confirm this is a real, logged-in account. Every skill calls it first and stops if it errors.
• check_entitlement — is this account licensed for the plugin? Stops and asks you to buy/connect if not.
• pull_config — read your plan, entitled plugins, and feature flags so the skill can adapt at run start.
• emit_telemetry — record the run (plugin, skill, counts, outcome, duration). Metadata only.
• sync_brain — push brain state for a scope. No raw contact PII by default.

The last two are what turn a run in Cowork into something you can see here. The full contract lives in cowork-marketplace/docs/control-plane-mcp.md.

The brain — and why it compounds

The brain is the durable memory of your go-to-market. Each plugin keeps a scope of brain state — Company OS its offer/ICP/voice, GTM Engine its signal weights and funnel, Content Engine its voice model and what's published — and syncs that scope up on every run via sync_brain. The brain is empty on day one and gets sharper every week because each outcome (a won deal, a lost deal, a post that drove signups) feeds the next run.

Generic prompts don't get sharper. A brain that learns from your runs does — and because it lives in a shared scope, every plugin sees it.

Learning from losses

The brain learns most from losses. Mark a deal closed-lost and the GTM Engine prompts for a structured postmortem (symptom · root cause · what you'd do differently), stored as a dated entry in the sales-craft playbook. The next time an open deal shows the same early signals, that prevention rule fires. Here's a representative entry — anonymized, but the rule and the integration are exactly the shape that ships:

The playbook brain carries dated loss postmortems, win patterns, anti-patterns, and objection branches — all wired into the plugins. Every loss adds one. Every win adds one.

Content Studio

The Content Engine plugin is a 10-agent pipeline — Scout, Strategist, Writer, Media, Formatter/SEO, Repurposer, Compliance, Publisher, Community/Engagement, Orchestrator. It researches trends, drafts in your voice, cuts video, checks brand safety, and stages everything for you to approve at /studio. Each channel has a publish mode you control — Auto (e.g. LinkedIn personal), Draft → Approve (YouTube, Reddit), or Assisted (you submit, for Substack / Hacker News). It then drafts replies to comments and attributes signups back to the piece that drove them. Full detail on the Content Studio page.

Integrations — Cowork is the integration plane

You connect your tools inside Claude Cowork, not here. The plugins call Cowork's native MCP connectors — Gmail, Google Calendar, Drive, Slack, Apollo, Attio, Clay, Zoom, and any other MCP server you configure. salesascode.com holds your license, entitlements, run telemetry, and brain-sync — never your third-party access tokens.

• Where to connect. In Cowork, add the connectors your plugin's CONNECTORS.md lists (a CRM, an email tool, a prospecting/enrichment tool, a chat tool). The setup skill maps each category to what you connected.
• What flows back here. Only run metadata (which skill ran, when, counts, outcome) and the plugin's brain state — never raw contact data by default. See the privacy policy for the exact contract.
• Coverage gaps. If a tool has no Cowork connector yet, a plugin can still call any MCP server you configure. A small set of first-party connectors remains as an enterprise escape hatch, off by default.

Supported tools — reference

The plugins are tool-agnostic: they read whatever category of tool you point them at (a CRM, a sequencer, a data warehouse), through Cowork's connectors. This table is the reference for the tools we have working knowledge of and the small set of first-party connectors that ship as an enterprise escape hatch (off by default — you enable them only if a tool has no Cowork connector).

The tier column describes only the first-party connector, not the Cowork path:

• GA — the first-party connector's API path is verified; it works for any account with credentials.
• Preview — the connector is built but the vendor API path is unverified. The OAuth handshake works; events may or may not flow until we confirm against a live tenant. Prefer the Cowork connector where one exists.
• Partner-gated — the vendor requires a partner-program approval step before any data flows. Connect is disabled until you're approved; the UI links the application.

How to connect, in one line: add the tool's connector in Cowork (preferred), or — for a tool with no Cowork connector — enable its first-party connector here and complete the OAuth handshake; the plugin's setup skill maps the category to what you connected. What flows back to salesascode.com: only run metadata and brain state, never raw contact data by default.

Conversation intelligence is covered by Gong, Clari, and Zoom. Chorus and Avoma are not built as first-party connectors; use their Cowork connector (or any MCP server) if you need them, and tell us if it's a gap worth closing.

The rollup

Everything the plugins report — the emit_telemetry and sync_brain calls — lands on your rollup: runs and actions week over week, top outcomes, per-plugin health (Healthy / Failed / Not started), the newest runs, and the latest brain state per scope. It's read-only by design — the work happens in Cowork; the rollup is how you see it without leaving a tab open. Managers get the team-level version at /team-admin/rollup. How to read it: Cowork Rollup.