Skip to content
Notifications
Clear all

Thoughts on the agency plan? Is the seat minimum flexible?

3 Posts
3 Users
0 Reactions
0 Views
(@ava23)
Reputable Member
Joined: 3 weeks ago
Posts: 234
Topic starter   [#24700]

Alright, I've been kicking the tires on Anyword's agency plan. On paper, it's the obvious choice for our shop—we manage multiple client brands, need the AI writing, forecasting, brand voice, the whole nine yards.

But that 5-seat minimum is giving me serious pause. We're a lean operation. Some clients just need light copy touch-ups, others are full-service. Realistically, only 2-3 of us would be heavy users. The rest would be logging in once a month to check a score, which feels like burning money.

So my question for anyone else in the trenches:
* Is that 5-seat floor set in stone, or have any of you managed to negotiate a custom deal for fewer "power user" seats? I've heard whispers some vendors will do this if you commit to a longer term.
* What's the actual utility like for the "occasional" user seat? If it's just a glorified reporting dashboard, that's a hard sell.
* Are there any hidden costs or limitations on the number of client accounts/projects under the agency plan? The sales page is suspiciously quiet on that front.

The per-seat pricing in SaaS always feels like a tax on collaboration. I get they need their ARR, but forcing seats that won't be used is a classic vendor move. 👀


Trust but verify.


   
Quote
 annt
(@annt)
Estimable Member
Joined: 3 weeks ago
Posts: 171
 

The seat minimum is often presented as non-negotiable, but my experience in vendor security reviews suggests it's almost always a starting point for discussion. I've seen concessions made for longer contract terms or higher-tier commitments on other modules. You should absolutely push back on that floor, framing it as a long-term partnership with specific, evolving user needs. Treat the negotiation like a risk assessment.

On your point about utility for occasional users, that's where the audit trail gets thin. If the secondary seat is merely a read-only portal, the value proposition collapses. I'd insist on a detailed feature matrix delineating "admin" versus "viewer" permissions before any commitment. The cost of unused seats isn't just monetary, it's a compliance and access control headache.

You're right to be suspicious about quiet sales pages regarding client account limits. That's a common soft cap. I'd draft a direct inquiry asking them to confirm, in writing, any hard limits on active projects or brand voices under the agency tier. If they hedge, consider it a red flag for future scalability.


—at


   
ReplyQuote
(@devops_not_grunt)
Reputable Member
Joined: 5 months ago
Posts: 292
 

I've been on the other side of that "starting point for discussion" and found the floor is often concrete once you actually get to procurement. Sales might nod, but legal and finance teams have these seat bundles baked into their SKUs and revenue models. The real concession usually isn't fewer seats, it's more features thrown in for the same price to make the waste palatable.

Your point about compliance headache is sharper than most realize. Every unused seat is a user profile that needs to be onboarded, offboarded, and audited. I've spent more time cleaning up dormant "viewer" accounts in SaaS tools than I have getting value from them. It's a silent tax.

Treating it like a risk assessment is clever, but flip it. The vendor's risk is you walking away. If you're lean, your negotiation power is pretending you're fine walking away.



   
ReplyQuote