Skip to main content
Think like you’re hiring. If you could add one great AI employee tomorrow, which job would you give them? The proposal follow-up nobody owns? The invoice check you rebuild every Friday? The morning plan that keeps your day from getting away from you? Runner lets you build your fleet one job at a time. You still talk to Runner. That’s how you describe the job, check the work, and improve the Runner. Every AI employee needs one clear, valuable job.
Writes follow your tool permissions. Ask stages an Action Card for review. Allow acts without asking. Off blocks the tool unless a user-created Runner has its own override.

​
Start with a number

Look for work tied to one of these: A 45-minute task done five days a week takes 195 hours a year. A forgotten 200monthlysubscriptioncosts200 monthly subscription costs 2,400 a year. You don’t need perfect math. You need enough of a number to rank this work against everything else.

​
Sketch your fleet

​
Jobs that protect revenue

  • Check each weekday for proposals still waiting on a reply.
  • Check the CRM for new leads with no first response.
  • Find open deals with no next step or no activity in seven days.
  • Surface renewals and customer risks before the deadline.
  • Draft the right follow-up from the email thread, CRM record, and proposal.

​
Jobs that cut costs

  • Match incoming invoices against signed agreements.
  • Flag renewals, recurring charges, and spend that changed unexpectedly.
  • Find campaigns spending above your target without producing pipeline.
  • Catch duplicate work across teams before another person does it again.
  • Assemble recurring reports without spending another afternoon copying numbers between apps.

​
Jobs that keep delivery moving

  • Turn a signed proposal or order form into an onboarding checklist.
  • Find projects waiting on a client, owner, or approval.
  • Draft weekly client updates from the work that actually happened.
  • Prepare meeting briefs, then draft a decision log from the owners and dates people agreed.
  • Check that every commitment has an owner and date.
Why these? They repeat, they cross several apps, and missing them costs you something.

​
Jobs that give time back

Personal work is often the easiest place to start. The stakes are lower and the pattern is obvious.
  • A morning plan built from Gmail and Google Calendar.
  • A daily check for messages and commitments waiting on you.
  • A Sunday preview of family events, appointments, and bills.
  • A monthly subscription and renewal review.
  • Meeting prep before the first call of the day.
Once one of these works, use the same pattern on a business process with a bigger number attached.

​
Write the job description

  1. One job. Not “help with sales.” Try “find proposals waiting more than three business days for a reply.”
  2. Named sources. Gmail, HubSpot, a Google Sheet, a Drive folder, or a site in the browser.
  3. A schedule. Every weekday at 8am. Friday at 4pm. The first day of each month.
  4. Rules and limits. Who to include, what to ignore, and when to stop.
  5. A result and review point. A ranked list, a drafted follow-up, an updated record, or an Action Card waiting for approval.
  6. Human work. The judgment, relationship, creative choice, or final decision that stays with a person.
If you can’t describe the outcome and the stop condition, the job isn’t ready for a Runner yet. More runs use more of your plan. Start daily. Increase the frequency only when the number attached to the work justifies it.

​
Ask Runner to help you choose

Use this when you need help but don’t know which job to start with:
This is where chat belongs. It helps you turn a fuzzy problem into a clear job.

​
Runner, Workflow, or one-off?

  • Build a Runner when you want an AI employee to own the job on a schedule.
  • Save a Workflow when you want a reusable playbook that you start with /slug.
  • Keep it in one session when the work truly happens once.
If a job is tied to real revenue or cost and should happen on a schedule, give it to a Runner.

​
Give the first Runner a durable brief

Once you’ve picked the job, give the Runner the details that shouldn’t change:
A durable Runner keeps its saved prompt, schedule, timezone, Project, intelligence setting, and any Runner-specific permission overrides. Each run still starts in a separate session. Previous run output doesn’t carry automatically. Put standing business rules in the saved prompt. Use Project context for shared background. Save durable personal facts and preferences to Personal Memory. Keep live status in the source app, such as your CRM, inbox, or tracking sheet, so the next run can read it again.
A user-created Runner becomes active as soon as it’s created. Review its schedule and tool permissions before you confirm.

​
Add one Runner at a time

Don’t begin with “run my company.” Add one Runner with one job, one schedule, and one clear result. Review the first three runs and fix the saved prompt when the same problem appears again. Once the result is useful and consistent, add the next job. Three useful Runners beat a sidebar full of clever prompts.

​
What’s next?

See AI employees by role

See the jobs that can protect revenue, remove cost, and save time.

Create a Runner

Give one job a schedule, sources, rules, and tool permissions.

Build a Personal Assistant

Start with a Personal Assistant, Gmail, Calendar, and a useful 9am plan.