# partnercron · Docs · Sales as Code [← All feature docs](https://salesascode.com/docs/library) Feature docs · /get-started/partnercron # partnercron The partner / channel manager's week on scheduled agents: signal-driven partner outreach drafts, a co-sell pipeline dashboard, a partner signal monitor, an enablement digest ranked by sourced pipeline, deal-registration hygiene, and a partner scorecard. [Open partnercron →](https://salesascode.com/get-started/partnercron) [All docs](https://salesascode.com/docs/library) ## Overview partnercron runs a partner or channel manager's week on a schedule, on our servers. Its scheduled tasks run the partner week: Contact-Queue-gated partner outreach drafts, a read-only co-sell pipeline dashboard of sourced and influenced deals, a partner signal monitor sweeping news and org moves, a Monday enablement digest ranked by sourced-pipeline impact, a deal-registration hygiene scan for stale/expiring/conflicting registrations, and a Friday partner scorecard with a DO-TODAY list, plus a daily brain synthesis. Everything is draft-first: nothing reaches a partner without your yes. There is nothing to install. Partner outreach is **Contact-Queue gated** so partners are never over-messaged. ## Built-in partner craft library partnercron ships with a deep, cited **partner craft library** so your drafts read like a seasoned channel leader from day one, before you have uploaded a thing. It covers building a joint business plan around a shared number with owners and dates, recruiting partners for account overlap and motivation (not logos), tracking sourced and influenced pipeline separately, defusing channel conflict with rules of engagement agreed early, enabling a partner to win when you are not in the room, running a co-sell as one deal with two teams, prioritizing partners and accounts by real ecosystem overlap, and governing the relationship with a quarterly review on shared numbers. On your first scheduled run these notes seed your knowledge library, so every AI draft grounds on real channel method instead of generic prose. Add your own proof points on top in the console **Library** tab. ## Get started - Subscribe at [/pricing](https://salesascode.com/pricing#products) ($250/yr), then follow [/get-started/partnercron](https://salesascode.com/get-started/partnercron). - Open your [console](https://salesascode.com/partnercron/console) and connect your CRM and partner-management (PRM) tools in **Settings**. We custody each token encrypted and read it on the schedule; there is nothing to install. - In the console, run setup (*"run partnercron setup"*). The wizard collects your identity, partner roster, and co-sell context, verifies connectors, registers the scheduled tasks, and writes your config. - Choose where drafts land in **Settings**: an in-app draft queue, your Google Drive, or your mailbox as a draft. Nothing is sent without your approval. ## Connectors it uses You connect these in the console and we custody the tokens encrypted, reading them on the schedule: your CRM and partner-management (PRM) tools, plus optional inbox and analytics. The wizard verifies each and skips gracefully what you don't have. ## Licensing & the control plane Your licence is checked before a run, never during one. The scheduler enumerates only the tenants whose partnercron subscription is current, so a lapse means the next run is not scheduled, and a run already under way is never cut off. Every run reports its telemetry to your [Rollup](https://salesascode.com/rollup) either way. Details: [Licensing & renewal](https://salesascode.com/docs/library/licensing). ## Your console (runs on our servers, nothing to install) **By the numbers (live).** partnercron ships **7** hosted skills, **2** of them on an auto-run schedule (daily driver: `partner-daily-drafts`). Tier: leadership. These counts are read from the live registry, not hand-typed. partnercron has a control surface in your browser at [/partnercron/console](https://salesascode.com/partnercron/console). It drives the **hosted runtime** that runs partnercron's agents on our servers on a schedule, so nothing depends on you keeping an app open. Scheduled work runs on a metered key (ours by default, capped and priced into your subscription, or **your own** Anthropic or OpenRouter key). Bedrock is built but not accepting keys yet; Settings shows it as coming soon until the transport is validated. - **Schedule.** A runtime on/off switch, plus every skill with its cadence and tier. Toggle any skill or run one now. - **Draft queue and Runs.** Review the drafts your runs produced and see what ran, when, and what it cost. - **Live coach (front-line seats).** On-demand interactive coaching: practice a live buyer roleplay, build a pre-call brief for a connected meeting, or draft a reply to an inbound thread. Draft-only, on your budget, nothing sent. - **Build.** Probe an MCP server you have already connected to see the tools it offers, and check a custom skill draft against the same compiler the fleet runs. Both are read-only: probing lists tools without calling one, and validating saves nothing. - **Settings.** Budget meter, identity, and bring-your-own-key. **Delivery.** Output is draft-first and lands where you choose: your in-app draft queue by default, and optionally your Google Drive "Accounts" folder. For a security-strict team that needs real Gmail or Outlook drafts and CRM writes on their own credentials, an optional self-hosted path (n8n on your own machine) is available. Nothing is ever auto-sent. Full walkthrough: [Persona Console](https://salesascode.com/docs/library/persona-console). --- More for agents: [llms.txt](https://salesascode.com/llms.txt), [full reference](https://salesascode.com/llms-full.txt), [OpenAPI](https://salesascode.com/openapi.json), [sitemap](https://salesascode.com/sitemap.xml).