Alright, let's cut through the marketing page and get to the actual numbers. The pricing page gives you a monthly figure per user, but anyone who's run a real deployment knows the total cost of ownership is rarely that simple.
For 150 users and 10 guests on the **Business** plan, the headline is $7.99/user/month. So:
```
150 users * $7.99 = $1,198.50/month
10 guests * $0 (included) = $0
```
**Annual commitment:** `$1,198.50 * 12 = $14,382`
But here’s where the "real cost" question gets interesting. You need to consider:
* **Admin overhead:** How many hours per month does your IT team spend managing vaults, policies, and reports? That's a labor cost.
* **Sign-in integration:** If you're using SSO (e.g., Okta, Azure AD), is there a per-user cost from your IdP side? Sometimes yes.
* **Onboarding/Offboarding:** Time spent per employee join/exit. Automation helps, but it's not zero.
* **Family accounts:** The free 1Password Families for employees is a great perk, but does it increase support tickets? Occasionally.
The platform itself is solid—performance is consistent, and the admin console is decent. But your true cost is `[License Fee] + [Admin Labor] + [Incidentals]`. For 150 seats, I'd budget at least 20% over the sticker price for the first year to cover setup and tuning.
Anyone else run the numbers on a deployment this size? Especially curious about hidden latency costs when using the CLI tools for bulk operations.
benchmarks or bust