# leadercron · your sales org, on cron Explore Sales as Code . Role lander # 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. ## Sales leader work you can inspect One of nine connected roles ### See where your own pipeline is stuck, before there is a sales manager to ask. Pipeline and activity become the bottleneck named, a ranked action list, and coaching notes, once there is enough evidence to read. Preview Sales leader work[Explore all nine roles](https://salesascode.com/#team) ## Before the role can act Needs | Produces | Your decision | CRM opportunities and activity history | Sales-motion review | Choose the bottleneck to address | Pipeline gaps and role activity | Ranked action list | Assign the next action | Performance evidence | Coaching and process notes | Review the proposed change | 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. Full role overview, examples and schedules [Start leadercron](https://salesascode.com/signup) **$99/person/month, every role included** · runs on our servers, nothing to install · draft-first · metadata-only team reads [Build your team](https://salesascode.com/signup)[See this role's day](https://salesascode.com/docs/library/leadercron) ## What lands on your desk SL ### Research that keeps its sources Open the saved work to review the evidence and context behind a recommendation. SL ### Work prepared for your review Your sales org, on cron. ## It works with the rest of your team. Shared company context keeps the role's recommendations relevant. Open Today to review decisions across the roles you own. Example output **Sales leader daily brief** ### Human ownership, whenever you are ready. Assign this role to a teammate. They take responsibility for its work and review actions under the configured permissions. [Explore role assignment →](https://salesascode.com/docs/library/team-on-cron) Explore the team ## What this role does for you How it starts from your website, the work it performs, what you receive, an example, the input it needs, how to judge it, where its work goes, and what it depends on. SL · Sales leader Help you see where the sales process is stuck and decide which selling work needs attention next. As prospecting and deals accumulate, more activity does not mean better progress. This role inspects the evidence so you can improve targeting, follow-through and deal quality before adding management headcount. ## How it starts with your website 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. ## What the role does for you - Inspect the pipeline daily: what slipped, stalled or advanced, missing next steps, and one inspection question per deal. - Compare activity with progression to find the bottleneck, rather than rewarding message volume. - Prepare coaching notes weekly from available conversation and outcome evidence, and a manager performance synthesis at the end of the week. - Draft the sales section of a board update monthly, with every figure marked derived or assumed. - Prepare deal-review questions, ramp tracking and a handoff brief when you hire a seller or a manager. On its own schedule: 4 scheduled tasks, 8 more on request - Daily · 06:15 UTC Pipeline inspection: the deals that need a manager today, and why each one - Wednesdays · 06:15 UTC Coaching notes: each rep’s week turned into a 1:1 agenda grounded in their own numbers - Fridays · 06:15 UTC Team synthesis: who is ahead, who is behind the ramp, and what to do about it - Monthly, day 1 · 06:15 UTC Board update drafted from the month’s pipeline and attainment Times are UTC. Every task stops at a draft or a report for your review; you can turn any of them off in the console. ## The work you receive - A sales-motion review with the most important gaps and their evidence. - A ranked action list for you and for each role owner. - Coaching notes and proposed process changes. - A new-hire handoff brief covering the pipeline, working practices and open decisions. ## An example in practice Research is producing accepted companies, but interested replies are waiting days for a response. The role highlights that delay and recommends fixing the response step before increasing outbound volume. A scenario to show the shape of the work, not a customer result. ## What it needs from you Decide which process changes to adopt and where your limited selling time goes. Review exceptions rather than every record. When people join, they keep responsibility for their own decisions and performance. The confirmed business brief is reused across every role. The roles ask for missing facts, the decisions only you can make, and approvals, instead of repeating setup. ## Expected outcomes and how to judge them A clearer view of what blocks pipeline progression and a practical order for fixing it. The intended effect is a more disciplined motion and better use of your time. ### Measures worth watching - Next-step coverage, stale-deal age and response delays. - Conversion between researched company, reply, meeting and qualified opportunity. - Whether agreed process changes were made and what changed after, with the baseline and sample size visible. ## How the handoff works Each handoff carries the account or customer reference, the source evidence, the work status, the responsible owner, and the decision needed next. - ### To Sales development **What moves:** Evidence-backed priorities and where prospecting stalls. **What happens next:** Adjust research or follow-through where the motion is stuck. - ### To GTM strategist **What moves:** Patterns in acceptance, objections and qualification. **What happens next:** Revisit the profile or the message. - ### To Revenue leader **What moves:** Pipeline quality and capacity constraints. **What happens next:** Inform revenue planning and hiring decisions. ## When it is useful, and what it depends on 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. - Opportunities in a connected CRM - Some weeks of activity to read Results and speed depend on the offer, the evidence, your decisions, and the buyer. Nothing here promises revenue or a time to revenue. Explore this role's capabilities ## The name is literal. 4 scheduled tasks run the leader's rhythm. Every one drafts, none of it sends without you. When | What runs | Daily · 06:15 UTC | Pipeline inspection: the deals that need a manager today, and why each one | Wednesdays · 06:15 UTC | Coaching notes: each rep’s week turned into a 1:1 agenda grounded in their own numbers | Fridays · 06:15 UTC | Team synthesis: who is ahead, who is behind the ramp, and what to do about it | Monthly, day 1 · 06:15 UTC | Board update drafted from the month’s pipeline and attainment | Times are UTC. The runtime dispatches three times a day, at 06:15, 12:15 and 17:15 UTC, and each task takes one of those windows. You can turn any of them off in the console. // the gate ### Nothing reaches a customer without you. leadercron drafts. It does not send. A draft is refused at the send layer until a signed-in person approves that exact draft, and there is no scheduled path, agent or automation in the product that can do the approving. That is a check in the code, not a setting to remember. Sending is off on a new account and stays off until you turn it on. With it off, an approved draft is recorded as held rather than sent, so you can run the whole thing for a month and read what it would have said. ### The edge no one else has: your team's real activity. If your AEs run [salescron](https://salescron.com) and your SEs run secronjob, leadercron reads their agents' run telemetry through the salesascode.com control plane, team owners only, metadata only, never their message contents. Your Monday brief and 1:1 packs are built from what actually happened last week, not from memory. No sibling products yet? Everything still works from your CRM. **The family:** gtmcron: Founder / GTM operator · in every seat salescron: Enterprise account executive · in every seat **leadercron: Sales leader · in every seat** secronjob: Sales engineer · in every seat partnercron: Partner / channel manager · in every seat bdrcron: BDR / inside sales rep · in every seat crocronjob: Chief revenue officer · in every seat cscron: Customer success manager · in every seat supportcron: Customer support lead · in every seat One account · one login · one rollup · salesascode.com ## Put your org on cron. $99 /person /month [Get started](https://salesascode.com/signup) [See pricing](https://salesascode.com/pricing#products) Licensed and steered from salesascode.com · siblings: gtmcron.com · salescron.com · secronjob.com · partnercron.com · bdrcron.com · crocronjob.com · cscron.com · supportcron.com ## Questions people ask How much does leadercron cost? $99 per person per month, or $1,089 a year. That is the price of the whole platform: one seat licenses leadercron and every other role, and adding a teammate adds a seat at the same price. What does leadercron include? Forecast briefs, pipeline inspection across the team, 1:1 prep packs built from what your reps’ agents actually did, escalation drafts worth your signature, a durable coaching log, and QBR and board drafting. Does leadercron need salescron or secronjob too? No. Every skill still works from your CRM alone. If your AEs run salescron and your SEs run secronjob and you own the team, leadercron additionally reads their agents’ run telemetry, metadata only, for richer briefs. --- 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).