Weekly competitive radar in Slack from Ramp spend data

Build me a weekly competitive radar that runs on a cron schedule every Monday at 8am America/New_York. The trigger is purely time-based, no other inputs.

Configurable inputs for the workflow:

1) category_slug — the Ramp Rate software category we compete in (for example crm or marketing-automation). 2) our_vendor_name — our company name as it would appear in the leaderboard (for example HubSpot). 3) slack_channel — the channel ID or name to post into (default #competitive). 4) competitor_count — how many top competitors to profile alongside us (default 3).

Each Monday the agent should do the following with the Ramp Data integration (no auth, public dataset):

Step 1: Resolve our_vendor_name to a canonical vendor slug using Resolve Ramp Rate Vendor Name. If the resolver returns nothing, post a short Slack message to slack_channel saying the radar could not identify our vendor and stop.

Step 2: Call Get Ramp Rate Category Summary for category_slug to get overall adoption and growth context for the category.

Step 3: Call Get Ramp Rate Category Vendor Leaderboard for category_slug. Read the ranked list and identify (a) our current rank, (b) the top competitor_count vendors that are not us, (c) any vendor whose rank shifted notably versus the previous run (the agent should remember last week's leaderboard between runs).

Step 4: Call Get Ramp Rate Vendor Profile once for our vendor and once for each of the top competitor_count competitors. From each profile capture adoption rate, year-over-year growth, new adopter share, and competitor switch-in / switch-out rate.

Step 5: Compose an analyst-brief Slack message and post it to slack_channel using Slack — Send a Message. The message must:

• Lead with a single one-sentence headline calling out the most important shift this week (a leaderboard move, a competitor with surging new-adopter share, our switch-in rate inflecting up or down, or a category-level growth turn). • Then a short Where We Stand line: our rank, our adoption rate, and our YoY growth versus the category. • Then a Movers section: who climbed or fell on the leaderboard since last run, with the size of the move. • Then a Momentum section: which competitor has the strongest new-adopter share right now and whether ours is rising or falling. • Then a Switch flow line: is our switch-in rate trending up or down, and which competitor we are pulling from or losing to most. Keep the tone tight and analyst-like, no marketing fluff, no emojis beyond at most one in the headline, no hedging language.

Persist the leaderboard snapshot between runs so the next Monday's message can compare against it. On the very first run, skip the week-over-week comparison sections and note that this is the baseline.

Handle empty data gracefully: if any Ramp Data response comes back with an empty data array, post a short message to slack_channel saying the radar found no rows for that category this week and skip the rest of the brief.