Ramp

Ramp is a corporate card and spend management platform for small businesses, venture-backed startups and mid-market companies. It launched in 2019 with an unusual commercial premise: the software is free and Ramp earns its revenue from interchange, the fee that merchants pay when a card is used. That premise has held through most of the product's life, and it explains why Ramp's onboarding materials focus so heavily on the cost of a subscription rather than on features. The companies that get the most out of it are those with meaningful card volume across software subscriptions, cloud infrastructure, advertising, travel and professional services, and a finance team that wants policy enforcement to happen at the moment of purchase rather than during month-end review.

The regulatory structure is worth stating clearly because it is often misdescribed. Ramp is not a bank. Its banking services, including deposit accounts and card issuance, are provided by partner banks that are members of the Federal Deposit Insurance Corporation, and its cards are issued by those partner institutions under licence from the card networks. Ramp's own contribution is the software layer sitting on top of that banking relationship: the controls, the approvals, the accounting sync and the analytics.

The card programme includes physical and virtual Visa cards. Virtual cards can be issued in seconds for a specific vendor, a specific amount or a specific time window, which makes them practical for one-off purchases, contractor access and trial signups that would otherwise be charged to a founder's personal card. Limits are set per card, per team and per category, and a card can be locked, adjusted or destroyed from the dashboard or the mobile app by whoever holds the right permission. Because every card is tied to a named employee and a cost centre, attribution is automatic rather than reconstructed later.

Policy enforcement is the feature that separates Ramp from a plain card programme. Administrators write rules covering merchant category, merchant name, single-transaction amount, aggregate spend per period and geographic restrictions. Rules can warn, require approval before the transaction settles, or decline outright at authorisation. A rule that blocks purchases above a threshold outside an approved vendor list is enforced by the card network rather than by a spreadsheet review, which is what stops shadow IT spend accumulating in the first place.

Receipt capture is largely automated. Ramp requests receipts by email, SMS or in-app notification after a transaction, and users can photograph one or forward it to a dedicated Ramp address. Extraction reads the merchant, date and line items and proposes a match to the card transaction. Because Ramp sees line-item detail on many software invoices, it can attach the actual invoice rather than a photograph of a card slip.

Accounting sync is deep and bidirectional. Ramp integrates with QuickBooks Online, Xero, NetSuite, Sage Intacct and several other systems, mapping cards to accounts, cost centres to classes and vendors to payables. Transactions post with their receipt and their policy metadata attached, which turns reconciliation into an exception-handling exercise. Ramp also provides a full audit trail of who approved what and when, which is what external accountants and auditors ask for first.

Bill pay extends the platform beyond cards. Vendors who do not accept cards can be paid by ACH, wire or check, and Ramp can issue a virtual card to a vendor who would accept one, converting an accounts payable item into a rewards-earning transaction. Approval workflows, purchase orders, vendor management and Ramp Travel all sit in the same interface, so procurement requests and itineraries land in the ledger rather than in email threads.

The analytics layer is where Ramp makes its savings argument. Ramp Intelligence compares a company's software spend against anonymised benchmarks from similar businesses and flags subscriptions that are unused, duplicated across teams or priced above the median comparable companies pay, along with price increases at renewal and seats that were purchased and never assigned. For a company spending a few thousand dollars a month on SaaS, the detected savings frequently exceed what a paid expense platform would cost.

More recently Ramp has layered artificial intelligence over the same data, with natural language queries into spend patterns, agents that draft expense reports and approve low-risk transactions inside a policy envelope, and automatic categorisation. Most deployments still keep a human in the loop above a modest threshold.

Pricing is the part that requires verification before a decision. The standard Ramp platform has been free, funded by interchange, with no per-user charge for cards, expense reports, bill pay or accounting sync. Ramp has also sold a paid tier, historically marketed as Ramp Plus, which adds advanced controls, deeper multi-entity administration, expanded approval routing and higher support levels, priced per user per month. Ramp's eligibility rules for new customers have shifted over time, including requirements around having a United States business entity, a linked US bank account and a minimum cash balance, and both the minimum balance figure and the paid tier price have changed more than once. Current pricing, tier boundaries and qualification thresholds should be confirmed on Ramp's own pricing page or with its sales team rather than taken from anything published earlier.

Against Brex, Ramp competes on free software plus automated savings detection, while Brex has traditionally been stronger in multi-currency accounts, international payments and treasury products for globally operating startups. Against Expensify, Ramp is card-first with expenses attached, while Expensify is expense-first with a card added later, and Expensify supports reimbursement workflows in far more countries. Against a traditional bank's commercial card, Ramp offers materially better controls, faster virtual card issuance and real accounting integration, without the branch network, relationship manager or lending products.

The limitations are concrete. Ramp requires a US business entity and a US bank account for the core card product, which excludes most non-US companies. There is a minimum cash balance requirement, and underwriting is based on the company's financial position, so very early-stage businesses and those with thin margins may not qualify or may receive small limits. There is no consumer card and no personal use. Lending is not the core product, and companies needing a term loan or revolving credit line will look elsewhere. Multi-entity and advanced approval routing push buyers toward the paid tier. Receipt extraction still needs correction on unusual documents, and the savings recommendations depend on having enough comparable data, so they are weaker for businesses with unusual spend profiles.

Ramp fits United States companies from roughly ten employees upward that spend heavily on software, cloud, advertising and travel and want those purchases controlled at authorisation with clean accounting sync. It does not fit non-US businesses, companies without a meaningful cash balance, organisations that need branch banking or credit facilities, and businesses whose main problem is reimbursing employees in many countries rather than controlling card spend. When comparing alternatives, Ramp is the strongest default for a domestic US company that wants spend controls at no software cost, Brex is the stronger choice for global payments and cash management, and Expensify remains the better fit where reimbursement across borders matters more than card controls.