Procurement due-diligence brief for new Ramp vendors

Build me an agent workflow that runs whenever a new vendor is added in Ramp and posts a procurement due-diligence brief to our #procurement Slack channel, so finance has market context before approving any spend with that vendor.

Trigger: poll Ramp for the New Vendor event.

What the agent should do on each new vendor:

1. Use Ramp's Get Vendor to pull the vendor name and the category we recorded in Ramp.

2. Use Ramp Data's Resolve Ramp Rate Vendor Name to canonicalize the vendor name to a Ramp Rate vendor_slug. If the name cannot be resolved with reasonable confidence, skip cleanly without posting anything.

3. Use Ramp Data's Get Ramp Rate Vendor Profile on that slug to pull the vendor's adoption rate, year-over-year adoption growth, dominant FTE segment (e.g. SMB / mid-market / enterprise), and competitor switch rate.

4. Use Ramp Data's Get Ramp Rate Category Vendor Leaderboard for the same category the vendor sits in, and pick the top three alternative vendors ranked by adoption.

5. Use Slack's Send a Message to post a single procurement brief to #procurement (make the channel configurable). The brief should include: the vendor name, where they sit in the category leaderboard, their adoption trend (rate plus YoY growth), the top three alternatives with their adoption rates, and a recommendation flag with one of three values: looks-like-leader, niche-but-growing, or declining-consider-alternatives.

Recommendation logic: looks-like-leader if the vendor is in the top of the category leaderboard with positive YoY growth; niche-but-growing if the vendor is lower on the leaderboard but has strong positive YoY growth and a low or negative competitor switch rate against it; declining-consider-alternatives if YoY growth is meaningfully negative or competitors are pulling switchers away. Keep the thresholds simple and explicit so they're easy to tune later.

Other requirements: keep the Slack message short and scannable (vendor headline first, then a leaderboard line, then alternatives, then the flag). Skip silently and log a note when the vendor cannot be resolved to a Ramp Rate slug, when the category isn't tracked, or when Ramp returns no category for the vendor. Don't post duplicate briefs for the same vendor if the trigger fires twice.