Per-org pricing, explained

Most SaaS pricing is per-seat per-tier per-cloud. A 30-person team using Sales Cloud + Service Cloud + Marketing Cloud at the right tiers pays $200+/seat/month — $6,000/month for a small team that just wants a real CRM.

We charge per-organization. $39/month. $79/month. Custom. Each tier covers a team up to a size — 25 on Starter, 100 on Business, no cap on Enterprise — and within that, headcount does not change the bill.

Here's why.

Per-seat pricing rewards us for the wrong thing

Per-seat pricing rewards the vendor for adding more seats. It does NOT reward the vendor for making the product more useful per seat. The incentive is backwards: we want to give your team a tool that more people use, not punish you for adopting it widely.

Per-org pricing flips this. We make money when your team gets more value per dollar, not more seats per dollar. Our job is to make the product matter for the work, and we get paid the same whether 12 people or 49 people are using it on the Business plan.

Per-module pricing fragments the product

Look at what happens when CRMs charge per "cloud" or HRIS charge per add-on:

• HubSpot Sales Hub + Service Hub + Marketing Hub at Professional: roughly $1,800/month for 10 seats.
• Salesforce Sales + Service + CPQ + Pardot: easily $250+/seat.
• Zoho One with the Sales/Marketing/Finance/HR bundle: $45/employee.

The per-module model encourages the vendor to split the product — because each "add-on" is an upsell opportunity. Customers end up paying for adjacent capability they may not use heavily, OR they skip the add-on and the integration story falls apart.

Per-org pricing forces us to make the WHOLE PRODUCT worth the price. Every module is in every tier. There's no upsell. We make money if you stay; we don't make money by charging you for things you don't need.

What about heavy AI users?

This is the obvious objection. "If AI is bundled and you charge per org, won't heavy AI users cost you a fortune?"

The honest answer: yes, sometimes. But:

1. AI actions are state-changing, not generative. "Send the invoice" counts as one action. "Summarize the deal" counts as zero. By the time someone is hitting the cap (2,000 actions/day on Business), they're doing real operations, not vibe-coding.

2. The cap is a real cap. If you hit it, the AI waits till tomorrow. No overage fee, no surprise charge. We absorb the upside surprise; we don't let it become your downside surprise.

3. The math works. Per-token cost on a frontier model at our usage rate is bounded by the cap. We've modeled the worst case and it doesn't break us.

The trade-offs we accept

Per-org pricing has real downsides:

• A 90-person company on Business pays the same $79/mo as a 30-person team. That feels weird; intuition says we're leaving money on the table. We are. Past the tier's cap you move up a tier, and the largest teams land on Enterprise where the contract is custom anyway.
• Some buyers want per-seat for budget-tracking purposes. Their finance team is used to seat-counting. We say no at the public price level; Enterprise contracts can negotiate.
• Heavy AI users effectively subsidize light AI users on the same plan. That's true and intentional. The Business plan averages out.

What this means for you

If you're a 30-person agency reading this and currently paying $4,000/month in SaaS: switch to Odexy Business at $79/month and write us a note saying we're wrong about the pricing model. We promise to read it.

— The Odexy team