Othello Raises $8M Seed for Live AI Sales Coaching

Half a second is an unusually demanding place to put a sales playbook. Othello builds AI guidance for the interval between a buyer saying something and a salesperson deciding how to respond, making the usefulness of an answer inseparable from when it arrives.

The New York company announced $8M in Seed funding on October 14, 2026, with a16z speedrun, Owl Capital and Long Journey Ventures participating. Cofounder and CEO Jared Zelman and cofounder and CTO Raphael Assor are developing a business around supporting a human seller during a live exchange. For enterprise buyers, that moves a software purchase into the quality of customer-facing decisions.

What Othello's Seed Financing Supports

Othello describes itself as an applied AI lab building models for live sales calls. The announcement establishes the financing amount, stage and participating institutions, while leaving valuation and detailed allocation of the proceeds undisclosed. None of the three institutional investors is designated as lead in the release, so their participation should be understood without an invented hierarchy.

The a16z speedrun company profile independently identifies Zelman and Assor and describes Othello's focus on AI models for B2B sales conversations. That institutional relationship gives the financing a specific commercial subject: helping revenue teams turn their preparation into choices made while customers are present. Capital enters a product category where the person using the software also carries responsibility for what the customer hears.

The financing matters because organizational knowledge is costly to assemble and easy to leave outside the conversation that needs it. Sales leaders invest in product material, customer examples and qualification methods; distributing that material still leaves sellers to retrieve and apply it. Othello is selling assistance with that application, a proposition that links the quality of company knowledge to the experience of an individual rep.

For operators reading the announcement, the useful distinction is between a funding event and a deployment decision. The $8M gives the startup financial backing, while each enterprise still has to decide how its people will use the product. Othello's published claims and workflow help explain what that decision involves.

How Hamlet Enters a Live Sales Call

Hamlet is Othello's proprietary model for live sales calls. According to the company, a desktop application supplies prompts in under 500 milliseconds and works as an overlay without joining the meeting as a separate participant. That latency claim describes the supplier's stated capability, rather than an independently reproduced benchmark.

Othello's product material describes suggestions for discovery, objection handling, qualification steps and product questions. A qualification method may give a team a common language for understanding an opportunity, but the next useful question depends on what a buyer has just said. The commercial appeal of live assistance is its ability to bring relevant preparation into that changing context, without asking the seller to pause the conversation to search.

That arrangement gives the interface a demanding job. Guidance competes for attention with the customer's words, facial expressions and immediate response. A detailed answer may be correct yet arrive in a form that is difficult to use while speaking. An enterprise evaluating the product can therefore examine usefulness in the flow of conversation: which suggestions a rep accepts, which they dismiss, and how quickly they can understand the material.

The same design creates a responsibility around knowledge freshness. A product document can change after a feature launch, an approval rule can vary by account, and a case study can have limits on how it is presented. Those are ordinary sales-management concerns that become especially visible when software places the information beside a live customer exchange.

Enterprise Adoption and the Existing Revenue Stack

Othello reports deployment at more than 50 large enterprises, naming Microsoft, Capital One and Lyft as customers. It also says licensed reps use the application on at least 95% of their calls. These company-reported figures establish the adoption story Othello is presenting; the announcement does not provide an independently audited revenue-impact study.

The published integration catalog places Othello alongside Salesforce, HubSpot, Gong and common meeting platforms. The supplier describes a workflow spanning meeting preparation, live guidance and subsequent records or actions. Integration listings explain intended compatibility, while leaving each enterprise to validate its own configuration and operating requirements.

This positioning makes an existing conversation-intelligence purchase part of the context for a new one. A team that reviews recorded calls may still want guidance during them, and a manager who studies past outcomes may want lessons to reach the next customer exchange. Othello's own description presents its Gong connection as complementary. That is a supplier's positioning statement, rather than evidence that every customer needs both products.

The distinction is useful alongside DevCuration's coverage of Scuba's shared-context financing. Organizational knowledge is becoming an input to AI-assisted work, and the destination of that knowledge matters. In Othello's case, the destination is a seller preparing to speak, which creates a different interface and accountability problem from maintaining a searchable team memory.

The Management Decision Behind Live Guidance

Othello's About page lists offices in New York and Tel Aviv and describes Zelman's longstanding interest in selling. Its current careers page advertises roles across engineering and go-to-market work. These details show the operating organization around the product, without establishing a specific hiring allocation for the new financing.

For a revenue leader, implementing live guidance reaches beyond buying seats. Somebody has to decide which product material the system can use, what advice reflects the organization's selling standards, and how feedback reaches the people maintaining that information. A manager's judgment enters the product through those choices before a suggestion ever appears on a rep's screen.

Privacy and retention also belong in that implementation conversation. Othello says it offers a mode that does not retain audio, transcripts or personally identifiable information, and says customer data is not used to train public or shared models. Buyers should assess the mode they actually deploy and their own requirements; the provider's description alone cannot establish universal compliance or eliminate the need for a consent policy.

The financing brings investor backing to a company putting assistance inside one of the enterprise's most personal workflows. Zelman and Assor are building software for moments when preparation meets an unfamiliar answer. As sales leaders supply the material and sellers choose what to say, Othello's product keeps encountering the part of the business that cannot be settled in a playbook: another person responding.