Collaborative Screen Sharing — you each get your own mouse, and…
Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.
If you only have a few minutes to spare, here’s what investors, operators, and founders should know about Screenhero (W13).
Screenhero was a collaborative screen-control product founded by Jahanzeb Sherwani, Vishal Kapur, Jason DiCioccio, and Faraz Khan before its February 2013 launch and accepted into Y Combinator's Winter 2013 batch. It let two people control the same Mac or Windows desktop with independent cursors and keyboards, making remote pair work feel closer to sharing one machine.[1]
Slack acquired Screenhero on January 28, 2015 in an undisclosed cash-and-stock deal. All six employees joined Slack to build voice, video, and screen-sharing capabilities. Screenhero remained available during integration, then shut down on December 4, 2017 after interactive control appeared in Slack.
This is both an acquisition success and a standalone-service shutdown. The team and product behavior influenced Slack Calls and interactive sharing, but public evidence does not establish direct code reuse. Current Slack Huddles retains screen sharing and drawing, not the full dual-cursor remote-control model.
YC identifies Sherwani as founder and CEO, Kapur as founder and CTO, and DiCioccio and Khan as founders. Secondary company data says the four had previously built iTeleport, a remote-desktop product for iOS and Mac, but the packet does not provide a primary origin record or complete role history.[2]
The exact incorporation and founding dates were not found. The public evidence establishes that the company existed before its February 2013 launch, but not the year it was founded.
The founding insight was behavioral. Existing screen-sharing tools such as WebEx and GoToMeeting emphasized presentation. Remote developers and help-desk workers needed responsive co-control. Screenhero let each participant move a separate pointer and type into any desktop application, an interaction YC described as Google Docs-style collaboration for the entire desktop.[3]

Remote pair programming became the largest use case. Sherwani later wrote: “The main reason why Screenhero was loved was because it was fast.”[4] Responsiveness mattered because small delays break conversational turn-taking and make shared control feel like remote support rather than collaboration.
Screenhero supported Mac and Windows, integrated HD voice, and reported that 92 percent of sessions were peer-to-peer encrypted. It said remaining sessions were encrypted and not trackable by Screenhero, though the packet contains no security audit, relay design, or key-handling details.
No second origin-era founder quote surfaced. The team's later “We’ve finally done it” statement belongs to the Slack integration and closure, not the founding period.

Screenhero shared any Mac or Windows application while giving both participants an independent mouse pointer and keyboard input. Unlike presentation-first conferencing, both people could act inside the same development environment, design tool, browser, or support workflow.
The product combined low-latency screen sharing, multi-mouse control, and voice. TechCrunch's hands-on review reported little lag but did not provide measurements. Sherwani's later 30 to 50 millisecond figures concerned a subsequent product, not Screenhero, so they should not be back-applied.
Read the complete post-mortem, the rebuild playbook, and the exact reasons Screenhero is still worth studying now.