<?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[Yanda’s Blog - Medium]]></title>
        <description><![CDATA[Yan-David “Yanda” Erlich’s blog - Medium]]></description>
        <link>https://medium.com/yanda?source=rss----8a8226b8e005---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Yanda’s Blog - Medium</title>
            <link>https://medium.com/yanda?source=rss----8a8226b8e005---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:30:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/yanda" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Where AI Value Will Be Built Next]]></title>
            <link>https://medium.com/yanda/where-ai-value-will-be-built-next-504ba113e425?source=rss----8a8226b8e005---4</link>
            <guid isPermaLink="false">https://medium.com/p/504ba113e425</guid>
            <category><![CDATA[ai-coworker]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Yan-David (Yanda) Erlich]]></dc:creator>
            <pubDate>Thu, 29 Jan 2026 19:07:08 GMT</pubDate>
            <atom:updated>2026-01-29T19:07:07.010Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Not in the Model, in the Enterprise Environment</em></p><p>I wrote this article for <a href="https://b.capital/insights/where-ai-value-will-be-built-next/">B Capital News &amp; Insights</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RSCyXaDrCF-k4v9UoEAQAA.png" /></figure><h3>The Model Isn’t the Moat Anymore</h3><p>For two years, “AI progress” meant “the model got better.” That era is ending.</p><p>The evidence is stark: according to MIT’s State of AI in Business 2025 report, only 5% of enterprise GenAI pilots achieve measurable P&amp;L impact. S&amp;P Global found that 42% of companies abandoned most AI initiatives in 2025, up from 17% in 2024. The average organization scrapped 46% of AI proof-of-concepts before reaching production.</p><p><strong>These aren’t bad models. They’re bad environments.</strong></p><p>Model capability is still improving, but for most enterprises it is no longer the limiting constraint. What matters now is everything around the model: integration, governance, distribution, measurement and the ability to learn in production without breaking trust.</p><p>One constraint is consistently underweighted in almost every AI strategy deck I see: <strong>organizational fit.</strong></p><p>If AI is going to deliver durable value, it must function less like a tool and more like a <strong>coworker</strong>. One that collaborates with humans, operates inside real team workflows and carries context over time.</p><p>The winners won’t be the teams with the “smartest” model. They’ll be the teams with the best <strong>environment</strong> to deploy, trust and continuously improve AI.</p><h3>The Coworker vs. Tool Distinction</h3><p>This isn’t semantics. The difference between AI-as-tool and AI-as-coworker determines whether value compounds or collapses.</p><p><strong>A tool</strong> waits to be invoked. It processes inputs and returns outputs. It has no memory of your organization, no understanding of how your team actually works, no awareness of who should approve what. Every session starts from zero.</p><p><strong>A coworker</strong> maintains context across interactions. It knows your domain, your team’s terminology and your approval workflows. It can be delegated to, supervised and held accountable. It gets better at its job over time because it learns from outcomes, not just prompts.</p><p>The MIT data validates this distinction. Their research found that vendor-built solutions succeed at a 67% rate, while internal builds fail at a 67% rate. Why? Vendors who win are the ones building coworker-like systems with deep workflow integration, not generic tools bolted onto existing processes.</p><p>Consider what a new human hire experiences: onboarding, permissions, a manager, feedback loops, access to institutional knowledge, clear escalation paths. We don’t hand them a keyboard and expect productivity on day one. Yet that’s exactly how most enterprises deploy AI.</p><h3>The Shift: From Capability Race to Execution Advantage</h3><p>In practice, this shift shows up when AI performs well in pilots but fails to survive first contact with real workflows. Buyers are no longer asking “Does it ace a benchmark?” They’re asking a different class of questions altogether:</p><ul><li><strong>Integration</strong>: Can it plug into my workflows without rewriting my org chart?</li><li><strong>Governance</strong>: Can it touch sensitive data without creating security, privacy or compliance blowback?</li><li><strong>Accountability</strong>: Who is responsible when it’s wrong?</li><li><strong>Measurement</strong>: Can we evaluate it in production and improve it safely?</li><li><strong>Scale</strong>: Can we roll it out to thousands of users without adoption collapsing?</li><li><strong>Collaboration</strong>: Can it work with my team like a competent new hire, or does it just generate text?</li></ul><p>Those are not model questions. Those are execution questions.</p><p>And execution compounds. Deployment creates feedback. Feedback enables improvement. Improvement drives adoption. Adoption earns deeper integration. <strong>That loop becomes the moat.</strong></p><p>McKinsey’s 2025 AI survey confirms this pattern: organizations reporting “significant” financial returns are twice as likely to have redesigned end-to-end workflows before selecting models. The execution advantage emerges less from initial capability and more from the ability to learn safely in production over time.</p><h3>5 Ingredients of AI Execution Advantage</h3><p>By “environment,” I mean the structural conditions that let AI compound in production. These conditions determine whether improvement accumulates or stalls after deployment.</p><p><strong>1. Integration Surface</strong> <em>How quickly AI can ship into real workflows.</em></p><p>Value compounds fastest when AI lives inside the system of record, removes steps, reduces cycle time and tightens feedback loops. The MIT research shows that ROI is lowest in sales and marketing pilots, where most GenAI budgets are concentrated, and highest in back-office automation where integration is deepest.</p><p>The integration question isn’t “can we connect via API?” It’s “can we embed deeply enough to observe outcomes and improve?”</p><p><strong>2. Data Rights and Governance</strong> <em>What the system can legally and operationally learn from in production.</em></p><p>If you can’t observe outcomes, you can’t improve. If you can’t improve, you don’t compound. Companies that solve this and can learn from production without violating governance will outperform those that can’t.</p><p><strong>3. Distribution and Procurement</strong> <em>How deployments become default, not optional.</em></p><p>AI doesn’t win by demos. It wins by rollout. PwC’s 2025 survey found that 79% of organizations have adopted AI agents at some level, but only 35% report broad adoption, and 68% say half or fewer employees interact with agents in their daily work. The gap between “we have AI” and “AI is how we work” is primarily a distribution problem.</p><p><strong>4. Production Learning Loop</strong> <em>Evaluation, monitoring and improvement without breaking trust.</em></p><p>Real-world evaluation tied to business KPIs. Monitoring for drift and failure modes. Human routing for uncertainty. Continuous improvement with governance guardrails. Gartner predicts that 30% of GenAI projects will be abandoned after proof-of-concept by the end of 2025. Not because the technology failed, but because organizations couldn’t build the infrastructure to improve safely in production.</p><p><strong>Organizational Fit</strong> <em>AI must function as a coworker, not a tool.</em></p><p>This is the missing pillar that most AI strategies ignore entirely. Enterprises are networks of roles, permissions, incentives and handoffs. “Agentic” only works when AI behaves like a well-scoped teammate: collaboration mechanics inside existing workflows, identity and least-privilege permissions, durable memory and context and on-the-job learning that operates without violating governance.</p><p>When I evaluate AI companies, I ask: “Would you hire this system as a junior employee?” If the answer requires caveats about supervision, permissions and trust boundaries, you’ve identified the product work that matters.</p><h3>Where AI Value Compounds Fastest</h3><p>Value concentrates where execution environments support compounding</p><p><strong>Instrumented digital workflows</strong> where shipping is fast and telemetry is rich. Software development, customer support, back-office operations. Anywhere outcomes can be observed quickly and iteration is cheap.</p><p><strong>High-volume operational workflows</strong> with clear accountability and measurable outcomes. Claims processing, compliance review, financial operations. Environments where “better” is quantifiable and feedback is continuous.</p><p><strong>Physical operations with telemetry</strong> and hard KPIs. Manufacturing, logistics, healthcare delivery. Domains where the system of record captures reality and improvement is directly measurable.</p><p>Generic assistants without durable data rights, distribution leverage and a compounding learning loop get competed down to commodity margins.</p><h3>What This Means for Founders</h3><p>Markets are not just industries. They are execution environments. This favors teams that optimize for compounding environments over early polish or surface-level performance.</p><p><strong>Wedge into the system of record.</strong> Don’t build alongside the workflow. Become the workflow. The difference between “we integrate with Salesforce” and “we are where deals get done” is the difference between tool and coworker.</p><p><strong>Secure data rights early.</strong> The legal and operational ability to learn from production is a moat. Companies that negotiate this upfront, while offering clear value exchange, will outperform those who treat it as a Phase 2 problem.</p><p><strong>Design for procurement from day one.</strong> Audit logs, SSO, role-based access and compliance certifications. These aren’t features; they’re prerequisites for the environments where AI compounds.</p><p><strong>Treat evaluation as product.</strong> If you can’t show measurable improvement on business KPIs, you can’t justify continued investment.</p><p><strong>Build the AI coworker layer.</strong> Collaboration, identity, permissions, memory and handoffs. This is the unsexy work that separates pilots from production systems.</p><p>Environments that support compounding often look weaker early yet outperform over time. This allows founders to look wrong early and still be right in the long run.</p><h3>What This Means for Enterprises</h3><p>Buying AI like ordinary software and expecting it to behave like ordinary software does not work. AI systems improve only when they are treated as production systems with owners, feedback and failure modes.</p><p><strong>Establish an AI operating model.</strong> Clear owners, defined accountability and incident response. Who is responsible when the AI makes a mistake? If you can’t answer this question, you’re not ready for production.</p><p><strong>Tie AI performance to business KPIs.</strong> Not accuracy metrics, not user satisfaction scores. Actual business outcomes: revenue, cost, cycle time and error rates.</p><p><strong>Reduce fragmentation where learning loops need consistency.</strong> Every team using a different AI tool means every team learning in isolation. Consolidation isn’t about cost savings; it’s about compounding.</p><p><strong>Treat AI coworker fit as a first-class requirement.</strong> When evaluating vendors, ask: “How does this integrate with how my team actually works?” Not how it works in a demo. How it works in your environment, with your permissions, your approval flows and your existing tools.</p><h3>What This Means for Investors</h3><p>Model quality is no longer the primary diligence question. Instead, evaluate:</p><p><strong>Ownership of the integration surface.</strong> Does the company control the system of record, or are they dependent on someone else’s platform?</p><p><strong>Durable data rights and credible governance.</strong> Can they legally and operationally learn from production? Is their data strategy a moat or a liability?</p><p><strong>A scalable distribution path.</strong> Can they reach thousands of users without a proportional increase in sales and support costs?</p><p><strong>Evidence of a production learning loop.</strong> Are they improving from deployment, or shipping static models?</p><p><strong>A credible path to AI coworker fit.</strong> Can they function inside real enterprise environments with real permissions and real accountability?</p><p>We believe the best AI investments right now are companies building execution infrastructure, not model capability alone. The model layer is commoditizing; the execution layer is where durable value will be built.</p><p>How This Shows Up in Our Portfolio</p><p>This framework has shaped our investing strategy for some time. A few examples:</p><p><strong>Perplexity:</strong> Enterprise knowledge work is an execution environment problem. Perplexity’s enterprise offering is explicitly about deploying AI into organizational context: collaboration in Spaces, answers from organizational apps and files, enterprise permissioning, auditability and “no training on your data.” This is governance, distribution and coworker-fit working together in production.</p><p><strong>Unblocked:</strong> A literal AI coworker for engineering teams. Unblocked plugs into the tools engineers already use, connects code, documentation and conversations, supplies shared team context that makes other AI coding tools more effective. Enterprise fit is table stakes: SSO, RBAC, audit logs and security posture designed for production.</p><p><strong>Goodfire:</strong> If you care about production reliability, you eventually care about controlling behavior, not just prompting it. Goodfire is building interpretability tooling that surfaces failure modes, enables behavior design and supports durable fixes. This maps directly to the production learning loop and governance required for AI systems to improve safely.</p><p><strong>Axiom:</strong> In domains where correctness is existential, value shifts toward systems that can reason rigorously and be evaluated against hard truth. Axiom’s focus on an AI mathematician is a wedge into verifiability-first reasoning. It’s upstream capability in service of downstream production requirements.</p><h3>Where Advantage Compounds</h3><p>For the next decade, the biggest AI outcomes will not come from “the model got better.”</p><p>They will likely come from environments where AI can be deployed, trusted, measured and improved continuously inside real workflows. The environments we choose to build in will determine which AI systems endure.</p><p>The data is already pointing the way: 95% of pilots fail not because AI doesn’t work, but because organizations haven’t built the necessary working environment. The 5% that succeed share common characteristics: deep workflow integration, clear governance, production learning loops and organizational fit.</p><p><strong>Capability is table stakes. Execution advantage is the moat.</strong></p><p>The question for founders, enterprises and investors isn’t “which model is best?” It’s “which environments support compounding?”</p><p><strong>Build there, and if you’re already building there, I’d love to talk to you.</strong></p><p><em>Yan-David “Yanda” Erlich (that’s me </em>😀<em>) is a General Partner at </em><a href="https://b.capital/"><em>B Capital</em></a><em>, where he focuses on AI infrastructure and AI coworker investments. Previously, he was COO &amp; CRO at </em><a href="https://wandb.ai/site"><em>Weights &amp; Biases</em></a><em> and a GP at Coatue.</em></p><p>LEGAL DISCLAIMER <br><em>All information is as of 1.21.2026 and subject to change. This content is a high-level overview and for informational purposes only. Certain statements reflected herein reflect the subjective opinions and views of B Capital personnel. Such statements cannot be independently verified and are subject to change. The investments discussed herein are portfolio companies of B Capital; however, such investments do not represent all B Capital investments. It should not be assumed that any investments or companies identified and discussed herein were or will be profitable. Past performance is not indicative of future results. The information herein does not constitute or form part of an offer to issue or sell, or a solicitation of an offer to subscribe or buy, any securities or other financial instruments, nor does it constitute a financial promotion, investment advice or an inducement or incitement to participate in any product, offering or investment. Much of the relevant information is derived directly from various sources which B Capital believes to be reliable, but without independent verification. This information is provided for reference only and the companies described herein may not be representative of all relevant companies or B Capital investments. You should not rely upon this information to form the definitive basis for any decision, contract, commitment or action.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=504ba113e425" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yanda/where-ai-value-will-be-built-next-504ba113e425">Where AI Value Will Be Built Next</a> was originally published in <a href="https://medium.com/yanda">Yanda’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Valuing Early Stage Equity: An Optimism-Weighted Approach]]></title>
            <link>https://medium.com/yanda/valuing-early-stage-equity-an-optimism-weighted-approach-ce97510609c3?source=rss----8a8226b8e005---4</link>
            <guid isPermaLink="false">https://medium.com/p/ce97510609c3</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[venture-capital]]></category>
            <dc:creator><![CDATA[Yan-David (Yanda) Erlich]]></dc:creator>
            <pubDate>Thu, 27 Aug 2020 18:09:24 GMT</pubDate>
            <atom:updated>2020-08-27T20:44:24.351Z</atom:updated>
            <content:encoded><![CDATA[<p><em>If you’re looking for the worksheet and want to skip reading the associated post, you can find it </em><a href="https://docs.google.com/spreadsheets/d/1Cw1JK1EzU0n0tsq5vk5dSs85liAFtXZTwSWjMyOkiaA/edit?usp=sharing"><em>here</em></a><em>.</em></p><h3>Who Is This For?</h3><p>If you’re reading this, you may already have an offer from an early-stage startup and are looking to understand the value of the equity portion of your comp package. For simplicity, let’s call this prospective employer <em>Early Inc.</em> You may even have multiple offers, including one from a later-stage company <em>(Later Corp)</em> that you’re comparing it with.</p><p>Let’s start with three things you should NOT do at this juncture:</p><ol><li>Discount the value of the equity to zero and focus solely on the base/cash portion of the package. If you choose your startup correctly, the equity will be the most significant portion of your compensation, possibly by orders of magnitude of your cash comp.</li><li>Choose to work at a later-stage or public company strictly because their equity is easier to value. There are many reasons to choose a <em>specific</em> later-stage company over a <em>specific</em> earlier stage one, but ease of equity calculation shouldn’t be one of them.</li><li>Multiply the shares you’d be granted by either the price-per-share (PPS) of the most recent round of financing or the most recent 409A valuation. Both of these calculations will provide you with the current value of the equity, essentially the value at which you’re “buying” the equity, but they won’t give you the value at exit, which is when the equity would be “equivalent to cash.” It’s the latter you’re looking to understand.</li></ol><p>Estimating the value of startup equity at exit is hard work. An early-stage company faces a long and arduous journey prior to an exit that could take a number of forms, e.g. an acquihire, a medium-sized sale for product and technology, a larger acquisition, or an IPO in addition to a shutdown in the worst case or, on the flip side, the moonshot scenario of becoming a deca-billion-dollar category-defining disruptor.</p><p>The best way to account for all of these variables is by performing an <em>optimism-weighted calculation</em>.</p><h3>Why Does This Matter?</h3><p>Let me first tell you about a mistake I made many years ago.</p><p>In 2005, I had an offer from Google, a tech giant fresh off of its IPO. I also had an offer from Facebook, which was a tiny early-stage startup at the time. The value of Google’s equity in “2005 value” was 10x that of Facebook’s. I joined Google.</p><p>When Facebook went public seven years later, the value of both equity offers in “2012 dollars” (when Facebook’s equity was finally “equivalent to cash”) flipped dramatically — Facebook’s equity offer was all of a sudden 50x greater than Google’s.</p><p>Now, don’t get me wrong. I had a great time at Google and met many of my closest friends there, but I wish I had known to perform my own optimism-weighted calculation for both companies before making my final choice.</p><p>I want to help you avoid this mistake.</p><h3>How Does It Work?</h3><p>First, you’ll need to get some data from the company:</p><ol><li>The number of shares they are granting you (this should be in the offer)</li><li>The latest valuation</li><li>The latest price per share (PPS)</li></ol><p>If they are unwilling to share this data, don’t join! It’s a massive red flag for a company to withhold any important materials you might need to make an informed decision about the next decade of your life.</p><p>Second, you need to forecast a series of scenarios that the company could ultimately wind up in. At the very least, I would propose sketching out the following:</p><ul><li>A shutdown whereby the company ends up being worth $0</li><li>A small acquihire</li><li>A modest sale to a competitor</li><li>A meaningful sale to a large private company or a public one</li><li>An IPO</li><li>Becoming a category-defining public company</li></ul><p>Next to each scenario, you should estimate the probability of the outcome as well as the amount the company would be worth.</p><p>One thing you absolutely do NOT want to do is ask the founders or hiring managers to provide these forecasts. You can and should do your own due diligence regarding the company’s thought process on the grander vision, the opportunities that lie ahead, the pitfalls, etc. But you need to fill in the outcomes and probabilities yourself because you want your optimism reflected back, not theirs.</p><p>There are three questions I like to ask the company representatives to help me think through the possible outcomes and their probabilities:</p><ol><li>In your wildest dreams what does this company look like? And what needs to go right for that outcome to be realized?</li><li>The company hasn’t achieved your wildest dreams. What happened and what does it look like instead?</li><li>Tell me about the worst-case scenario, i.e. the company failed. What happened and why?</li></ol><p>You should end up with a table that looks like this, but with your own scenarios and numbers:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x6dhU7KNfWjlvfogwIg6kQ.png" /></figure><p>Next Steps:</p><ol><li>For each scenario, compute the price per share for that scenario using the following formula:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*WHTlZ7fnhd1ktooH04kfhg.png" /></figure><p>2. Compute the optimism-probability weighted average PPS</p><p>3. Multiply that PPS by the number of shares you are being offered</p><p>This calculation is incredibly informative as it’s a reflection of your own view of the future potential of <em>Early Inc</em>. The more excited you are about it being a big category-defining company, the more you will see that reflected back in the optimism-weighted value of your shares and vice versa.</p><p>To make this interactive, I’ve set up a worksheet that you can copy and play around with <a href="https://docs.google.com/spreadsheets/d/1Cw1JK1EzU0n0tsq5vk5dSs85liAFtXZTwSWjMyOkiaA/edit?usp=sharing"><strong>here</strong></a>.</p><h3>What Are Reasonable Probabilities?</h3><p>What is a reasonable expectation for the probability of a company shutting down or going public? Base rates can inform your judgment. For the cohort of startups founded since 1995, the histogram of the probability of outcomes looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JpvlUbhriNjo92LvQLakQA.png" /><figcaption>Source: <a href="https://rmksv.com/category/silicon-valley/">https://rmksv.com/category/silicon-valley/</a></figcaption></figure><p>That said, if you’re relying exclusively on the base rates above, you’re essentially telling yourself that <em>Early Inc</em> is an “average company,” and that could end up dramatically underestimating the outlier outcomes that you’re so carefully attempting to factor-in. So you should use these base rates as a sanity check rather than a replacement for your own probability projections.</p><h3>Advanced: Additional Dilution</h3><p>In an effort to increase the accuracy of your final projections, albeit slightly, you could also estimate how much additional dilution the company will incur from future rounds of financing. I wouldn’t worry too much about getting this 100% correct as the effects from additional dilution will likely be subsumed by the margin of error of your probability estimations anyway. But the general adage here is that the bigger the exit valuation (as a multiple of today’s valuation), the more rounds of financing (and dilution) the company is likely to incur along the way.</p><p>To incorporate this, you’d have to make a small tweak to the PPS calculation in the algorithm above:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gLP1e5gvyEd5ewmDLboRcg.png" /></figure><p>This variable is reflected in the <a href="https://docs.google.com/spreadsheets/d/1Cw1JK1EzU0n0tsq5vk5dSs85liAFtXZTwSWjMyOkiaA/edit?usp=sharing">linked worksheet</a>. If you want to ignore additional dilution, just set it to 0% for every scenario.</p><h3>Comparing Offers</h3><p>The optimism-weighted approach is also incredibly useful if you want to compare two companies against each other. Fill in the values for each entity and see how the weighted average differs. This approach affords the ability to do an “apples-to-apples” comparison between an early-stage opportunity with a later-stage one, which the more commonly used approach of multiplying the granted shares by the latest valuation PPS does not.</p><p>For illustration purposes, let’s look at two hypothetical scenarios:</p><h4>1. Versus another Early Stage Offer</h4><p>First, let’s compare <em>Early Inc</em> to <em>OtherEarly Corp</em>. To showcase the importance of the optimism-weighted probabilities, I’ve made the values equal across the board for both companies except for the P(Outcome) columns (Columns C and K <a href="https://docs.google.com/spreadsheets/d/1Cw1JK1EzU0n0tsq5vk5dSs85liAFtXZTwSWjMyOkiaA/edit?usp=sharing">in the worksheet</a>). Notice how this impacts the end result: <em>Early Inc’s</em> optimism-weighted value for your shares is more than 40% greater than for <em>OtherEarly Corp</em>. Also compare the (useless) value today to the optimism-weighted average: the latter is 120x greater.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nz12zETkfm6eT2lyA9PtGw.jpeg" /></figure><h4>2. Versus a Later Stage Offer</h4><p>Now, let’s compare <em>Early Inc</em> to a later-stage company (<em>Later Corp</em>) with a current valuation that’s 20x greater. In this case, <em>Later Corp’s</em> valuation today is $200M to <em>Early Inc’s </em>$10M, and the today value of <em>Later Corp’s</em> equity grant is 5x that of <em>Early Inc’s</em>.</p><p>The probability of worse outcomes for <em>Later Corp</em> is also lower, given that the mortality rate of startups tends to decrease as they raise more money. Nevertheless, since we have a more optimistic view for Early Inc over the long run, the optimism-weighted average reveals that Early Inc shares are worth more than 3x those of Later Corp.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NVbKAvhHLpzcC-Jhio5P5g.jpeg" /></figure><h3>Conclusion</h3><p>Is the optimism-weighted value the correct one? The only way to find out is to work at <em>Early Inc</em> for the next few years, or decades. If your own optimism for the company suggests that you should take the offer, you hopefully won’t regret it, even if your calculations are a little off.</p><h3>About the Author</h3><p>Yanda Erlich is a General Partner at Coatue Management (“Coatue”), where he leads the enterprise software practice for Coatue’s venture fund, which invests in pre-Seed to Series B companies. Yanda led Coatue’s investments in Weights &amp; Biases, Impira, Fin, and Bonjour.io, among others. The opinions contained herein are his own and are not the opinions or views of Coatue. Moreover, the opinions expressed in this blog should not be considered employment, investment, tax or other advice from Coatue and Coatue may or may not hold positions in the in the companies referenced in this article.</p><p>Prior to joining Coatue, Yanda founded four venture-backed B2B companies: two were acquired (Mogad and ChoiceVendor), one failed (Happiness Engines), and one is still going. The latter is Parsable, which he founded with colleagues Ryan Junee and Chase Feiger and ran as CEO for the first 5 years before Lawrence Whittle, then CRO, was promoted to CEO.</p><p>Before becoming a professional investor, he was an active angel and an early investor in Mixer Labs (acq. Twitter), Thumbtack, MasterClass, CircleUp, and Buddybuild (acq. Apple). Yanda started his career with software engineering and product management roles at both Microsoft and Google.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce97510609c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yanda/valuing-early-stage-equity-an-optimism-weighted-approach-ce97510609c3">Valuing Early Stage Equity: An Optimism-Weighted Approach</a> was originally published in <a href="https://medium.com/yanda">Yanda’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crypto rabbit-hole: the saga continues.]]></title>
            <link>https://medium.com/yanda/crypto-rabbit-hole-the-saga-continues-ca518b39ba1a?source=rss----8a8226b8e005---4</link>
            <guid isPermaLink="false">https://medium.com/p/ca518b39ba1a</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Yan-David (Yanda) Erlich]]></dc:creator>
            <pubDate>Wed, 11 Jul 2018 16:21:53 GMT</pubDate>
            <atom:updated>2018-07-11T16:21:53.407Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Disclaimer: </em></strong><em>The views expressed herein are my own and do not reflect the view of any third party. This is not a recommendation to buy or sell securities or other products and should not be considered investment advice.</em></p><p>I spent the last year going deep down the cryptoasset rabbit hole. (Side note: If you’re just getting started, <a href="https://medium.com/yanda/getting-up-to-speed-on-crypto-195e5d494bb7">check out my crypto primer</a>.) Below is my latest thinking on areas I find interesting:</p><h3>Regulated Moats</h3><p>The number of cryptoasset holders grew to ~20-25M since 2011. In comparison, the number of banked adults worldwide grew by ~700M over the same period. One of the major building blocks to widespread adoption is to get more people owning (&amp; feeling safe owning) the category. This could take several shapes:</p><ul><li>Regulated exchanges, particularly mobile-first ones. For comparison, mobile-first banking is what drove the increase of banked accounts worldwide.</li><li>Financial infrastructure “copies” for crypto: custody, insurance, etc. Things to make institutions feel comfortable investing in crypto.</li><li>Other forms of on-ramps that provide retail or mass-market investors with access without (1) the need to deploy significant fiat capital and (2) the mental load or fear of not knowing which assets to select. These could be: (a) index funds (cf Bitwise HOLD10), (b) round-up-the-change models (eg. Acorns, but for crypto), (c) investment management (cf. Scout), etc…</li></ul><p>Why these are interesting:</p><ul><li>Regulation makes them hard to build, so they have natural moats.</li><li>Regulation makes them regional, so there is natural fragmentation &amp; opportunity to diversify.</li><li>Value is proportional to volume (vs price) and should at-scale be uncorrelated from cryptoasset swings.</li><li>Value accrues to equity in the corporation and largely uncorrelated from which cryptocurrencies ultimately win.</li></ul><h3>Products that own the user relationship</h3><p>Throughout the ages, companies that have created immense shareholder value have: (1) owned the relationship with their end user, (2) had some form of demand-side increasing returns (aka. network effects), particularly if they could create new networks or new network shapes. There’s no reason to believe this won’t also be true in crypto. If you believe, as I do, that the protocol layer will become commoditized over time (cf. <a href="https://medium.com/yanda/getting-up-to-speed-on-crypto-195e5d494bb7">John Pfeffer’s paper</a>), then more value is likely to accrue to the “experience layer.” Some interesting potential examples:</p><ul><li><strong>For utility cryptoassets</strong>: “banks” that hold SoV tokens (eg. Bitcoin) and dynamically shift in &amp; out of non-SoV tokens to purchase protocol resources/tokens on an as-needed/spot basis. Think a file storage app that automagically provisions the cheapest utility storage resources behind the scenes</li><li><strong>For tokenized securities</strong>: being the tokenization / administrator layer for tokenized securities (eg. Harbor for real estate, a similar play for tokenized equity). This also puts you in a great position to be the market maker for primary &amp; secondary transactions.</li><li><strong>For new tokenized assets</strong>: Platforms to transact attention, DNA, healthcare records (eg for pharma research), etc…</li></ul><p>Reasons these are interesting:</p><ul><li>Owning the user relationship + network effects are historical great sources of value for businesses. No reason to assume this won’t work in crypto</li><li>These won’t be quick flip ICOs but will have to be built over the long-run into long-lasting businesses. This hopefully means the entry valuations more resemble non-crypto investments.</li></ul><h3>A parallel ecosystem in Asia</h3><p>Technology (search, communications, commerce, …) and finance (currency exchange, banking, credit, etc…) have both historically followed a parallel model in Asia. It’s possible crypto will buck the trend but early signs seem to indicate otherwise. As with non-crypto tech, Asia is a notoriously difficult market to tract but also present potentially enormous opportunities.</p><h3>What’s not interesting</h3><p>I’d be remiss if I didn’t state the things I don’t find as interesting:</p><ul><li><a href="https://medium.com/yanda/eth-bulls-are-doomsday-preppers-scenario-analysis-for-high-utility-token-value-b65dcc754221">Utility cryptoassets</a>. These may create a lot of value but I don’t see the path for them claiming any of it. It’s the crypto equivalent to undersea internet cables or open source software.</li><li><a href="https://medium.com/yanda/icos-are-charity-fundraisers-3d397a8be0f3">ICOs</a>. They’re overpriced, useless, and likely illegal. Why would you want to hoard the crypto equivalent of Chucky Cheese tokens?</li><li>Businesses that add crypto to places where it’s not value-add to their customers. If your product doesn’t need to be distributed and censorship-resistant, don’t use a cryptoasset. Startups are hard enough. Don’t make a difficult challenge worse. Remember, VCs are not your customers.</li></ul><p>If you liked reading this, <a href="https://twitter.com/yanda">follow me on Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca518b39ba1a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yanda/crypto-rabbit-hole-the-saga-continues-ca518b39ba1a">Crypto rabbit-hole: the saga continues.</a> was originally published in <a href="https://medium.com/yanda">Yanda’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ETH bulls are doomsday preppers. Scenario analysis for high utility token value.]]></title>
            <link>https://medium.com/yanda/eth-bulls-are-doomsday-preppers-scenario-analysis-for-high-utility-token-value-b65dcc754221?source=rss----8a8226b8e005---4</link>
            <guid isPermaLink="false">https://medium.com/p/b65dcc754221</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Yan-David (Yanda) Erlich]]></dc:creator>
            <pubDate>Tue, 10 Apr 2018 14:16:19 GMT</pubDate>
            <atom:updated>2018-04-10T14:16:18.990Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently re-read <a href="https://medium.com/u/47b98efcd618">John Pfeffer</a>’s excellent paper: <a href="https://medium.com/john-pfeffer/an-institutional-investors-take-on-cryptoassets-690421158904"><em>An (Institutional) Investor’s Take on Cryptoassets</em></a><em> </em>(the full paper is linked at the bottom of his blogpost). A quick cliff notes of John’s view of protocol/utility tokens is below, though I encourage you to read his paper to get the full picture:</p><ul><li>The total value (M) of a utility or protocol token (eg. ETH) can be calculated by the formula PQ/V where P is the total price of the utility provided, Q is its quantity, and V is the velocity of money (eg. how fast it moves through the system. A token’s individual value is hence M/T where T is the total of tokens.</li><li>For protocol/utility tokens, John argues that PQ is a function of the total compute resources required to deliver the utility itself: network, compute, etc and no more.</li><li>Over the long-term horizon PQ should be low as the value of all these resources (through Moore’s law, etc.) depreciates over time. Cf. the cost of a gigabyte (GB) was <a href="https://www.statisticbrain.com/average-cost-of-hard-drive-storage/">more than 400k in 1980 and less than 2 cents in 2016</a>.</li><li>Furthermore V should be high because the currency here is digital, so moves at the speed of light. Hence PQ/V is low, essentially the marginal cost of providing the utility divided by the velocity.</li><li>This makes utility protocols (read: any cryptoasset that is not the ultimate non-sovereign store of value) a pretty unappealing investment. Note the value created by these protocols can still be very high, but most of that value is claimed by the users, not the creators of the protocol itself.</li></ul><p>I’ve been thinking about the relative value of native cryptoassets (here “native”, as opposed to tokenized securities), and I come back to agreeing with John’s perspective. I think ICOs for utility tokens amount to public good (eg, charity) fundraisers, which will be the subject of a later post.</p><p>That said, I thought it might be interesting to</p><ol><li>Assume John’s model for evaluating the value of a utility protocol is accurate, namely that M = PQ/V</li><li>Figure out if there’s a scenario where utility or protocol tokens (eg. Ethereum) can actually be worth a lot</li></ol><p>To wit, in order for a utility protocol to be worth a lot, the following must be true:</p><ol><li>PQ is high, which implies (a) P is high and/or Q is high and (b) P ≠k/Q for some constant k</li><li>V is low</li><li>Forks are hard</li></ol><p>One case where 1–3 are likely to be true is a universe where cryptoassets are illegal in a large enough subset of the world, and where ownership &amp; production thereof are prosecuted brutally (eg. prison time, death sentences, etc.) In that universe:</p><ul><li>P is likely to be <strong>high</strong>. Even if general compute, network, etc. costs are depreciating, the aforementioned risk in allocating these resources to a protocol would be reflected in their price.</li><li>V is likely to be <strong>low</strong>. For protection, cryptoasset networks would likely use multiple hops across decentralized Tor-like networks to evade prosecution, and likely layer-on privacy primitives such as zk-SNARKs which would both increase computational complexity (PQ higher) and decrease velocity.</li><li>Forks are likely to be <strong>hard</strong>. One reason might be that the cryptoasset community would have reason to be wary of forks as potential honeytraps by hostile government actors. In this universe, networks that have been around longer (and hence with fewer arrests or negative consequences) develop a reputation as safer, thus giving them the ability to extract rents higher than their newer forks.</li><li>Q is the hardest to imagine being high, but it seems more feasible to imagine a world where Q ≫ k/P. In a world where enough wealth is embodied in cryptoassets (we’re pretty close) and several large countries (eg. China) were to ban cryptoassets, this would likely hold. If P is sufficiently high (think black market prices) and Q is modestly high, PQ is high</li></ul><p>Turns out John alludes to this on page 3 of his paper with the sentence: <em>“use cases will be limited to dematerialised networks where the value of decentralization, censorship-resistance and trustlessness is high enough to justify the inherent inefficiency and redudancy of the consensus mechanism”</em></p><p>AKA: (crypto) doomsday scenarios.</p><p>To be fair, Bitcoin is also likely to be worth a lot in doomsday scenarios, so rather than hold a basket of cryptocurrencies, a better asset mix might be Bitcoin + whiskey + bullets.</p><p><strong>What are other scenarios where PQ/V is high &amp; forks are hard?</strong></p><p>If you’re curious where the crypto world is going, I’m always excited for a chat.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b65dcc754221" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yanda/eth-bulls-are-doomsday-preppers-scenario-analysis-for-high-utility-token-value-b65dcc754221">ETH bulls are doomsday preppers. Scenario analysis for high utility token value.</a> was originally published in <a href="https://medium.com/yanda">Yanda’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cap Table Simulator]]></title>
            <link>https://medium.com/yanda/cap-table-simulator-11bcb415eac3?source=rss----8a8226b8e005---4</link>
            <guid isPermaLink="false">https://medium.com/p/11bcb415eac3</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[venture-capital]]></category>
            <dc:creator><![CDATA[Yan-David (Yanda) Erlich]]></dc:creator>
            <pubDate>Tue, 27 Mar 2018 15:46:49 GMT</pubDate>
            <atom:updated>2018-03-27T15:46:49.130Z</atom:updated>
            <content:encoded><![CDATA[<p>Almost exactly two years ago, I wrote a post about helping friends navigate the eternal “<a href="https://medium.com/yanda/what-does-this-financing-do-to-my-ownership-b85fa918627">what will this financing do to my ownership?</a>” question. Two years later, it’s still fundraising season (yes, it’s still always fundraising season), and while the original spreadsheet was good, it’s time for something better.</p><p><a href="http://captable.yanda.com/"><strong>An interactive simulator</strong></a><strong>!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2v8N-uw8RdDH1lsbNHfonA.gif" /><figcaption>The cap table simulator in action</figcaption></figure><h3>What does it do?</h3><p>With this simulator, you can:</p><ul><li>Add Common Stock or Option Grants</li><li>Add Convertible Notes or SAFEs</li><li>Add Equity rounds</li></ul><p>You can layer as many rounds as you’d like, with one or multiple investors per round.</p><p>The simulator will take care of:</p><ul><li>Automagically calculating everyone’s ownership stakes at every round</li><li>Understanding if your notes convert uncapped, at cap, or discount</li><li>If a down round is triggered (startups are hard &amp; this happens sometimes), what the broad-based weighted-average anti-dilution protection looks like for all previous equity &amp; noteholders</li></ul><h3><strong>A note on sharing &amp; privacy</strong></h3><p>Everyone, including me, is sensitive about their cap tables, so by default the data you create is kept on your <strong>local machine only</strong> and not sent to any server.</p><p>That said, sometimes you want to compare notes with colleagues, advisors, board members, etc. If so, you can enable the sharing toggle, at which point your data has to be sent to a server (so it can then be shared).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HWJSThYjwrlAfU4aOhdLww.gif" /><figcaption>Activating sharing</figcaption></figure><p>That said, when you’re done sharing, just flip the toggle off. Not only will all the data be deleted from the server, but it will also clear out the shared versions on everyone else’s machines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pab5LIJYMcYU0ekZHgoDMQ.gif" /><figcaption>Deactivating sharing &amp; deleting the data from the server</figcaption></figure><h3>Caveats</h3><ol><li>I’m not an accountant or attorney, nor do I play one on TV or on Netflix. So please treat this data as <strong>directionally accurate</strong> and consult with your trusted service providers before making any final decisions on whether to take or pass on that investment offer.</li><li>This is software &amp; software has bugs. Especially software written by someone who hasn’t been a full-time engineer for over a decade. If you find bugs, DM me on Twitter and I’ll do my best to squash them.</li></ol><h3>Enjoy!</h3><p>If you found this useful and want to get updates when I post more tools like this, you can <a href="https://twitter.com/yanda">follow me on Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11bcb415eac3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yanda/cap-table-simulator-11bcb415eac3">Cap Table Simulator</a> was originally published in <a href="https://medium.com/yanda">Yanda’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Digitization isn’t enough — Lessons from WEF]]></title>
            <link>https://medium.com/yanda/digitization-isnt-enough-lessons-from-wef-2893dbc7bb42?source=rss----8a8226b8e005---4</link>
            <guid isPermaLink="false">https://medium.com/p/2893dbc7bb42</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Yan-David (Yanda) Erlich]]></dc:creator>
            <pubDate>Thu, 22 Mar 2018 05:47:31 GMT</pubDate>
            <atom:updated>2018-03-22T05:47:25.190Z</atom:updated>
            <content:encoded><![CDATA[<p>A few weeks ago the World Economic Forum invited some of the folks driving tech strategy in Oil &amp; Gas to help workshop their Digital Transformation Initiative. <a href="http://parsable.com/">Parsable</a> was honored to be the only startup among senior leaders from major multinational corporations, academics, authors, and analysts invited to attend.</p><p>A couple of takeaways stand out. I invite interested parties to <a href="https://www.parsable.com/contact">get in touch</a> directly to dive deeper into these conversations.</p><h3><strong>Key Takeaway #1: Successful Digitization Requires Collaboration</strong></h3><p>Collaborative execution — not simply digitization — is the key to driving:</p><ul><li>Safety</li><li>Human and asset efficiency</li><li>Operational excellence</li><li>Supply chain transparency</li></ul><p>Digitization efforts alone aren’t sufficient to fulfill the above priorities.</p><p>Collaboration provides critical leverage within the context of an individual job, interdepartmentally, and even along an increasingly complex supply chain. Digital collaboration means you can replace opaque sequences with real-time oversight; and build safeguards and regulatory reminders into processes, but retain the flexibility to modify them when circumstances require. Collaboration can’t just be picking up the phone or the walkie-talkie, it needs to enable capturing photos, videos, even digital signatures and sharing them across sites and geographical locations so all of the parties needed to get the job done can get the full context.</p><p>In “The Checklist Manifesto,” Atul Gawande takes lessons learned observing operational excellence in aviation and applies them to healthcare. His main discovery is that the checklist is essential, but only when paired with collaborative execution are you assured that each step has been performed correctly. When things don’t go according to plan (which occurs more than we’d like to admit), it’s again collaboration that enables the freeform, urgent, all-hands-on-deck approach required to solve the problem and get back to normal.</p><p>Moving to a collaborative execution approach in healthcare resulted in a <em>dramatic </em>reduction in key metrics like post-operative infection rates. Imagine what it’ll mean for Oil &amp; Gas. Many companies still rely on paper binders and walkie talkies, so a move towards digital procedures may seem forward-thinking. But stopping short of this collaborative element leaves aside the critical driver of impact.</p><h3><strong>Key Takeaway #2: Velocity → Value</strong></h3><p>Our second insight, hotly debated at the workshop, is that iterative deployment <em>precedes</em> end-to-end value.</p><p>The two are often set-up as counterpoints: a choice between <em>velocity</em> (rapid iteration, try → improve → improve) and <em>value</em> (get the perfect end-to-end solution). If it’s really a choice, then <em>value</em> seems the clear winner.</p><p>The problem is that going straight for <em>value</em> means you end up getting neither. The good intention to future-proof, risk-proof, and use-case-proof a solution for all possible scenarios unfortunately results in feature creep, endless delays, and most often a digital solution too complex for anyone to actually use in the field — expensive shelfware.</p><p>In comparison, if you seek <em>velocity</em> first, you get both. By starting a digital transformation project focused on a seemingly narrower pain point — a use case, a business unit — you can deploy a solution that delivers value to that group from day one. Then, you can iterate with them to address any issues or obstacles that no one knew would exist until the solution was actually field-tested. You derive patterns from those learnings that allow that solution to solve more use cases and more business drivers, quickly expanding across the entire organization. Proving quick and effective iteration is the most future-proof model you can buy.</p><p>We’d love to hear where you and your organization stand on these topics. <a href="http://parsable.com/contact">Get in touch</a> or feel free to <a href="/service/mailto:yanda@parsable.com?subject=WEF%20findings%20blogpost">reach out directly</a> to discuss.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2893dbc7bb42" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yanda/digitization-isnt-enough-lessons-from-wef-2893dbc7bb42">Digitization isn’t enough — Lessons from WEF</a> was originally published in <a href="https://medium.com/yanda">Yanda’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The next chapter]]></title>
            <link>https://medium.com/yanda/the-next-chapter-dca142e54fb6?source=rss----8a8226b8e005---4</link>
            <guid isPermaLink="false">https://medium.com/p/dca142e54fb6</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Yan-David (Yanda) Erlich]]></dc:creator>
            <pubDate>Thu, 22 Mar 2018 05:46:07 GMT</pubDate>
            <atom:updated>2018-03-22T05:46:00.229Z</atom:updated>
            <content:encoded><![CDATA[<p>After 4.5 years as Parsable’s CEO, I’m passing the baton. I’m excited to announce that <a href="https://www.linkedin.com/in/lawrencewhittle/">Lawrence Whittle</a> — formerly our Chief Revenue Officer — is <a href="https://www.parsable.com/">Parsable</a>’s next CEO.</p><p>When Ryan, Chase, and I founded Parsable, we had a vision to empower industrial workers globally to get their jobs done right, every time by replacing legacy paper-based workflows with a modern collaboration &amp; workflow platform designed from the ground up for industrial work.</p><p>We discovered early on that, while industrial firms had widely adopted digital collaboration technology in their back offices, their field and factory workers still do their jobs with the same error-prone tools they used in the 1950s: clipboards, sharpies, and walkie-talkies. Globally connected supply chains, higher quality standards, and tighter margins mean companies are eager to help their operations teams work safer and be more productive.</p><p>Today our vision is becoming reality. We are deployed at category-leading Global Fortune 500 companies across a wide berth of industries: from <a href="https://www.parsable.com/press-releases/unilever-implements-parsables-industry-4-0-connected-worker-platform-to-drive-plant-productivity">Unilever</a> in CPG to Schlumberger in Oil &amp; Gas. We are recognized by <a href="https://www.parsable.com/parsable-blog/in-executing-industry-4.0-machines-are-easy-its-the-humans-that-are-hard">McKinsey</a> and the <a href="http://reports.weforum.org/digital-transformation/mining-metals-video-1/">World Economic Forum</a> as being a critical engine of transformation for Industry 4.0. We are backed by a consortium of Silicon Valley’s top venture firms and the venture arms of some of the world’s largest industrial companies. And we’re just getting started.</p><p>I’m proudest of the team and <a href="https://www.parsable.com/parsable-blog/culture-drafting-your-teams-constitution">culture</a> that we’ve built. With offices in 5 cities — and customers in close to 60 countries — we’ve retained the same drive and purpose of mission we had back when we all fit in a small conference room.</p><p>Since joining us as CRO, Lawrence has been instrumental in assembling our customer facing teams, driving our marketing efforts, and forging strong relationships with our ecosystem. As Parsable scales to meet its massive market opportunity, there’s no better person to take the company forward. I’ll remain involved as an advisor to the company.</p><h3><strong>What’s next</strong></h3><p>As to my next chapter, I want to finally focus my full energies on my love of helping early stage companies succeed. While I’ve been a operator and founder as my “full time job” the past 20 years, I’ve scaled up my advising and investing activities over the last decade. Starting with small angel checks and scaling to deploying millions of dollars of capital, I’ve been fortunate to have been among the earliest investors in, and advisor to, category-defining companies including Mixer Labs, <a href="https://www.thumbtack.com/blog/announcements/thumbtack-com-fastest-growing-marketplace-local-services-announces-broad-investor-support-whos-silicon-valley/">Thumbtack</a>, <a href="https://angel.co/circleup">CircleUp</a>, <a href="http://www.fashinvest.com/rocksbox-just-raised-8-7m-for-its-jewelry-subscription-service/">Rocksbox</a>, Howdy.ai, and <a href="http://variety.com/2017/digital/news/masterclass-funding-ivp-1202017530/">MasterClass</a>.</p><p>Many of my happiest moments have been watching these entrepreneurs succeed, and some of my proudest have been when these talented founders still call me for advice — even after having raised follow-on rounds from incredible investors at First Round, Sequoia, Accel, Matrix, NEA, and more.</p><p>I’m still figuring out what form this investing activity will take, whether I’ll join an existing venture firm or start my own, but I’m thrilled for the next chapter. In the meantime, I’m going to spend some time relaxing with my <a href="https://medium.com/@merci">badass wife</a>, travel a bit, and continue doing what I love: cheering for Parsable’s success and working my ass off to make the next crop of entrepreneurs succeed. If you’re such an entrepreneur, <a href="http://twitter.com/yanda"><strong>I’d love to meet you</strong></a>.</p><p>Onwards.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dca142e54fb6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yanda/the-next-chapter-dca142e54fb6">The next chapter</a> was originally published in <a href="https://medium.com/yanda">Yanda’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What jobs will be left for us humans? What I learned by challenging some industry experts.]]></title>
            <link>https://medium.com/yanda/what-jobs-will-be-left-for-us-humans-what-i-learned-by-challenging-some-industry-experts-e312a99dd78a?source=rss----8a8226b8e005---4</link>
            <guid isPermaLink="false">https://medium.com/p/e312a99dd78a</guid>
            <category><![CDATA[homo-deus]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[human-augmentation]]></category>
            <dc:creator><![CDATA[Yan-David (Yanda) Erlich]]></dc:creator>
            <pubDate>Thu, 22 Mar 2018 05:45:36 GMT</pubDate>
            <atom:updated>2018-03-22T05:45:28.167Z</atom:updated>
            <content:encoded><![CDATA[<p>On Tuesday, I was honored to lead two roundtable discussions for the <a href="http://influencerseries.com/">Influencer Series</a> on the topic of <strong>Fulfilling the Promise of Industrial IoT</strong>. Thank you to <a href="https://twitter.com/rbelani">Ravi Belani</a> and <a href="https://twitter.com/michhgonz">Michelle Gonzalez</a> for inviting me to speak, for <a href="https://twitter.com/badnima">Nima Badiey</a> and <a href="https://twitter.com/DebNoller">Deb Noller</a> for each moderating one of the discussions, and for USVP for hosting us.</p><p>I was asked to lead with a controversial point of view. Having recently read <a href="https://www.amazon.com/Homo-Deus-Brief-History-Tomorrow/dp/0062464310/">Homo Deus by Yuval Harari</a>, and strongly ascribing to his description of humanity’s potential future, I labeled myself a <a href="https://en.wikipedia.org/wiki/Humanism">humanist</a>, then asked the room <strong>which jobs will be left for us humans?</strong></p><p>In his book, Harari suggests that it would be significantly harder for AI to replace a Paleolithic hunter-gatherer than it would to replace a modern human. The reason being that the hunter-gatherer needed to do many things well: hunt, gather nuts &amp; seeds, know which plants were edible, tan hides, build structures, etc… The modern human has professionalized themselves to do one thing very well: manipulate Excel spreadsheets or write Go backend code — while the rest of her needs are fulfilled by other deeply professionalized humans. Doing many things well is hard for AI, whereas doing one thing really well is a machine’s home turf.</p><p>One might suggest that we are no closer to creating conscious machines, but Harari suggests this is no consolation. Though intelligence &amp; consciousness have historically been strongly intertwined, this is no longer the case: intelligence is decoupling from consciousness. For example, a Waymo self-driving car does not carry out thoughtful conversations with its passengers, contemplate the beauty of the starlit sky, nor get frustrated at the driver who cut it off in traffic — but it is fast becoming a better driver than you &amp; I. It turns out that, given the choice between intelligence and consciousness, society— economically, militarily, politically, etc… — picks intelligence over consciousness every time. What will happen when machines are more intelligent than us (even if less conscious)?</p><p>I suggested that the room — filled with IIOT experts from big companies, VCs, startups, and thought leaders — might think the first jobs to go would be the industrial jobs. After all, the rage — and thesis for many VCs and entrepreneurs— is to usher the <a href="https://en.wikipedia.org/wiki/Lights_out_(manufacturing)">lights-out factory</a> through a combination of IIOT, robotics, and AI. I however believe many industrial jobs are safer than those of most knowledge workers. With some exceptions, industrial workers still have to navigate difficult terrain, manipulate heavy tools, and make on-the-fly “one-off” decisions that don’t rely on a wealth of data to pattern-match from. As such, they are more akin to the hunter-gatherer who needed to be proficient at many things. Knowledge workers on the other hand have largely become data processing engines for emails, Slack messages, spreadsheets, radiology reports, etc… You may not even need to build robots to replace knowledge workers because they rarely move around to do work — computers will suffice.</p><p>Having framed my argument, I opened up the conversation to the broader group by asking:</p><ul><li>What jobs do you think machines will do “last”?</li><li>What will happen to un-augmented humans in the job market &amp; how do we address this on a societal scale?</li></ul><p>Both roundtable conversations were heated, touching on topics ranging from:</p><ul><li>Will machines be able to emulate and/or replace human intuition and emotions — and does it matter if they do or don’t?</li><li>Can we teach machines to treat humans nicely when the time comes, and how is our treatment of animals and pets a good or bad model for how super-intelligent beings might treat humans in the future?</li><li>Are knowledge workers really more at risk?</li><li>Are minds shaped by certain professions more or less “plastic” (eg. re-trainable) than others?</li><li>Is Universal Basic Income (UBI) necessary, and will it be enough? In particular, UBI provides a means for survival, but does not provide a sense of purpose — can humans live without purpose?</li><li>What about human happiness? Does it matter, especially if it can be manipulated chemically with prescription or illegal drugs?</li></ul><p>Some of the professions suggested as being “last to go” included:</p><ul><li>Care/empathy givers — less about providing of the technical medical care itself, but more the delivery mechanism for empathy &amp; bedside manner.</li><li>Human organizers — whatever groups humanity congregates in, these groups will need to be organized &amp; motivated, and humans may best be suited for this task.</li><li>Archeologists, NGO members, etc. other jobs that care specifically about the human experience, vs. the economic or military outcomes.</li><li>Humans in the service of training/improving machine learning systems — teachers, but for the AI.</li></ul><p>The general consensus in the room was that super-intelligent systems are coming. For industrial &amp; knowledge workers alike, one way to improve our chances in the future market for a purpose-driven life is to embrace that change and “merge” with machines to make ourselves hybrid super-intelligent beings.</p><p>While the future of this merger may sound like science fiction today — cybernetic limbs, neural lace, brain-enhancing chemicals, etc… — the first steps of this merger are already happening. Many of us in the room already consider ourselves cyborgs given how we use our smartphones as an extension of our brains. It’s been a long time since I’ve had to remember a birthday, a phone number, driving directions, my task or shopping list.</p><p>Mediated by today’s mobile devices, workers — both desk-less and desk-bound — can have access to a vast repository of knowledge and instructions. They have the means to expand their own cognitive abilities to continue to keep pace with the advancing tide of technology. Working in conjunction with smart data on a mobile device today may be the best step to prepare us for a future where hybrid human/machine intelligence is the norm. It may sound strange, but I think it is considerably more appealing than becoming economically and socially irrelevant.</p><p>Clearly this is a passion of mine. At <a href="https://www.parsable.com/">Parsable</a>, the company I co-founded, we are helping industrial workers globally do their jobs right every time by augmenting them (today) with a mobile collaboration &amp; workflow platform they access via their mobile device. Their ability to collaborate in real-time and have immediate access to all of the best-practice standard work instructions and operating procedures gives them a leg up in an increasingly complex and technologically advanced world. As technology progresses, our software may end up getting delivered via wearable devices, or even by neural lace. Irrespective of delivery mechanism, the goal of making industrial workers safer &amp; more productive, and thus help secure their place in the future economy, remains our north star.</p><p>I’m a humanist, and there’s hope for us humans.</p><p>If you’re constantly thinking about this stuff, I’d love to talk. Let’s start by connecting on <a href="https://www.linkedin.com/in/yanda/">LinkedIn</a> or <a href="https://twitter.com/yanda">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e312a99dd78a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yanda/what-jobs-will-be-left-for-us-humans-what-i-learned-by-challenging-some-industry-experts-e312a99dd78a">What jobs will be left for us humans? What I learned by challenging some industry experts.</a> was originally published in <a href="https://medium.com/yanda">Yanda’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thoughts on Entrepreneurship]]></title>
            <link>https://medium.com/yanda/thoughts-on-entrepreneurship-181f82d8eb6f?source=rss----8a8226b8e005---4</link>
            <guid isPermaLink="false">https://medium.com/p/181f82d8eb6f</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Yan-David (Yanda) Erlich]]></dc:creator>
            <pubDate>Thu, 22 Mar 2018 05:44:37 GMT</pubDate>
            <atom:updated>2018-03-22T05:44:45.341Z</atom:updated>
            <content:encoded><![CDATA[<p>It was a great honor to recently come back to my alma mater, <a href="http://www.rice.edu/">Rice University</a>, to give the opening keynote at the Rice Alliance for Technology &amp; Entrepreneurship’s 14th annual Energy &amp; Clean Technology Venture Forum.</p><p>My first experience with entrepreneurship dates back to a presentation I gave in May 2000 at the Rice Alliance — then their 6th venture forum— on a startup idea that two classmates and I had developed for the monitoring &amp; control of industrial process flow lines. It was called EJP Technologies, though you’re unlikely to find it on the web.</p><p>After work at Microsoft and Google, and four startups later — not counting the ill-fated EJP Technologies — it was fun to come full circle and sit before the next batch of young entrepreneurs. In the 16 years since I graduated from Rice, its commitment to entrepreneurship has only increased, as has the quality of the presenters and startups.</p><p>The talk was not videotaped, but I’ve put a link to the slide deck here for those interested.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2F2AK4z1VvvnjcPv&amp;url=http%3A%2F%2Fwww.slideshare.net%2FYanDavidErlich%2Frice-alliance-2016-opening-keynote&amp;image=http%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Friceprezzojpg-160924233746-thumbnail-4.jpg%3Fcb%3D1474760363&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/a40d16ae24e5ddc5af40bc8d0fa8f738/href">https://medium.com/media/a40d16ae24e5ddc5af40bc8d0fa8f738/href</a></iframe><p>Thank you Rice Alliance for giving me this opportunity, and for admitting me into your ranks 20 years ago.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=181f82d8eb6f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yanda/thoughts-on-entrepreneurship-181f82d8eb6f">Thoughts on Entrepreneurship</a> was originally published in <a href="https://medium.com/yanda">Yanda’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Culture: Drafting your team’s Constitution]]></title>
            <link>https://medium.com/yanda/culture-drafting-your-teams-constitution-9506f186db6d?source=rss----8a8226b8e005---4</link>
            <guid isPermaLink="false">https://medium.com/p/9506f186db6d</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Yan-David (Yanda) Erlich]]></dc:creator>
            <pubDate>Thu, 22 Mar 2018 05:44:06 GMT</pubDate>
            <atom:updated>2018-03-22T05:44:14.103Z</atom:updated>
            <content:encoded><![CDATA[<p>Culture matters — but why, and what does it even mean?</p><p>For many organizations — large/small, traditional/techy — culture is oft defined by a list of words describing shared values. Many include words you might expect, like <em>customer obsessed</em> (Microsoft), <em>empathy</em> (Slack), <em>results-oriented</em> (Salesforce). Others sound more unique like <em>draw the owl</em> (Twilio), <em>you can make money without doing evil</em> (Google), <em>servant’s heart</em> (Southwest Airlines)</p><p>At Parsable, we believe culture serves two purposes:</p><ol><li>It allows teammates — especially as we grow — to have a shared understanding of what it means to be a good Parsable citizen. It’s our Constitution: how we should behave every day in the service of our mission.</li><li>It guides us to hire folks who share in these common values and screen out folks who are bad fits. It’s our Immigration Policy.</li></ol><p>In that light, I found the words above which are meant to describe culture lacking, because:</p><ol><li>How do I know when I close my eyes and imagine <em>empathy</em> that I’m imagining the same thing as my co-workers? How can we have a shared understanding of culture if it’s described by words for which we don’t have a shared understanding? We don’t want a vague Constitution.</li><li>How can I screen a candidate for <em>draw the owl</em> or <em>customer obsessed</em>? What questions do I ask that candidate? What does a good answer look like? A bad answer? We don’t want a vague Immigration Policy.</li><li>Where do these culture words come from in the first place? Are they a reflection of the values of the founders/execs, decided by a committee, a grab bag of words that sound good? We want guides that reflect the cultural <em>aspirations</em> of the company: the best selves we want to continue to become.</li></ol><p>I was looking for a better, more authentic way to describe &amp; implement our culture. A few months ago, <a href="https://medium.com/u/fb192aaf4b41">Christina Kelly</a> at <a href="https://medium.com/u/aef2a725508e">First Round</a> (FRC is one of our awesome set of investors) recommended I read <a href="https://www.amazon.com/dp/B005NASJRS/">Hiring for Attitude</a>, by Mark Murphy. The book details a simple and powerful algorithm to discover, describe &amp; enforce culture. I encourage you to read it, particularly if you’ve founded or are running a company.</p><p>Simple and powerful, but not easy: it took ~6 weeks and significant effort to discover &amp; describe our culture. The book suggests hiring a consultancy to help, but as a founder, I thought it important to drive this journey myself.</p><p>The process looked like this:</p><ul><li>I interviewed 15 team members (we were about 40 at the time) for 1–2 hours each, sampled randomly across the entire company (Engineering, Product, Design, Sales, Customer Operations, Execs) and across our three offices (San Francisco, Austin, Vancouver). I asked them the following 4 questions:</li></ul><blockquote>1. Please list 3-to-5 attitudes or personality traits that you think describe the most successful people at our Company. When describing each trait, describe it in a such a way where two strangers could observe the behavior.</blockquote><blockquote>2. Please list 3-to-5 attitudes or personality traits that you think describe the least successful people at our Company. When describing each trait, describe it in a such a way where two strangers could observe the behavior.</blockquote><blockquote>3. Think of someone in the organization who truly represents our culture. Could you tell me about a time he or she did something that exemplifies having the right attitude? It could be something big or small, but it should be something that made an impression on you. Also tell me why it made an impression.</blockquote><blockquote>4. Without naming names, think of someone who works (or worked) in the organization who did not represent our culture. Could you tell me about a time this person did something that exemplifies having the wrong attitude? It could be something big or small, but it should be something that made an impression on you. Also tell me why it made an impression.</blockquote><ul><li>I collected ~500 stories from these answers, and grouped them into themes which formed the basis of our cultural pillars (we discovered we have 7 of them). It’s important to note that my teammates did most of the work here: by generating the stories. Grouping them just involved finding similarities among the stories, both negative &amp; positive. My dining room table looked like this for about a month.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*auxqwAEXmMKu5SLB8KdOIw.jpeg" /><figcaption>Stories getting assembled into cultural pillars</figcaption></figure><ul><li>The stories above were also used to generate Word Pictures for each cultural pillar. You turn stories into Word Pictures by removing names and turning them into “<em>When ___ , I ____ .” </em>statements. The principle is that <em>empathy</em> can mean different things to different people, but when teammates read <em>“When talking to someone, I ask open-ended questions and seek to understand their perspective before adding my inputs.”</em> it’s pretty likely they will imagine the same scene = Word → Picture. To read more about the power of behavioral specificity and Word Pictures, I encourage you to read the book. It’s really worth it.</li><li>Finally, the themes above were used to generate interview questions for each cultural pillar. These interview questions have a very specific format, also described in the book.</li><li>Interview questions without an answer guide — to discern good vs. bad answers — are not very useful. To create our Answer Guide, I surveyed the entire company with these same questions (10 of them in total) and collected hundreds of answers.</li><li>I mapped these answers into Positive Signals (congruence with the cultural pillar) and Warning Signs (sign of lack of congruence). These real answers serve as our Answer Guide when comparing answers given by our interview candidates to the same questions.</li><li>Because we love Star Wars at Parsable, we ascribed a different Star Wars character as the “patron totem” for each cultural pillar.</li></ul><p>During this process, two things of note happened:</p><ol><li>Teammates opened up and told me amazing stories of their peers going above &amp; beyond: coming through for a teammate in time of need, making personal sacrifices for the good of the team &amp; company, etc. Often, these were silent heroes, so I hadn’t known of many of these feats until I performed the interviews. That alone made running this process myself worth it. We recognized these Parsable culture heroes with LEGO Star Wars characters for the specific cultural value they exemplified with their actions.</li><li>Some of our answers to our own interview questions (mine too) ended up in the Warning Signs section for some cultural pillar. A team &amp; company is a work in constant progress, and this exemplifies the aspirational nature of culture: we are not all good at all things. Rather than get demoralized, the team has rallied and seen this as an opportunity to improve. It helps validate why <em>seeing opportunity in difficult situations</em> is one of our cultural pillars.</li></ol><p>Below is the presentation I gave our entire team at the culmination of that discovery process.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2FtIy5tkVoWC0KdS&amp;url=http%3A%2F%2Fwww.slideshare.net%2FYanDavidErlich%2Fparsables-culture&amp;image=http%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fparsableculture-externalpresentation-160825215650-thumbnail-4.jpg%3Fcb%3D1472162605&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/cb74dc19d5eca14852fb52f1a7ac5da9/href">https://medium.com/media/cb74dc19d5eca14852fb52f1a7ac5da9/href</a></iframe><p>This is only a milestone in Parsable’s long journey. If you’re curious to live &amp; shape our culture, consider <a href="https://www.parsable.com/careers">joining us</a>. As reward for introspective and action-oriented work, many LEGO Star Wars characters may be in your future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jj-hub84Wv44Nk43J0IbXg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9506f186db6d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yanda/culture-drafting-your-teams-constitution-9506f186db6d">Culture: Drafting your team’s Constitution</a> was originally published in <a href="https://medium.com/yanda">Yanda’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>