Skip to main content
A full pipeline can still be a dead pipeline. The problem usually isn’t the number of records. It’s the gaps: a new lead with no reply, a proposal with no follow-up, a deal with no next step, or a renewal nobody owns. Those gaps repeat every week. They are good jobs for AI employees.
Writes follow your tool permissions. Keep CRM updates and email sending on Ask while you test. Runner stages each write as an Action Card. Allow acts without asking. Off blocks the tool unless the Runner has its own override.

​
Recurring jobs for revenue

Each Runner works independently. Runners can read the same source apps, but they don’t pass work or results to one another automatically.
Don’t build one AI employee to “do sales.” Give them one gap you can see and measure. The 8am and 4pm lead check uses more of your plan. Start with the morning check until the second one is worth the cost.

​
Start with: pipeline inspection

A user-created Runner becomes active as soon as it’s created. Review its schedule and permissions, then click Run now. The result should be small enough to act on. Ten real gaps beat a 60-page pipeline export.

​
Keep the sources reliable

Use a sales Project for background such as the ideal customer, deal-stage names, ownership, product facts, and source locations. Put disqualifiers, stage requirements, follow-up timing, do-not-contact rules, approved claims, and pricing boundaries in the saved prompt. Keep deal status in the CRM and conversation status in email. The next run reads those sources again. It doesn’t automatically receive the previous run’s output. Start with writes on Ask. Review the first ten email and CRM Action Cards. If a rule keeps needing correction, change the saved prompt. Don’t leave the fix in one run’s session.

​
Other jobs to schedule

​
New lead response

Run at the start and end of each workday. Find new inbound leads with no owner or reply, read the available company and CRM context, and stage a short first response. Stop as soon as the record or thread shows somebody handled it.

​
Proposal follow-up

Run each weekday morning. Check proposals sent 3 to 14 business days ago. Draft the next message only when the client hasn’t replied and the opportunity is still open.

​
Renewal watch

Run twice a week. Find renewals in the next 60 days, then gather recent email, open issues, usage data that is actually connected, and the named owner. Surface missing plans early.

​
Weekly sales report

Run Friday afternoon. Pull what changed from the CRM, not from memory. Show won, lost, slipped, stale, and missing data. Keep forecast judgment with the sales owner.

​
Measure the gap, not the output

Don’t count how many emails Runner drafted. Count leads that got a first response, proposals that received a next step, and open deals that stopped sitting without an owner. That’s the revenue work.

​
What’s next?

Professional services

Build proposal follow-up and client onboarding Runners.

Connect your apps

Link your CRM and Gmail, then review their tools.

Create a Runner

Save the check, schedule, and review boundary.