- Industry
- Procure AI
- Department
- Marketing
- Team
- Demand Generation
- Kind
- Decision-maker
- Approver
- Marketing Lead
- Code
- MKT-01
It plans cross-channel campaigns aimed at chief procurement officers, finance directors and heads of shared services, and proposes budget shifts between search, professional social, trade media and review sites from their cost per sales-accepted lead and pipeline per dollar. It stays within the monthly budget and pacing rules and pushes the approved budgets and campaign statuses to the ad accounts.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the ad accounts' reporting: spend, clicks and conversions by campaign, joined with sales-accepted leads and pipeline from the CRM..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Marketing Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the ad accounts' campaign manager: it updates campaign budgets and statuses. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The demand plan: target accounts and buying committees for managed procurement services, channel benchmarks for cost per sales-accepted lead, the monthly budget and pacing rules and the claims rules for savings figures.
Reads from
the ad accounts' reporting: spend, clicks and conversions by campaign, joined with sales-accepted leads and pipeline from the CRM.
Acts in
the ad accounts' campaign manager: it updates campaign budgets and statuses.
Hands back
An object with period, channels (a list with channel, current_budget, proposed_budget, pipeline_per_dollar and reason), total_planned, campaign_changes (a list with campaign, change and reason) and within_cap (true or false).
Asks a person when
The proposal moves more than 20 percent of any channel's budget, raises total planned spend, launches a new campaign, or pauses a campaign while off is false.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Monthly paid media budget (USD) | 60000 | Planned spend never exceeds this. |
| Largest budget shift per channel (%) | 20 | A larger move needs the approver. |
| Target pipeline per dollar of spend | 15 | Pipeline value expected per dollar spent, given long service-contract sales cycles. |
| Lookback window (days) | 60 | Long enough for a procurement buyer to move from click to sales-accepted lead. |
| Spend before a campaign is judged (USD) | 2000 | Campaigns below this are not cut. |
| Allow pausing campaigns | Off | When off, a pause is proposed, never applied. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Keep total planned spend within 60000.
- Judge campaigns on pipeline per dollar against 15 over 60 days, not on clicks or raw leads.
- Never cut a campaign that has spent less than 2000.
- Move at most 20 percent of a channel's budget at once.
- Ad copy states savings figures only from client-validated case studies, labelled as typical or as one client's result.
- Pause only when off is true; otherwise propose the pause.
See the Advertising Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.