When should you use it?
- You manage LinkedIn Ads for clients or your own company and write a status update every week
- Pipeline targets matter more to the reader than click metrics
- You want early warning when an ad starts to wear out
Not for: Accounts with too little spend for weekly changes to mean anything; Teams that cannot export or connect their ad and CRM data; Final budget decisions; the report points to problems, a person decides
What do you need, and what do you get?
You need
- A weekly export or connection for LinkedIn Ads results at campaign, ad set and ad level
- Pipeline targets and the CRM figures you count as sourced or influenced
- Your task list for the account, from a project tool or a simple sheet
- A Google Doc or folder where the report should go
You get
- A pacing table comparing pipeline and platform metrics with targets
- A ranked list of the ads, ad sets, campaigns and audiences trailing their targets
- A creative fatigue section naming ads whose landing page click-through keeps falling
- A short summary of work completed this week and planned for the coming month
How does it work, step by step?
- Agree the targetsWrite down the pipeline goals and the platform metrics you report on, with their target values.
- Collect the dataExport or connect the weekly ad results, CRM pipeline numbers and the account's task list.
- Write the report promptUse our prompt below and save it as a reusable Claude project or skill.
- Check the first reportsCompare a few figures with the ad platform and CRM before trusting the numbers.
- Schedule itOnce the numbers hold up, run it at the same time every week and send it to the shared doc.
The prompt
Our own prompt, inspired by Patrick Cumming and written to work in Claude, Claude Code and Claude Cowork. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You prepare the weekly LinkedIn Ads update for {client}. Use only the files I provide: ad results for {week} at campaign, ad set and ad level ({ads_export}), pipeline figures from {crm_export}, and tasks from {task_list}. 1. Pacing: compare pipeline against the program and influenced pipeline goals, then conversions, cost per landing page click, reach, frequency and CPM, with these targets: {targets}. Show the gap and whether we are on track for {period_end}. 2. Problems: rank the ads, ad sets, campaigns and audiences that trail their targets, with the numbers that show it. Note when spend is too small to judge. 3. Fatigue: name any ad whose landing page click-through rate dropped for two or more weeks running, with its frequency. 4. Work: list tasks finished this week and those due in the next four weeks. Keep it under one page, quote figures exactly, and recommend actions without making any changes.
Inspired by Patrick Cumming: LinkedIn post: five AI automations running a one-person LinkedIn Ads agency. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Influenced pipeline depends on your attribution rules. State them in the prompt so the figure means the same thing each week.
- Week-over-week swings on small budgets are noise. Ask the report to note sample size before flagging a drop.
- A falling click-through rate can come from audience saturation, not the creative. Check frequency before swapping ads.
- Never let the report pause or change campaigns. Keep it read-only.
Our take
Reporting is where paid media time disappears, especially for a solo operator with several clients. Cumming's report is useful because it starts from what a client actually cares about, progress against pipeline goals, and only then drops into platform metrics such as conversions, cost per landing page click and reach and frequency. The creative fatigue check is the part we would copy first: a steady fall in landing page click-through on one ad is easy to miss in a dashboard and cheap for a model to catch. Adding the account's finished and upcoming tasks turns a metrics dump into a status update a client can read in two minutes. Our cautions: define how influenced pipeline is counted before automating it, check the first few reports against the source systems, and keep the report read-only so it never touches budgets. In our dry run with fictional exports for a software client, the report showed program pipeline at 62% of the quarterly target with five weeks left, flagged one audience with a cost per click 40% above the rest, and named two ads whose click-through had fallen three weeks in a row.
Where the time goes back: The weekly status write-up, usually an hour or more per account of copying numbers and spotting trends, becomes a draft you check, and fading ads get flagged before they waste a month of budget.
FAQ
Does Claude connect to LinkedIn Ads directly?
How long did it take him?
Can it make the monthly version too?
Source and credit
Inspired by Patrick Cumming. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- LinkedIn post: five AI automations running a one-person LinkedIn Ads agency
- Creator
- Patrick Cumming
- Published on
- Original date
- Nov 2, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Nov 3, 2026: passed. Dry-run tested by our AI test agent on sample input. Correct pacing math, flagged the costly audience and both fading ads, task summary included, read-only.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 3, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.