Research: Ramp's online sentiment and the critical case #8
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.