Skip to content
Notifications
Clear all

My agency's pricing feedback: The per-seat model doesn't work for us.

6 Posts
6 Users
0 Reactions
75 Views
(@ethanv)
Honorable Member
Joined: 4 months ago
Posts: 429
Topic starter   [#11788]

We’ve been trialing Sora for the last two months at our small web dev agency (12 people, about 8 who would actively use a tool like this). I was really excited about the video generation quality and the API options, but we’ve hit a wall with the pricing.

The per-seat model forces us to make a tough choice: either buy licenses for everyone (which is overkill, as not everyone needs daily access) or constantly juggle a couple of shared logins, which kills accountability and breaks any individual workflow history. It’s clunky and frankly feels at odds with how a creative team actually operates.

Here’s our core issue:
* **Project-based usage:** Video needs spike around specific client deliverables. We might have 3 people needing heavy access for two weeks, then barely anyone the next month.
* **Role variability:** Our designers need it for storyboards, devs for placeholder content, and project managers for client pitches. They don’t all need it at the same time or with the same frequency.
* **Cost predictability:** A flat per-seat monthly fee is hard to justify during quieter periods, making it a constant "are we getting value?" conversation.

I’d love to see a model that offers more flexibility. Something like:
* A small base fee for the team workspace, plus consumption-based credits for actual generation.
* Or, a pool of seats that can be dynamically assigned to active projects.
* Even a "light" seat option with lower priority or generation limits would be better than the all-or-nothing approach.

The tool itself is impressive, but the pricing structure is a real barrier to adoption for us. I’m curious if other agencies or small teams have found a workaround, or if Sora is considering more flexible plans.


Ship fast, measure faster.


   
Quote
(@infra_architect_rebel_alt)
Honorable Member
Joined: 6 months ago
Posts: 487
 

Spot on about the per-seat model being a poor fit for project-based work. It's a classic case of a pricing strategy built for a different kind of customer, probably an internal enterprise team where heads are static.

Your juggling shared logins scenario is exactly the kind of operational debt these models create. You end up spending more time managing the license than using the tool, and you lose all the telemetry on who did what. I've seen teams resort to a dedicated "service account" user just to run up the bill, which makes forecasting impossible.

Have you pushed your account rep for a pooled credit system? Some of these AI services offer a monthly credit allowance that can be consumed by anyone authenticated via SSO, without individual named seats. It's often buried as an "enterprise" feature, but for 12 people, you might have the leverage to ask. If they say no, that tells you everything about their market focus.


keep it simple


   
ReplyQuote
(@data_skeptic_ray)
Honorable Member
Joined: 8 months ago
Posts: 429
 

"Buried as an 'enterprise' feature" is the key phrase there. Vendors love to use that to gatekeep a sensible pricing model, reserving it for the whales while the minnows get the rigid per-seat setup. It's a market segmentation tactic disguised as a feature.

But even a pooled credit system has its own forecasting nightmare, just of a different flavor. Now you're watching a communal meter drain, and you get to have the monthly argument about who burned through the credits on experimental renders. At least a seat gives you a named culprit.

Have you actually seen a vendor be transparent about the per-credit cost structure? Or is it always a black box where you just get an invoice for "overage"?


Data skeptic, not a data cynic.


   
ReplyQuote
(@charlie9)
Reputable Member
Joined: 4 months ago
Posts: 284
 

It's not just a black box, it's often a bait-and-switch. They'll happily show you the "clear" per-credit cost during the sales demo, but that model only exists on paper until you commit. The real invoice comes with the nebulous "platform fee," "support premium," and the ever-popular "infrastructure surcharge" that makes unit costing a fantasy.

You're right about the communal meter, but at least that's an internal fight. The vendor's opaque overage model is a declaration of war. And they always win.


Show me the TCO.


   
ReplyQuote
(@jenniferm)
Trusted Member
Joined: 4 months ago
Posts: 43
 

Totally hear you on the project-based usage spikes. That's exactly how my last agency ran into trouble with a design tool.

We ended up having to buy a seat for a freelancer for just one project, which felt ridiculous. It made the whole tool feel like a liability, not an asset.

Did your Sora rep even acknowledge this as a common issue for agencies? Or was it just the standard enterprise line?


Learning every day


   
ReplyQuote
(@garethp)
Estimable Member
Joined: 4 months ago
Posts: 226
 

The freelancer seat problem is a direct consequence of the per-seat model's rigidity. It transforms a flexible resource into a fixed capital expense, which is anathema to project-based economics.

In my experience, reps rarely acknowledge this as an *agency-specific* flaw. They're trained to sell into IT departments where headcount is relatively stable. The standard line is, "You can deprovision and reprovision seats as needed," but that ignores the administrative lag and the reality of urgent project timelines. You can't tell a client you're waiting on a license reactivation.

The real failure is that vendors see this as a pricing problem to be negotiated away with discounts, not a fundamental workflow mismatch. A discount on a bad model still leaves you with a bad model.


Plan the exit before entry.


   
ReplyQuote