Sales as Code · learns your territory, for every seat in the revenue org

The whole revenue org, compounding.

Most sales AI runs your playbook. These learn from it. Eight products, one per seat, each running the role's day on a schedule in Claude Cowork — then, every night, hardening what worked, retiring what didn't, and naming what it still doesn't know. You approve what matters.

Runs in Claude Cowork on your tools. Licensed and steered from salesascode.com.
// the portfolio

One product per seat. All on cron.

Your revenue org has a front line that carries a number and a leadership layer that owns the org. There's a product for each. All 8 are live today.

Founder / GTM operator
gtmcron

Your go-to-market, on cron.

$150 /year
See gtmcron →
Enterprise account executive
salescron

Your sales day, on cron.

$250 /year
See salescron →
Sales leader
leadercron

Your sales org, on cron.

$350 /year
See leadercron →
Sales engineer
secronjob

The SE’s day, on cron.

$250 /year
See secronjob →
Partner / channel manager
partnercron

Your partner motion, on cron.

$250 /year
See partnercron →
BDR / inside sales rep
bdrcron

Your pipeline day, on cron.

$150 /year
See bdrcron →
Chief revenue officer
crocronjob

The revenue org, on cron.

$350 /year
See crocronjob →
Customer success manager
cscron

Your post-sale motion, on cron.

$250 /year
See cscron →
// two planes, one account

The agents do the work in Cowork.
You steer it from here.

One account spans both planes. Agents work in Cowork; you steer from here.

// where the work happens

In Claude Cowork.

  • Agents run inside Cowork
  • On your CRM, inbox, calendar, and network
  • They research, write, and publish
  • They send only where it's safe
  • They run on a schedule or on ask
  • Telemetry streams out as they go
The engine room. Your data, your connections.
// where you control it

On salesascode.com.

  • Point it at the context your product needs — a repo or site for gtmcron, your CRM for salescron, your team's activity for leadercron and secronjob
  • License and authenticate your account
  • Generate the key Cowork connects with
  • Approve drafts before they go out
  • Watch the rollup — what it drove, what it learned, and what it flagged as still unknown
  • Manage your plan and access
The cockpit. Onboarding, approval, and the rollup.

One account, two planes. See how connecting works →

// the name is literal

While you slept, it got smarter.

A sample of the real schedules — one slice from each product. Every task ships its work as drafts; nothing reaches a person without your yes. And every night the brain reflects on the day: it hardens what actually moved a deal into durable plays, retires what didn't, and writes down what it still doesn't know — so tomorrow's runs start smarter than today's, on your territory specifically.

WhenProductWhat ran
M–F · 6:00am salescron Morning account briefing — signals scanned, industry-matched outbound drafted into Gmail
Mon · 7:00am leadercron Forecast brief — commit/best-case vs quota, movers, risks, team activity
Daily · 6:00am secronjob Demo prep briefs — stack, use cases, likely objections, the flow to run (silent when no demos)
Weekly gtmcron Content calendar — a week of drafts in your voice, staged for approval
M–F · 6:00pm salescron Reply tracker + CRM hygiene — what landed, what’s stale, what’s missing
Fri · 4:00pm secronjob Weekly SE synthesis — where the technical cycles concentrated, what to unblock

// how it works

Five steps once. Then it runs.

The same flow for every role — pick, trial, install, connect, run.

1
choose

Pick your seat.

BDR to CRO — one product for each seat in the org.

2
subscribe

Subscribe.

One yearly subscription for your role. Renews automatically each year.

3
install

Install in Cowork.

Add your product's marketplace inside Claude.

4
connect

Connect your key.

Generate it here; paste it once in Cowork.

5
run

It runs. You approve.

The schedule does the work; the rollup shows it.



// questions

Honest answers.

Which product is for me?

One per seat in the revenue org. Front line: bdrcron (BDR), salescron (enterprise AE), secronjob (sales engineer), cscron (customer success). Leadership: gtmcron (founder / GTM), partnercron (partnerships), leadercron (sales leader), crocronjob (CRO). They share one account and one rollup. All eight are live today.

What actually runs on the schedule?

Each product ships a literal cron table — morning briefs, hygiene scans, prep packs, follow-up drafts. Every product page lists its full schedule.

Do you see my data?

No. The agents run inside your Claude, on your tools, with your logins. salesascode.com holds your license and run telemetry (metadata), never your CRM rows, emails, or tokens.

Does anything send without me?

Draft-first everywhere. Anything that reaches a person waits for your approval; automation is opt-in per channel and only where a platform welcomes it.

How does licensing work?

Yearly subscription per product. If it lapses, skills degrade softly — you get a renewal link, never a bricked run.


// eight seats, one account
BDR. AE. SE. CSM. Partner. Founder. Leader. CRO.

Every seat in the revenue org, on cron.

Scheduled agents run each role's day — research, drafts, follow-ups, hygiene. You approve what matters.

Runs in Claude Cowork · steered from salesascode.com · your tools, your connections, your call.