Ramp vs Relay

Close automation

1. ai-native userUse AI automations to close my books faster each month

   weight 2 · round to Ramp
   Ramp✓fullclaimed8/10

   Ramp documents AI-driven auto-coding, auto-categorization, real-time bidirectional ERP sync eliminating manual journal entries, and dedicated AI agents for auto-coding/fraud/approvals/payments, directly targeting faster book closing; broad accounting integration list (NetSuite, QuickBooks, Sage Intacct, etc.) supports this at scale. Missing for 10: independent/hands-on verification of close-time reduction and no specific 'days to close' benchmark or customer-reported close-cycle metric.

   • [claimed-docs] “Real-time bidirectional sync with ERPs eliminates manual journal entries”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Accounting: NetSuite, Sage Intacct, QuickBooks Online, QuickBooks Desktop, Xero, Workday Financial Management, Acumatica, Microsoft Dynamics…”

   proof ↗⚑ flag

   Relay—none0/10

   Relay offers rule-based automation (auto-transfers, categorization, sync to QuickBooks/Xero) but there is no evidence of AI-driven automation specifically aimed at closing the books faster—no mention of AI reconciliation, AI-assisted month-end close, or similar. missing for 10: any AI-specific book-closing automation, evidence of month-end close acceleration, AI-powered reconciliation or reporting features.

   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”
   • [claimed-docs] “Relay syncs ultra-detailed, easy-to-understand transaction data directly into QuickBooks Online and Xero.”
   • [claimed-docs] “Use Plaid to securely connect Relay to your other money apps like Expensify.”

   proof ↗⚑ flag

2. ai-native userHave AI automatically assign GL codes to transactions across entities to accelerate close

   weight 3 · round to Ramp
   Ramp✓fullclaimed8/10

   Ramp documents AI-driven auto-coding of transactions (auto-categorization based on transaction details/history/feedback, syncing to ERP) alongside a dedicated 'auto-coding' AI agent, multi-entity support with consolidated reporting, and real-time bidirectional ERP sync that eliminates manual journal entries — directly supporting cross-entity GL coding to accelerate close. Missing for 10: independent/hands-on evidence specifically validating GL-coding accuracy across multiple entities during a close cycle, and no third-party accounting-team testimonial on close-time reduction.

   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “Multi-entity support with entity-level restrictions and consolidated reporting”
   • [claimed-docs] “Real-time bidirectional sync with ERPs eliminates manual journal entries”
   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”

   proof ↗⚑ flag

   Relay—none0/10

   Relay is a business banking platform whose evidence shows expense categorization and syncing to QuickBooks/Xero, but no mention of AI-driven GL code assignment across entities or multi-entity close acceleration. Missing for 10: any AI-based GL coding feature, multi-entity support, or close-acceleration workflow.

   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”
   • [claimed-docs] “Relay syncs ultra-detailed, easy-to-understand transaction data directly into QuickBooks Online and Xero.”

   proof ↗⚑ flag

Developer accounting access

1. developerView and manage accounting data through a dedicated API

   weight 1 · round to Ramp
   Ramp✓fullprobed8/10

   Ramp documents a dedicated Developer API with OpenAPI spec, machine-readable docs (llms.txt, llms-api.txt), and bidirectional ERP sync for accounting data (transactions, coding, GL sync), confirmed by a live probe showing the API docs endpoint is reachable. Missing for 10: no independent developer testimonial or hands-on confirmation of actual accounting-data CRUD via the API, and no detail on specific accounting endpoints/scopes.

   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [claimed-docs] “Real-time bidirectional sync with ERPs eliminates manual journal entries”
   • [claimed-docs] “Ramp also supports custom CSV exports and an open API for flexible connectivity.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”

   proof ↗⚑ flag

   Relay—none0/10

   Evidence shows Relay syncing transaction data into QuickBooks/Xero and Plaid-based app connections, but there is no mention of a developer-facing API to view or manage accounting data programmatically. Missing for 10: any public API docs, endpoints, authentication, or SDK for accounting data access.

   • [claimed-docs] “Relay syncs ultra-detailed, easy-to-understand transaction data directly into QuickBooks Online and Xero.”
   • [claimed-docs] “Use Plaid to securely connect Relay to your other money apps like Expensify.”

   proof ↗⚑ flag

Erp sync

1. finance-leadSync transactions and expenses automatically with my accounting software

   weight 3 · round to Ramp
   Ramp✓fullcommunity9/10

   Ramp documents real-time bidirectional ERP sync, automatic categorization/coding synced directly to accounting systems, and a broad list of accounting integrations (NetSuite, QuickBooks, Xero, Sage Intacct, etc.), plus community corroboration of the platform working well for expense tracking. missing for 10: independent hands-on verification specifically of accounting-sync accuracy/reconciliation rather than vendor claims.

   • [claimed-docs] “Real-time bidirectional sync with ERPs eliminates manual journal entries”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Accounting: NetSuite, Sage Intacct, QuickBooks Online, QuickBooks Desktop, Xero, Workday Financial Management, Acumatica, Microsoft Dynamics…”
   • [claimed-docs] “Ramp also supports custom CSV exports and an open API for flexible connectivity.”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

   Relay✓fullclaimed7/10

   Relay's docs explicitly describe receipt capture, real-time categorization, and automatic syncing to accounting software (relay-docs-3), plus named integrations with QuickBooks Online and Xero for detailed transaction sync (relay-docs-19) and Plaid-based connections to apps like Expensify (relay-docs-20). Missing for 10: independent/hands-on verification of the accounting sync quality and no detail on reconciliation accuracy or setup friction reported by users.

   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”
   • [claimed-docs] “Relay syncs ultra-detailed, easy-to-understand transaction data directly into QuickBooks Online and Xero.”
   • [claimed-docs] “Use Plaid to securely connect Relay to your other money apps like Expensify.”

   proof ↗⚑ flag

2. finance-leadRely on real-time bidirectional sync with my ERP instead of manual journal entries

   weight 3 · round to Ramp
   Ramp✓fullclaimed8/10

   Ramp explicitly claims real-time bidirectional sync with ERPs eliminating manual journal entries, backed by auto-categorization and sync to ERP details, plus a broad list of supported ERP integrations (NetSuite, Sage Intacct, QuickBooks, etc.). Missing for 10: independent/hands-on verification of true bidirectional (not just push) sync and any community confirmation of eliminating manual JE work.

   • [claimed-docs] “Real-time bidirectional sync with ERPs eliminates manual journal entries”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Accounting: NetSuite, Sage Intacct, QuickBooks Online, QuickBooks Desktop, Xero, Workday Financial Management, Acumatica, Microsoft Dynamics…”

   proof ↗⚑ flag

   Relay~partialclaimed4/10

   Relay documents syncing transaction data into QuickBooks Online and Xero (relay-docs-19) and categorizing expenses in real time (relay-docs-3), which reduces manual entry, but this is one-way transaction sync into small-business accounting software, not bidirectional sync with an ERP system replacing journal entries. Missing for 10: evidence of true ERP (e.g., NetSuite/SAP) integration, bidirectional sync (journal entries flowing back), and any independent confirmation of 'real-time' accuracy beyond marketing copy.

   • [claimed-docs] “Relay syncs ultra-detailed, easy-to-understand transaction data directly into QuickBooks Online and Xero.”
   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”
   • [claimed-docs] “Use Plaid to securely connect Relay to your other money apps like Expensify.”

   proof ↗⚑ flag

Account structure

1. finance-leadView account and routing numbers and generate a bank verification letter anytime

   weight 1 · round to Relay
   Ramp—none0/10

   No evidence in the pack mentions account/routing numbers, bank verification letters, or any similar account-detail retrieval feature for Ramp accounts.

   ⚑ flag

   Relay✓fullclaimed8/10

   Relay's own support docs explicitly state that account/routing numbers can be viewed anytime under Accounts → Account Details, and a bank verification letter can be generated from the same screen, directly matching the story. Missing for 10: independent/hands-on community confirmation of this specific feature and detail on letter format/turnaround time.

   • [claimed-docs] “Go to Accounts → Account Details in the Relay app to view your numbers anytime, or generate a bank verification letter from the same screen.”

   proof ↗⚑ flag

2. finance-leadOpen multiple checking sub-accounts and auto-allocate incoming deposits across them

   weight 2 · round to Relay
   Ramp—none0/10

   Evidence shows only auto top-up from a single linked checking account to Ramp's card account with target-balance automation (ramp-docs-6), not the creation of multiple checking sub-accounts or auto-allocation of incoming deposits across them. Missing for 10: any mention of multiple sub-accounts, deposit-splitting/allocation rules, or treasury account structuring.

   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”

   proof ↗⚑ flag

   Relay✓fullprobed8/10

   Relay's docs clearly support opening up to 20 checking sub-accounts (including Profit-First style nicknaming) and automating transfers across them by dollar amount or percentage, and community evidence corroborates the auto-partitioning behavior in practice. missing for 10: independent verification of allocation reliability/edge cases (e.g., failed or delayed auto-transfers) and more detail on configuring percentage-based rules beyond marketing copy.

   • [claimed-docs] “Open up to 20 checking accounts and auto-transfer every deposit so you always know what’s tied up and what’s safe to spend.”
   • [claimed-docs] “Open up to 20 checking accounts and nickname them to match your Profit First setup: Income, Profit, Owner's Pay, Taxes, Operating Expenses.”
   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://support.relayfi.com/llms.txt # Relay > Relay is an online business banking platform for small businesse…”

   proof ↗⚑ flag

Bill pay

1. ai-native userHave AI read incoming bills and auto-populate payment details for my review

   weight 3 · round to Ramp
   Ramp✓fullclaimed8/10

   Ramp Bill Pay explicitly describes AI reading/matching vendor invoices, auto-coding to GL, PO matching, and routing for approval before payment, directly matching the AP auto-population-for-review story, backed by the four dedicated AI agents (auto-coding, fraud, routing, payment) and ERP sync docs. Missing for 10: independent hands-on verification of invoice-reading accuracy and no third-party review specifically confirming bill-reading AI performance.

   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “Real-time bidirectional sync with ERPs eliminates manual journal entries”

   proof ↗⚑ flag

   Relay—none0/10

   Evidence shows bill upload, delegation, and approval automation (relay-docs-4) but nothing about AI reading bill contents to extract payment details for review — no OCR/AI-parsing capability is documented anywhere in the pack.

   ⚑ flag

2. finance-leadUpload bills and route them through an approval workflow before paying vendors

   weight 3 · round drawn
   Ramp✓fullcommunity8/10

   Ramp documents bill upload (drag-and-drop invoices), automatic PO matching and GL coding, dynamic multi-department approval routing, and automated vendor payment (ramp-docs-2, ramp-docs-16, ramp-docs-17), corroborated by a positive hands-on community account of easy approval-to-payment workflows (ramp-comm-2). Missing for 10: independent third-party audit of the full bill-pay approval chain and more granular detail on rejection/exception handling in approvals.

   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

   Relay✓fullcommunity8/10

   Relay's docs directly support bill upload and vendor payment with approval workflows: relay-docs-4 explicitly states 'Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid,' and relay-docs-17 confirms 'Multi-step approval rules' as a product feature, matching the persona's need to route bills through approvals before paying vendors. Community evidence (relay-comm-1) corroborates that Relay handles money partitioning and payments, though notes manual execution steps for external payments. Missing for 10: independent hands-on review of the bill-approval workflow specifically (most community evidence focuses on account partitioning/cards rather than AP approval routing), and no detail on how many approval steps/roles are configurable.

   • [claimed-docs] “Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid.”
   • [claimed-docs] “Multi-step approval rules”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”

   proof ↗⚑ flag

3. finance-leadSet up approval permissions so designated teammates can approve and send payments with one click

   weight 2 · round drawn
   Ramp~partialcommunity6/10

   Ramp docs describe dynamic approval routing across departments and one-click, AI-driven payment flows (vendor invoice matched, coded, routed for approval, and paid), plus AI agents that handle approval routing and automatic payment, implying configurable permissions for who can approve/send. Community evidence corroborates a fast, one-click approve-and-fund experience for expenses. However, there's no explicit documentation of granular permission-setting UI/roles specifically for designating which teammates can approve and send payments with one click. Missing for 10: explicit admin-permission configuration screens/roles documentation, and independent confirmation of one-click send-payment permission setup.

   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

   Relay~partialcommunity6/10

   Relay docs mention 'automate approvals' and 'define roles' for teammates, and pricing page lists 'Multi-step approval rules' as a feature, supporting configurable approval permissions for payments. However, there's no detailed documentation on the one-click approve/send UX for designated approvers, and community reviews note some users experienced 'issues with permissions,' suggesting occasional friction. Missing for 10: explicit description of one-click approve/send workflow, detailed permission granularity (e.g., approval thresholds per teammate), and hands-on confirmation the feature works smoothly.

   • [claimed-docs] “Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid.”
   • [claimed-docs] “Multi-step approval rules”
   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

4. ai-native userHave vendor invoices automatically matched to purchase orders, coded, and routed for payment

   weight 2 · round to Ramp
   Ramp✓fullclaimed8/10

   Ramp's docs directly describe the exact workflow: invoices dragged in are auto-matched to POs, auto-coded to GL, routed for approval, and paid, with dedicated AI agents for coding, approval routing, and payment execution. This is corroborated by ERP sync and categorization details, though evidence is entirely vendor-sourced with no independent hands-on validation of AP-specific matching accuracy. Missing for 10: independent/community confirmation of invoice-to-PO matching accuracy and edge-case handling.

   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “Real-time bidirectional sync with ERPs eliminates manual journal entries”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”

   proof ↗⚑ flag

   Relay—none0/10

   Relay's evidence shows bill upload, approval routing, and vendor payment (relay-docs-4, relay-docs-17), but nothing about matching invoices to purchase orders or automated GL/expense coding tied to POs — a specific three-way-match AP capability that is absent from all docs and community sources.

   • [claimed-docs] “Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid.”
   • [claimed-docs] “Multi-step approval rules”

   proof ↗⚑ flag

Invoicing

1. finance-leadCreate and send branded invoices with built-in payment collection

   weight 2 · round to Relay
   Ramp—none0/10

   Ramp's evidence covers expense management, bill pay/AP automation, procurement, and ERP sync, but there is no mention of creating or sending branded customer-facing invoices with payment collection (accounts receivable), which is a distinct capability from bill pay.

   ⚑ flag

   Relay✓fullclaimed8/10

   Relay's docs explicitly describe building and sending branded invoices with built-in payment collection ('no separate tool needed'), plus flexible payment options, automated follow-up, and recurring invoices as a feature tier. Missing for 10: independent/hands-on community corroboration of invoicing feature usage and details on branding customization depth.

   • [claimed-docs] “Create invoices, request payments, offer flexible payment options, and let Relay handle the follow-up.”
   • [claimed-docs] “Build and send a branded invoice with built-in payment collection from Invoices — no separate tool needed.”
   • [claimed-docs] “Recurring invoices”

   proof ↗⚑ flag

Money movement

1. founderSend money abroad that arrives in under a minute

   weight 2 · round drawn
   Ramp—none0/10

   No evidence in the pack addresses international money transfer or cross-border payment speed; Ramp's evidence covers cards, bill pay, ERP sync, and vendor integrations but nothing about sending money abroad or transfer time guarantees. missing for 10: any mention of international/cross-border wire or transfer capability, evidence of transfer speed, currency/FX support.

   ⚑ flag

   Relay—none0/10

   Evidence shows Relay wires (domestic and international) can send 'same-day' at best, and ACH takes 1-3 business days — nothing supports transfers arriving in under a minute. The axis applies since cross-border payments are a core banking feature, but no evidence of near-instant delivery exists.

   • [claimed-docs] “ACH transfers take 1–3 business days; wires (domestic and international) can send same-day. You'll see the exact delivery estimate before co…”
   • [claimed-docs] “How to Activate Receiving International Wires on Relay”
   • [community] “Relay's international transfer system is incredibly easy to use. Pricing is straightforward - although not exactly affordable at $10 per out…”

   proof ↗⚑ flag

2. finance-leadSend domestic ACH and wire payments to vendors

   weight 3 · round to Relay
   Ramp~partialclaimed4/10

   Ramp's docs describe vendor invoices being routed, approved, and 'paid' automatically via a dedicated payment AI agent, implying built-in bill-pay/payment execution, but no evidence explicitly confirms domestic ACH or wire rail support, transfer limits, or same-day options. Missing for 10: explicit mention of ACH/wire payment methods, processing times, and any independent confirmation that payments are actually disbursed via bank rails rather than just approval routing.

   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”

   proof ↗⚑ flag

   Relay✓fullcommunity8/10

   Relay's docs explicitly describe paying vendors via ACH and wire, with delivery estimates (1-3 days ACH, same-day wires), bill upload/approval workflows, and limit management, and community evidence confirms these payments work in practice (with the caveat that execution is manual, not autonomous). Pricing tiers also confirm faster ACH is available on Pro plan. Missing for 10: independent hands-on verification of wire payment success/reliability at scale, more detail on wire fees/limits.

   • [claimed-docs] “Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid.”
   • [claimed-docs] “ACH transfers take 1–3 business days; wires (domestic and international) can send same-day. You'll see the exact delivery estimate before co…”
   • [claimed-docs] “Check your current limits under Accounts → Limits, then request an increase right from that screen.”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”
   • [community] “Relay's basic plan is entirely free, at $0/month... if your business needs faster, same-day ACH and more advanced billing features, then the…”

   proof ↗⚑ flag

3. finance-leadSend international payments in local currencies with transparent fees

   weight 3 · round to Relay
   Ramp—none0/10

   No evidence in the pack addresses international payments, local currency support, or FX fee transparency—only US-focused corporate card, expense, and AP automation features are documented.

   ⚑ flag

   Relay~partialcommunity4/10

   Relay supports sending and receiving international wires (docs-9, docs-23) with a clear $10 fee disclosed and waived on Pro plan (relay-comm-5), giving some fee transparency, but there is no evidence of actual local-currency disbursement, FX rate handling, or multi-currency accounts — wires appear to be standard bank wires, not localized payouts. Missing for 10: local currency payment execution, FX rate transparency, multi-currency support evidence, independent confirmation of international payment reliability.

   • [claimed-docs] “ACH transfers take 1–3 business days; wires (domestic and international) can send same-day. You'll see the exact delivery estimate before co…”
   • [claimed-docs] “How to Activate Receiving International Wires on Relay”
   • [community] “Relay's international transfer system is incredibly easy to use. Pricing is straightforward - although not exactly affordable at $10 per out…”

   proof ↗⚑ flag

Multi currency

1. founderHold and manage balances in multiple currencies from one account

   weight 2 · round drawn
   Ramp—none0/10

   The evidence pack covers card issuance, expense automation, ERP sync, and integrations, but contains no mention of multi-currency account balances or FX holding capabilities. Multi-currency balance management is a fair axis for a corporate finance/spend platform, so absence of evidence yields 'none'.

   ⚑ flag

   Relay—none0/10

   Relay's evidence describes opening up to 20 checking accounts and receiving/sending international wires, but all of these appear to be USD sub-accounts for organizing cash, not accounts that hold balances in multiple currencies (e.g., EUR, GBP) simultaneously. No evidence pack item describes multi-currency balance holding or FX conversion features.

   • [claimed-docs] “Open up to 20 checking accounts and auto-transfer every deposit so you always know what’s tied up and what’s safe to spend.”
   • [claimed-docs] “Open up to 20 checking accounts and nickname them to match your Profit First setup: Income, Profit, Owner's Pay, Taxes, Operating Expenses.”
   • [claimed-docs] “How to Activate Receiving International Wires on Relay”
   • [community] “Relay's international transfer system is incredibly easy to use. Pricing is straightforward - although not exactly affordable at $10 per out…”

   proof ↗⚑ flag

2. founderReceive payments using local account details in multiple currencies

   weight 2 · round drawn
   Ramp—none0/10

   Ramp's evidence pack covers cards, expense management, bill pay, ERP sync, and banking integrations, but nothing describes receiving inbound payments via local account details (e.g., local IBAN/ACH/SWIFT receiving accounts) in multiple currencies — this is a receivables/multi-currency collection capability not mentioned anywhere in the pack. Missing for 10: any mention of local currency receiving accounts, multi-currency invoicing/collections, or global payment-in details.

   ⚑ flag

   Relay—none0/10

   Evidence shows Relay is a US business banking platform offering USD checking accounts and the ability to receive international wires into those accounts (relay-docs-13, relay-docs-23), but there is no evidence of local account details (e.g., IBAN/sort code equivalents) issued in multiple currencies for receiving payments locally in each currency, which is what this story requires.

   • [claimed-docs] “Deposit ACH transfers, wires, checks, cash and payouts from payment processors like PayPal, Stripe, Square and more.”
   • [claimed-docs] “How to Activate Receiving International Wires on Relay”
   • [claimed-docs] “ACH transfers take 1–3 business days; wires (domestic and international) can send same-day. You'll see the exact delivery estimate before co…”

   proof ↗⚑ flag

Operational efficiency

1. finance-leadSearch across all transactions, vendors, and cards from one universal search bar and jump straight into initiating a payment

   weight 1 · round drawn
   Ramp—none0/10

   No evidence pack item describes a universal/global search bar spanning transactions, vendors, and cards, nor any 'jump straight into initiating a payment' from search results. The evidence covers auto-categorization, invoice matching, approval routing, and integrations, but nothing about a unified search UX.

   ⚑ flag

   Relay—none0/10

   No evidence in the pack mentions a universal/global search bar that spans transactions, vendors, and cards, nor any workflow for jumping from search results into initiating a payment; the docs describe discrete screens (Accounts, Cards, Invoices, Limits) rather than a unified search experience. missing for 10: any mention of a search feature, cross-entity search UI, or search-to-payment flow.

   ⚑ flag

Payment transparency

1. finance-leadSee the exact delivery estimate for an ACH or wire transfer before confirming it

   weight 2 · round to Relay
   Ramp—none0/10

   No evidence pack item mentions ACH/wire delivery time estimates or any pre-confirmation display of settlement dates for payments; evidence covers card capture, invoice matching, ERP sync, integrations, and dev tools, none of which touch payment delivery estimates.

   ⚑ flag

   Relay✓fullclaimed8/10

   relay-docs-9 explicitly states ACH takes 1–3 business days, wires can send same-day, and that users see the exact delivery estimate before confirming a transfer — directly matching the story. Missing for 10: independent/hands-on confirmation (e.g. screenshot or user report) of the pre-confirmation estimate UI beyond first-party support docs.

   • [claimed-docs] “ACH transfers take 1–3 business days; wires (domestic and international) can send same-day. You'll see the exact delivery estimate before co…”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Ramp
   Ramp✓fullprobed9/10

   Ramp publishes a documented llms.txt indexing structure (llms.txt, llms-guides.txt, llms-api.txt, llms-full.txt, OpenAPI spec) explicitly designed for LLM/agent consumption, and a live probe confirms HTTP 200 with machine-readable usage instructions. Missing for 10: independent third-party corroboration of an agent actually consuming these files in a real workflow.

   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference)... or…”
   • [claimed-docs] “If the URL is under /developer-api/v1/rate-limiting -> /llms-guides/rate-limiting.txt”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”

   proof ↗⚑ flag

   Relay✓fullprobed7/10

   There is direct probe evidence that Relay's support site serves a working llms.txt file at https://support.relayfi.com/llms.txt returning HTTP 200 with structured content describing the product, confirming an agent-oriented docs endpoint exists. Missing for 10: no evidence of broader agent-oriented documentation beyond this single file, no confirmation it covers full product surface, and no independent/community corroboration of agents actually using it.

   • [probe] “PROBE llms.txt: HTTP 200 at https://support.relayfi.com/llms.txt # Relay > Relay is an online business banking platform for small businesse…”

   proof ↗⚑ flag

2. ai-native userDrive the product through a documented public API

   weight 3 · round to Ramp
   Ramp✓fullprobed8/10

   Ramp publishes a documented public Developer API with OpenAPI spec, LLM-readable docs (/llms.txt, /llms-api.txt), and rate-limiting guides, confirmed by direct probes (200 OK) plus an official MCP server and CLI extending programmatic/AI-native access. Missing for 10: independent third-party developer reports of building against the API, and more detail on auth/scopes beyond the doc index.

   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference)... or…”
   • [claimed-docs] “If the URL is under /developer-api/v1/rate-limiting -> /llms-guides/rate-limiting.txt”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
   • [probe] “official MCP server documented at https://support.ramp.com/ramp-mcp”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

   Relay—none0/10

   No evidence of a documented public API for programmatic/agentic access; all evidence pertains to the banking product's manual UI features, integrations via Plaid/QuickBooks, and support docs, not an API for driving Relay programmatically. missing for 10: public API docs, authentication/reference, SDKs, or any mention of API endpoints.

   ⚑ flag

3. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Ramp—none0/10

   The evidence pack details Ramp's developer API, OpenAPI spec, MCP server, and CLI, but never mentions webhook subscriptions or event notifications anywhere. Webhooks are a plausible capability for a platform with a full developer API, so absence of evidence means this axis is unmet rather than inapplicable.

   ⚑ flag

   Relay—none0/10

   Relay is a business banking platform; no evidence anywhere in the pack mentions webhooks, event subscriptions, or any API-based notification system for developers/agents. Missing for 10: any webhook documentation, event types, subscription/callback mechanism, or API reference.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Ramp
   Ramp✓fullcommunity7/10

   Ramp documents multiple AI-generated insights/suggestions embedded in the product itself: auto-filled memos/categories at swipe, AI-driven invoice coding and matching, hotel rebooking suggestions, contract/screenshot parsing for intake, and dedicated AI agents for coding, fraud, approvals and payments. These are first-party claims with some corroboration via community praise of smooth automated workflows (e.g., instant card issuance and approval flows), though independent verification of the 'AI-generated insight' quality specifically is thin. Missing for 10: independent hands-on evaluation of AI insight accuracy/usefulness, and clearer distinction between rule-based automation vs. true generative insights.

   • [claimed-docs] “Auto-receipt capture at the moment of card swipe with AI-filled memos and categories”
   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Hotel rate monitoring with automatic rebooking when prices drop $50+”
   • [claimed-docs] “AI-powered intake parses contracts and screenshots to auto-populate request forms”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

   Relay—none0/10

   No evidence in the pack mentions AI-generated insights, suggestions, forecasting, or any AI/ML-driven analysis within Relay; all listed features are manual banking, transfer, invoicing, and card-management tools. missing for 10: any mention of AI-powered insights, anomaly detection, spend suggestions, or predictive analytics, first-party or independent corroboration of such a feature.

   ⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Ramp
   Ramp✓fullclaimed8/10

   Ramp's docs describe multiple autonomous background automations — auto-receipt capture, invoice matching/coding/approval/payment, hotel rate monitoring with auto-rebooking, auto top-up with balance targets, and four dedicated AI agents handling coding, fraud, approvals, and payment end-to-end without manual triggering. This directly matches the story of AI-native background automation. Missing for 10: independent/hands-on verification that these automations run fully autonomously in production (community evidence only confirms manual card/expense workflows, not the autonomous agent features).

   • [claimed-docs] “Auto-receipt capture at the moment of card swipe with AI-filled memos and categories”
   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Hotel rate monitoring with automatic rebooking when prices drop $50+”
   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”

   proof ↗⚑ flag

   Relay~partialcommunity5/10

   Relay offers rule-based automations that run without manual intervention — auto-transfers on deposit, percentage/dollar-based multi-account splits, multi-step approval rules, and recurring invoices (relay-docs-1, relay-docs-6, relay-docs-15, relay-docs-17, relay-docs-18) — which qualifies as background automation. However this is traditional banking rule automation, not AI/agent-driven decisioning, and community evidence notes manual execution is still required for many external payments (relay-comm-1). Missing for 10: any AI/LLM-based autonomous decision-making, agent-triggered actions, or evidence of automations beyond simple scheduled/rule-based transfers.

   • [claimed-docs] “Open up to 20 checking accounts and auto-transfer every deposit so you always know what’s tied up and what’s safe to spend.”
   • [claimed-docs] “Build a cash cushion with high-yield accounts and automated rules that help you stay ready for whatever’s next.”
   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [claimed-docs] “Multi-step approval rules”
   • [claimed-docs] “Recurring invoices”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”

   proof ↗⚑ flag

3. ai-native userOperate the product with natural-language commands

   weight 2 · round to Ramp
   Ramp✓fullprobed7/10

   Ramp publishes an official MCP server (support.ramp.com/ramp-mcp) plus llms.txt/CLI docs, which directly enables AI agents/assistants to operate Ramp via natural-language commands, and it also ships internal AI agents for coding/approval/payment automation. missing for 10: hands-on/independent evidence of a user actually issuing natural-language commands through the MCP server, and detail on what actions/scopes the MCP server exposes.

   • [probe] “official MCP server documented at https://support.ramp.com/ramp-mcp”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”

   proof ↗⚑ flag

   Relay—none0/10

   Relay is a business banking platform with a standard app UI; the evidence pack shows only manual navigation flows (menus, screens like Accounts → Limits) and no natural-language command interface, chatbot, or agentic control surface. There is an llms.txt file which suggests machine-readability but not that end users can operate the product via natural language. Missing for 10: any evidence of a natural-language interface, chat-based commands, or AI assistant for operating the account.

   • [probe] “PROBE llms.txt: HTTP 200 at https://support.relayfi.com/llms.txt # Relay > Relay is an online business banking platform for small businesse…”
   • [claimed-docs] “Go to Accounts → Account Details in the Relay app to view your numbers anytime, or generate a bank verification letter from the same screen.”
   • [claimed-docs] “Check your current limits under Accounts → Limits, then request an increase right from that screen.”

   proof ↗⚑ flag

Api quality

1. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Ramp
   Ramp✓fullprobed9/10

   Ramp's developer docs explicitly expose a downloadable OpenAPI spec at /openapi/developer-api.json, confirmed by both documentation references and a live probe returning HTTP 200 at the llms.txt index that lists this spec alongside other machine-readable formats. Missing for 10: independent third-party confirmation that the OpenAPI file itself is complete/valid beyond the vendor's own docs.

   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference)... or…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”

   proof ↗⚑ flag

   Relay—none0/10

   No evidence of an OpenAPI/Swagger spec or any machine-readable API documentation; evidence only covers banking features, support articles, and an llms.txt file (which is not an API spec).

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Ramp
   Ramp~partialprobed6/10

   Ramp exposes a public API, official CLI, and MCP server (ramp-probe-1/2/3) plus CSV export/import (ramp-docs-12) that would let an AI-native user script bulk actions, and AI agents already auto-code/categorize transactions at scale across the platform (ramp-docs-15, ramp-docs-17). However there's no direct evidence of a dedicated bulk-edit/bulk-approve UI or documented batch endpoints for acting on many items simultaneously. Missing for 10: explicit bulk-operation API endpoints or UI (bulk approve, bulk export, batch transaction updates) and independent confirmation these programmatic paths work for large-scale bulk actions.

   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “Ramp also supports custom CSV exports and an open API for flexible connectivity.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
   • [probe] “official MCP server documented at https://support.ramp.com/ramp-mcp”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

   Relay~partialclaimed4/10

   Relay offers some bulk-style automation — auto-transferring funds across up to 20 accounts, issuing up to 50 cards, multi-step approval rules, and bulk vendor bill uploads — but these are manual UI-driven configurations rather than a programmatic/bulk-API interface an AI-native user could drive across many items at once. Missing for 10: evidence of an API or agent-facing bulk operation endpoint, batch transaction processing, or CSV/bulk import-export capability confirmed by independent testing.

   • [claimed-docs] “Open up to 20 checking accounts and nickname them to match your Profit First setup: Income, Profit, Owner's Pay, Taxes, Operating Expenses.”
   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [claimed-docs] “Issue 50 virtual or physical Visa debit cards to your team”
   • [claimed-docs] “Multi-step approval rules”
   • [claimed-docs] “Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Ramp
   Ramp~partialprobed6/10

   Ramp ships several built-in automations that fire actions on events—auto top-up triggered by low balance, hotel rate rebooking on price drops, dynamic approval routing, and AI agents auto-coding/paying invoices—showing real automation depth, and its public API/MCP/CLI let developers extend this. However these are largely preset, product-specific automations rather than a general user-defined rule engine (arbitrary trigger→condition→action authoring), and there's no evidence of a configurable rules/webhooks builder for custom event handling. Missing for 10: a documented custom rule-builder UI or webhook/event API for arbitrary automations, and independent confirmation of rule flexibility beyond the shipped presets.

   • [claimed-docs] “Hotel rate monitoring with automatic rebooking when prices drop $50+”
   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [probe] “official MCP server documented at https://support.ramp.com/ramp-mcp”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

   Relay~partialclaimed5/10

   Relay supports rule-based automation for money movement — auto-transferring deposits across accounts, percentage/dollar-based automated transfers, and multi-step approval rules — which satisfies a narrow slice of 'define rules that trigger actions on events.' However, these are fixed banking-specific triggers (deposits, thresholds, approvals) rather than a general-purpose, AI-native event/action framework (no webhooks, API-triggered rules, or custom event definitions are evidenced). Missing for 10: evidence of programmable/custom event triggers via API or webhooks, broader condition-action rule builder beyond transfers/approvals, and any AI-agent-facing automation interface.

   • [claimed-docs] “Build a cash cushion with high-yield accounts and automated rules that help you stay ready for whatever’s next.”
   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [claimed-docs] “Multi-step approval rules”
   • [claimed-docs] “Open up to 20 checking accounts and auto-transfer every deposit so you always know what’s tied up and what’s safe to spend.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Ramp~partialprobed4/10

   Ramp ships specific built-in recurring automations (auto top-up with target-balance thresholds, hotel rate monitoring/rebooking, dynamic approval routing) that run continuously without user re-triggering, and exposes an API/MCP server/CLI that could be used to build custom scheduled jobs. However there's no evidence of a general-purpose workflow/job scheduler (e.g., cron-style triggers, custom recurring automation builder) that an AI-native user could configure via the API or MCP server themselves — the cited automations are fixed product features, not user-defined scheduled workflows. Missing for 10: documentation of a programmable scheduling/trigger API for arbitrary recurring jobs, evidence the MCP server or CLI supports defining custom recurring workflows, and independent confirmation of these automations working as advertised.

   • [claimed-docs] “Hotel rate monitoring with automatic rebooking when prices drop $50+”
   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [probe] “official MCP server documented at https://support.ramp.com/ramp-mcp”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”

   proof ↗⚑ flag

   Relay~partialclaimed4/10

   Relay supports recurring financial automations like scheduled/percentage-based account transfers, recurring invoices, and automated approval rules, which count as recurring workflow scheduling within its banking domain. However there's no evidence of a general-purpose job/workflow scheduler, API/webhook triggers, or any AI-native automation surface for arbitrary tasks. Missing for 10: API-based scheduling, arbitrary workflow/job automation beyond money movement, AI-agent-facing scheduling interface.

   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [claimed-docs] “Recurring invoices”
   • [claimed-docs] “Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid.”
   • [claimed-docs] “Multi-step approval rules”

   proof ↗⚑ flag

Card controls

1. finance-leadSet department or program budgets with automatically enforced spend limits

   weight 2 · round to Ramp
   Ramp~partialcommunity6/10

   Ramp docs reference multi-entity support with entity-level restrictions, dynamic approval routing, and card issuance controls, implying budget/spend-limit enforcement by department, but there is no explicit first-party documentation of setting a hard department/program budget cap with automatic enforcement (e.g., blocking spend once a budget threshold is reached) nor independent confirmation of this specific behavior. missing for 10: explicit documentation of budget-setting UI/API tying spend limits to departments/programs, evidence of automatic blocking/alerts when budgets are exceeded, and independent/hands-on confirmation of enforcement in practice.

   • [claimed-docs] “Multi-entity support with entity-level restrictions and consolidated reporting”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

   Relay~partialcommunity5/10

   Relay lets admins issue cards with set spend limits, define roles, and separate funds into up to 20 checking accounts (useful as informal department/program buckets) with automated transfer rules, and 'multi-step approval rules' are mentioned on the pricing page. However there's no explicit 'budget' object with rolling caps per department/program beyond individual card limits, and community reviews note 'problems with prescribed limits,' suggesting enforcement isn't perfectly reliable. Missing for 10: a dedicated budget-creation feature (vs just card limits/accounts), documented department-level aggregate spend caps, and clear evidence enforcement is robust in practice.

   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [claimed-docs] “Multi-step approval rules”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”
   • [community] “For Relay's physical cards, there is a maximum daily card transaction limit of $7,000 and an ATM withdrawal limit of $1,000 per card.”

   proof ↗⚑ flag

2. finance-leadSet per-card spend limits and granular controls for each employee

   weight 3 · round to Relay
   Ramp~partialcommunity5/10

   Evidence shows employees can quickly spin up new cards with approval workflows (ramp-comm-2) and that Ramp supports entity-level restrictions and dynamic approval routing (ramp-docs-14, ramp-docs-16), implying some granular control, but there is no explicit documentation of setting per-card numeric spend limits or category/merchant-level restrictions per employee. missing for 10: explicit docs on per-card spend limit configuration, merchant/category-level card controls, and independent verification of granularity.

   • [claimed-docs] “Multi-entity support with entity-level restrictions and consolidated reporting”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

   Relay~partialcommunity7/10

   Relay's docs confirm card issuance with spend limits, role definitions, real-time transaction tracking, and multi-step approval rules (relay-docs-2, relay-docs-16, relay-docs-17), directly supporting granular per-card controls for employees. However, community reviews note occasional 'problems with prescribed limits' and permission glitches (relay-comm-2), and hard caps like a $7,000 daily card limit (relay-comm-4) suggest some inflexibility. Missing for 10: deeper documentation on category/merchant-level restrictions, audit trails for limit changes, and independent confirmation that granular controls work flawlessly at scale.

   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [claimed-docs] “Issue 50 virtual or physical Visa debit cards to your team”
   • [claimed-docs] “Multi-step approval rules”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”
   • [community] “For Relay's physical cards, there is a maximum daily card transaction limit of $7,000 and an ATM withdrawal limit of $1,000 per card.”

   proof ↗⚑ flag

3. finance-leadInstantly freeze a lost or stolen card and order a replacement

   weight 2 · round to Relay
   Ramp—none0/10

   Ramp is a corporate card platform where freezing/replacing lost cards is a standard, expected capability, but no evidence item describes card freezing or replacement workflows — only card issuance speed (ramp-comm-2) and unrelated features (receipts, AP automation, bill pay, ERP sync) are covered. Missing for 10: any documentation or community mention of freezing a lost/stolen card, ordering a replacement, or related self-service card controls.

   ⚑ flag

   Relay✓fullcommunity8/10

   relay-docs-8 directly documents freezing a card instantly in-app and ordering a replacement (5–7 business days), matching the story exactly, with community reviews (relay-comm-2) corroborating a functional, user-friendly card management experience. Missing for 10: independent hands-on confirmation specifically of the freeze/replace flow (vs general app usability).

   • [claimed-docs] “Open Cards in the app to freeze it instantly and order a replacement — it typically arrives in 5–7 business days.”
   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

4. finance-leadRequest a transaction limit increase directly from a self-service screen

   weight 1 · round to Relay
   Ramp—none0/10

   The evidence pack contains no mention of a self-service screen for requesting card/transaction limit increases; only general card issuance and expense-tracking mentions appear (ramp-comm-2) but nothing about limit-increase requests.

   ⚑ flag

   Relay✓fullcommunity8/10

   First-party support docs explicitly describe a self-service flow: view current limits under Accounts → Limits and request an increase directly from that screen, with related help articles confirming the limits view. This matches the finance-lead story closely. Missing for 10: independent/hands-on confirmation that limit-increase requests are actually approved smoothly (one community review vaguely mentions 'problems with prescribed limits'), and no explicit persona-specific (finance-lead role) detail.

   • [claimed-docs] “Check your current limits under Accounts → Limits, then request an increase right from that screen.”
   • [claimed-docs] “How to View Your Account Limits in Relay”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

Card issuance

1. finance-leadInstantly create virtual cards scoped to a specific purpose like ad spend or a single vendor

   weight 3 · round to Ramp
   Ramp~partialcommunity6/10

   Community evidence confirms Ramp lets users spin up a new virtual/business expense card in under a minute for a specific purchase, supporting instant, purpose-scoped card creation. However, there's no direct first-party documentation explicitly describing vendor- or category-locked virtual card controls (e.g., merchant-lock, spend-category restrictions) beyond general references to approvals and multi-entity restrictions. Missing for 10: explicit docs on merchant/category-locking rules for virtual cards, admin UI screenshots/workflow for scoping a card to a single vendor or ad-spend category, and independent verification of that specific control granularity.

   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [claimed-docs] “Multi-entity support with entity-level restrictions and consolidated reporting”

   proof ↗⚑ flag

   Relay~partialclaimed5/10

   Relay supports issuing multiple virtual/physical Visa cards with spend limits and role-based controls (relay-docs-2, relay-docs-16), which enables purpose-scoped cards for things like a vendor or ad spend, but there's no evidence of instant creation flows, per-card vendor/merchant-locking, or category-specific restrictions tailored to 'ad spend' style use cases. missing for 10: evidence of instant/quick card issuance UX, vendor-lock or merchant-category restriction features, and independent confirmation of ease/speed of scoped card creation.

   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [claimed-docs] “Issue 50 virtual or physical Visa debit cards to your team”
   • [claimed-docs] “Check your current limits under Accounts → Limits, then request an increase right from that screen.”

   proof ↗⚑ flag

2. finance-leadIssue physical debit or credit cards to employees with defined roles

   weight 2 · round to Relay
   Ramp~partialcommunity4/10

   Community evidence confirms Ramp lets a finance user quickly spin up a company card with approval and fund transfer, and docs mention entity-level restrictions and approval routing that imply role-based controls, but nothing explicitly confirms physical (vs. virtual) card issuance or granular role-based card permissions. Missing for 10: explicit mention of physical card issuance, and documentation of role-based spend controls/limits tied to employee roles.

   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”
   • [claimed-docs] “Multi-entity support with entity-level restrictions and consolidated reporting”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”

   proof ↗⚑ flag

   Relay✓fullcommunity8/10

   Docs explicitly state issuing Visa debit or credit cards with defined roles and spend limits, real-time tracking (relay-docs-2), physical/virtual card issuance up to 50 cards (relay-docs-16), and card freeze/replacement management (relay-docs-8). Community evidence corroborates card limits and permissions in practice (relay-comm-4, relay-comm-2). Missing for 10: independent hands-on verification of role-based permission granularity and credit card specifics beyond marketing copy.

   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [claimed-docs] “Issue 50 virtual or physical Visa debit cards to your team”
   • [claimed-docs] “Open Cards in the app to freeze it instantly and order a replacement — it typically arrives in 5–7 business days.”
   • [community] “For Relay's physical cards, there is a maximum daily card transaction limit of $7,000 and an ATM withdrawal limit of $1,000 per card.”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

Card rewards

1. founderSpend and withdraw cash abroad on a company card without hidden foreign fees

   weight 1 · round drawn
   Ramp—none0/10

   The evidence pack contains no mention of foreign transaction fees, international card usage, currency conversion, or cash withdrawal abroad — only receipt capture, AP automation, ERP sync, and integrations are covered. Axis applies to a corporate card product, but nothing in the pack supports the specific claim about fee-free international spend/withdrawal.

   ⚑ flag

   Relay—none0/10

   The evidence covers Relay's domestic checking, cards, invoicing, and international wire transfers (with a $10 fee), but nowhere states or documents that its Visa debit/credit cards have no foreign transaction fees or how cash withdrawals abroad are priced. This is a fair question for a business card product, but no first-party or community evidence confirms fee-free foreign card spend/withdrawal.

   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [claimed-docs] “How to Activate Receiving International Wires on Relay”
   • [community] “Relay's international transfer system is incredibly easy to use. Pricing is straightforward - although not exactly affordable at $10 per out…”

   proof ↗⚑ flag

2. founderEarn automatic cashback on card spend without manual redemption steps

   weight 2 · round drawn
   Ramp—none0/10

   The evidence pack covers expense automation, receipt capture, ERP sync, approvals, and AI agents, but contains no mention of cashback rewards or automatic cashback redemption on card spend anywhere in the docs or community evidence.

   ⚑ flag

   Relay—none0/10

   Evidence covers card issuance, spend limits, savings APY, and expense tracking, but nothing in the pack mentions cashback rewards on card spend at all. missing for 10: any mention of cashback program, rewards rate, or automatic redemption on Relay cards.

   ⚑ flag

Procurement automation

1. ai-native userHave vendor contracts parsed by AI to auto-populate procurement request forms

   weight 2 · round to Ramp
   Ramp✓fullclaimed7/10

   Ramp's docs explicitly state AI-powered intake parses contracts and screenshots to auto-populate procurement request forms, directly matching the story. Missing for 10: independent/hands-on corroboration of this specific contract-parsing feature and detail on accuracy/edge cases.

   • [claimed-docs] “AI-powered intake parses contracts and screenshots to auto-populate request forms”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”

   proof ↗⚑ flag

   Relay—none0/10

   No evidence anywhere in the pack of AI parsing vendor contracts or auto-populating procurement request forms; Relay's evidence covers banking, cards, invoicing, bill pay, and accounting sync but nothing about contract parsing or procurement workflows. missing for 10: any AI contract-parsing capability, any procurement request form feature, any evidence of document ingestion/AI extraction.

   ⚑ flag

Receipt management

1. ai-native userHave receipts automatically captured and coded the moment a card is used, without manual entry

   weight 3 · round to Ramp
   Ramp✓fullcommunity8/10

   Ramp's own docs claim auto-receipt capture at the moment of card swipe with AI-filled memos/categories, plus automatic categorization based on transaction details, history, and team feedback that syncs coded transactions to ERP — directly matching the story. Community evidence corroborates general ease-of-use of card issuance/expense flow, though no independent hands-on confirmation specifically of receipt auto-capture accuracy exists. Missing for 10: independent/hands-on verification of receipt-matching accuracy and edge cases (e.g., lost receipts, disputes).

   • [claimed-docs] “Auto-receipt capture at the moment of card swipe with AI-filled memos and categories”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

   Relay~partialclaimed5/10

   Relay's own docs state it can 'Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically' (relay-docs-3), directly matching the story, but there's no detail on the actual capture mechanism (e.g., automatic prompt at time of swipe vs. manual photo upload) and no independent or hands-on corroboration of this specific feature working seamlessly. Missing for 10: independent/community validation of the receipt-capture flow, technical detail on how capture is triggered at point-of-sale, and any evidence it truly requires zero manual entry.

   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”
   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”

   proof ↗⚑ flag

2. finance-leadHave receipts automatically attached to the right transaction by emailing or uploading them

   weight 2 · round to Ramp
   Ramp✓fullclaimed7/10

   Ramp's docs claim auto-receipt capture at swipe with AI-filled memos/categories, and automated matching/coding for vendor invoices dragged into the platform, which covers the core of automatic receipt-to-transaction matching via upload or email-based capture. Missing for 10: explicit documentation of the email-forwarding-to-transaction workflow specifically, and independent/hands-on confirmation of matching accuracy beyond vendor claims.

   • [claimed-docs] “Auto-receipt capture at the moment of card swipe with AI-filled memos and categories”
   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”

   proof ↗⚑ flag

   Relay~partialclaimed5/10

   Relay's marketing docs mention capturing receipts and categorizing expenses in real time with sync to accounting software, implying some auto-matching capability, but there is no evidence of an email-in receipt feature or detailed matching logic to specific transactions. missing for 10: explicit email-to-receipt ingestion method, confirmation that receipts are auto-matched to the correct transaction, and independent/hands-on verification of this workflow.

   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”

   proof ↗⚑ flag

Signup flow

1. founderCheck my account application status while it's under review

   weight 1 · round to Relay
   Ramp—none0/10

   No evidence in the pack describes an account application, review process, or status-tracking feature for founders during onboarding; all onboarding evidence relates to time-to-deploy after approval (e.g., ramp-docs-8), not application status tracking.

   ⚑ flag

   Relay✓fullclaimed7/10

   relay-docs-12 directly confirms founders can check application status anytime from the homepage during the 1-2 business day review period, with email notification on decision. missing for 10: no independent/community corroboration of the status-checking UX itself, and no detail on what status states are shown.

   • [claimed-docs] “Most applications are reviewed within 1–2 business days. You can check your status anytime from the homepage — we'll email you as soon as a …”

   proof ↗⚑ flag

Switching

1. founderReplace multiple point solutions for spend, bill pay, and banking with one consolidated platform

   weight 2 · round drawn
   Ramp✓fullcommunity8/10

   Ramp's docs and case studies directly support the story: unified spend/card, bill pay/AP automation, banking/treasury (auto top-up, balances), multi-entity consolidation, and explicit customer proof of consolidating tools (Studs replacing 4 tools, AIRCO fast onboarding vs 6 months). Community evidence corroborates real-world use for expense/card issuance and approvals, reinforcing the platform's breadth beyond marketing claims. Missing for 10: independent case studies verifying bill-pay/banking consolidation claims (not just card/expense), and more third-party evidence on multi-entity/ERP sync accuracy.

   • [claimed-docs] “A vendor invoice is dragged into Ramp, automatically matched to its PO, coded to the right GL account, routed for approval, and paid — 7x fe…”
   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”
   • [claimed-docs] “Studs: Replaced 4 separate tools with Ramp's all-in-one platform”
   • [claimed-docs] “AIRCO: Full onboarding in 1 week vs. 6 months on prior platform”
   • [claimed-docs] “Multi-entity support with entity-level restrictions and consolidated reporting”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

   Relay✓fullcommunity8/10

   Relay documents an all-in-one platform combining multiple checking/savings accounts, cards with spend controls, bill pay with approvals, invoicing/receivables, receipt capture, and accounting sync (QuickBooks/Xero), directly replacing separate spend management, bill pay, and banking tools, and community reviews corroborate the multi-account and interest features in real use. missing for 10: independent case studies explicitly confirming founders consolidated away from other named point solutions, and more hands-on verification of bill pay/invoicing depth beyond docs and one HN mention.

   • [claimed-docs] “Open up to 20 checking accounts and auto-transfer every deposit so you always know what’s tied up and what’s safe to spend.”
   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”
   • [claimed-docs] “Upload bills, delegate tasks, automate approvals, and pay vendors the way they want to be paid.”
   • [claimed-docs] “Create invoices, request payments, offer flexible payment options, and let Relay handle the follow-up.”
   • [claimed-docs] “Build a cash cushion with high-yield accounts and automated rules that help you stay ready for whatever’s next.”
   • [claimed-docs] “Relay syncs ultra-detailed, easy-to-understand transaction data directly into QuickBooks Online and Xero.”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

2. founderFully onboard onto a new banking platform in about a week instead of months

   weight 2 · round to Ramp
   Ramp✓fullcommunity8/10

   Ramp provides a concrete customer proof point (AIRCO: full onboarding in 1 week vs 6 months on prior platform) directly matching the story, plus general positive hands-on feedback about quick setup of cards/expenses. Missing for 10: independent third-party verification of onboarding timelines beyond vendor case studies, and detail on the actual onboarding process/steps for a new customer.

   • [claimed-docs] “AIRCO: Full onboarding in 1 week vs. 6 months on prior platform”
   • [community] “It's what we use for tracking expenses and getting comped for travel, meals, software licenses etc - works great in my experience. I can cli…”

   proof ↗⚑ flag

   Relay~partialcommunity5/10

   Relay shows a fast application review (1-2 business days per relay-docs-12) and easy setup of accounts, cards, and invoicing, suggesting quick onboarding, but there's no explicit evidence of an end-to-end 'week-long' onboarding timeline or migration process from another bank. missing for 10: documented full onboarding timeline/case study, evidence of migrating existing banking relationships/data within a week, independent confirmation of onboarding speed beyond application approval.

   • [claimed-docs] “Most applications are reviewed within 1–2 business days. You can check your status anytime from the homepage — we'll email you as soon as a …”
   • [claimed-docs] “Go to Accounts → Account Details in the Relay app to view your numbers anytime, or generate a bank verification letter from the same screen.”
   • [claimed-docs] “Open up to 20 checking accounts and auto-transfer every deposit so you always know what’s tied up and what’s safe to spend.”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Ramp
   Ramp~partialprobed6/10

   Ramp exposes a documented Developer API with OpenAPI spec, LLM-readable docs, an official MCP server, and even a public CLI, indicating broad programmatic access aligned with AI-native workflows. However, there is no explicit claim or evidence that every UI capability (e.g., hotel rebooking automation, contract intake AI, dynamic approval routing) is fully exposed via the API — only general API/ERP sync and CSV export mentions. Missing for 10: an explicit statement or independent verification of full feature parity between API and UI, and evidence covering advanced workflow features (approvals, travel, intake) being API-accessible.

   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [claimed-docs] “Ramp also supports custom CSV exports and an open API for flexible connectivity.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”
   • [probe] “official MCP server documented at https://support.ramp.com/ramp-mcp”
   • [probe] “official CLI documented at https://github.com/ramp-public/ramp-cli”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”

   proof ↗⚑ flag

   Relay—none0/10

   No evidence pack item mentions a public API, developer platform, or programmatic access to Relay's banking features; all evidence describes UI/app-based workflows (mobile app, web app screens) with no API documentation or endpoints referenced.

   ⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Ramp
   Ramp~partialprobed5/10

   Ramp explicitly supports custom CSV exports and an open API for connectivity, plus a documented OpenAPI spec and developer API, which gives users a path to extract their data in open formats. However, there is no evidence of a full data-portability/export-everything guarantee, no mention of standardized bulk export tooling for account closure, and no independent confirmation of completeness of exports. missing for 10: dedicated 'export all data and leave' documentation, evidence of open/standard format for full account export (not just transactions via API/CSV), independent verification of export completeness.

   • [claimed-docs] “Ramp also supports custom CSV exports and an open API for flexible connectivity.”
   • [claimed-docs] “fetch: /llms.txt (LLM index), /llms-guides.txt (guides index), /llms-guides/<slug>.txt (specific guide), /llms-api.txt (API reference), /llm…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.ramp.com/llms.txt # Ramp Developer API Machine-readable index for Ramp's Developer API documentati…”

   proof ↗⚑ flag

   Relay—none0/10

   Relay is a business banking platform; nothing in the evidence pack mentions bulk data export in open formats (CSV/JSON/OFX) or account portability/closure workflows for users to 'leave' with their data. Accounting sync (relay-docs-3) implies data transfer to third-party software but is not documented as a user-controlled full data export/exit mechanism.

   • [claimed-docs] “Capture receipts, categorize expenses in real time, and sync everything to your accounting software automatically.”

   proof ↗⚑ flag

Access control

1. finance-leadDefine granular user roles and permissions across team members, locations, and departments

   weight 3 · round drawn
   Ramp~partialclaimed5/10

   Ramp docs mention multi-entity support with entity-level restrictions and dynamic approval routing across finance, IT, legal, and security, which implies some role/permission granularity across entities and departments, but there is no explicit documentation of a granular role/permission system covering locations and individual team members. missing for 10: dedicated documentation of role-based access control, granular permission settings per user/location/department, and independent corroboration of these controls.

   • [claimed-docs] “Multi-entity support with entity-level restrictions and consolidated reporting”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”

   proof ↗⚑ flag

   Relay~partialcommunity5/10

   Relay documents role definition, card-level spend limits, and multi-step approval rules (relay-docs-2, relay-docs-17), which supports basic team permissioning, but there's no evidence of granular controls segmented by location or department, nor detailed role-based access management. A community review also notes 'issues with permissions' as a minor complaint (relay-comm-2), suggesting the feature isn't fully robust in practice. Missing for 10: department/location-level permission scoping, audit trail of permission changes, and independent confirmation that role granularity works reliably at scale.

   • [claimed-docs] “Issue Visa® debit³ or credit cards⁴, set spend limits, define roles, and track every transaction in real time.”
   • [claimed-docs] “Multi-step approval rules”
   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

Fraud detection

1. ai-native userHave AI flag anomalous or out-of-policy transactions automatically for review

   weight 2 · round to Ramp
   Ramp~partialclaimed5/10

   Ramp claims a dedicated AI 'fraud prevention' agent alongside auto-coding and dynamic, multi-department approval routing, which implies automated flagging of anomalous or out-of-policy transactions for review (ramp-docs-17, ramp-docs-16). However, there is no detailed documentation of how anomaly detection thresholds work, no explicit 'flag for review' workflow description, and no independent/hands-on evidence corroborating this specific capability. Missing for 10: detailed docs on anomaly/policy-violation detection logic, explicit reviewer workflow, and independent verification of fraud-flagging accuracy.

   • [claimed-docs] “Four AI agents handle auto-coding, fraud prevention, approval routing, and automatic payment”
   • [claimed-docs] “Dynamic approval routing with parallel workflows across finance, IT, legal, and security”
   • [claimed-docs] “Ramp automatically categorizes transactions based on transaction details, historical information, and your team's direct feedback, then sync…”

   proof ↗⚑ flag

   Relay—none0/10

   No evidence in the pack mentions AI-driven anomaly detection, fraud monitoring, or automated flagging of out-of-policy transactions; Relay's documented features are manual controls like spend limits, roles, and multi-step approval rules, not AI-based review triggers.

   ⚑ flag

Customer support

1. founderReach live customer support at any time for urgent account issues

   weight 2 · round to Relay
   Ramp—none0/10

   No evidence in the pack mentions live customer support, support channels, response times, or availability guarantees; the pack only covers product features, integrations, and general community sentiment unrelated to support access.

   ⚑ flag

   Relay~partialcommunity4/10

   Community reviews mention 'helpful customer support' generally, but no evidence specifies 24/7 or live/urgent support availability, response times, or channels (phone/chat). missing for 10: documentation of support hours/availability, urgent-issue escalation process, live-agent channel details, and independent verification of responsiveness during emergencies.

   • [community] “On Trustpilot, Relay has received 776 reviews and has a 4.2/5 rating. Users appreciate the ability to open many accounts, their helpful cust…”

   proof ↗⚑ flag

Deposit protection

1. finance-leadHave deposits automatically swept across partner banks to maximize FDIC insurance coverage

   weight 2 · round drawn
   Ramp—none0/10

   Evidence shows only auto top-up from a linked checking account with balance targets (ramp-docs-6), not a multi-bank sweep program for maximizing FDIC coverage; no mention of partner-bank sweep networks or FDIC insurance expansion anywhere in the pack.

   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”

   proof ↗⚑ flag

   Relay—none0/10

   Evidence shows Relay lets users open multiple checking accounts and automate internal transfers between them (Profit First style) and offers high-yield savings, but there is no mention of a multi-bank sweep network or expanded FDIC coverage across partner banks. missing for 10: any documentation of an FDIC sweep program, partner bank network, or expanded insurance coverage mechanism.

   • [claimed-docs] “Open up to 20 checking accounts and auto-transfer every deposit so you always know what’s tied up and what’s safe to spend.”
   • [claimed-docs] “Open up to 20 checking accounts and nickname them to match your Profit First setup: Income, Profit, Owner's Pay, Taxes, Operating Expenses.”
   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [claimed-docs] “Relay moves idle cash out of operating accounts and into your savings. Earn up to 3.00% APY1 on every spare dollar.”

   proof ↗⚑ flag

Cash automation

1. finance-leadAutomate cash management with auto top-up between accounts and low-balance alerts

   weight 2 · round to Ramp
   Ramp~partialclaimed6/10

   Ramp explicitly documents auto top-up from linked checking accounts with target balance automation and low-balance alerts, directly matching the story, but this rests on a single vendor claim with no independent/hands-on corroboration and no detail on multi-account 'treasury-yield' style cash optimization or yield features. missing for 10: independent verification of auto top-up working in practice, detail on interest/yield optimization across accounts, and community evidence confirming alert reliability.

   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”

   proof ↗⚑ flag

   Relay~partialcommunity5/10

   Relay supports automated transfer rules between accounts by dollar amount or percentage (relay-docs-15) and cash-cushion/high-yield savings automation (relay-docs-6, relay-docs-24), corroborated by a community report of automatic money partitioning (relay-comm-1). However, there is no evidence of a specific 'low-balance alert' notification feature or threshold-triggered auto top-up logic. Missing for 10: explicit low-balance alert/notification capability, confirmation that transfers can be triggered by balance thresholds rather than just fixed schedules/percentages, independent verification of alerting reliability.

   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [claimed-docs] “Build a cash cushion with high-yield accounts and automated rules that help you stay ready for whatever’s next.”
   • [claimed-docs] “Relay moves idle cash out of operating accounts and into your savings. Earn up to 3.00% APY1 on every spare dollar.”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”

   proof ↗⚑ flag

Yield generation

1. finance-leadEarn yield on operating cash balances without moving funds to a separate institution

   weight 3 · round to Relay
   Ramp—none0/10

   The evidence pack mentions auto top-up from linked checking accounts and target balance automation, but there is no mention of Ramp offering interest/yield on operating cash balances held within Ramp itself, nor any treasury/yield product distinct from moving funds elsewhere.

   ⚑ flag

   Relay✓fullcommunity7/10

   Relay offers built-in high-yield savings accounts (up to 3.00% APY) that automatically pull idle operating cash into yield-bearing accounts within the same platform, and community evidence corroborates that tax/reserve balances earn extra interest without moving funds elsewhere. missing for 10: independent verification of actual APY competitiveness/consistency over time, and clearer detail on withdrawal friction or limits on savings-account access for operating cash.

   • [claimed-docs] “Build a cash cushion with high-yield accounts and automated rules that help you stay ready for whatever’s next.”
   • [claimed-docs] “Relay moves idle cash out of operating accounts and into your savings. Earn up to 3.00% APY1 on every spare dollar.”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”

   proof ↗⚑ flag

2. finance-leadBuild a cash cushion in a high-yield savings sub-account with automated transfer rules

   weight 2 · round to Relay
   Ramp~partialclaimed3/10

   Ramp documents auto top-up and target-balance automation with low-balance alerts (ramp-docs-6), which supports the 'automated transfer rules' part of the story, but no evidence explicitly confirms a high-yield savings sub-account or yield-bearing cash cushion feature. missing for 10: explicit high-yield/interest-bearing savings sub-account documentation, evidence of yield rates, and independent corroboration of treasury cash-cushion use case.

   • [claimed-docs] “Auto top-up from linked checking accounts with target balance automation and low balance alerts”

   proof ↗⚑ flag

   Relay✓fullcommunity8/10

   Relay explicitly offers high-yield savings accounts (up to 3.00% APY) plus automated rules to move idle cash from operating accounts into savings, directly matching the story, and community evidence corroborates automated partitioning with interest earned on set-aside funds. Missing for 10: independent verification of actual APY rates achieved and hands-on testing of the automation rule reliability specifically for savings sweeps.

   • [claimed-docs] “Build a cash cushion with high-yield accounts and automated rules that help you stay ready for whatever’s next.”
   • [claimed-docs] “Relay moves idle cash out of operating accounts and into your savings. Earn up to 3.00% APY1 on every spare dollar.”
   • [claimed-docs] “Automate transfers from one to multiple accounts using dollar amounts or percentages.”
   • [community] “Relay does a good job of automatically partitioning money, though you still need to manually execute external payments. Gives you a little e…”

   proof ↗⚑ flag

3. founderEarn interest on balances held in multiple currencies

   weight 1 · round drawn
   Ramp—none0/10

   No evidence in the pack mentions multi-currency accounts, FX holding, or interest/yield on non-USD balances; Ramp evidence covers cards, expense automation, integrations and AI agents but nothing about earning interest on multi-currency balances. Missing for 10: any mention of multi-currency account support, interest/yield rates, or treasury/FX yield features.

   ⚑ flag

   Relay—none0/10

   Relay's evidence shows only USD-based high-yield savings (up to 3.00% APY) and international wire transfers, but no support for holding balances in multiple currencies or earning interest on non-USD balances. Missing for 10: multi-currency account support, evidence of interest-bearing balances in currencies other than USD.

   • [claimed-docs] “Relay moves idle cash out of operating accounts and into your savings. Earn up to 3.00% APY1 on every spare dollar.”
   • [claimed-docs] “How to Activate Receiving International Wires on Relay”

   proof ↗⚑ flag