Heysan was a mobile instant messaging aggregator founded on January 24, 2007, by Gustaf Alstromer, Marie Brattberg, Pär Lindhe, and Michael Ossareh. Part of Y Combinator's Winter 2007 batch, the company built a free, ad-supported mobile …
Heysan was a mobile instant messaging aggregator founded on January 24, 2007, by Gustaf Alstromer, Marie Brattberg, Pär Lindhe, and Michael Ossareh. [1] Part of Y Combinator's Winter 2007 batch, the company built a free, ad-supported mobile app that unified MSN, Yahoo Messenger, AIM, ICQ, and Google Talk into a single interface — a technically ambitious bet that SMS and desktop IM could be bridged on the handset. [2] It relocated from New York to San Francisco after YC and raised seed capital from Khosla Ventures and Atomico. [3]
The company reached over one million users and 100 million monthly pageviews, but never solved the growth problem that would have made its ad-supported model viable. [4] Its core product was structurally dependent on the openness of third-party IM networks that were simultaneously building their own mobile clients, eroding Heysan's differentiation from both sides.
Good Technology acquired Heysan in May 2009 for undisclosed terms — almost certainly a modest acqui-hire rather than a product acquisition. [5] The outcome was a soft landing for the team, but the more consequential legacy was Gustaf Alstromer's transformation into one of the technology industry's most prominent growth practitioners, a career arc that began precisely because Heysan was a product he could not grow.
In late 2006, Gustaf Alstromer, Marie Brattberg, and Pär Lindhe were sharing a freezing New York apartment when they drafted the application that would get them into Y Combinator's Winter 2007 batch. [6] Michael Ossareh joined the founding team shortly after. [7] Alstromer served as CEO; Pär Lindhe brought prior experience from Rebtel, the Swedish voice-over-IP company, and Upoc, an early mobile community platform — backgrounds that gave the team direct exposure to the friction of mobile communications in the pre-smartphone era. [8]
The founding thesis was explicit and technically ambitious. The YC application described the product as: "We are creating a mobile social networking application that enables free interoperable mobile instant messaging on your mobile handset." [9] In 2007, mobile messaging was expensive and fragmented: SMS carriers charged per message, and the major desktop IM networks — MSN Messenger, AIM, Yahoo Messenger, ICQ, Google Talk — had no coherent mobile presence. The founders saw an opportunity to be the layer that unified them, for free, on the device people already carried.
The YC interview itself produced a moment that would become a footnote in startup history. During the demo, Alstromer showed a feature that allowed users to take a photo on their phone and send it directly to a social media profile. Paul Graham stopped him: that feature, Graham said, "could be a company in itself." [10] Heysan did not pursue it. Instagram was founded three years later, in 2010.
After acceptance into W07, the team relocated to San Francisco, establishing offices at 301 8th Street. [11] Crunchbase records indicate Heysan was incubated alongside Twitter during this period, though the precise nature of that relationship — shared office space, informal mentorship, or something else — is not documented. [12] By the summer of 2007, the company had closed a seed round from Khosla Ventures (Vinod Khosla) and Atomico (Niklas Zennström), two investors with direct credibility in mobile and communications infrastructure. [13]
Alstromer's retrospective framing of the YC experience is notably warm despite the outcome: "Our startup Heysan didn't become WhatsApp (WhatsApp became WhatsApp), but joining the winter 2007 batch would shape our lives in almost every aspect." [14] That framing — acknowledging the gap between ambition and outcome while crediting the institutional experience — is consistent with a founder who processed the failure productively rather than defensively.
Heysan's core product was a free mobile application that aggregated five major instant messaging networks — MSN Messenger, Yahoo Messenger, AIM, ICQ, and Google Talk — into a single interface accessible from a mobile handset. [24] In 2007, this was a genuine technical achievement. Each of those networks used a different underlying protocol; building a client that could authenticate with all five simultaneously, relay messages in real time, and do so on the constrained hardware and network conditions of pre-smartphone mobile devices required meaningful engineering effort.
The user experience was straightforward in concept: a user would sign into Heysan once, enter their credentials for whichever IM networks they used, and receive a unified inbox on their phone. Messages sent from desktop MSN would appear alongside AIM messages and Google Talk conversations. The value proposition was clear — instead of paying per SMS or switching between apps, users got a single free messaging layer.
The product also incorporated a viral growth mechanism. When users signed in, they were prompted to invite contacts, earning credits redeemable in a virtual store. [25] The implementation proved controversial: the "Share with friends" feature sent messages to contacts automatically, without requiring explicit confirmation from the user. A November 2008 review in Mobile Industry Review documented user complaints about this behavior, describing it as a "shady viral mechanism." [26] The credits themselves could be redeemed in a virtual store, though what the store offered is not documented in available sources.
Over time, the product evolved beyond pure messaging aggregation. Heysan began describing itself as a "mobile cross-protocol chat app and community," suggesting the team added social features — user profiles, community interactions — on top of the messaging layer. [27] The YC company page describes this as "launching a mobile community," though the specific features and their timeline are not documented in available sources. [28]
What distinguished Heysan from alternatives in 2007 was the combination of cross-network reach and zero cost. Carrier SMS was expensive. Individual IM network mobile clients were fragmented and inconsistent. Heysan offered a single point of access to a user's entire messaging graph, for free, funded by advertising. The model was coherent — but it depended on two conditions holding: that the major IM networks would remain accessible via third-party clients, and that Heysan could acquire users fast enough to generate meaningful ad revenue before those networks built their own mobile experiences.
Neither condition held long enough.
Heysan's primary users were mobile consumers who maintained active accounts on multiple desktop IM networks and wanted to access those conversations from their phones without paying SMS rates. [29] The November 2008 data showing the UK and US as the largest markets is consistent with this profile: both countries had high IM network penetration (MSN was dominant in the UK; AIM and Yahoo had strong US user bases) and relatively high SMS costs compared to data plans.
The 5+ hours per month engagement figure suggests the core user was not a casual experimenter but someone who had genuinely shifted messaging behavior to the platform. [30] This is a meaningful signal: the product worked for the users who found it. The problem was that the addressable pool of such users — people with multiple IM accounts, a mobile data plan, and willingness to use a third-party client — was narrower than the total mobile messaging market.
The mobile messaging market in 2007–2009 was large but structurally contested. Global SMS volumes were in the hundreds of billions annually, and mobile data adoption was accelerating. The iPhone launched in June 2007 — the same year Heysan was founded — and Android followed in 2008, beginning the transition that would eventually make mobile-first messaging the default.
The total addressable market for mobile IM aggregation, however, was more constrained than the broader messaging market. It required users who were already active on desktop IM networks, had mobile data access, and were willing to authenticate a third-party app with their network credentials. In 2007, that intersection was real but not massive. The more important market dynamic was directional: as smartphones proliferated, the IM networks themselves would build mobile clients, collapsing the gap Heysan was filling.
Heysan's competitive position was structurally precarious in a way that was not immediately obvious in 2007 but became decisive by 2009.
The direct competitors were other mobile IM aggregators: Nimbuzz, eBuddy, and Fring all operated in the same space, offering similar cross-network mobile messaging. These companies faced identical structural constraints — their value proposition depended on the same third-party network access that Heysan relied on.
The more consequential competitive threat came from the IM networks themselves. MSN, Yahoo, AIM, and Google all had strong incentives to build their own mobile clients: doing so would keep users within their own ecosystems, preserve their advertising relationships, and eliminate the need to share user attention with aggregators. As each network launched a native mobile app, the aggregation layer became less necessary for users who primarily used one or two networks.
The deepest structural problem was that Heysan competed on a dimension — cross-network reach — where incumbents had an inherent advantage: they owned the networks. Heysan's access to those networks was permissive, not contractual. Any of the major IM providers could have restricted third-party API access at any time, and all of them had commercial incentives to do so as mobile became strategically important.
WhatsApp, founded in 2009, illustrated the alternative approach: rather than bridging existing networks, it built a new network from scratch using phone numbers as identifiers, eliminating the dependency on incumbent cooperation entirely. Heysan's aggregation model was a bet on the continued openness of networks that were simultaneously becoming competitors.
Heysan's revenue model was advertising-supported: the service was free to users, with revenue generated through mobile ads displayed within the application. [31] This was a standard consumer internet model applied to mobile, and it carried a well-understood constraint: ad revenue scales with user volume and engagement, requiring both to reach meaningful levels before the business becomes self-sustaining.
The company never disclosed revenue figures. The absence of any public revenue data — even directional figures in press coverage or investor commentary — is itself a signal that monetization was not a story the company was telling.
Inferring from available data: at 600,000 users in November 2008, with 5+ hours of monthly engagement, Heysan had a credible engagement base. [32] Mobile advertising CPMs in 2008 were low — industry estimates for mobile display ads ranged from $0.50 to $2.00 per thousand impressions. At 100 million monthly pageviews (the peak figure), [33] a $1.00 CPM would imply roughly $100,000 in monthly gross revenue — approximately $1.2M annualized. This is an inference, not a documented figure, and the actual CPMs Heysan achieved on a 2008-era mobile platform were likely at the lower end of that range.
Against total funding of approximately $875K–$1.02M [34] and a four-person founding team operating in San Francisco for roughly two years, the implied burn rate would have consumed the seed capital well before the acquisition. The absence of a Series A — despite credible seed investors and over one million users — indicates that Khosla Ventures and Atomico did not see a growth trajectory that justified further investment.
By November 2008, Heysan had approximately 600,000 registered users. [35] Average engagement exceeded 5 hours per user per month — a figure that compares favorably to many consumer mobile apps of the era and suggests genuine habitual use among the active user base. The UK and US were the two largest markets.
The company ultimately reached over 1 million users conducting tens of millions of monthly messages, with 100 million monthly pageviews at peak. [36] [37] The gap between the November 2008 figure (600,000) and the eventual 1 million+ is undated; the trajectory of growth in the final months before the May 2009 acquisition is unknown.
What the traction data reveals is a product that worked for the users who found it, but could not find enough of them. The engagement metrics rule out a pure product quality failure — users who adopted Heysan used it heavily. The growth ceiling was a distribution and acquisition problem, not a retention problem. Gustaf Alstromer's own diagnosis confirms this: Heysan was "a product we couldn't grow." [38] The distinction matters because it shaped his entire subsequent career: the failure was not in building the product, but in scaling it.
The most fundamental problem Heysan faced was not one it could solve through better execution. Its entire value proposition — unified access to MSN, Yahoo, AIM, ICQ, and Google Talk — depended on the continued willingness of those networks to allow third-party client access. That willingness was never guaranteed, and each network had strong commercial incentives to eliminate it.
In 2007, the major IM networks had not yet built coherent mobile clients. Heysan's aggregation layer filled a genuine gap. By 2008–2009, that gap was closing rapidly: MSN, Yahoo, and Google were all investing in mobile versions of their own products. As native mobile clients improved, the marginal value of Heysan's aggregation declined for users who primarily used one or two networks. The company's competitive position eroded not because it made mistakes, but because the market condition it depended on — incumbent inaction on mobile — was temporary.
This is the structural explanation that sits beneath all the company-level decisions. Heysan was building on top of platforms it did not control, in a category where those platforms had both the incentive and the capability to absorb its core feature. The same dynamic would later affect other aggregators across different categories: the aggregation layer is valuable precisely until the platforms it aggregates decide to compete directly.
Gustaf Alstromer's own diagnosis is the clearest available evidence of what the team experienced internally: Heysan was "a product, a messaging product on mobile that we couldn't grow so we spent a lot of time trying to learn how to grow." [39]
The team's response to the growth problem was the credits-for-referrals viral mechanism. The implementation — a "Share with friends" feature that automatically messaged a user's contacts without requiring explicit confirmation — generated complaints almost immediately after it was documented publicly in November 2008. [40] The mechanism was designed to engineer virality, but it did so by borrowing trust from users' contact lists without their explicit consent. This approach damaged the product's reputation at the precise moment it needed word-of-mouth growth.
The deeper problem with the viral mechanism was that it addressed the symptom (insufficient new user acquisition) without addressing the cause (insufficient organic pull). A messaging aggregator's natural viral loop is the network effect: users invite contacts because those contacts need to be on the same platform to communicate. But Heysan's users could already reach their contacts through the underlying IM networks — the aggregation layer was a convenience, not a communication prerequisite. This made the natural viral loop weaker than it would have been for a standalone messaging network.
The business model created a specific growth threshold: Heysan needed to reach a user base large enough to generate meaningful advertising revenue before its seed capital was exhausted. With approximately $875K–$1.02M raised [41] and a four-person team in San Francisco, the runway was finite and the scale required was substantial.
At 600,000 users in November 2008, the company was generating engagement but almost certainly not enough ad revenue to cover operating costs. The absence of a Series A — despite investors of the caliber of Khosla Ventures and Atomico — indicates that the growth trajectory did not convince those investors that the scale threshold was achievable. Whether the team attempted to raise a Series A and was declined, or chose not to pursue one, is not documented.
The ad-supported model also created a misalignment between the product's natural user base and the scale required for viability. The users who most valued Heysan — heavy multi-network IM users with mobile data plans — were a specific demographic, not the mass market. Reaching the mass market would have required either a different product or a different distribution strategy, neither of which the team appears to have executed before the acquisition.
The evolution of Heysan's self-description — from "free interoperable mobile instant messaging" to "mobile cross-protocol chat app and community" — suggests the team recognized that protocol bridging alone was insufficient differentiation. [42] Adding community features was an attempt to create a layer of value that the underlying IM networks could not easily replicate: a social graph and identity that lived on Heysan rather than on MSN or AIM.
The attempt was reasonable in theory but arrived too late and without sufficient resources to execute. Building a mobile community in 2008 required competing with platforms that had existing social graphs, distribution, and brand recognition. The community pivot did not generate documented traction, and the acquisition occurred approximately six months after the pivot was visible in the product's public description.
Paul Graham's observation during the YC interview — that Heysan's photo-to-social-media feature "could be a company in itself" [43] — is a retrospective lesson about focus that Alstromer has chosen to document publicly. Instagram was founded in October 2010 and reached 1 million users in its first two months, eventually selling to Facebook for $1 billion in 2012.
The counterfactual is not that Heysan should have become Instagram — the specific execution, timing, and team decisions that made Instagram successful are not replicable in retrospect. The more precise lesson is that Heysan was demonstrating a feature in 2007 that a sophisticated observer identified as a standalone opportunity, and the team did not pursue it. Whether this was a resource constraint, a strategic judgment, or simply a failure to hear the signal clearly is not documented.
Good Technology acquired Heysan on May 1, 2009, for undisclosed terms. [44] Good Technology was an enterprise mobile software company — a context that suggests the acquisition was more likely for the team's mobile engineering expertise than for the consumer product or its user base. The estimated exit value of approximately $4 million against roughly $1 million raised [45] implies a modest return for investors and a soft landing for founders — not a failure in the catastrophic sense, but not the outcome the seed investors were underwriting when they backed a consumer mobile messaging company.
Aggregation is a temporary moat when the aggregated platforms have mobile ambitions of their own. Heysan's value proposition — unified access to MSN, AIM, Yahoo, ICQ, and Google Talk — was real in 2007 when none of those networks had coherent mobile clients. By 2009, each was building one. Any startup that derives its core value from bridging platforms those platforms control faces a countdown clock, not a sustainable competitive position. The question is not whether the incumbents will respond, but how long the window lasts.
Viral mechanisms that borrow user trust without explicit consent can damage the product they are designed to grow. Heysan's auto-blast "Share with friends" feature generated documented user complaints in November 2008 — precisely when the company needed word-of-mouth to accelerate. The mechanism treated users' contact lists as a distribution channel rather than a trust relationship, and the backlash was predictable in retrospect. Growth tactics that work by exploiting rather than extending user trust tend to produce short-term spikes and long-term brand damage.
Engagement without growth is a warning signal, not a validation. Heysan's 5+ hours per month engagement figure was strong, but it masked a distribution problem: the users who found the product loved it, but the product could not find more users. In an ad-supported consumer model, engagement without growth means the unit economics never close. Heysan's seed investors — who had visibility into both the engagement data and the growth trajectory — chose not to fund a Series A, which is the clearest available signal that engagement alone was insufficient.
The YC interview is a product review, not just a funding gate. Paul Graham's observation that Heysan's photo-sharing feature "could be a company in itself" was made in early 2007 — three years before Instagram launched and four years before it sold for $1 billion. Alstromer has chosen to document this moment publicly, suggesting he views it as a lesson about listening to signal in high-stakes feedback contexts. The specific feature Graham identified was not Heysan's core product, but it was the one that a pattern-matching investor flagged as independently valuable. That signal was available and was not acted upon.
Failure at a specific problem can be more career-defining than success at an easier one. Gustaf Alstromer's inability to grow Heysan became the founding insight of his subsequent career: he went on to lead growth at Voxer, then served as Product Lead of Growth at Airbnb during its scaling years, and eventually became a Group Partner at Y Combinator focused on growth. [46] The specific problem Heysan could not solve — user acquisition and growth at scale — became the domain in which Alstromer built his professional identity. The company failed; the founder's learning did not.