Okay, team, I need a reality check here. We’ve been using Divvy for about a year now, and as we’ve grown from 20 to 50 people, the bill has just... ballooned. It feels like we’re hitting a wall where the per-card pricing model stops making sense.
I was all in on their "free" platform at first—it’s fantastic for budgeting and the Bill Pay feature is solid. But at $5 per virtual card per month (and we use a LOT for SaaS subscriptions and department budgets), we’re now looking at hundreds just in card fees, before any of the add-ons. Our monthly spend on the platform itself is creeping uncomfortably close to what we pay for some of our core accounting software.
Has anyone else run into this? I’m trying to justify it by looking at the automation we’ve built—the sync to NetSuite is decent, and we’ve automated receipt collection which saved our AP person maybe 10 hours a month. But I’m starting to wonder if we could replicate the core workflow (budgets, vendor limits, reconciliation) with a combo of something like Ramp (flat fee per company?) and a bit more Zapier magic.
Specifically:
* Is the per-card fee just a fact of life with this level of control?
* For those who left, what was the breaking point for you on pricing?
* Any good alternatives that scale better for 50-100 person companies without losing the granular budget features?
Love the platform, but the cost per head is making me question its long-term fit. Would love to hear your experiences. 🚀
Automate everything.
Yeah, that per-card cost really stings at your size. We hit the same wall around 40 people.
The automation savings are real, but the math does change. For us, the breaking point was realizing we were paying for card instances, not active usage. We had dozens of cards for one-time or low-spend vendors just sitting there.
We switched to a platform with a flat fee based on active users, not cards. It did mean rethinking some budget categories, but the cost predictability was worth it. The core workflows you mentioned are definitely replicable elsewhere. Have you talked to their sales about a custom plan? Sometimes they'll bend before they lose you.
Docs save time
You're not alone, that per-card fee really becomes a pain point. The automation savings are real, but it's an accounting problem when your management platform costs rival core software.
To your question about it being a fact of life: not necessarily. The per-card model makes sense if you need a unique card for every single vendor or budget line. But at 50 people, you might be over-segmenting. We consolidated vendor cards (one for all SaaS under $X/month) and moved some department budgets to a single card with strict category limits instead. It cut our card count by 40%.
We did talk to their sales and got a small volume discount, but the structure was the same. We eventually moved to a flat-fee model (not Ramp, another player) and rebuilt the automation. The core workflow is absolutely replicable. The real question is whether the time to rebuild that integration is worth more than your current Divvy bill for the next 12 months. For us, it was.
You've hit on the exact structural weakness in their pricing model at your scale. The per card fee isn't a fact of life for that level of control, it's an architectural choice they've made that becomes punitive for granular budgeting.
I ran a cost analysis for a client last quarter comparing Divvy to a flat fee competitor. At 50 employees with ~120 active cards (a common ratio for granular SaaS/department spend), Divvy's monthly card fees alone were $600. The competitor's all inclusive platform fee was $299. The automation you value, like NetSuite sync and receipt collection, was included. The "control" was identical, it was just implemented via spend category rules and merchant level locks on a smaller set of physical cards, not a proliferation of virtual ones.
Your instinct about Ramp is correct for the core workflow. The trade off you'll evaluate isn't control, but the depth of the native integration. Replicating a deep NetSuite sync might require more than Zapier; you'd need to check if their native connector matches the field mapping and daily sync frequency you rely on. That's where the hidden cost of a switch lies, not in the functionality itself.
You're correct to question it. The >automation you've built, like the NetSuite sync, is a fixed saving. Its value doesn't scale with card count, but its cost does. That's the core mismatch.
At 50 people, you're in a zone where the operational savings are plateauing but the platform's variable costs keep climbing. I've modeled this: if your AP person saves 10 hours monthly at a fully loaded cost of, say, $50/hour, that's $500 in value. If your Divvy card fees exceed that, the platform becomes a net cost center for that function alone. That's the math you need to run.
Ramp's flat-fee model addresses this structurally. The trade-off isn't less control, it's architecting control through category rules on fewer cards, as user1018 noted.
Spreadsheets or it didn't happen.
You're hitting the classic trap of conflating a specific tool's architecture with a necessary cost. That >automation you've built isn't unique to Divvy. It's just logic and API calls.
The per-card fee isn't a fact of life for control, it's a fact of life for *their* business model. You can get the same granular control with category rules and merchant locks on a fraction of the cards. The trick is whether your finance team is disciplined enough to manage budgets in software, not by having 120 separate card numbers to look at.
Moving to a flat-fee platform means you're paying for the automation and features, not for the illusion of organization via card proliferation. It's a better scaling model, period. Zapier might be overkill if you pick a platform with decent native integrations.
null