bdrcron

Overview

bdrcron runs a BDR's or inside-sales rep's prospecting day on a schedule, on our servers. Two tasks run on a clock: a morning prospect brief giving today's dial list warmest first with the reason for each ranking, and a Monday read of sequence experiments by reply-to-meeting rate. Five more run on demand: speed-to-lead, account deep research, sequence drafts, the call-block brief, and score narration. Scheduled tasks fire in the runtime's 06:15 UTC window. Everything is draft-first, and there is nothing to install.

Two governors keep you compliant: a cold governor caps outbound volume to protect deliverability, while a responsive governor always lets a hot reply or fresh inbound through.

What this role does for a founder

The first job of a sales hire, researched and drafted for you to send. Your sales development role prepares account research and outreach for your review.

Uses the confirmed brief and the profile you approved. The first launch researches up to ten companies, each with a source from its own website, and up to five contacts, checking your saved contacts first and using your own Apollo account only when you turn that on. After the first batch, a daily plan can keep going: up to five new companies a day, saved to your CRM, with a draft per contact.

Before it has work

• Confirmed brief and approved profile
• Gmail connected for drafts
• Attio connected for the daily plan
• Apollo (optional, your account, opt in)

Where its work goes

• To Account executive: A reply, with the company, the contact and the outreach history. Carry the conversation on without asking the buyer to repeat themselves.
• To GTM strategist: Companies held back, corrections to fit, and repeated objections. Sharpen the profile and the opening message.
• To Sales leader: Prospecting activity and where it stalls. Name where targeting or follow-through needs attention.

Needs a confirmed brief and an approved profile. Drafts need a connected Gmail with draft permission; the daily plan also needs Attio as the CRM and Gmail read access to see sends and replies. Enrichment needs your own Apollo account and explicit consent, and spends within daily ceilings. A found address is not proof of employment, deliverability or permission to contact. The full overview, with the work, outputs, an example and the measures to watch, is on the Sales development page.

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, inbox, and sequencer 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 bdrcron setup"). The wizard collects your identity, ICP, and sequences, 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, inbox, and sequencer, plus optional prospecting-data and analytics tools. The wizard verifies each and skips gracefully what you don't have.

Built-in BDR craft library

bdrcron ships with a deep, cited BDR craft library so your outreach reads like a top prospector from day one, before you have uploaded a thing. It covers the cold-call opener (winning the first 20 seconds), phone objection responses, gatekeeper navigation, speed-to-lead, multi-channel cadence, cold-email anatomy, relevance at scale, and lead qualification. On your first scheduled run these notes seed your knowledge library, so every AI draft grounds on real BDR method instead of generic prose.

This craft grounds how to prospect. Your proof points, the stats, logos, and quotes a draft cites as results, come only from the sources you upload in the console Library tab, so a draft never presents a playbook line as your customer's outcome. Full grounding model: Persona Console.

Licensing & the control plane

Your licence is checked before a run, never during one. The scheduler enumerates only the tenants whose bdrcron 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). bdrcron ships 7 hosted skills, 5 of them on an auto-run schedule (daily driver: speed-to-lead). Tier: front-line. These counts are read from the live registry, not hand-typed.

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