Why sales teams schedule their AI agents
Sales work is full of small recurring checks. Who signed up for a trial overnight, which target account just posted a job for the role you sell to, which deals have not moved in two weeks, which contacts bounced. Each check is easy, but nobody does all of them every day. A scheduled agent does. It runs at the time you set, pulls the data, reasons about it and delivers a short list your reps can act on before their first call.
Because the cron keeps memory between runs, it reports only new leads and only new signals. Your reps stop scrolling through the same names every morning and start with what changed.
Sales jobs worth scheduling
| Instruction | Schedule | Destination |
|---|---|---|
| Research every new trial signup, find company size and industry, score fit from 1 to 5 | Every weekday at 8 AM | Slack channel for the sales team |
| Check our 50 target accounts for new funding news, leadership hires and job posts in our category | Every Monday at 7 AM | Slack, one message per account with a signal |
| List open deals with no activity in 14 days and draft a follow up note for each | Every Tuesday at 9 AM | Gmail drafts, sent only after approval |
| Enrich new HubSpot contacts missing job title or company website | Every 2 hours | HubSpot update after approval |
| Summarize last week of closed won and closed lost deals with the stated reasons | Every Friday at 4 PM | Notion page for the sales lead |
| Find contacts that bounced or left their company and flag them for cleanup | First day of each month | Google Sheets |
The fastest way to start is the AI lead generation template, which already contains the research, scoring and Slack delivery steps.
A time math example for a small sales team
Hypothetical example, not a measured result. Picture a team of four reps who each spend about 30 minutes every weekday researching new signups and target accounts before outreach. That is 2 hours a day across the team, or roughly 40 hours a month. If a morning cron does the first pass and the reps spend 10 minutes each reviewing the shortlist, research time drops to about 13 hours a month. The numbers in your team will differ, so measure your own baseline for a week before and after.
On run count, a daily weekday cron uses about 22 runs a month, and a two hourly enrichment cron during business hours uses about 110. Both fit comfortably inside Starter.
Controls that keep your CRM clean
Sales data is shared by the whole company, so writes need care. In Crons any step that writes to HubSpot, sends an email to a prospect or posts to a public channel can sit behind an approval gate. The run pauses, the approver sees exactly what would be written, and nothing happens until they approve. Read more in memory and approvals.
- Approval before CRM updates and before any email leaves Gmail
- Full run log with every step, input, output, retry and timing
- Dry run mode to test a new cron without touching HubSpot
- Alerts by email or Slack when a run fails after three retries
- Memory so the same lead is never sent twice
How to set up your first sales cron
- 1Open the homepage demo or your account and type the job in one sentence, for example 'Every weekday at 8 AM research new trial signups and post the best fits to Slack'.
- 2Check the parsed schedule and timezone, then read the steps Crons proposes, such as a HubSpot read, a web fetch per company, an AI scoring step and a Slack message.
- 3Connect HubSpot and Slack once. Credentials are stored per integration and reused by every cron.
- 4Add an approval gate in front of any step that writes to HubSpot or sends email.
- 5Run it in dry run mode, read the output in the run log and tighten the scoring rules in the instruction.
- 6Turn on the schedule. From the next run on, memory makes sure only new leads appear.
Most sales teams start with one research cron, watch it for a week, and then add a stale deal check and a monthly cleanup job once they trust the output.
Which plan fits a sales team
A single founder or one rep running a handful of daily research crons fits Starter, with 10 active crons, 300 runs and 3,000 AI calls a month at $49 per month billed yearly. A sales team of up to five people that wants hourly enrichment every 15 minutes, shared crons with editor and viewer roles and the REST API usually needs Pro at $149 per month billed yearly. Larger teams that need approval rules per team, SSO and a one year run log choose Teams. Compare limits on the pricing page.
Frequently asked questions
Can an AI sales agent send outreach emails by itself?
It can draft them, and sending can require approval. Most teams keep an approval gate on every email to a prospect so a rep reads it before it leaves Gmail.
Does it work with HubSpot?
Yes. Crons reads and writes HubSpot contacts, companies and deals. Writes can wait for approval, and every change is recorded in the run log.
How does the agent avoid sending the same lead twice?
Each cron has memory. It stores which leads it already reported and only delivers new ones on the next run.
Where does the lead research come from?
From the sources you name in the instruction, such as company websites, public job boards, news pages or your own systems through an API. Web fetch and headless browser steps read those pages on each run.
How often can a sales cron run?
Every hour on Starter, every 15 minutes on Pro and every 5 minutes on Teams. Most sales crons run daily or a few times a day.
Can I see why a lead got a certain score?
Yes. The AI reasoning step output is stored in the run log, so you can read the reasoning behind each score and adjust the instruction.