partnercron

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.

What this role does for a founder

Partner introductions proposed for your approval, before anyone owns partnerships. Find and prepare partner opportunities that can open customer conversations beyond your direct outreach.

Uses the offer and target market from the confirmed brief. It adds partner profiles, account overlap and relationship evidence as you connect them; overlap data comes through a partner-data connector that is still in preview.

Before it has work

• Partner profiles or overlap data
• Your approval of every introduction
• Enablement records entered by hand

Where its work goes

• To Account executive: An accepted introduction and the shared-account context. Work the opportunity with a clear owner.
• To Sales engineer: Partner enablement needs and technical questions. Prepare accurate technical material once, for reuse.
• To Revenue leader: Partner activity and attribution evidence. Judge whether the partner motion deserves more investment.

Useful when the offer benefits from a partner motion and there is partner data to read. Partner certification and enablement records are entered by hand today; overlap data needs the partner connector, which is in preview. It cannot create partner consent, guarantee an introduction, or share account information beyond the scope you approve. The full overview, with the work, outputs, an example and the measures to watch, is on the Partnerships page.

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

1. Buy a seat at /pricing ($99 per person per month, which licenses this role and every other one), then set up at /onboarding.
2. Open your 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.
3. 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.
4. Choose where drafts land in Settings: an in-app draft queue, or your Google Drive. 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 either way. Details: Licensing & renewal.

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. 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 AI work runs on your own provider key (Claude, OpenAI or OpenRouter; every tier is bring-your-own-key), after any platform-funded first-run allowance the deployment turns on. The free deterministic checks need no key. A key turns drafting on; nothing is sent until you turn the send layer on. Bedrock is built but not accepting keys yet; Settings shows it as coming soon until the transport is validated.

Today and Activity link to the original work in this workspace. Work also opens saved research and drafts. A direct link can retrieve an older finding or draft beyond the recent queue. Research expands its facts and quotes; historical drafts keep their status and disable unavailable edit actions.

Under its heading the console shows the one number partnercron was hired to move: the first week of connected data after the hire, day 30, day 60 and your target, or a note naming the connection that would supply a missing week. A role with no number the platform can measure says why instead. You pick the number and set the target on Home.

• 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, draft a reply to an inbound thread, write a deal-specific battle card for a competitor, or draft the lesson out of a deal you closed. 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, where the console names the last files that landed so you can tell delivery is working without going to look. 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.