What do practitioners actually say about Ramp when they are not on a vendor review page, and what is the strongest case against the company and its model?
## Question
What do practitioners actually say about Ramp when they are not on a vendor review page, and what is the strongest case against the company and its model?
---
Parent: #1
Sentiment is bimodal, not rosy. The core card + expense product is genuinely well-liked across G2 (~4.8), Capterra (4.9), TrustRadius (~9.1) and — more tellingly — on Hacker News, where commentary is unsolicited. Note Trustpilot sits at 3.5, and unsolicited channels skew more critical than vendor-solicited ones.
Recurring complaints. No bulk editing of coding fields; shallow reporting for enterprise needs; bill-pay gaps; ~3% FX fees; and above all support that has not scaled — priority support is reserved for paid tiers, so some of this is a monetization choice rather than an operational failure.
The two structural criticisms that matter for anyone copying the model:
Interchange fragility. Forbes (Kauflin, Mar 2026) argues Ramp's headline revenue is gross, not net of interchange pass-through and rewards — real net revenue possibly 40%+ lower, implying a ~50x effective multiple. Durbin-style cap expansion is an existential regulatory risk. And the self-cannibalization bind, stated by a bullish source: "If the product works, customers spend less. If customers spend less, interchange revenue shrinks."
The free line moved. In 2026 Ramp put previously-bundled features (multi-entity, multi-currency reimbursement, NetSuite/Sage integrations, procure-to-pay) behind the $15/user Ramp Plus tier — roughly $9k/yr for a 50-person team that did not exist before. Multiple sources now name this as a churn trigger. This is the single most transferable warning: if you promise a side 'free', draw that line where your costs do not scale with their usage.
Churn triggers. Credit-limit volatility from real-time balance underwriting (limits cut automatically, no external alert); the Ramp Plus paywall; multi-entity and heavy-ERP gaps.
Competitive boundary. Analysts name Bill.com's two-sided network as lock-in Ramp lacks — "I still use it because the companies who pay me use it." Ramp handles AP but not AR. This is the strongest structural argument in favour of a two-sided design.
Insider sentiment. Engineering and product read strongly positive. Sales/GTM carries essentially all the negative signal — 'toxic', 65–80 hour weeks, and RepVue showing only ~1% of reps hitting annual quota.
## Resolution
**Sentiment is bimodal, not rosy.** The core card + expense product is genuinely well-liked across G2 (~4.8), Capterra (4.9), TrustRadius (~9.1) and — more tellingly — on Hacker News, where commentary is unsolicited. Note Trustpilot sits at 3.5, and unsolicited channels skew more critical than vendor-solicited ones.
**Recurring complaints.** No bulk editing of coding fields; shallow reporting for enterprise needs; bill-pay gaps; ~3% FX fees; and above all **support that has not scaled** — priority support is reserved for paid tiers, so some of this is a monetization choice rather than an operational failure.
**The two structural criticisms that matter for anyone copying the model:**
1. **Interchange fragility.** Forbes (Kauflin, Mar 2026) argues Ramp's headline revenue is gross, not net of interchange pass-through and rewards — real net revenue possibly 40%+ lower, implying a ~50x effective multiple. Durbin-style cap expansion is an existential regulatory risk. And the self-cannibalization bind, stated by a *bullish* source: *"If the product works, customers spend less. If customers spend less, interchange revenue shrinks."*
2. **The free line moved.** In 2026 Ramp put previously-bundled features (multi-entity, multi-currency reimbursement, NetSuite/Sage integrations, procure-to-pay) behind the $15/user Ramp Plus tier — roughly $9k/yr for a 50-person team that did not exist before. Multiple sources now name this as a **churn trigger**. **This is the single most transferable warning: if you promise a side 'free', draw that line where your costs do not scale with their usage.**
**Churn triggers.** Credit-limit volatility from real-time balance underwriting (limits cut automatically, no external alert); the Ramp Plus paywall; multi-entity and heavy-ERP gaps.
**Competitive boundary.** Analysts name **Bill.com's two-sided network as lock-in Ramp lacks** — *"I still use it because the companies who pay me use it."* Ramp handles AP but not AR. This is the strongest structural argument in favour of a two-sided design.
**Insider sentiment.** Engineering and product read strongly positive. Sales/GTM carries essentially all the negative signal — 'toxic', 65–80 hour weeks, and RepVue showing only ~1% of reps hitting annual quota.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Question
What do practitioners actually say about Ramp when they are not on a vendor review page, and what is the strongest case against the company and its model?
Parent: #1
Resolution
Sentiment is bimodal, not rosy. The core card + expense product is genuinely well-liked across G2 (~4.8), Capterra (4.9), TrustRadius (~9.1) and — more tellingly — on Hacker News, where commentary is unsolicited. Note Trustpilot sits at 3.5, and unsolicited channels skew more critical than vendor-solicited ones.
Recurring complaints. No bulk editing of coding fields; shallow reporting for enterprise needs; bill-pay gaps; ~3% FX fees; and above all support that has not scaled — priority support is reserved for paid tiers, so some of this is a monetization choice rather than an operational failure.
The two structural criticisms that matter for anyone copying the model:
Churn triggers. Credit-limit volatility from real-time balance underwriting (limits cut automatically, no external alert); the Ramp Plus paywall; multi-entity and heavy-ERP gaps.
Competitive boundary. Analysts name Bill.com's two-sided network as lock-in Ramp lacks — "I still use it because the companies who pay me use it." Ramp handles AP but not AR. This is the strongest structural argument in favour of a two-sided design.
Insider sentiment. Engineering and product read strongly positive. Sales/GTM carries essentially all the negative signal — 'toxic', 65–80 hour weeks, and RepVue showing only ~1% of reps hitting annual quota.