1Password Teams or Business? Price the 10-Seat Jump

The awkward 1Password choice starts around the eleventh person. Teams Starter Pack has a low flat base price, while Business is priced per member and adds controls that some developer teams need before they get large.

Commercial note: links through loke.dev/go are measured as outbound clicks. The 1Password link is currently direct and earns no commission. 1Password runs an affiliate program through CJ, but this site is not enrolled.

I use 1Password personally and would recommend it. That experience informs the practical workflow emphasis in this guide, but it is not a claim that I have deployed every Business control or tested every plan limit.

Use the 1Password Teams vs Business calculator to compare your current quote, member and guest counts, required controls, and first-year rollout work. It stores no input.

The short answer

Teams Starter Pack is the simpler price reference for up to 10 members when basic shared vaults, permissions, recovery, and developer tools cover the job. Business becomes the useful reference when the team needs custom groups, identity-provider integration, automated provisioning, stronger reporting, security-event export, or organization policies.

Do not choose from seat count alone. A 7-person company can need Business controls. An 11-person company may only need shared vaults, but it must get a real quote because the public pricing and support wording do not produce a reliable extra-seat total.

Current pricing has a documentation mismatch

On 24 July 2026, the official 1Password pricing card showed Teams Starter Pack at $24.95 USD per month for 10 members and Business at $8.99 USD per member per month. Both references used annual billing.

On the same product surface, some explanatory copy still described the Teams price as $19.95. That older amount also appears in other localized product copy. Treat the pricing card as a current reference, not a guaranteed invoice, and verify checkout or a written quote.

The public card says Teams can add up to 10 additional seats at per-member pricing, but it does not expose that extra-member price. Support documentation says to contact support when adding members beyond the included group. The calculator leaves that price at zero until you enter a quote.

Teams monthly = base price + extra members × quoted extra-member price

Business monthly = active members × quoted Business seat price

Use the same currency, billing term, promotion status, and tax treatment for both sides. A first-year discount compared with a standard renewal is not an equal comparison.

The 10-member boundary needs a quote

The current subscription billing policy says Teams Starter Pack includes 10 team members and 5 guests. It tells customers to contact support for additional members or guests. Business bills for each team member and includes 20 guests.

For 11 to 20 members, ask for these items in writing:

• the monthly or annual extra-member price for Teams
• the maximum Teams member count offered to this account
• the renewal price after any promotion
• the included and additional guest price
• the payment method, invoice timing, tax, and cancellation terms

Do not assume a sales minimum or exception from a forum post. Account eligibility and procurement terms belong in the quote.

Business-only requirements can settle the choice

The public plan comparison places several controls on Business rather than Teams Starter Pack. Verify the exact current table, but use these as early gates:

• custom groups for organizing access and delegating administration
• identity-provider login or automated user and group provisioning
• custom reports, stronger activity review, or SIEM event streaming
• administrative and security policies that must be enforced centrally

A required control makes the lower Teams price irrelevant. Record the control, the owner who needs it, and the evidence that it exists in the quoted plan.

1Password’s current groups documentation says custom groups are available with Business. Built-in groups still exist in Teams, so define the access model before treating custom groups as mandatory.

Developer tools do not remove the plan review

The current plan table lists developer tools across Teams and Business, including SSH key signing, Git commit signing, CLI, and SDKs. That does not mean every developer workflow has the same limits or administration.

The service-account rate-limit documentation publishes different limits for Teams and Business. Teams uses an account-level read/write reference, while Business lists a larger per-service-account read reference. Confirm current limits against the automation’s request pattern.

For scripts, the 1Password CLI guidance recommends service accounts for least-privilege access to specific vaults. It documents op run, op read, and op inject as ways to supply secrets without placing plaintext values directly in a script.

A password manager is not automatically the deployment secret store for every workload. Human access, local development, CI, production runtime, and emergency access have different identities and rotation needs.

For each machine-used credential, write down:

• which workload needs it and from which environment
• the smallest vault and item access it needs
• how the workload authenticates without a person present
• where the bootstrap token is stored and rotated
• what happens when 1Password or the network is unavailable
• how access is logged, reviewed, revoked, and tested

Never move a production secret into a developer vault merely to make a demo easier. Start with a non-production item and test denial as well as success.

Guests are not cheap substitute members

The current guest documentation says Teams includes 5 guests and Business includes 20. A guest can access one vault at a time.

Use a guest for a contractor or collaborator who genuinely needs one limited vault. A person who needs several team vaults, developer tools, recovery, or normal employee access should be modeled as a member.

Count future members separately from guests in the calculator. Misclassifying people to reduce the invoice creates access work and can produce a poor offboarding trail.

Add rollout work to the first-year budget

Subscription price is only one line. A useful rollout also includes account-region selection, owner setup, recovery, vault design, data cleanup, import, device enrollment, training, browser settings, CLI tests, and offboarding.

First-year total = 12 × subscription + initial rollout hours × hourly value + 12 × monthly administration hours × hourly value

Suppose 8 members use the current $24.95 Teams reference. If onboarding and setup take 10 hours in total, monthly administration takes 1 hour, and time is valued at $50 per hour, the first-year estimate is $1,399.40. Business at $8.99 per member produces $1,963.04 with the same rollout work.

Those values are calculator examples, not a claim that a rollout always takes that long. Replace them with a pilot log.

Sweden: choose the account region deliberately

1Password’s region documentation says an account can be created in the United States, Canada, or European Union region. The region determines billing currency and where secure data is hosted. The EU region uses EUR and hosts secure data in the EU.

For a Swedish organization, the EU account is the natural candidate to assess, but region does not complete a GDPR review. Check the data processing terms, subprocessors, support access, retention, legal roles, internal purpose, and employee information.

The region page says changing region requires moving data to a new account. Choose the region before inviting the team, then confirm the sign-in domain in onboarding material and recovery instructions.

Use the real EUR invoice for Swedish accounting. VAT treatment, promotions, renewal dates, card fees, and rounding can make a converted USD estimate wrong.

Design recovery before importing credentials

Name at least two account owners, keep owner count small, and test recovery with a pilot member. Store emergency instructions somewhere the team can reach when the password manager is unavailable.

Decide what happens when a person leaves, a device is lost, a shared credential is exposed, an owner is unavailable, or a service account token appears in a log. A plan purchase without these procedures is unfinished.

The current Business security practices recommend limiting Owners and Administrators and using custom groups to grant narrower administrative permissions. Teams should apply the same least-access idea with the controls it provides.

Run a two-week pilot

Use a small group with a developer, an administrator, and a non-technical colleague when possible. Test:

• account creation in the intended region and successful recovery
• one shared vault with deliberate read and edit permissions
• one contractor-style guest with only the intended vault
• one SSH or CLI workflow against non-production credentials
• one offboarding exercise that revokes access and rotates what must change
• one denied action proving a member or workload cannot reach another vault

Record setup time, help requests, recovery friction, missing controls, and ongoing admin work. Update the calculator from the pilot rather than a vendor efficiency claim.

Choose Teams Starter Pack when

• the member count and written extra-seat terms fit the plan
• built-in groups and vault permissions cover the access model
• guest limits match people who truly need only one vault
• developer-tool limits fit tested CLI, SSH, and automation workloads

Choose Business when

• custom groups, identity integration, provisioning, reports, SIEM export, or policies are required
• per-member pricing is lower than the complete Teams quote
• the larger guest allowance or service-account limits solve a measured requirement
• the access model needs stronger delegation as the organization grows

Make the quote prove the decision

Attach the feature list, member and guest assumptions, region, currency, billing term, renewal price, pilot findings, and recovery owner to the purchase decision. Recheck the plan before renewal because pricing and packaging can change.

Run the current numbers in the Teams vs Business calculator. If 1Password still fits, check the live plans and request a written quote for every price the public page does not show.