Which 11x plan is right for me?
Choose between 11x Growth, Pro, and Enterprise. A decision guide based on volume, team size, languages, and enterprise requirements like SSO and custom DPAs.
Pick the tier by whichever constraint binds first: volume, seats, languages, or enterprise requirements. Most teams are sized by volume, but a single security requirement — SSO, a custom DPA, or Alice API access — moves you to Enterprise regardless of how small your volume is. Decide the worker first, then the tier.
Who this applies to: anyone evaluating 11x or considering a tier change. For the underlying numbers, see the pricing overview.
Step 1 — Choose the worker
| Start with | If your problem is | Then read |
|---|---|---|
| Alice | Not enough qualified pipeline entering the funnel; SDR capacity is the constraint | Alice overview |
| Julian | Inbound leads going cold before a rep reaches them; response time is the constraint | Julian overview |
| Both | You have real inbound volume and a pipeline gap | Run one ICP definition across both |
Buy one first even if you'll eventually run both. Launching both simultaneously makes it much harder to attribute results to a configuration, and configuration quality is what determines whether this works.
Step 2 — Find the constraint that binds first
Work down this list. The first row you answer "yes" to sets your floor.
| Requirement | Minimum tier |
|---|---|
| Need SSO | Enterprise |
| Need custom integrations | Enterprise |
| Need a custom DPA or SLA | Enterprise |
| Need Alice API access | Enterprise |
| Need unlimited seats | Enterprise |
| Need 10,000+ prospects/month (Alice) | Enterprise |
| Need 50,000+ calls/month (Julian voice) | Enterprise |
| Need multi-language outreach (105+ languages) | Pro |
| Need more than 5 seats | Pro |
| Need more than 2,000 prospects/month (Alice) | Pro |
| Need voice cloning or simulated testing (Julian) | Pro |
| Need more than one Julian use case | Pro |
| None of the above | Growth |
Security and procurement requirements are the most common surprise. If your company mandates SSO or a negotiated DPA, that decides your tier before volume ever enters the conversation — surface it early rather than after you've been quoted for Growth.
Step 3 — Size your volume honestly
Volume is the main driver of the quote, and both over- and under-sizing cost you.
The unit is new prospects per month, not emails sent.
Work it out from the bottom up:
- How many meetings per month do you need?
- What meeting rate do you expect per prospect contacted? Be conservative for a first quarter.
- Divide. That's your prospect volume.
Because Alice is priced per prospect rather than per send, don't inflate volume to buy "more activity." Adding channels and lengthening cadences is free. A smaller, better-targeted prospect list on a longer multi-channel cadence usually beats a bigger list on a short one — at the same price.
| Tier | Prospects/mo | Seats |
|---|---|---|
| Growth | 2,000 | 5 |
| Pro | 5,000 | 10 |
| Enterprise | 10,000+ | Unlimited |
Julian is sized per channel, and concurrency matters as much as total volume.
- Total volume — calls or chats per month, from your actual inbound numbers
- Concurrency — how many simultaneous conversations at your busiest moment. Growth allows 3 concurrent calls; Pro allows 10.
Concurrency is the constraint teams underestimate. If your inbound arrives in bursts — after a webinar, a launch, or a campaign send — average monthly volume can sit comfortably inside Growth while your peak exceeds 3 concurrent calls. Size for the peak, not the average.
| Tier | Calls/mo | Concurrent | Chats/mo |
|---|---|---|---|
| Growth | 2,000 | 3 | 3,000 |
| Pro | 4,000 | 10 | 7,000 |
| Enterprise | 50,000+ | Advanced routing | 100,000+ |
Step 4 — Decide what support you need
Support level differs meaningfully across tiers, and it's worth weighing if this is your team's first AI GTM deployment.
| Growth | Pro | Enterprise | |
|---|---|---|---|
| Onboarding | Standard, 2 weeks | Dedicated, 2 weeks | White-glove, 4 weeks |
| Support | Standard | Dedicated + Slack channel | Dedicated CSM + forward-deployed engineer |
| Ongoing reviews | — | — | Weekly optimization reviews |
Configuration quality — the knowledge base, the ICP definition, the call flow — is what determines results. If nobody on your team owns that work full time, the dedicated onboarding on Pro and above is doing more than it looks like on a feature matrix.
Common scenarios
Next steps
Pricing overview
Full tier tables and contract terms.
Security and compliance
What your security review will ask for.
Getting started as an Admin
What happens once you've bought.
Get a quote
Pro and Enterprise are custom-priced.
Still need help
Email support@11x.ai or book time with the team to size a tier against your actual volume.