<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Eric Migicovsky on Medium]]></title>
        <description><![CDATA[Stories by Eric Migicovsky on Medium]]></description>
        <link>https://medium.com/@ericmigi?source=rss-499f96b76542------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*C0wVZVtPHC7bLGOg.jpeg</url>
            <title>Stories by Eric Migicovsky on Medium</title>
            <link>https://medium.com/@ericmigi?source=rss-499f96b76542------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 01:52:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ericmigi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why Pebble failed]]></title>
            <link>https://medium.com/@ericmigi/why-pebble-failed-d7be937c6232?source=rss-499f96b76542------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7be937c6232</guid>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[ycombinator]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[founder-stories]]></category>
            <dc:creator><![CDATA[Eric Migicovsky]]></dc:creator>
            <pubDate>Mon, 11 Apr 2022 16:16:30 GMT</pubDate>
            <atom:updated>2022-04-12T00:55:06.196Z</atom:updated>
            <content:encoded><![CDATA[<h3>Success and Failure at Pebble</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1005/0*EY6IjXLzis3NbZuX" /></figure><p><strong><em>I’ve been giving a talk on the importance of learning from failure to every YC batch for last few years. I wrote this post in 2017 but never published it. I dusted it off for the 10 year anniversary of Pebble’s launch on Kickstarter.</em></strong></p><p>I started Pebble with some friends from the University of Waterloo in 2008. We were the first company to work on smartwatches. Pebble defined what a smartwatch was meant to do — vibrate and display incoming calls and messages, control music without taking out your phone, track your exercise and sleep, and be customizable by downloading <a href="https://apps.rebble.io/en_US/watchfaces">fun watchfaces</a>.</p><p>You might remember us from 2012 we launched <a href="https://www.kickstarter.com/projects/597507018/pebble-e-paper-watch-for-iphone-and-android">Pebble on Kickstarter</a> and raised over $10m from 68,000 people around the world. This was our first breakthrough (a classic 5 year overnight success!) Over the next few years, we sold 2 million watches and did over $230m in sales.</p><p>We succeeded at inventing the smartwatch and an entirely new product category. The product itself is amazing, people still use it to this day. I personally still use my Pebble 2 HR every single day and I wouldn’t trade it for any other smartwatch on the market.</p><p>But in the end, we failed to create a sustainable, profitable business. We sold parts of our business to Fitbit at the end of 2016.</p><p>What happened? Here’s my TL;DR of why we failed:</p><ul><li>Sales for our version 2.0 (Pebble Time) in 2015 didn’t hit forecasts and the oversupply in inventory put us into a major cash crunch (targeted ~$100m in sales, we did $82m).</li><li>Pebble Time did not succeed because in a quest for huge growth we attempted to expand beyond our initial geeky/hacker user base and failed to reposition it — first as a productivity device, then as a fitness watch. In hindsight, this was stupid and obvious and 100% my fault. We didn’t know if there was actually a market for a more ‘productivity’ smartwatch and we weren’t a fitness company at the core.</li><li>Another reason — the bezel on Pebble Time was too damn big! I knew this in my heart but the project was so behind at the time that I didn’t have the guts to change it.</li><li>In 2015, we also doubled our operating expenses in anticipation of future growth. This, combined with lower gross margins as we tried to cram more technology into our 2015 lineup, caused us to lose profitability (we did $9m in net profit in 2013 and broke even in 2014).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*X2H-bozFD2eEV1e9.png" /><figcaption>Uhh, we definitely we made compromises, why did I approve this title 😂</figcaption></figure><p>We spent 2016 desperately trying to cut costs, retain the team, build another product, raise money and, eventually, sell the company.</p><blockquote><strong>The underlying problem was that we shifted from making something we knew people wanted, to making an ill-defined product that we hoped people wanted.</strong></blockquote><p>In the days after our Kickstarter campaign, it was easy for me as the CEO to explain what our goal was. Ship the best damn smartwatch that we ourselves wanted to use. Over the years, I tried several times to reposition the product and company onto a variety of new tracks, but none were based on a strong long term vision.</p><p>Startup founder lesson learned — never forget to define and talk about your long term vision for the future. When things are going well, it’s easy to get caught up in growth. But you need this to carry your company through hard times.</p><p>Looking back with hindsight, I should not have aggressively grown the company without a stronger plan. We should have just stuck to what we knew best and continued to build quirky, fun smartwatches for hackers. Pebble, the product, was and still is awesome. Even though we released it 5 years ago, the Pebble 2 HR on my wrist (powered by <a href="https://rebble.io/">Rebble.io</a>) still does everything I want it to do :)</p><p>Feel free to read the rest of the post below with a bunch of details!</p><blockquote><strong><em>In 2021</em></strong><em>, I decided to jump off into the deep end again and start a new company called </em><a href="https://www.beeper.com/"><strong><em>Beeper</em></strong></a><strong><em>. </em></strong><em>We’re building a universal chat app. Chat today is still surprisingly broken. Your contacts are spread out across a dozen different chat networks. You have to check several inboxes to keep tabs on everyone. It’s easy to miss messages and hard to avoid junk texts. We’re fixing this. Most chat apps are not real products, instead they are loss-leaders for other services. We love chat and treat it with the respect and focus that it deserves. Our goal is to build the best damn chat app. In the process, it’s likely that Beeper will become the underlying communication system for everyone on earth. I wrote about our plan in more detail </em><a href="https://blog.beeper.com/p/the-universal-communication-bus-42dfb9a141ad?s=w"><em>here</em></a><em>.</em></blockquote><blockquote><em>I think a lot about my experience at Pebble, and the many lessons learned in the process. It makes me a better CEO and leader. As I like to say, I’m glad to have learned so much from Pebble, and I’m excited to make new, more interesting mistakes at Beeper 😉</em></blockquote><h3>The Longer Story</h3><p>I began working on smartwatches in 2008, but I had been building small electronics projects for a while. My uncle had actually asked me to hack together a bedside clock that would project your Blackberry emails on the ceiling 😂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XmmLlgcmBJG_ZPP2" /></figure><p>While studying at TU Delft in 2008 I started to working on smartwatches. There wasn’t <a href="https://www.wareable.com/smartwatches/smartwatch-timeline-history-watches">much competition</a> at that point. I looked for one to buy but the only thing I could find was a <a href="https://www.cnet.com/reviews/sony-ericsson-bluetooth-watch-mbw-100-review/">Sony Erisson wa</a>tch that showed caller ID and cost $300. A few friends (Steve, Garret, Brad, Nick, Rahul, Derek) and I started working on our first watch, called <a href="https://web.archive.org/web/20111016072157/http://www.getinpulse.com/">inPulse</a>. We even had a <a href="https://web.archive.org/web/20130526100520/http://blog.getinpulse.com/?page=2">blog</a> back then too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*VpTTWVV19hoIXdUI" /><figcaption><em>First inPulse prototype — 2008</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vKwtXsObGgxELWhF" /><figcaption><em>Product positioning in 2011, a year before we launched on Kickstarter</em></figcaption></figure><p>Our second act really started in 2011 when Andrew Witte joined the team and designed our next generation watch. We launched Pebble on <a href="https://www.kickstarter.com/projects/getpebble/pebble-e-paper-watch-for-iphone-and-android">Kickstarter</a> in April 2012. Over the next 5 years, we sold over 2 million watches.</p><p>I won’t be covering the entire history of Pebble. Instead, I want to focus on the latter stages, explain some of our failures and extract some lessons learned that I will apply to future ventures.</p><h3>Did Pebble Fail?</h3><p>Yes, in the end we failed. We failed to build a long term successful and profitable company. We certainly had successes on the way (the company was over 8.5 years old when we sold!) but the end result was definitive. We ran out of money and <a href="https://www.wired.com/2016/12/the-inside-story-behind-pebbles-demise/">sold what we could</a> to preserve the product experience for the millions of people out there with Pebbles.</p><p>Pebble was always an odd startup. We only were able to raise $150k from angel investors in the year after we went through Y Combinator’s Winter 2011 batch. This was much lower than our batch average. We luckily survived long enough to launch Pebble on Kickstarter.</p><p>The vast majority of startups die before experiencing anywhere near the success we had. Before getting too deep in the stuff we screwed up, we definitely had a few things to be proud of:</p><ul><li>We recruited a super talented team that invented and defined an entirely new multibillion dollar product category.</li><li>We had early success in this market, selling over $230 million worth of Pebble smartwatches in 4 years. There are more than 2 million Pebbles spread around the world.</li><li>Through a combination of luck, timing, and dedication we inspired the imagination of a passionate community that grew around Pebble, watchfaces, apps, skins, mounts, accessories, and even 19 Pebble accessory Kickstarter projects.</li><li>One of my favourite things in the world… catching a glimpse of a Pebble on someone’s wrist when I travel. (<strong><em>2022 update</em></strong>: I saw another father with a Pebble Time on his wrist at the playground a few weeks ago!)</li></ul><p>Anyways, Pebble doesn’t exist today. A startup is always cycling from lows to highs. The trick is to stay alive between local minima and maxima. While we tried our best in 2016 to pull up from a year-long dive, we weren’t able to make it work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*caAnDed0BJRaTiMA" /><figcaption><em>The Startup Process — from the whiteboard at YC</em></figcaption></figure><h3>Here’s How We Failed</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wFMYXtl5E_iVYBPR.png" /></figure><p>In 2015 we came out with a new range of watches — Pebble Time. We had a very successful launch mid year on Kickstarter and began preparing for a wider retail rollout in the fall. Similar to most consumer electronics products, our watches had long production lead times (over 4 months) which meant we had to place all our build orders for the holiday quarter before we had results from the retail rollout.</p><p><em>I bet you can see what’s coming.</em></p><p>Retail sales were much lower than expected. Our <a href="https://www.kickstarter.com/projects/getpebble/pebble-time-awesome-smartwatch-no-compromises">2015 Kickstarter campaign</a> was huge — we sold over $20m watches and built our retail sales forecasts around this early traction. Our marketing efforts (outside of the Kickstarter campaign) were pretty awful. We basically dropped units into Best Buy and Amazon and expected them to sell accordingly. We didn’t do any of the standard practices like synchronizing a campaign across all channels or building a strong influencer network. We struggled with making strong decisions on marketing (and sticking to them) and wavered on hiring a head of marketing for years, before making a decision in early 2015.</p><p>This forecast miss left us at the end of 2015 with over $15m of inventory sitting in our warehouses. This put us into a cash crunch in early 2016 that we worked through the whole year to solve.</p><p>Other factors massively complicated this effort.</p><p>From 2013 to 2014 our revenues doubled from ~$30m to $60m. In 2015, we grew the company to catch up with growth but dramatically overshot in anticipation of future growth. We hired a bunch of talented people (filling big gaps in technical and team debt), moved to a new office and doubled our operating expenses. Unfortunately, in 2015 our revenue only grew 35% and our gross margin dropped from an okayish 35% to a dismal 27%. Our 2015 products also cost more to make than we anticipated.</p><p>We also struggled a ton in 2015 with our marketing and positioning.</p><p>In 2013, Pebble was the cool nerdy colourful watch that your coworker kept looking at during lunch. In 2014, Pebble Steel got shinier but still had a geek core (the box proudly displayed a Bitcoin tracker app). Around this time Apple came out with the Apple Watch and we thought the smartwatch market was about to explode. So in a quest for big sales growth, we figured our 2015 strategy would need to shift focus to a broader market, away from our core early adopter market positioning.</p><p>We settled on efficiency and productivity.</p><p>Pebble Time included our new timeline-based operating system that let you perform short, quick interactions (checking weather, calendar, sports, Uber) on your Pebble. We figured this would give us competitive differentiation from sports focused wearables and be useful for a broader set of users. While this software was certainly useful and made sense in the context of a watch, it was exceedingly difficult to explain why customers should care. It failed the ‘make something people want’ test. It was cool and some people used it a lot, but ‘I want my smartwatch to be more efficient’ was not a widespread hair on fire problem. We didn’t do our product research, we didn’t talk to enough of our users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*NwqsZd5ob_faGB_1" /></figure><p>We weren’t the only one with positioning problems. Look back at the original Apple Watch marketing. ‘Most precise timepiece ever.’ Ultra luxury $17,000 gold models. LVMH partnerships. Thousands of apps on your wrist. $350+ price point. It took Apple 2 years to reposition as a sports/fitness device. This turned out to be the largest market for wearables in 2016/2017. We eventually got there as well with <a href="https://www.kickstarter.com/projects/getpebble/pebble-2-time-2-and-core-an-entirely-new-3g-ultra">Pebble 2 and Pebble Core</a> but it was too late for us. This delay was solely my fault; my team had been pressuring me in 2015 to adopt a sports/fitness focus but I resisted, unsure of how we could differentiate and optimistic that our efficiency focus would work out.</p><blockquote>2022 addition<em>: It’s funny looking back on what I wrote back in 2017. I don’t think we would have really succeeded as a fitness watch even if we had doubled down on it in 2015. We weren’t a fitness company at our core.</em></blockquote><p>Another significant point that I’ll dive deeper into some other time: we started designing Pebble Time back in 2013. It took us way too long to get it to market. The industrial design was good, but it looked a lot more like a playful, colourful geeky watch than a productivity machine. There was a big mismatch between positioning and physical appearance. This demoralized our software design team as well as the industrial design folks because we weren’t being effective at targeting a specific user base. They both did a tremendous job in getting us back on track with our 2016 product lineup, though! RIP Cutts, PT2 and Core.</p><blockquote>My colleague <a href="https://twitter.com/notthatwitty">Andrew Witte</a> adds: <em>I think there’s a bit more to this. Not only did we not have a clear understanding of our target customer that was shared across hardware, software, and marketing, I think we allowed early success (KS1 and even to some extent KS2) to mask the fact that we never gained a good understanding of what our actual customers valued the most. We lucked into having made something people wanted (the original Pebble) and, IMO, never really were able to figure out exactly why it was successful. So it was hard to reproduce that success.</em></blockquote><h3>Some of the major lessons learned:</h3><ul><li><strong>Forecasting</strong>. This is the single most difficult challenge for a consumer hardware company, especially if it has a retail presence. There’s no silver bullet solution that I know of. We should have made smaller inventory purchases, risking less. We should have reacted quicker. And developing a shorter lead time supply chain would have helped a lot. Reducing the number of SKUs that you offer helps tremendously.</li></ul><p><em>2022 update</em>: <a href="https://www.businessinsider.com/peloton-company-history-rise-fall-2022-2">Peloton just got hit hard by this</a> last year. That made me feel like less of an idiot.</p><ul><li><strong>Don’t grow OPEX</strong> unless your revenue continues to grow. Duh. Seems obvious but still I screwed this up.</li><li><strong>Losing profitability</strong> didn’t help, but probably wasn’t the biggest problem. I got onto the VC fundraising treadmill without really acknowledging it, and didn’t create a fundraising strategy to support us.</li><li><strong>Market positioning</strong>. We forgot the cardinal YC rule: talk to customers. Build something people want. In 2015, we had the option to narrow our focus to a smaller but more distinct market positioning. Looking back, this is one of my biggest regrets. We could have been <em>the</em> smartwatch for hackers but we tried to grow our volumes and market share (and failed).</li></ul><p>That’s a broad look at where the company was back in 2015. But all of those issues could have been fixed if we had caught them a bit earlier and conserved our capital. After many months of pondering, <strong><em>I think two other issues were actually more critical and would have killed us even if we had solved all the other things.</em></strong> I’ll cover the biggest one in this post, and write a separate post on the other issue (how Pebble was in a ‘hits driven business’ and didn’t recognize it early enough). <em>2022 update: </em>I haven’t written this post yet, but long story short Pebble was on the ‘consumer electronics’ release cycle. We had to launch new products each year in order to make money. Instead, we could have charged a subscription or created enduring product lines that could be sold year-over-year.</p><p><strong>But our main issue was that I did a terrible job at defining our long-term vision</strong></p><p>I struggled over and over to define a strong long term vision for what Pebble as a company would accomplish. In some ways we were spoiled…when our Kickstarter in 2012 was super successful, we never had to go through the exhausting process of iterating on sales techniques to acquire customers. We had crystal clear marching orders in 2012: build exactly what we had promised our backers and make it as high quality as possible. That’s what we did in 2012–2014…we just built great smartwatches that we ourselves (young hackers) wanted to use. After Pebble Steel in 2014, we came up for air and found ourselves in a more competitive space. As discussed above, we attempted to expand into a new market, and failed.</p><p>When I would host our Friday all-hands meetings I’d talk about aspirational goals like ‘becoming the future of computing’. This was really my dream goal, inspired by decades of reading sci fi (like Jane<em> </em>from the <em>Speaker For The Dead</em>, <em>Daemon</em>, <em>Neuromancer</em>, <em>The Light Of Other Days</em>, <em>Devil On My Back</em>, etc etc).</p><p><em>Side note — one of my favourite celebrity Pebble sightings was on the wrist of William Gibson. A fellow Vancouverite, he very kindly answered an email later to hang out!</em></p><p>My personal vision was that Pebble would become a brain-computer interface company, with the smartwatch as the first always-on, always-worn gateway between computers and our bodies. But I rarely discussed this with the team, or even the exec team. My rationalization for not talking about this more, I think, was that this would distract us from the many tasks and problems we had at hand of just making and selling smartwatches.</p><p>I never invested time in building out a structured plan to <em>actually</em> make the brain-computer interface our company’s vision. It never guided our product development. We didn’t talk to customers about problems they had in this space. We never trained or hired engineers to pursue research in the space. It was never in our pitch decks to investors. Every so often it would come up in passing but when colleagues inevitably found holes with the logic I just moved on and focused on tasks at hand instead of trying to address concerns and improve the idea.</p><p>It got to a point where I didn’t even discuss it that much because I got apprehensive about folks thinking it was stupid or that I was just wrong; I was worried they’d lose confidence in me.</p><p>The irony is that while we were successful and growing revenue, I could have spent some of the social capital I’d earned to flesh out the idea and weathered any complaints about it being a stupid idea while it improved with feedback.</p><p>As soon as our growth slowed down in 2015, my colleagues began voicing their concerns more loudly about our lack of long term vision or strategy. I got the question many times ‘What are we really working on at Pebble? Are we a smartwatch company or something else?’. At that point, though, any answer I had for them just hadn’t been fleshed out enough. I toyed with different strategies, testing them out on my exec team and individuals around the company. But there was no foundation to the ideas; they all just felt like band-aids. We were also trying to dig ourselves out of the financial difficulties that we were in, so this took even a further backseat.</p><p>I’m continually amazed and thankful that so many talented colleagues stuck with me and the company through 2016. As I said before, startups are a continuing cycle of ups and downs. I really wish I could have provided a stronger, more motivating vision to keep us together in 2016.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*PutW9ZyOzn47DjMU" /></figure><p>Anyways, that’s a longer than expected post about Pebble in 2015/2016. Let me know in the comments if you have any questions or feedback. I’ll try to answer as much as I can. I’m now a partner at YC, where my goal is to help as many startups as possible become successful–and not just hardware companies!</p><p>Thanks for reading!</p><p>Eric Migicovsky</p><p><em>Thanks to several friends and past Pebble colleagues for reading earlier drafts of this back in 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7be937c6232" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Universal Communication Bus]]></title>
            <link>https://medium.com/@ericmigi/the-universal-communication-bus-42dfb9a141ad?source=rss-499f96b76542------2</link>
            <guid isPermaLink="false">https://medium.com/p/42dfb9a141ad</guid>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[instant-messaging]]></category>
            <dc:creator><![CDATA[Eric Migicovsky]]></dc:creator>
            <pubDate>Tue, 09 Jun 2020 18:37:11 GMT</pubDate>
            <atom:updated>2021-04-01T02:11:19.369Z</atom:updated>
            <content:encoded><![CDATA[<p><em>From the desk of Eric Migicovsky</em></p><p><strong><em>Edit</em></strong>: Interested in what you read below? Check out <a href="http://beeper.com/">Beeper</a>, an app that we built to solve this problem.</p><p><strong>Chat is only the latest incarnation of human communication.</strong> Technology gave us the ability to extend in-person conversations over large distances beginning (probably) with papyrus + carrier pigeons and continued with the postal system and telegraph, reaching its pinnacle recently with the invention of the Yo app.</p><p>The problem, now, is that basic communication is too complicated and time consuming. Today, even with fancy smartphones and LTE networks, exchanging bits of text is getting more difficult instead of easier! There are too many different chat apps. I can’t search across all of them. I can’t even remember which of my friends are on each app. It’s become even worse than the rats nest of cables we had to deal with before USB.</p><p>This is meant to be <em>human</em> communication. Technology needs to fade into the background, so I can simply chat with my friends, family and work colleagues. We need a universal communications bus.</p><h3>Chat Woes</h3><h4>Network Proliferation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/0*spjqWubVlYnCbt6N.png" /><figcaption><a href="https://xkcd.com/1810/">XKCD</a> on chat</figcaption></figure><p>In general, there are two distinct types of people:</p><ol><li><strong>Siloed</strong> — People who only use one chat network (eg iMessage) and force other people to use their preferred network in order to get in touch with them.</li><li><strong>Ambi-social</strong> — These folks use many chat networks, have 5+ chat apps on their phone, need to keep track of which friends are on which network so they know how to contact them.</li></ol><p>Maybe life would just be simpler as a siloed chat user but probably less fun! Many of us are cursed blessed with having friends in different countries, or in different age groups. We’ve experienced the proliferation of chat apps first-hand and fall into the ambi-social club, with a few good friends on every single platform.</p><p>Keeping track of which networks are friends are on is a communication tax. It’s extra cognitive load on simple stuff, like remembering where my friend sent me the name of the restaurant, or thinking ‘Should I send the photo I took to her via Whatsapp, iMessage or Instagram?’</p><p>My pet theory around why business is gets done so much faster in China: because there is only one channel for everything — WeChat. No confusion about how to get in contact with someone. One scrollback to WeChat makes it easy to introduce friends to each other. Voice and video calls just work. And because the default is chat, not email, everyone sends shorter messages, responds quickly and keeps their inbox at zero. I want that world! Minus the authoritarian overlords reading all your messages.</p><p>Known caveat: sometimes the medium is the message. A postcard is noticeably more personal than an email, a phone call conveys more emotion than a text, an Instagram message is more friendly than a Linkedin message. TBD how this is works out if all chats are merged into one.</p><h4>Slow-to-no innovation</h4><p>WhatsApp is fine, but how come you still can’t make a voice or video call from the desktop client? Signal may finally let you sign up without a phone number as the main identifier…5 years after the <a href="https://signal.org/blog/the-ecosystem-is-moving/">ecosystem got its move on</a>?</p><p><strong>There is a dearth of innovation in chat</strong>. It’s all weighed down by network effects. If you’re a developer, not only do you have to create your cool new feature (see Houseparty or Squadapp), you also need to bootstrap a network so that your users have friends to chat with.</p><blockquote>How come I can’t search across all my chat networks instantly?</blockquote><blockquote><em>Why don’t my ‘work’ WhatsApp notifications switch off after 6pm?</em></blockquote><blockquote>Why is there still a risk of losing message history when I switch phones?</blockquote><blockquote><em>How many tabs do I need to have open on my laptop at once just to stay in touch with my friends?</em></blockquote><blockquote>Why can’t I reply by voice to a text from my wife on my Google Home, or an Instagram message while I’m driving?</blockquote><p>Compare the speed of chat innovation with email. Front, Superhuman, Inbox (RIP😢), Substack and more continually push boundaries of what is possible with email. It feels like there’s a new email app every week on Product Hunt! On the work chat side, Slack has certainly enabled some great new features with bots and integrations, but switching between workspaces is still a pain.</p><p>Most new chat apps die before they build a network. And since all the major networks are closed-source and not federated, it’s hard to hack on top of an existing network and add in just one or two new features. It’s sad that there is nothing like Gmail plugins for WhatsApp. Even Signal, an open-source chat app, enforces a ‘no-federation’ rule — which means that you can’t host your own Signal server and add new features.</p><h3>Enter the Matrix</h3><p>A year ago I discovered <a href="https://matrix.org/">Matrix</a>. It’s an open-source federated, encrypted and decentralized database protocol. The main use for Matrix is chat, but theoretically it could be used to synchronize any bits of data across a network of federated servers.</p><p>Matrix actually caught my attention because it solves the exact problems that I outlined above, without exacerbating everything by creating yet another chat network. See, the Matrix folks <a href="https://xkcd.com/927/">know their XKCD</a>. Instead of creating a new siloed chat app, they enabled developers to write ‘bridges’ between Matrix and other chat networks, like Whatsapp, Telegram, Discord, Skype and even more obscure networks like Keybase. Now, instead of keeping 5+ different chat apps open, you can use just one app (Matrix) and talk to friends on their preferred chat network. The other person won’t even know that you’re using Matrix!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*OhyUrSqkyvzzFY7LuWK3ZQ.png" /></figure><p><a href="https://presents.half-shot.uk/slides/!mfikNYyXndTTDgQjAu:half-shot.uk/$F-4FHKkgjcLDJaKvw7C19NJ6BWkrk6n7GeIxK-TcxWg"><em>Image credit</em></a></p><p>I had been searching for something like this for years! I loved using Trillian and Meebo back in the day.</p><p>When I started getting into Matrix last year bridges were still missing to many networks I used regularly. I wanted to contribute but since my coding abilities peaked on my TI-83 20 years ago I started by funding developers to create open source Matrix bridges to popular chat networks. Bounties start at $500 or more per bridge — I’ve had fun funding the <a href="https://github.com/tulir/mautrix-hangouts">Hangouts</a>, <a href="https://github.com/Sorunome/mx-puppet-slack">Slack</a>, <a href="https://github.com/Sorunome/mx-puppet-instagram">Instagram</a>, <a href="https://github.com/tulir/mautrix-facebook">Facebook</a>, <a href="https://github.com/Sorunome/mx-puppet-twitter">Twitter</a> bridges and pressured my friend into building one for <a href="https://github.com/wechaty/matrix-appservice-wechaty">WeChat</a>. I still have bounties out for Line, Linkedin, Airbnb, Tinder, Gmail (getting a jump on jwz’s law), Snapchat and more. Ping me @eric:nova.chat!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vILzcbWOi7e4RtK0" /></figure><p><a href="https://twitter.com/matrixdotorg/status/1252888484211240963"><em>Image credit</em></a></p><p>These bridges are actually just an intermediate step. Since Matrix itself is an amazing chat network, eventually as more people start using bridges on Matrix, they’ll notice that their friends are already on Matrix, eliminating the need for bridges gradually over time.</p><p>I really believe that the world will be a better place when everyone is in the Matrix. Matrix is the non-proliferation treaty of chat. I think Matrix could form the basis for a true universal communications bus.</p><blockquote>The only downside to Matrix is that it’s still very complicated to set up and use with bridges. That’s a pretty big downside! A few Matrix developers and I are working on a way to make it easier to use — we’re building an app called <a href="https://beeper.com/"><strong>Beeper</strong></a>. Our goal is to make Beeper the best chat client for ambi-social people. Beeper (client) is to Matrix (protocol) as Gmail is to email.</blockquote><h3>Life on the UCB</h3><p>Cool, we’ve started using Matrix and bridged all our chat networks into one client. Now what’s possible?</p><ul><li><strong>Glorious productivity and time-saving</strong>. One desktop client that contains all your chats — no more alt-tabbing between apps and switching slack workspaces. Search across all networks instantly</li><li><strong>Sort your chats into ‘work’, ‘friends’, ‘family’ regardless of which network they are on</strong>. Avoid context switching during the workday, and switch off all work notifications when you need a break.</li><li><strong>Merge all communication with an individual person into one continuous timeline</strong>. I’m excited about this feature. My mom still hasn’t mastered the art of using one communication channel, she prefers to sprinkle messages throughout the week across Whatsapp, SMS and email.</li><li><strong>Hackable interface on which to experiment and build new chat features</strong>. It’s much easier to prototype new features if all your chat messages are in one database. We’re envisioning a plug-in framework allowing Gmail addon-like extensions.</li><li><strong>Escape Sauron’s eye</strong>. Matrix itself is a fantastic chat network. It’s end-to-end encrypted and federated, making it hard to block. The Matrix team is even working on portable identities — don’t like your host? Switch to a different provider. They even have a prototype of a p2p server that runs entirely in your browser.</li><li><strong>Communicate beyond the display.</strong> Networks like Facebook, Instagram and Twitter rely on ad impressions to make money, so there’s little incentive for them to work on devices without a display. Matrix can easily support new platforms like AirPods, Google Assistant and <a href="https://github.com/turt2live/matrix-alexa-skill">Alexa</a>.</li></ul><p>If you’re as interested in chat clients as I am, check out our new app <a href="http://beeper.com/">Beeper</a>. We built this specifically so solve this problem!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42dfb9a141ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hardware Founders: (When) Should You Try To Raise VC Money?]]></title>
            <link>https://medium.com/@ericmigi/hardware-founders-when-should-you-try-to-raise-vc-money-17bb01cbc1ee?source=rss-499f96b76542------2</link>
            <guid isPermaLink="false">https://medium.com/p/17bb01cbc1ee</guid>
            <category><![CDATA[ycombinator]]></category>
            <category><![CDATA[hardware-startup]]></category>
            <category><![CDATA[venture-capital]]></category>
            <dc:creator><![CDATA[Eric Migicovsky]]></dc:creator>
            <pubDate>Mon, 09 Jul 2018 22:31:25 GMT</pubDate>
            <atom:updated>2018-07-09T22:31:25.325Z</atom:updated>
            <content:encoded><![CDATA[<p>If you choose to raise any amount of venture capital investment you are making an implicit agreement with your investor that your aim is to grow the company to a valuation of more than $1bn within 5–10 years. Given a typical hardware multiple of 5x, that’s a minimum of $200m in yearly revenue. That is an incredibly large amount of money.</p><p>I recently heard a maxim about recurring software sales:<br>‘Growing from $0 to $1m ARR is impossible, $1m to $10m improbable, $10m to $100m inevitable’</p><p>With hardware sales, especially one-off consumer purchases, $1 earned this month has no bearing on future revenue. Unfortunately the effect can actually be the opposite — if you make an excellent long-lasting product, you will not earn another dime from that customer for a while!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F4plaHsHFg8Y49XcbdncgA.png" /></figure><p>At Pebble, we realized (too late) that we were in a ‘hits driven’ business, similar to video games. One hit product needs to provide enough profit to fuel many years of middling success. Looking back, I wish we had done more to grow sales and marketing of our first gen watch (a massive hit with over 1.1 million units sold) instead of solely shifting resources into our next gen watch.</p><p>On top of that, each stage of revenue for hardware companies is actually increasingly complex and difficult. We scaled production of 0 to 100,000 watches quite easily with a team of 12 people. But as we tried to find new markets for growth our baseline operational costs (team, marketing, logistics and manufacturing) grew in larger discrete chunks as we hunted for new revenue while supporting our millions of early customers.</p><p><strong>What does this have to do with VCs and investment?</strong></p><p>VCs (from seed to large institutions) build financial models and raise money from limited partners with the promise that they will return a profit according to the model. As a general rule of thumb, VCs operate with models that require $1bn valuations at an exit like acquisition or IPO. Anything smaller does not return enough profit to cover losses. With a few notable exceptions (Indie.vc comes to mind) this is evidence to support the meme in the HN/hacker world that VCs will push a startup to grow at all costs.</p><p>I don’t think VCs should be embarrassed about this, it’s just their business model. The important thing is transparency to founders.</p><p>For hardware founders, especially those in the consumer space, it’s important to recognize your choice when raising money from investors. It’s not just VCs either; angel investors almost exclusively want to see their founders grow companies through increasingly large funding rounds.</p><p>There are other paths available! Even though hardware is traditionally capital intensive, I recommend starting small. Try to spend as little money as possible launching an initial product for a small audience. See if they like it. Improve. Adjust your marketing. Work towards finding <a href="https://blog.ycombinator.com/the-real-product-market-fit/">real product market fit</a>. E-commerce has also made it much cheaper and efficient to market products directly to consumers without going through expensive distribution channels.</p><p>For example, bootstrapping or taking small (&lt;$1m) investment is a great starting point for building a solid, multi-million revenue generating and profitable business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jj1MkldzGMjdY9NIIVb7pQ.png" /><figcaption><a href="https://lumoshelmet.co/">Lumos</a> sells a beautiful and useful LED helmet for cyclists</figcaption></figure><ul><li>Lumos (awesome bike helmets),</li><li>Moment (mobile photography),</li><li>Adafruit and Sparkfun (electronics suppliers),</li><li>Nomad (phone accessories) and</li><li>Peak Design (accessories for photographers)</li></ul><p>If you find product market fit and experience exponential growth, great! That’s the best time to raise money. You know what your customers want and how to market to them. Now you can pour the VC gasoline into the tanks and accelerate.</p><p>Some fantastic hardware startups over the past few years backed by VC money.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zsv7YEWTeL7NXhAe8NPyNg.png" /><figcaption><a href="http://simplisafe.com/">Simplisafe</a> rocked ADT’s world with a smart, cheaper take on home security</figcaption></figure><p>Peloton started with a $600k Kickstarter then grew to $M’s in revenue. Ring and Dropcam built fantastic and affordable solutions to home security before sizable acquisitions by Amazon and Google. Simplisafe took 8 years to get up to speed, but then raised $50m from Sequoia and recently was acquired at a $1bn valuation.</p><p>Bellabeat (YC) has built a sizable fitness tracker business by focusing on a narrow niche. Cruise (YC) dismissed haters who said that a few smart engineers couldn’t overpower Google’s self driving car team and were acquired by GM to lead their entire autonomous efforts.</p><p>Be aware of the growth requirements that come with VC funding. If you are not already experiencing exponential growth or if that isn’t even your goal at all, consider bootstrapping or financing your business through other means.</p><p>If you are considering the VC journey, I would highly encourage applying to Y Combinator (<a href="https://www.ycombinator.com/apply/">applications open now</a>). YC has seen almost every single path you can take (positive and negative). We can help tremendously as you seek product market fit and after as you translate that success into a growing company.</p><p><em>Thanks to Marc Barros, Yuri Sagalov, Michael Seibel and Geoff Ralston for reading drafts of this post.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17bb01cbc1ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>