Runner for marketing and growth teams

A campaign report can be perfectly accurate and still be useless. Clicks went up. CPA went down. Great. Did any of it create pipeline? Is one campaign burning through the week’s budget? Is a high-value lead still waiting for a response? Give that job to an AI employee and put it on a schedule.

Writes follow your tool permissions. Keep budget changes, CRM updates, and posts 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 growth

AI employee	What they own	Why the job matters	You stay focused on
Spend watch	Checks campaign results against approved targets and CRM outcomes	Catches waste before month-end	The budget decision
Campaign-to-pipeline review	Matches campaign and CRM records and calls out gaps	Moves the conversation past clicks	Attribution judgment and strategy
Lead aging	Finds marketing leads with no owner or first response	Protects demand you already paid for	Qualification and follow-through
Content delivery	Finds blocked, overdue, or ownerless work	Keeps production moving	Taste and editorial judgment
Weekly growth review	Assembles current metrics, experiments, spend exceptions, and pipeline changes	Starts the meeting with current evidence	What to try next

Each Runner works independently. Runners can read the same source apps, but they don’t pass work or results to one another automatically.

Runner can compare the sources and apply your rules. It shouldn’t invent causality. A metric moving after a campaign launched doesn’t prove the campaign caused it.

Start with: spend watch

Create a Runner named Spend Watch.

Every weekday at 8:00am in my timezone, review campaign performance in
[connected ad source or Google Sheet], our approved targets in [Google Sheet],
and pipeline outcomes in [HubSpot or Salesforce].

Only include a campaign when one of these is true:
- daily spend is more than 20% above its approved pace
- cost per qualified lead is more than 20% above target
- spend increased but the connected CRM shows no matching qualified leads
- required campaign or source data is missing

For each exception, show campaign, spend, target, variance, qualified leads or
pipeline shown in the CRM, and the exact source period. Separate facts from
possible explanations. Don't claim why a metric changed unless a source says it.

Recommend one thing for a person to inspect. Don't change budgets, pause ads,
post messages, or update the CRM. Draft a short team summary for my review.
If nothing is outside the rules, say that clearly and stop.

Before you create the Runner, show me the final name, prompt, schedule, and
timezone. Wait for my confirmation.

A user-created Runner becomes active as soon as it’s created. Review its schedule and permissions, then click Run now. Twenty percent is an example. Use a threshold your team already trusts.

Add the definitions

Use a marketing Project for shared background:

Where the current numbers live.
What your team means by a qualified lead or pipeline opportunity.
Naming conventions for channels and campaigns.

Put approved targets, thresholds, reporting windows, timezone, and prohibited changes in the saved prompt. Use Ask or Off for changes that must wait for a person. The ad source, CRM, and reporting sheet hold the live numbers. Previous run output doesn’t carry forward automatically. Run the first few checks with writes on Ask. If the same false positive appears twice, fix the rule in the saved prompt. Don’t just correct one session and hope the next run knows.

Other jobs to schedule

Campaign-to-pipeline review

Run Monday morning. Match campaign and lead records using the identifiers your data actually provides. Show matched pipeline, unmatched records, and missing fields. Don’t turn correlation into attribution.

Lead aging check

Run each weekday morning. Find new marketing leads with no owner or first response, then stage an alert or CRM update. Stop when the source record shows the lead is handled.

Content bottleneck check

Run each weekday morning. Find content due in the next seven days with no owner, blocked status, or overdue dependency. Draft the nudge, then let a person decide what moves.

Weekly growth review

Run Friday afternoon. Pull the approved metrics, current experiments, spend exceptions, and pipeline changes into one short report. Flag missing data instead of smoothing over it.

A report isn’t the outcome

The goal is to catch wasted spend early, follow up on demand, and start the team meeting with current evidence instead of rebuilding the report.

What’s next?

Sales and RevOps

Follow demand from first response to next step.

Which AI employee should you add next?

Find the next job tied to spend, pipeline, or time.

Tool permissions

Keep budget and CRM changes behind review.

Start here

By role

Runner for marketing and growth teams

Recurring jobs for growth

Start with: spend watch

Add the definitions

Other jobs to schedule

Campaign-to-pipeline review

Lead aging check

Content bottleneck check

Weekly growth review

A report isn’t the outcome

What’s next?

Sales and RevOps

Which AI employee should you add next?

Tool permissions

​Recurring jobs for growth

​Start with: spend watch

​Add the definitions

​Other jobs to schedule

​Campaign-to-pipeline review

​Lead aging check

​Content bottleneck check

​Weekly growth review

​A report isn’t the outcome

​What’s next?

Sales and RevOps

Which AI employee should you add next?

Tool permissions

Recurring jobs for growth

Start with: spend watch

Add the definitions

Other jobs to schedule

Campaign-to-pipeline review

Lead aging check

Content bottleneck check

Weekly growth review

A report isn’t the outcome

What’s next?