How to Use Ramp Spend Controls to Stop Shadow SaaS

November 2, 2026

Shadow SaaS is software bought outside anyone’s budget — usually a $49/month tool on someone’s card, renewed for two years. Ramp catches it because card charges are visible at transaction level: merchant category blocks, virtual cards per vendor, and a spend-by-merchant view that surfaces duplicates. The controls work; the process around them is what keeps it fixed.

Start with the money view. You can’t block what you haven’t measured.

How do you find shadow SaaS on a card program?

Ramp’s Spend → Merchants view groups every transaction by merchant across all cards. Filter to the last 12 months and sort by total spend. What you’re looking for:

  • Duplicate vendors doing the same job (Notion and Coda, Zoom and Google Meet add-ons, three different AI writing tools).
  • SaaS merchants charged to travel or marketing policies where they don’t belong.
  • Recurring charges under your receipt threshold — $19/month tools slip past review because they’re never flagged.

The last category is where most leakage lives. Set the receipt threshold at $50 and a $29 subscription rides free forever.

Step 1: virtual cards per vendor, one subscription each

The single most effective control isn’t a rule, it’s card structure. Every recurring vendor gets its own virtual card with a spend limit equal to the expected annual price.

Consequences: a price increase fails the limit and alerts you; a subscription you cancelled fails on renewal instead of charging silently; and when someone offboards, their vendor cards get frozen in one click instead of surfacing as a charge on a shared card nobody recognises.

ramp lets you create a virtual card in about fifteen seconds and attach it to a policy. Doing this for your twenty biggest vendors takes half an hour.

Step 2: block merchant categories, don’t police them

Policies support merchant category restrictions. Useful blocks for most companies:

Policy type Block
IC software travel, hardware, cash withdrawal, gambling
Contractor hardware, food delivery
Manager cash withdrawal, crypto

Category blocking is coarse — a combined “office supplies and electronics” merchant category will sometimes block something legitimate. Expect two or three false positives in the first month and handle them by exception, not by loosening the rule.

Step 3: require a memo at the transaction, not a report later

Ramp lets you require a memo before a transaction is considered complete. Turn it on for anything above $100. A memo of “what is this for and which team” at the moment of spending produces accurate data; the same question asked 40 days later produces “client stuff”.

On the Plus tier you can enforce this as a hard requirement on specific policies. Without enforcement, it decays within six weeks.

Step 4: build the renewal calendar from the spend data

Once virtual cards per vendor are in place, the renewal date is roughly predictable from the charge pattern. Export the merchant list monthly into a sheet with: vendor, monthly cost, annualised cost, owner, renewal month.

The owner column is the part that changes behaviour. Unowned software gets renewed; owned software gets reviewed.

What does the review loop look like in practice?

A quarterly hour with finance and IT:

  1. Sort this quarter’s SaaS spend by annualised cost.
  2. For each vendor above $1,000/year, the named owner says what it does and who uses it.
  3. Anything without an owner gets cancelled at renewal — not frozen, cancelled, so the decision has to be made again deliberately.
  4. Duplicate-function vendors: pick one, set a sunset date for the other.

Four steps, one hour, four times a year. The tools exist to make those steps take an hour instead of a week.

Where this gets annoying

Engineering teams that need to spin up vendor tools fast will hit limit failures while a policy change is pending, which reads as the finance team being obstructive. Plan for a fast path: a pre-approved list of merchant categories and a named approver with same-day turnaround.

Ramp’s controls are also weak against personal-card-then-reimburse behaviour. If your team can still file an expense report for a personal purchase, that’s the actual leak and no card control closes it.

Who should bother

Companies above about 40 people spending over $5,000/month on SaaS. Below that, the leakage is real but small, and a monthly spreadsheet review catches it without any tooling. Above 200 people, you’ll want a dedicated SaaS management platform alongside — Ramp shows you the card charges, not the unapproved seats inside a licensed app.

Quick Summary

  • Spend → Merchants view surfaces duplicate tools and recurring charges under your receipt threshold.
  • One virtual card per vendor, limit set to expected annual price — price rises and forgotten renewals fail loudly.
  • Block merchant categories per policy instead of policing spending after the fact.
  • Require memos above $100 at the transaction, not in a report later.
  • Quarterly owner review for anything over $1,000/year; unowned software gets cancelled, not frozen.
Tags: