Weekly Industry Report

What this bot does

Every Monday morning, this bot produces a longer, more considered report on an industry you care about, then emails it out. It is the “step up” from the daily news digest: fewer items, more context, more analysis.

Soul

You are a senior industry analyst who produces weekly reports on the
enterprise software market for a founder audience.

Every report you produce must:
- Cover the week in review, not just the last 24 hours
- Group items into clear themes rather than a flat list
- Identify the one most consequential move of the week and say why
- Cite a source URL for every factual claim

Never:
- Repeat what you covered in prior weeks without a reason
- Include speculation beyond what sources support
- Use hype language

Tasks

Stage 1, research (WebSearch attached)

• Task A: Funding and M&A. “Find the most significant enterprise software funding rounds and acquisitions from the past 7 days. Return each as a bullet with company, amount or deal, one-sentence summary, and source URL.”
• Task B: Product and platform news. “Find the most significant product and platform announcements from major enterprise software companies in the past 7 days. Return each as a bullet with company, announcement, one-sentence summary, and source URL.”
• Task C: Market signals. “Find notable hiring moves, earnings commentary, and regulatory shifts that affected enterprise software in the past 7 days. Return each as a bullet with the signal, one-sentence summary, and source URL.”

Stage 2, synthesise (no tools)

• Task D: Theme. “Read the inputs from stage 1. Identify 2 to 4 themes that connect the items across funding, product news, and market signals. Name each theme and list which items belong to it.”
• Task E: Call the week. “Pick the single most consequential move of the week and explain, in two or three sentences, why it matters for a founder.”

Stage 3, write (no tools)

• Task F: Compose. “Write the weekly report using the themes from task D and the lead from task E. Output HTML for an email body: <h2> for the week ending date, <h3> for each theme, <ul> and <li> for items, and a ‘Call of the week’ section at the top containing task E’s output. Stay under 800 words.”

Stage 4, send (SendEmail attached)

• Task G: Deliver. “Send the HTML report from task F to the address in input data with the subject Enterprise software weekly, week ending [date].”

Input data

{
  "recipient_email": "you@example.com"
}

Schedule

Recurring, weekly, interval 1, days: Mon. Start at next Monday 07:30 in your timezone.

What to tune

• If the themes feel generic, ask task D to name at least one theme that is surprising or counterintuitive.
• If the “call of the week” flip-flops each run, tighten the criteria in task E’s prompt.
• If the report is dense, ask task F to open each theme with a plain-English one-liner before the bullets.