New Ramp vendor procurement brief in Slack

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.

Additional information

What does this prompt do?

Watches Ramp for newly added vendors and kicks off a procurement review automatically.
Pulls the vendor's adoption rate, year-over-year growth, dominant team segment, and competitor switch rate from Ramp Rate market data.
Lists the top alternatives in the same category, ranked by how widely they're adopted.
Posts a one-glance brief to your procurement Slack channel with a clear recommendation flag: looks like a leader, niche but growing, or declining.

What do I need to use this?

A Ramp account with permission to read vendors.
A Ramp Rate connection for benchmarking new vendors against the broader market.
A Slack workspace and the channel where you want procurement briefs to land (for example, #procurement).

How can I customize it?

Change the destination Slack channel, or route different vendor categories to different channels.
Adjust the recommendation thresholds (what counts as a leader, what counts as declining) to match your procurement policy.
Add or remove fields in the brief, like spend benchmarks, dominant team segment, or a link back to the vendor in Ramp.

Frequently asked questions

What happens if the new vendor isn't a recognized software vendor?

If the vendor name can't be matched against Ramp Rate's catalog, the workflow exits cleanly without posting noise. You'll only get a brief for vendors with real market data behind them.

Will this fire on every vendor, including one-off contractors?

It runs on every new vendor added in Ramp, but skips quietly when there's no market profile to summarize. You can also narrow the trigger by category if you only care about software spend.

Can I send the brief somewhere other than Slack?

Yes. The brief is just a formatted message, so you can switch the destination to a different channel, a DM to your procurement lead, or a different tool entirely.

How quickly does the brief arrive after a vendor is added?

It runs on a short polling loop, so finance usually has the brief in hand within a few minutes of the vendor being created in Ramp, well before approvals start.

What's the recommendation flag based on?

It looks at where the vendor sits on the category leaderboard, its adoption trend, and how often customers switch to or away from it, then summarizes that into a simple leader, niche-but-growing, or declining call you can sanity check.