Start

From signup to your first product running in Claude Cowork in about 10 minutes. Five steps — the same for gtmcron, salescron, leadercron, and secronjob. Work happens in Cowork; this site licenses the product, holds the key Cowork authenticates with, and shows you a rollup of what ran.

Before you start: you need a Claude account with Cowork access — that's where the product runs. salesascode.com is the control plane, not the work surface. New to the model? Read Concepts → the two planes first.

Two paths:

/signup with your work email — we send a magic link; click and you're in. No password by default; set one later in Settings.
/login → "Continue with Google" to skip the email round-trip. We store the Google sub claim so the same Google account always resolves to the same Sales as Code account, even if you change your Google email later.

2. Pick a product & subscribe (2 min)

Open /pricing. 8 products are live today, one per role, each a yearly subscription:

gtmcron ($150/yr) — founder / gtm operator.
salescron ($250/yr) — enterprise account executive.
leadercron ($350/yr) — sales leader.
secronjob ($250/yr) — sales engineer.
partnercron ($250/yr) — partner / channel manager.
bdrcron ($150/yr) — bdr / inside sales rep.
crocronjob ($350/yr) — chief revenue officer.
cscron ($250/yr) — customer success manager.

Pick the one that matches your role — most buyers license one; sales leaders often add their team's via Team on Cron. After checkout you land on /get-started/<product> with your entitlement granted.

Four more products are on the way — partnercron (partner / channel managers), bdrcron (BDRs / inside sales), crocronjob (CROs), and cscron (customer success). Join their waitlists from the homepage grid to hear on launch day.

gtmcron only: it alone also sells as eight individual plugins, a Full Suite, or an All-Access membership — see the gtmcron page and Licensing & renewal for how that fits alongside the yearly subscription.

3. Issue your API key (60 s)

This is the credential Cowork uses to prove it's your licensed account. Open /settings/api-keys → + New key, name it (e.g. "Claude Cowork"), and copy it. It's shown once — only a hash is stored, so we can't show it again. One key powers every product you own. See API Keys & MCP for scopes and the security model.

4. Add the marketplace & install in Cowork (3 min)

Open /get-started/<product> (linked from your Settings after checkout) — it shows your live status and the same steps /onboarding walks through for gtmcron. The same four checks also live on /settings/connect:

In Claude Cowork, add your product's plugin marketplace (the URL is shown on its get-started page).
Configure the Sales as Code MCP server: point it at https://salesascode.com/api/v1/mcp and set SALES_AS_CODE_API_KEY to the key from step 3.
Install the plugin(s) you licensed.

The wizard shows four checks — Licensed → Keyed → Connected → Ran. "Connected" turns green once Cowork makes its first verify_session call; "Ran" turns green after your first execution. A health strip shows each plugin as Healthy / Failed / Not started yet.

5. Run the setup phrase (3 min)

In Cowork, say your product's setup phrase:

salescron — "run salescron setup"
leadercron — "run leadercron setup"
secronjob — "run secronjob setup"
gtmcron — "set up my Company OS" first (the one sanctioned exception to the "run <product> setup" phrase, kept for installed-base compatibility), then each other plugin's own setup skill.

Every setup phrase does the same three things:

Verify + entitle. Every skill calls verify_session and check_entitlement first, so it only runs on a licensed account.
Read your context. Point it at a repo, a Google Drive folder, your website, or an upload. It scans and researches that into a reviewable company / offer / ICP / voice dossier — the GTM Context Dossier. Every other skill reads from this.
Report back. When it finishes it calls emit_telemetry and sync_brain — metadata only, no raw contact PII by default — which is what populates your rollup.

gtmcron buyers with more than one plugin: Content Engine's drafts show up for approval in Content Studio.

Done. Your product is running in Cowork. Open /rollup to see runs, outcomes, and per-plugin health week over week — read Cowork Rollup for how to read it. For the full mental model, see Concepts.

Common first-day issues

"Connect says I'm not licensed." — Checkout hasn't granted entitlements yet, or you bought under a different account. Confirm your plan at /settings; if a purchase completed but isn't showing, give the Stripe webhook a minute, then reload.
"A skill stops and says my account isn't connected." — Cowork can't reach the control plane. Recheck the MCP server URL (/api/v1/mcp) and that SALES_AS_CODE_API_KEY is set to a current, non-revoked key. Issue a fresh key at /settings/api-keys if unsure.
"A skill says I'm not entitled to this product/plugin." — You installed something you haven't licensed. Buy it at /pricing (gtmcron: or switch to All-Access), then re-run.
"The rollup is empty." — Nothing has finished a run yet. Run the setup phrase in Cowork; the first emit_telemetry call populates /rollup within seconds.