Skip to content
NagentNagent
Log inSign upHire your AI team
Atlas/11x
Vendor dossier / BDR / SDR

11x

Digital sales workers for prospecting, outreach and phone-based engagement.

REVIEWED 29 SEPTEMBER 2026SalesNO HANDS-ON BENCHMARK

What it is

Official-source notesBDR / SDRscaling

11x promotes Alice for research, multichannel prospect engagement, replies and meetings, and Julian for phone conversations. Pipeline and autonomy outcomes are vendor claims. [V1] [V2]

Documented means the statement is present in the cited material. Capability effectiveness, customer outcomes and security assurances have not been independently audited here.

Promoted use cases

  • Research and prioritize prospects
  • Run multichannel outbound
  • Handle phone engagement and qualify meetings

Sales-development AI ranges from data enrichment to autonomous outreach. Research quality, contact permissions, sending infrastructure, reply handling and qualification are separate responsibilities. A buyer should compare the portion of the revenue motion each vendor actually owns and the amount of human supervision required to protect reputation and data quality.

Pricing and buying model

Published commercial evidence

From $3,750 / month

Alice Growth card, billed annually: 2,000 new prospects/month and up to five end users. Its FAQ gives a conflicting $36,000/year starting figure; confirm the contract total.

Check current commercial source ↗

Budget for implementation, model and tool usage, data, human review and ongoing support. Credit units and outcome definitions differ between vendors. A missing numeric rate is marked unverified rather than replaced with an old third-party estimate.

Collaboration and governance

The site claims enterprise security. Request evidence for suppression, escalation, domain safety and approval controls at the action level.

The relevant unit of control is permission to contact a prospect or change a CRM record. Inspect who can propose, approve, execute, interrupt and audit that action. Shared seats, shared content and a shared live agent session are different capabilities; require a demonstration of the one your process needs.

Evaluate memory correction, permission revocation and release control for updated instructions. An improvement loop should preserve the original evidence, proposed change, test results and named approver. A safety or security badge alone cannot establish those workflow properties.

Review and customer evidence

A visible G2 reviewer says its account manager showed how Alice could support research while staff sent the emails themselves. This is useful evidence of one human-in-the-loop mode, not proof that all deployments use it. The broader review page includes vendor product description and user feedback that must be kept separate.

Before relying on a testimonial, confirm the exact product, version, package, workload and baseline. Ask a relevant customer about setup effort, failed cases, ongoing manual work and support after launch. This dossier does not convert customer logos or vendor-hosted awards into independent proof.

Focused feature documentation

Focused documentation check · Sep 2026

Alice outbound ownership and commercial metric

11x’s Alice documentation describes an outbound digital worker that decides contacts and messaging from configured inputs. Its product page promotes account research, personalized outreach and meeting generation; published customer averages and “self-learning” statements are vendor claims. Alice is a focused SDR operator, so it should be measured against a real outbound team workflow, not treated as a general shared agent workspace.

The live Alice Growth card publishes a starting $3,750 per month billed annually for 2,000 new prospects per month and up to five end users, with managed mailboxes and bidirectional CRM sync; Pro and Enterprise are custom quoted. The same page’s FAQ says it starts at $36,000 per year, which conflicts with $3,750 times twelve ($45,000). Treat the annual contract price as unresolved until 11x confirms it in a quote. 11x describes pricing per new prospect rather than per send, so three or thirty touchpoints do not change that unit.

Alice’s personalization documentation distinguishes three outbound modes: review each message, a named-person approval step, and autopilot without per-message approval. These are published configuration choices, not proof of how a particular account is set up. Pilot with suppression lists, a corrected account fact, an email rejected by a reviewer and a reply needing human escalation. Audit what actually went out and how the sales rep receives context. The FAQ and pricing language should not be substituted for live tenant evidence.

Primary sources: Official Alice documentation ↗ · Official Alice pricing page and conflicting FAQ ↗ · Official Alice review and autonomy modes ↗ · Official Alice use cases ↗

Published documentation and public illustrations; account behaviour was not independently tested.

Visual source

Public 11x source page captured 22 September 2026
11x · Public page captured 22 Sept 2026. Vendor presentation, not an authenticated product test. Open source ↗

Fit, limitations and proof requests

Editorial assessment

11x is a direct comparator for a sales-development outcome, not necessarily a shared cross-functional workspace. Meeting quality and domain impact matter more than activity volume.

Priority question: Can we review reply handling and stop all active sequences immediately when a suppression rule changes?

The evaluation owner should be the sales-development and revenue-operations leads. Use accepted opportunities and qualified meetings that actually occur as the business target. Judge the solution in its own stack role: a cloud runtime, a specialist production tool and a managed AI team can be complementary purchases.

Use-case evaluation plan

Research that improves account selection

Start with the same account list and ideal-customer criteria. Ask for sourced research, a relevance explanation and a confidence assessment. Include ambiguous companies and stale contacts. Score whether the resulting priorities are useful to experienced representatives, not whether the system can fill every field.

Measure: factual accuracy, accepted accounts, data freshness and enrichment cost.

A controlled outbound sequence

Prepare outreach using approved claims and a suppression list. Add a reply that expresses disinterest, a referral to another person and a question the agent cannot answer. Test whether the workflow updates state, stops inappropriate follow-ups and escalates with a concise handoff.

Measure: reply handling, suppression compliance, review effort and domain-health indicators.

Meetings to accepted pipeline

Define qualification and attendance before the pilot. Audit booked meetings for fit, genuine interest, duplicates and no-shows. Follow the cohort into sales acceptance rather than counting calendar invitations as revenue. Record human effort spent repairing poor bookings and misleading personalization.

Measure: held qualified meetings, sales acceptance, pipeline progression and total cost per accepted opportunity.

Detailed comparison

Read the detailed Nagent vs 11x guide for operating models, shared context, governance, cost, evidence gaps and a staged pilot.

Nagent vs 11x

Sources and evidence register

Nagent · Multiplayer AI for growth teamsResearch: 21–29 September 2026 · Public-source analysis, no hands-on benchmark · Sources & method