Should 11x acquire Avoma in 2027?

The two companies are operational opposites, and that decides the deal

Almost every question in this analysis resolves once you look honestly at what each company actually is, because the acquirer's profile determines what it can afford and the target's profile determines what it will accept.

11x is an AI-native sales-execution company built around autonomous "digital workers": Alice, an AI sales development rep that researches accounts, writes and sends outbound sequences, and books meetings; and Julian, an AI phone agent. The pitch was always replacement rather than assistance — digital workers positioned as substitutes for human SDRs, priced and sold on that promise. It raised roughly $74M across a seed round, a Series A led by Benchmark, and a Series B led by Andreessen Horowitz, all against a hypergrowth thesis. By 2025–2026 it had also become a widely reported cautionary tale: press investigations and former-customer accounts alleged inflated ARR figures, customer logos on the site belonging to accounts that had churned or never fully deployed, elevated churn, and autonomous output that needed substantial human cleanup. Whatever the final truth of those disputes, the market-facing consequence is real — 11x enters 2027 as a high-burn, venture-dependent company with a contested revenue number, a credibility problem, and finite runway.

Avoma is the inverse on nearly every axis. Founded in 2017, it is an AI meeting assistant and conversation-intelligence platform: it records, transcribes, and summarizes sales and customer calls, extracts action items, scores conversations, surfaces coaching and deal insights, and writes structured notes back into the CRM. It raised comparatively little — on the order of $15M–$18M across seed and Series A from investors including Storm Ventures — and then deliberately stopped raising and grew on its own cash. Its motion is product-led with transparent, low pricing: per-seat plans in the tens of dollars per month, annual contract values frequently under $5,000, a broad base of small and mid-market customers, and strong gross retention. A defensible 2027 estimate puts Avoma somewhere in the $15M–$30M ARR range — durable, growing at a healthy but not explosive rate, and profitable or close to it.

Set those side by side and the shape of the deal is already visible. One company burns venture capital to chase a growth story; the other refused dilution for the better part of a decade to keep control of a profitable business. The asset that makes Avoma worth buying — capital efficiency, retention, a bottom-up motion that doesn't require an expensive sales org — is precisely the asset most likely to be destroyed by absorption into a high-burn parent that needs to show synergy fast. The thing you would be paying a premium for is the thing the acquisition would break.

There is a second consequence that corp-dev decks routinely skip: a profitable, founder-controlled company has no forcing function. Avoma's founders are not running out of runway, are not facing a preference stack that wipes them out at a low exit, and are not answering to investors who need a fund-cycle return. They can say no indefinitely, and every month they say no, their business is worth slightly more. That is the strongest negotiating position in software, and it belongs entirely to the seller.

The alternatives ladder that beats a full acquisition

Rejecting the acquisition does not mean the two companies have nothing to do with each other. There is a ladder of lighter-weight moves, and each rung reaches most of the same destination with a vehicle 11x actually has.

Commercial partnership with deep product integration. 11x books the meeting; Avoma is the recommended conversation layer; call outcomes flow back into 11x's targeting and messaging via API. Structure it as a mutual referral or revenue-share — typically 10–20% of first-year contract value on referred deals, well inside normal partner-program economics. Cost of capital: effectively zero. Engineering cost: a bidirectional integration of this type is realistically one to two engineers for a quarter on each side. It delivers the entire full-funnel customer narrative — "our AI books it, our partner's AI runs and analyzes it" — with no purchase price, no integration tax, no culture merge, and no lockup. Critically, it is reversible. If the joint motion doesn't convert, both sides walk with a lesson and a working integration.

Narrow IP license or acqui-hire. If what 11x genuinely wants is conversation-AI capability in-house rather than Avoma-the-business, it can license transcription and summarization technology or hire a small team outright, in the single-digit millions. This is roughly two orders of magnitude cheaper than the acquisition and gets 11x the capability without buying a customer base it overlaps with anyway.

Build it. In 2027, speech-to-text and call summarization are available as commodity API calls from multiple providers, and foundation models handle conversation understanding and basic coaching inference well out of the box. A competent call-capture-and-summary layer inside 11x's own product is a quarter or two of engineering work, not a $200M purchase. The capability is no longer scarce, and paying a control premium for a non-scarce capability is close to definitionally a mistake.

Do neither, and fix the core. The least glamorous option is probably the highest-return one. A company facing public disputes about its revenue figures, elevated churn, and a gap between marketing and product reliability should spend 2027 closing that gap. Every dollar and every week of executive attention spent on an adjacency is a dollar and a week not spent on the one thing that determines whether 11x is fundable in 2028.

Ranked by risk-adjusted return, the ladder runs: fix the core, partner, license or build, and only then — a distant last — acquire. The full buy is the only rung that requires money 11x doesn't have and attention it can't spare.

How to decide between them

The decision is not a coin flip between "buy" and "don't buy." It is a sequence of gates, and a disciplined acquirer walks them in a specific order — cheapest disqualifier first, so you stop spending diligence dollars the moment a fatal gate closes.

The order matters. Financing is the cheapest test to run and the hardest to fix, so it goes early. Seller willingness is nearly free to assess — one conversation — and kills more deals than valuation does, so it goes early too. Strategic fit and integration planning are expensive to evaluate properly, so they come after the cheap gates have cleared. Running the gates in the wrong order is how companies spend six figures on bankers and lawyers underwriting a deal that a two-hour financing conversation would have killed on day one.

Apply the same gates to the alternatives and they clear easily. A partnership needs no financing, no seller consent beyond a commercial agreement, no scarcity assumption, no base consolidation, and no culture merge. That asymmetry — five failed gates versus zero — is the whole answer in structural form.

One more decision rule is worth stating explicitly, because it generalizes: if you could obtain the capability another way for under 10% of the purchase price, a full acquisition needs an extraordinary justification. Conversation transcription and summarization in 2027 can be obtained another way for well under 10% of $200M. The burden of proof sits entirely on the buy side, and the strategic story does not carry it.

The numbers behind each option

Precision matters here, because the case against the acquisition is arithmetic before it is judgment.

Valuation. SaaS M&A multiples in 2027 sit in a different universe than the 2021 peak. Public SaaS re-rated hard through 2022–2025, and profitable mid-market B2B SaaS generally changes hands in the range of 6–14x ARR — the high end reserved for assets growing north of 40% at real margins, the low end for slower or less capital-efficient businesses. Avoma is profitable and retention-strong but growing at a healthy rather than explosive rate, which places it credibly in the 8–12x band.

Run that against the ARR estimate:

Add the control premium a profitable, no-need-to-sell company would extract, and the realistic acquisition range lands at $180M–$340M, with a base case near $200M–$260M.

Financing. 11x has raised roughly $74M in its entire existence. The low end of the price range is roughly 2.4x that figure; the high end is roughly 4.6x. Three instruments exist and all three fail:

• *Cash.* Unavailable. A high-burn company cannot drain runway into an acquisition, and even a full drain doesn't reach a quarter of the price.
• *Stock.* To issue equity, 11x must strike a value on itself. Given the public ARR disputes, any honest mark sits materially below the last venture round — so issuing stock either crystallizes a down-round markdown for existing investors and employees, or requires Avoma's founders to accept impaired paper at an inflated price. Founders who avoided dilution for nine years to keep a profitable company are not swapping it for illiquid stock in a higher-burn company with a credibility problem.
• *Debt.* Lenders underwrite off cash flow and enterprise quality. A high-burn company with a contested revenue base is effectively unbankable for a $150M+ acquisition facility, and any debt that did clear would carry covenants and rates that accelerate insolvency during exactly the period when integration costs peak.

The alternatives, priced. A partnership costs the engineering time for a bidirectional integration plus partner-program overhead — call it low hundreds of thousands all-in for the first year, with referral economics that self-fund if the motion works. An IP license or small acqui-hire runs in the single-digit millions. Building a lightweight capture-and-summary layer costs a quarter or two of engineering. Against $200M–$260M, every rung is a rounding error.

Customer overlap. The bull case assumes cross-sell adds revenue. Overlap says otherwise. Both companies sell into RevOps and sales teams, Avoma's sweet spot is SMB and lower-mid-market sales orgs, and 11x's logos skew toward venture-backed tech companies with exactly that profile. When bases overlap, a merger consolidates rather than stacks: the combined entity has fewer distinct logos than the sum, procurement uses consolidation as leverage to renegotiate down, and customers who deliberately chose best-of-breed point tools respond to forced bundling by churning. There is a trust problem too — a meaningful share of customers will not want their private call recordings flowing into a platform owned by their outbound-automation vendor. Net revenue retention, the metric that actually drives SaaS value, is more likely to fall post-close than rise.

Category structure. Conversation intelligence in 2027 is not an open frontier:

Avoma is a good product occupying a defended middle. Buying it does not buy a moat; it buys a company that has to re-justify its price every renewal against Gong's brand, HubSpot's bundle, and Otter's free plan.

Integration benchmarks. The broadly cited failure rate for M&A that fails to create value sits around 50–70%, and the dominant cause is culture and integration rather than product. Founder and key-employee attrition concentrates in the 12–24 month earnout window — the same window during which the acquirer is internally focused and externally vulnerable, and competitors are trained to attack. Announcing this deal hands Gong, HubSpot, and Microsoft a free reason to run one play against 11x's base: your vendor is distracted, burning, and disputed — consolidate on us instead.

Implementation and sequencing, if 11x does the sensible thing

Assume the verdict lands and 11x pursues the partnership plus core-repair path instead. The sequencing matters, because doing these in the wrong order wastes the one asset 11x has least of — time.

Quarter one — stabilize the core and open the partnership conversation in parallel. Core work first in priority, not in calendar: instrument the digital-worker product end to end so that reply rates, meeting-hold rates, and human-cleanup time per sequence are measured per account rather than asserted in aggregate. Publish an internal cohort-retention view that finance and the board see monthly. Simultaneously, open a straightforward commercial conversation with Avoma — no bankers, no LOI, just an integration and referral discussion. Partnership talks cost days, not quarters, and their outcome informs everything downstream.

Quarter two — ship the integration and set the referral economics. A bidirectional integration is the deliverable: 11x pushes booked-meeting context into Avoma so calls arrive pre-tagged with campaign and account data; Avoma pushes call outcomes and objection themes back so 11x's targeting and messaging can learn from what actually happened on the call. Set referral compensation in the normal 10–20% first-year band, name a single owner on each side, and agree on a joint-customer success metric up front — meetings booked that convert to a second call is a cleaner shared number than seats sold.

Quarter three — run the joint motion against a real cohort and measure honestly. Pick 20–40 shared or adjacent accounts, run the joint story, and compare against a control cohort that gets 11x alone. Two numbers decide whether the relationship deepens: does the joint-motion cohort show higher meeting-to-opportunity conversion, and does it show better logo retention at renewal? If both improve materially, there is now evidence for a deeper relationship. If neither moves, 11x has learned for a rounding error what an acquisition would have cost $200M+ to learn.

Quarter four — decide the capability question on evidence. Only now does the build-versus-license question deserve capital. If the integration proved the conversation layer materially improves outbound performance, build a lightweight native capture layer or license the technology, in the single-digit millions. If it didn't, the partnership stands on its own as a customer-facing narrative and no capital is committed at all.

Throughout, the core-repair track runs continuously and takes precedence in any resource conflict. The sequencing rule is simple: nothing on the adjacency track is allowed to pull engineers off reliability work, because reliability is the precondition for the clean Series C that is itself the precondition for any future acquisition.

What would have to change for "yes." Intellectual honesty requires naming the flip conditions, because this is a 2027 answer rather than a permanent law. Five things would all need to hold at once: 11x raises a large, genuine Series C at a defensible valuation, meaning its equity is worth issuing; Avoma's price clears near 6x rather than at a strategic premium, which requires genuinely motivated sellers; 11x demonstrably fixes its core with churn down and a clean revenue story; 11x shows some evidence it can run a product-led motion without forcing it top-down; and the data-flywheel claim becomes a demonstrated result rather than a slide. That list describes a different 11x, a different Avoma, and a different market. Several of those conditions are also mutually unlikely — a motivated Avoma seller at a distressed price and a fully rehabilitated 11x rarely co-occur.

On the data flywheel specifically, since it is the strongest card in the bull hand: the argument is that conversation intelligence generates a proprietary corpus of what works in real sales calls, and that corpus makes outbound AI measurably better. It fails for three reasons. The corpus is Avoma's customers' private call data, and using it to train a product sold to a different and overlapping set of customers is a contractual and trust minefield that spikes churn risk the moment customers understand it. The marginal value of a mid-tier conversation corpus is eroding fast, because foundation models already handle conversation understanding and coaching inference well without proprietary data — the edge that mattered when Gong was built in the late 2010s is far thinner now. And the flywheel presupposes a clean technical and organizational pipe between the two products, which is exactly what the culture collision and predictable team attrition make unlikely to get built at all. A slide that says "data flywheel" is not a flywheel that spins.

Related questions

What would 11x actually have to pay for Avoma?

A realistic range of $180M–$340M, base case $200M–$260M. That reflects an estimated $15M–$30M ARR at an 8–12x multiple, plus the control premium a profitable, unpressured seller would extract. Even the floor exceeds twice everything 11x has raised.

Could 11x pay in stock instead of cash?

Only by striking a value on its own equity. Given public ARR disputes, an honest mark sits below the last round — forcing a down-round markdown internally, or requiring Avoma's founders to accept impaired paper. Founders who avoided dilution for nine years have every reason to refuse.

Isn't conversation intelligence strategically valuable to an AI SDR company?

Valuable, yes; scarce, no. Gong owns the enterprise tier, HubSpot and Microsoft bundle it at zero marginal cost, and Otter and Zoom drive the low end toward free. A capability obtainable for under 10% of the purchase price doesn't justify a control premium.

What should 11x do instead in 2027?

Fix core product reliability and churn first, then run a deep commercial integration and referral partnership with a conversation-intelligence vendor. That captures the full-funnel customer story for a rounding error, stays reversible, and preserves the runway and focus 11x actually needs.

Would Avoma's investors push for a sale?

Unlikely. Storm Ventures and the other early backers hold a stake in a profitable, growing, undiluted company with no runway pressure. A known-good independent asset comfortably beats illiquid paper in a higher-burn, credibility-impaired parent.

FAQ

Is the answer "no forever," or just "no in 2027"?

No in 2027, specifically and firmly. The verdict rests on conditions that could theoretically change: 11x's balance sheet, its credibility, Avoma's willingness to sell, and the competitive structure of conversation intelligence. If 11x raises a clean Series C from a repaired core and Avoma's founders become motivated sellers at a non-premium price, the conversation reopens. Nothing in the analysis says the two companies could never combine — it says the 2027 versions of them cannot, at anything resembling 2027 terms.

Doesn't buying a profitable company fix 11x's efficiency problem?

It is the most sympathetic version of the bull case, and it still fails. Bolting profitable ARR onto a burning company does improve the blended financial picture on a spreadsheet — but only if you can pay for it without destroying the balance sheet, and only if the acquired profitability survives contact with the acquirer's operating model. Neither holds here. Financing the purchase would consume or impair every source of capital 11x has, and the pressure to show synergy post-close typically pushes acquired PLG businesses toward top-down pricing and enterprise motions, which is exactly how the retention gets destroyed. You cannot acquire discipline; you have to practice it.

How much of this depends on the ARR disputes being true?

Less than it appears. Even if 11x's revenue figures were fully vindicated tomorrow, the valuation gap remains — $74M raised against a $180M+ price is arithmetic independent of ARR accuracy. The overlap problem, the category commoditization, the culture collision, and the seller's lack of any reason to sell all stand on their own. The credibility issue makes the financing gate worse, but the financing gate was already closed.

What about acquiring a cheaper conversation-intelligence company instead?

More defensible, and worth scoping — but ask the scarcity question first. If a smaller target's technology is obtainable by license or a quarter of engineering work, the acquisition is still the wrong vehicle. The honest use case for a small acquisition here is talent and speed, not capability: a five-to-fifteen-person team with real production experience shipping call analysis, bought for single-digit millions. That is a different transaction with different math from acquiring an established $15M–$30M ARR business.

Why does customer overlap hurt rather than help?

Because merging overlapping bases consolidates spend instead of adding it. A customer paying both vendors becomes one contract with one procurement team that now has leverage to negotiate the combined price down. Some best-of-breed buyers leave outright rather than accept a bundle. The headline "combined ARR" figure double-counts shared accounts and then leaks as those accounts renegotiate or churn. Cross-sell math only works when the bases are genuinely complementary — different segments, different buyers, different budget lines.

Does a partnership really deliver the same customer story as owning the product?

For the customer-facing narrative, largely yes. Buyers care that the meeting gets booked, run, captured, and analyzed — not about the cap table behind it. A deep bidirectional integration with shared data flow delivers that experience. What a partnership does not deliver is exclusivity or control of the roadmap, which matters only if the conversation layer is genuinely scarce. It isn't. So the partnership gives up something 11x does not need in exchange for avoiding a purchase price it cannot pay.

Sources

• https://techcrunch.com/2025/03/24/ai-sales-startup-11x-has-been-burning-through-cash-and-alienating-customers-sources-say/
• https://www.avoma.com/
• https://www.gong.io/
• https://www.hubspot.com/products/sales/conversation-intelligence
• https://learn.microsoft.com/en-us/microsoft-sales-copilot/
• https://www.salesloft.com/
• https://www.bvp.com/atlas/state-of-the-cloud
• https://www.crunchbase.com/organization/11x-ai
• https://hbr.org/2011/03/the-big-idea-the-new-ma-playbook
• https://www.mckinsey.com/capabilities/m-and-a/our-insights

Related on PULSE

• [How do you value an AI-native SaaS company on an ARR multiple?](/knowledge.html?q=q1860)
• [Cash, stock, or debt — how should a startup finance an acquisition?](/knowledge.html?q=q1865)
• [How do incumbents respond when a competitor makes an acquisition?](/knowledge.html?q=q1866)
• [Should you acquire a capability or build it in-house?](/knowledge.html?q=q1868)
• [What replaces the RevOps stack as AI agents take over the motion?](/knowledge.html?q=q1870)
• [Does vertical integration still build a moat in AI-native SaaS?](/knowledge.html?q=q1873)