Feature docs · /crocronjob/console

crocronjob

The chief revenue officer's week on scheduled agents: a whole-org revenue pulse, ranked exec flags, a cross-team forecast rollup with a week-over-week delta, per-manager scorecards, a GTM-efficiency brief, and a weekly pipeline council.

Open crocronjob → All docs

Overview

crocronjob runs a chief revenue officer's week on a schedule, on our servers. Three tasks run on a clock: a Monday cross-team forecast rollup that reconciles one number across the org and shows where it disagrees, and, on the first of the month, a board narrative and a QBR pack assembled from the quarter's own numbers. Five more run on demand: the pipeline council, scenario modelling, a leader-development brief, the strategic-deal war room, and score narration. Scheduled tasks fire in the runtime's 06:15 UTC window. Everything is draft-first, and there is nothing to install.

Cross-team rollups read run telemetry through the control plane (team owners only, metadata only), never your reps' or managers' message contents. Every skill still works from your CRM alone.

What this role does for a founder

Decide from your own numbers when the next hire should be a person. Help you connect revenue evidence, spending and capacity to the next business decision.

Uses the confirmed commercial assumptions first, then your own opportunity, payment, usage and cost evidence as you connect it. A concept-stage business gets an assumptions-based plan, not an invented revenue forecast.

Before it has work

Opportunities with amounts in a connected CRM
A billing connection for collected revenue (optional)

Where its work goes

To GTM strategist: Evidence of which profiles and offers are working. Revise market priorities and campaign hypotheses.
To Sales leader: Revenue priorities and capacity constraints. Translate the plan into sales work and coaching.
To You: A sourced decision brief with assumptions and alternatives. Choose the next investment, experiment or hire.

Revenue analysis needs your own commercial data: a CRM with amounts and stages, and a billing connection for collected cash. Your subscription to this product is never counted as your revenue. Attribution and forecasts stay limited by the evidence and the method used. The full overview, with the work, outputs, an example and the measures to watch, is on the Revenue leader page.

Get started

Buy a seat at /pricing ($99 per person per month, which licenses this role and every other one), then set up at /onboarding.
Open your console and connect your CRM and forecasting 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 crocronjob setup"). The wizard collects your identity, org structure, and targets, verifies connectors, registers the scheduled tasks, and writes your config.
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 forecasting tools, plus, for team owners, run telemetry from the products your teams run, read metadata-only through the salesascode.com control plane. 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 crocronjob 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). crocronjob ships 8 hosted skills, 3 of them on an auto-run schedule (daily driver: org-forecast-rollup). Tier: leadership. These counts are read from the live registry, not hand-typed.

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