leadercron

Overview

leadercron runs an enterprise sales leader's rhythm on a schedule, on our servers. Four tasks run on a clock: a daily pipeline inspection naming the deals that need a manager today and why, Wednesday coaching notes that turn each rep's week into a 1:1 agenda grounded in their own numbers, a Friday team synthesis of who is ahead and who is behind the ramp, and a board update on the first of the month drafted from the month's pipeline and attainment. Eight more run on demand: deal-review prep, 1:1 prep, the hiring loop, the ramp tracker, the territory planner, the wins digest, escalation drafts, and score narration. Scheduled tasks fire in the runtime's 06:15 UTC window. Everything is draft-first, and there is nothing to install.

What this role does for a founder

See where your own pipeline is stuck, before there is a sales manager to ask. Help you see where the sales process is stuck and decide which selling work needs attention next.

Uses the confirmed direction, prospecting activity, opportunity history and whatever conversation evidence is connected. For a solo founder it reviews the motion as it is, rather than pretending a team already exists.

Before it has work

• Opportunities in a connected CRM
• Some weeks of activity to read

Where its work goes

• To Sales development: Evidence-backed priorities and where prospecting stalls. Adjust research or follow-through where the motion is stuck.
• To GTM strategist: Patterns in acceptance, objections and qualification. Revisit the profile or the message.
• To Revenue leader: Pipeline quality and capacity constraints. Inform revenue planning and hiring decisions.

Needs enough real activity to inspect: opportunities in a connected CRM and some history. With little history it reports limited evidence and the setup gaps, rather than confident performance judgements. The full overview, with the work, outputs, an example and the measures to watch, is on the Sales leader page.

The team edge

If your AEs run salescron and your SEs run secronjob, and you own the team on salesascode.com, leadercron reads their agents' run telemetry through two control-plane tools (team_rollup and team_member_summary), so 1:1 packs and briefs are built from what actually ran. Metadata only: run counts, outcomes, account labels; never message contents, CRM records, or brain payloads. Without sibling products, every skill still works from your CRM.

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 in Settings. We custody the token encrypted and read it on the schedule; there is nothing to install.
3. In the console, run setup ("run leadercron setup"): identity, company, team roster + 1:1 cadence, forecast rhythm, connector checks, schedule registration.
4. Choose where drafts land in Settings: an in-app draft queue, or your Google Drive. Nothing is sent without your approval.

Licensing, renewal reminders, and lapse behavior: Licensing & renewal.

Your console (runs on our servers, nothing to install)

By the numbers (live). leadercron ships 12 hosted skills, 4 of them on an auto-run schedule (daily driver: daily-pipeline-inspection). Tier: leadership. These counts are read from the live registry, not hand-typed.

leadercron has a control surface in your browser at /leadercron/console. It drives the hosted runtime that runs leadercron'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 leadercron 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.