When does an AI agent use this pattern?

When the trigger described above matches the situation the agent is handling. The agent queries FusedFrames at runtime, this pattern is returned and the agent follows the recorded reasoning and steps to reach the recorded outcome.

How were the steps captured?

By the desktop app on the machine of someone who actually does this work. It records clicks, keystrokes, copy and paste, drag and drop, selected text and screen regions across Ramp and NetSuite, then groups them into the meaningful steps shown above.

Where does the reasoning come from?

From the operator. When the desktop app sees a decision the action alone cannot explain, it asks why in the moment. The operator's answer is recorded and becomes the reasoning attached to the pattern, so the AI agent gets the thinking and not just the steps.

What if my team handles this differently?

Capture how your team actually does it. The desktop app records what your operator does on your tools and the web app distills that into a pattern shaped by your team. Each team's library reflects their own approach rather than the example shown here.

What if a case looks like this pattern but does not quite fit?

The pattern is linked to 1 alternative. The agent can follow the connections shown on this page to a related pattern that matches the case more closely.

How does my AI agent actually call this pattern?

Through the read-only REST API or the npm CLI. Create an API key in the dashboard, choose whether it accesses all libraries or specific ones and have your agent query at runtime. The response is structured JSON ready for tool use.

Is the data shown on this page from a live customer?

No. Example libraries on this site are illustrative. Patterns in your own account are built from your team's captured actions and stay private to your workspace.

How do I build a pattern like this for my team?

Install the desktop app on the machine of the person who already does this work, ask them to handle a real case end to end, then distill the captured action into a pattern in the web app. The pattern you end up with mirrors how your team actually operates.

Provisioning a Ramp virtual card for a SaaS vendor with a monthly cap

When a new SaaS subscription is approved, the spend operations lead provisions a Ramp virtual card with a monthly cap set at 110% of the contracted fee. The card carries the right GL code, the contract attachment and a domain lock so it cannot be used elsewhere.

Tags

virtual-cardsaasrampcapvendor-managementrenewal

Lets your agent filter to the right pattern

Categories and tags scope the retrieval set, so your agent receives only the patterns relevant to the task instead of scanning the full library.

What and why

The observed behaviour and the reasoning behind it.

Behaviour

When a new SaaS subscription is approved, the spend operations lead provisions a Ramp virtual card with a monthly cap set at 110% of the contracted monthly fee, GL code pre-filled to GL 6610 Software & SaaS, the contract PDF attached and the vendor name normalised to the legal entity name. The card is locked to the vendor's domain so it cannot be used elsewhere.

Reasoning

SaaS vendors quietly raise prices and bill above the contracted amount more often than any other vendor category. A 110% cap absorbs annual price increases that fall within the first month of renewal without breaking the card, but blocks the larger surprises that need a renegotiation conversation before payment. Locking the card to the vendor domain prevents accidental use on other subscriptions and surfaces any unauthorised attempt as a clean reject in the inbox rather than a quiet success.

Gives your agent an operator's reasoning

Behaviour records the action; reasoning records the rationale. Your agent applies both to handle cases that diverge from the captured examples.

Cause and effect

What initiates this pattern and what it produces.

Trigger

A new SaaS subscription has been approved and the contracted monthly fee, vendor and renewal date are confirmed.

Outcome

A Ramp virtual card is live with the right vendor lock, monthly cap, GL pre-fill and contract attachment, ready for the vendor to charge against. The first transaction will route automatically to the right approval inbox with the right GL code, and any unexpected price increase above 10% is blocked and surfaced for renegotiation.

Tells your agent when to act and what to verify

Your agent stays within the scope set by the trigger and outcome, so it doesn't extend beyond the work or finish before the outcome is met.

Standard operating procedure

Step-by-step instructions to reproduce this pattern.

Ramp

Click New Card and choose Virtual subscription card.

Virtual subscription card, not Virtual purchase card. Subscription cards have the recurring-charge flag on by default which fixes the auto-decline behaviour Ramp uses for one-off purchases. Purchase cards decline recurring charges as suspected duplicates and the card has to be replaced after a month.

Expected: The new card creation pane is open in subscription mode.

Ramp

Enter the vendor name as the legal entity name from the contract, not the trading name from the marketing site.

Vendors trade as snappy names but contract under longer legal entity names. The legal entity matches what shows up on the merchant string after the first charge; trading-name cards have to be rematched after charge one. The contract PDF carries the legal name on page one. Use that exactly.

Expected: Vendor name on the card is the legal entity name from the contract.

Ramp

Set the monthly cap to 110% of the contracted monthly fee, rounded up to the nearest dollar.

110% absorbs annual price increases that land in the first renewal month without breaking the card, but surfaces the larger surprises that need a renegotiation. Rounding up to the nearest dollar keeps the cap clean and gives one-dollar headroom for currency conversion noise on cards billed in non-USD currencies.

Expected: The monthly cap is 110% of contracted, rounded up to the nearest dollar.

Ramp

Lock the card to the vendor's domain by adding the domain to the merchant lock list.

Merchant lock prevents the card being used outside the vendor. If the vendor uses a payment processor with a different domain (Stripe, Paddle, Chargebee), add both the vendor's domain and the processor domain to the lock list. The first charge confirms which processor is in use; revisit the lock list after charge one if needed.

Expected: The card is locked to the vendor and processor domains.

Ramp

Pre-fill GL code 6610 Software & SaaS subscriptions on the card so all transactions inherit it.

GL 6610 is the right code for SaaS subscriptions across all team owners. Pre-filling on the card means the team owner approving each charge does not have to set the code; they confirm only. If the subscription crosses departments, leave the pre-fill on 6610 and let approvers override on individual charges.

Expected: The card spend programme has GL 6610 pre-filled for all charges.

Ramp

Attach the contract PDF to the card record under Documents.

The contract PDF lives on the card so disputes have the documentation in the same place as the transactions. Without the contract on the card, disputes have to chase the contract from a shared drive which adds a day or two when speed matters. The contract should be the signed version not the marketing pricing page.

Expected: The signed contract PDF is attached to the card under Documents.

Ramp

Activate the card and copy the card number to the password manager under the vendor's record.

Card numbers go into the password manager, not into Slack or email. Each vendor has its own password-manager entry and the card number sits alongside the vendor login. Ramp also surfaces the card number in the vendor's recurring-charge tab so the vendor's billing settings can be updated without exposing the number again.

Expected: The card is active and the number is in the password manager under the vendor's record.

Hands your agent your team's exact steps

Your agent executes the documented procedure in order, against the applications named at each step, producing consistent output across human and agent runs.

Book a demo

Related patterns

How this pattern connects to other patterns in the library.

Often next

Approving a Ramp transaction with the right NetSuite GL code

Alternative to

Approving a Ramp transaction with the right NetSuite GL code

Lets your agent confirm the match and its scope

Alternative patterns let your agent compare candidates and select the closest match. Previous and next patterns define position in the workflow, so the agent operates within the scope of this one.

Supporting actions

Actions that provide evidence for this pattern.

Provisioned Ramp virtual card for Snowflake Inc with $890/mo cap (110% of $810)

Locked card_RmpSnow42 to snowflake.com and stripe.com merchant domains

Attached signed Snowflake MSA 2026 PDF to card_RmpSnow42 documents

Pre-filled GL 6610 Software & SaaS on card spend programme

Stored card_RmpSnow42 number in 1Password under Snowflake vendor record

Shows your agent the evidence behind the pattern

Each pattern is derived from captured action sequences. Your agent can reference the source actions to verify any field, so nothing it acts on is authored by hand or hallucinated.

Metadata

Timestamps and identifiers.

Evidence	Observed 8 times across 2 connections
Applications	Ramp, NetSuite
First seen	17 Feb 2026, 11:08
Last seen	22 Apr 2026, 14:54

Helps your agent rank patterns by confidence

Action count and last-seen timestamp weight each pattern by frequency and recency, so your agent selects the highest-scoring match rather than the first returned.

Questions

Frequently asked questions

Book a demo View all examples

Speak to the founder

Get a demo. Watch a live capture, then an AI agent query the result.

Ask anything. Pricing, security or integrating with your stack.

No purchase obligation

Book a call

Start capturing

Record in minutes. Install once and work as normal.

Plug AI agents in. One API call from any AI agent stack.

Refund on unused credits if you cancel