Loading page…
A live video chat widget for sales and support teams, acquired for an approximate mid-six-figure price.
Median shows how a focused software asset can find a strategic buyer, but the exit price does not reveal its operating economics.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Median is described as a live chat video tool that lets a website visitor reach a person through an in-page interaction rather than a conventional text-only chat button. Andrew Gazdecki says teams could use it for sales and support, and mentions large enterprise agreements with public companies whose names he could not disclose. He recalls a sale price in the range of roughly $250,000 to $300,000, while explicitly qualifying that he does not remember the exact amount. The acquisition amount is therefore approximate and creator-reported. The interview gives no revenue, user count, margin, or product retention data. Its value as a case is the combination of a specific interaction format and business use cases where a human response can unblock a purchase or support issue.
For a live video support widget, the first customers are teams with high-value interactions where text chat leaves too much ambiguity: complex sales qualification, onboarding, or technical support.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself.
Data credibility: Andrew Gazdecki describes Median as a live chat video tool that could serve sales and support teams, including enterprise customers. He estimates the sale at roughly $250,000–$300,000 but says he does not recall the exact amount.
The first dollar should arrive when a sales or support team pays for a live interaction that changes a measurable business outcome. Price around agent seats, usage, or a team plan that fits the existing help-desk budget, and make the unit understandable.
A useful loop forms when teams see that real-time video resolves cases or accelerates qualified conversations, then place the widget on more pages and invite more agents. Session context and outcome tags help managers decide where live video is worth staffing.
A new support channel can take time to gain internal trust because staffing and privacy owners may be cautious. Begin with a narrow pilot window and a team willing to monitor sessions closely.
Our read: Median is a live video chat interaction for websites, aimed at sales and support teams that benefit from speaking with a visitor in real time. The described experience lets a visitor click a site control and reach an employee by video; the hosts also mention the ability to take control of a user’s screen. The product therefore needs a clear consent step, agent availability, routing, session context, browser compatibility, and a reliable fallback when no one can answer. The strongest starting point is a defined high-value moment, such as product evaluation or technical troubleshooting, rather than putting video on every page. Integrations with CRM and support tools can capture outcomes, but the core interaction must feel easy and safe for the visitor.
Our read: The sale estimate of roughly $250,000–$300,000 is approximate because the broker says he cannot recall the exact figure. It is a transaction outcome, not a disclosed revenue or profit metric. A new operator should test a subscription for teams based on agent seats or active service volume, while charging separately for implementation only when the work is real and repeatable. The buyer needs evidence that live sessions improve qualified sales conversations, reduce support resolution time, or prevent escalations. Report sessions offered, sessions completed, resolution, conversion, and retention rather than widget views alone. Enterprise agreements can produce larger contracts, but procurement, security review, and custom integrations add cost. Do not treat named enterprise customers as proof of broad demand when their identities and contract details are not public.
Our read: A live video support product depends on real-time media infrastructure, browser permission handling, routing, agent presence, and secure session controls. The interview does not identify Median’s vendors or technical architecture. Keep screen access explicit and revocable; record only what the customer needs and disclose any recording. Provide a text fallback, an accessible interface, and diagnostics for camera or microphone failures. Measure infrastructure cost per completed session and support burden by customer. Enterprise accounts may ask for retention controls, audit logs, and integration with their support stack. Start with the smallest reliable session workflow, then add CRM context or analytics when multiple customers need the same connection. Poor connection quality or unclear privacy behavior can erase the benefit of a faster human response.
Our read: Copy the interaction insight: some website visitors need a human conversation or shared screen to move forward, and conventional text chat can be limiting. Change the initial market to one with high-value questions and staffed specialists who can answer quickly. Place the widget only where the outcome can be observed, and compare live sessions with the team’s existing support or sales process. Keep participation optional and explain video permissions before connection. Do not lead with a generalized “video chat for every site” pitch; show a specific reduction in friction for a defined team. The reported enterprise agreements suggest that larger organizations may value the tool, but the identity and economics of those contracts remain confidential. A new entrant should prove one customer workflow before building broad enterprise sales infrastructure.
Our read: Adoption depends on agents being available at the moment a visitor asks for help. If the team cannot staff the channel, visitors may wait or abandon, making the widget a liability. Other risks include privacy concerns, browser permissions, network quality, screen-sharing security, and overlap with existing help desk tools. Enterprise customers can create concentration and support burden, while custom integrations may turn a SaaS product into a services business. The approximate sale price is the only business outcome described; revenue, margin, and customer retention are absent. Validate repeated paid use with a small team and measure completed sessions plus downstream outcomes. Keep recording off by default unless there is a clear, disclosed need. Make availability, escalation, and fallback behavior explicit before expanding deployment.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,403 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click