Skip to main content
A $25,000 proposal goes out Tuesday. Friday arrives. Everyone assumes someone followed up. Nobody did. That’s the kind of job an AI employee should own. Not writing another generic email on command. Checking the real pipeline every morning, finding the proposal that went quiet, reading the thread, and preparing the right next step. For agencies, consultancies, studios, and development shops, the first AI employees should sit close to revenue or client delivery.
Writes follow your tool permissions. Keep email sending on Ask while you test. Runner stages each send as an Action Card for review. Allow sends without asking. Off blocks the tool unless the Runner has its own override.

​
Recurring jobs for professional services

Each Runner works independently. Runners can read the same source apps, but they don’t pass work or results to one another automatically.
You don’t need all five AI employees. Add the one with the clearest number attached.

​
Start with: proposal follow-up

This works because the state already lives in Gmail and your CRM. Every run can see who replied, what was promised, and whether the opportunity is still open.
A user-created Runner becomes active as soon as it’s created. Open it, review the saved prompt and schedule, then click Run now for the first test. Turn on Carry unresolved Action Cards into new runs so a still-pending follow-up can appear in the next run. A pending card still expires 24 hours after it was staged.

​
Save the job rules

Use a Project for background such as your offer, audience, account owners, and source locations. Put these in the Runner’s saved prompt:
  • The voice to use with prospects.
  • Deal stages and exclusion rules.
  • The minimum gap between follow-ups.
  • What needs a partner or account owner to review.
Keep the live state in Gmail and the CRM. That’s what tells tomorrow’s run whether the client replied. The previous run’s output doesn’t carry forward automatically. Start sends on Ask. Read the first ten Action Cards. Fix the saved prompt when you see the same mistake twice. Move a send tool to Allow only when you’re comfortable letting that exact action happen without review.

​
Other jobs to schedule

​
New lead response

Run at the start and end of each workday. Find new inquiries with no owner or first reply, read the account context from connected sources, and stage a response. Stop when the CRM or email thread shows someone already handled it.

​
Client onboarding

Run each weekday morning. Find newly won work, then prepare the welcome email, kickoff checklist, and list of missing inputs. Keep contract, payment, and scope decisions with a person.

​
Delivery risk

Run before the team starts work. Find deliverables due in the next seven days, blocked tasks, and client questions waiting more than two business days. Draft the nudge and name the owner.

​
Weekly account review

Run Friday afternoon. Pull what shipped, what slipped, open client questions, and the next milestone into a clean account summary. No green status based on vibes. Use the work and messages that actually exist.

​
The point isn’t more activity

A proposal follow-up Runner isn’t valuable because it writes five emails. Measure how often a proposal waits ten days without a next step. Fix that gap, then build the next Runner.

​
What’s next?

Create a Runner

Save the job, schedule, sources, and review rules.

Sales and RevOps

Go deeper on lead response, pipeline gaps, and next steps.

Tool permissions

Decide which actions wait for review.