Every Monday, emails you the week's industry news read against your business: what happened, why it matters to you and what to do.
Uses
Claude
Gmail
Perplexity
Get a weekly briefing on what your industry's news means for you
industry to B2B spend management and accounts payable software.Set industry to B2B spend management and accounts payable software.businessContext to blank.Set businessContext to blank.recipientEmail to blank.Set recipientEmail to blank.industry
Only report things that actually happened in the last 7 days. Cover funding rounds and acquisitions, product and feature launches, pricing and packaging changes, regulatory or policy changes, notable hires and departures, outages and security incidents, published market or analyst data, and anything else that materially changes how companies in this industry compete.
Give each item as a single line: what happened, who it involves, the date, and the source URL.
List 8 to 15 items, most consequential first. Skip opinion pieces, listicles, sponsored posts, SEO filler and anything you cannot attach a real source URL to. If the week was genuinely quiet, return fewer items rather than padding the list. Report only; no analysis and no recommendations.'. Save it as research.research.response_text and save it as researchText.Trim research.response_text and save it as researchText.researchText is emptyIf researchText is emptyYes
No
No steps
businessContext
INDUSTRY
industry
THIS WEEK'S NEWS
researchText
Every line you write has to answer 'so what for us'. Drop anything in the news list that has no bearing on this business, however large the headline, and never restate a headline without saying what it changes for us. If the week was quiet, say so in one line and keep the briefing short; a short honest briefing is worth far more than a padded one.
Structure it exactly like this, in Markdown:
1. Open with two or three sentences saying what mattered most this week and what, if anything, the team should do about it. Do not put a heading above this opening paragraph.
2. Then one section per theme that earned one, at most four, each introduced by a '## ' heading. Useful section names look like 'What changed for our buyers', 'Competitive moves', 'Regulation and policy', 'Signals worth watching'.
3. Inside a section, one '- ' bullet per item: what happened, then why it matters to us, then the source as [publication](url).
4. Finish with a '## What we would do about it' section holding at most three bullets, each a concrete next step and who would own it.
Formatting rules, which matter because this goes straight into an email: use '## ' for every heading and never '#' or '###'; use '- ' for every bullet and never nest one bullet under another; write links as [text](url) and never as bare URLs; keep the whole briefing under 600 words.'. Save it as report.
Maximum response length: 2000report.response_text and save it as reportText.Trim report.response_text and save it as reportText.reportText is emptyIf reportText is emptyYes
No
No steps
]( with ( in reportText and save it as reportOpenLinks.Replace ]( with ( in reportText and save it as reportOpenLinks.[ with in reportOpenLinks and save it as reportPlainLinks.Replace [ with in reportOpenLinks and save it as reportPlainLinks.** with in reportPlainLinks and save it as reportUnbolded.Replace ** with in reportPlainLinks and save it as reportUnbolded.
- with
• in reportUnbolded and save it as reportBulleted.reportBulleted by "Split reportBulleted by
## and save it as reportSections.reportSections with "Join reportSections with
──────────────────────────────
and save it as emailBody.weekOf.Make today's date readable as “November 2, 2026” and save it as weekOf.recipientEmail.Send an email to recipientEmail.
Subject: Weekly industry update: industry, weekOfemailBody