Why did 2X acquire Knownwell in 2026?

Go-to-market services company 2X announced the acquisition of Knownwell on June 10, 2026. Knownwell develops commercial-intelligence and agentic AI systems for B2B organizations.

The transaction combines a large delivery organization with software designed to extract account signals from CRM records, communications, and project activity. The companies said the combined business is valued above $400 million, but they did not disclose the acquisition price or payment structure.

What changed in the 2X and Knownwell deal?

Knownwell founder and CEO David DeWolf became CEO of 2X. 2X founder Dom Colasante remains with the company as founder and a member of the leadership team.

The official 2X acquisition announcement says Knownwell’s engineers, data scientists, and commercial-intelligence specialists will form the foundation of 2X’s AI product layer.

2X reported more than 1,200 specialists and over 200 enterprise clients. It works with platforms including Salesforce, HubSpot, Gong, 6sense, Adobe, Clay, and Google.

What does Knownwell add to 2X?

Knownwell analyzes natural business communications and enterprise data to produce account intelligence. Its stated data sources include Slack, email, CRM records, and project activity.

The combined platform is intended to identify sentiment changes, emerging account concerns, and shifts in customer health. Account managers and customer-success teams could use those signals to prioritize intervention or expansion work.

That is broader than standard CRM reporting. A traditional health score may rely on structured fields and product usage. Knownwell’s approach also interprets unstructured conversations where concerns often appear before someone updates the CRM.

Why combine software with GTM services?

AI sales and customer-success projects often fail between a prototype and daily operation. Models need clean data, system integrations, workflow design, user training, monitoring, and ongoing adjustment.

2X can provide implementation and operational staff while Knownwell supplies the intelligence layer. The model may appeal to enterprises that want one accountable partner for strategy, execution, technology, and managed operations.

The tradeoff is dependency. A combined service-and-software engagement can be harder to replace than a standalone application. Buyers need clear ownership of data, workflows, prompts, integrations, and exported account intelligence.

What should CRM and RevOps teams ask?

Before allowing semantic analysis across customer communications, teams should ask:

• Which channels and CRM objects are ingested?
• Are private messages, attachments, or restricted fields excluded by default?
• How are sentiment and account-health conclusions sourced and explained?
• Can users correct a conclusion and prevent the same error from recurring?
• Which workflows can act automatically, and which require approval?
• What data and configuration can be exported at the end of the engagement?

Sentiment is especially sensitive. A model may misread negotiation language, regional communication style, sarcasm, or a temporary project issue as churn risk. Every material signal should link back to the underlying evidence.

Does the acquisition create a new CRM?

No. The announced model appears to sit across existing CRM, marketing, sales, and customer-success systems. 2X describes a GTM operating system in the organizational sense, but customers may still use Salesforce, HubSpot, or another CRM as their system of record.

This distinction matters for architecture. The CRM should retain authoritative customer and pipeline data, while the intelligence layer derives signals and coordinates work under defined permissions.

What does this mean for B2B sales technology?

The deal reflects a move from isolated AI features toward managed, cross-functional systems. Marketing, sales, and customer success all touch the same accounts, so an agent that sees only one department has incomplete context.

The combined 2X and Knownwell proposition addresses that fragmentation. Its value will depend on whether the company can produce accurate, auditable signals and repeatable outcomes without creating another opaque layer over the CRM.

Organizations considering this model should first resolve the adoption and data problems covered in our guide to why CRM implementations fail and define the responsibilities described in our CRM implementation checklist.