👇 Thread. New deck getting published this week: "Consumer startups are awesome, and here's what I'm looking to invest in at Andreessen Horowitz." If you want to read it, subscribe to my newsletter here: https://t.co/262t8eh0wf
\U0001f447Thread.
— Andrew Chen (@andrewchen) November 1, 2018
Published a new essay: The red flags and magic numbers that investors look for in your startup\u2019s metrics \u2013 80 slide deck included! pic.twitter.com/w6HRD4o22f
From a metrics standpoint, it's important to analyze the acquisition mix, the quality of the signups, and the platform dependencies. In the deck, I talk through a bunch of the red flags I'm looking for. pic.twitter.com/5eXkLB0aYQ
— Andrew Chen (@andrewchen) November 1, 2018
More from Startups
The Beatles wrote “Yesterday” in less than a minute.
Led Zeppelin wrote “Rock And Roll” in 30 minutes.
The White Stripes, “Seven Nation Army”, 10 min during a soundcheck.
The Rolling Stones, “I Can’t Get No Satisfaction”, 40min.
Making a startup in 24 hours is perfectly fine.
I worked on my first startup for 2.5years. It was an events app. Sunk in cost and expectations were so high, that I had to close it, despite getting consistent revenue.
In comparison, I wrote @CryptoJobsList in 2 days. And it's way more meaningful than what I've been doing in my events startup for 2.5 years.
When I let go of my engineering ego and let go of expectations that I need to raise capital and hustle for 4+ years — I started lauching fast and interating fast without any expectations — then I started coming up with something truly meaningful and useful ✨
12 startups in 12 months by @levelsio
24 hour startup by @thepatwalls
— are great challenges that make you focus on the end product value, iterate fast and see what sticks and ruthlessly kill what does not work.
Led Zeppelin wrote “Rock And Roll” in 30 minutes.
The White Stripes, “Seven Nation Army”, 10 min during a soundcheck.
The Rolling Stones, “I Can’t Get No Satisfaction”, 40min.
Making a startup in 24 hours is perfectly fine.
I really think this idea of starting a starup in 24 hours is bad idea. Gives people thinking that you can do something meaningful in short period of time. https://t.co/l3x2ov33Qn
— Myk Pono \U0001f60e (@myxys) November 10, 2018
I worked on my first startup for 2.5years. It was an events app. Sunk in cost and expectations were so high, that I had to close it, despite getting consistent revenue.
In comparison, I wrote @CryptoJobsList in 2 days. And it's way more meaningful than what I've been doing in my events startup for 2.5 years.
When I let go of my engineering ego and let go of expectations that I need to raise capital and hustle for 4+ years — I started lauching fast and interating fast without any expectations — then I started coming up with something truly meaningful and useful ✨
12 startups in 12 months by @levelsio
24 hour startup by @thepatwalls
— are great challenges that make you focus on the end product value, iterate fast and see what sticks and ruthlessly kill what does not work.
.@zapier built a $140M ARR business on $1.4M in VC that has become the logic layer of the no-code industry.
But it has the potential to be something even bigger: the Netflix of productivity.
Our report and a thread 👉
We believe @seqouia and @steadfast got a good deal buying into Zapier at $5B.
We value Zapier at $7B based on:
- 30-50% YoY growth over the next five years
- Zapier’s monopoly status in the solopreneur/SMB market
- 30-40% YoY growth of no-code TAM
No-code is huge and growing, but as @edavidpeterson has written, no-code is about more than tools: it’s about a philosophy that emphasizes interoperability and customizing your software to your needs.
https://t.co/UJY6BRtXwl
.@zapier enabled interoperability by building a solution to one of the intractable problems in SaaS: APIs that don’t talk to each other.
The product took off and hit $100M ARR in just 9 years, comparable to companies that have raised 100x as much money.
https://t.co/0Thk42eRpJ
Zapier was riding an explosion in APIs that started the same year they were founded—2011.
Suddenly, every SaaS business wanted to offer its users extensibility, but not spend time figuring out what integrations to build or building them.
That’s where Zapier came in handy.
But it has the potential to be something even bigger: the Netflix of productivity.
Our report and a thread 👉
We believe @seqouia and @steadfast got a good deal buying into Zapier at $5B.
We value Zapier at $7B based on:
- 30-50% YoY growth over the next five years
- Zapier’s monopoly status in the solopreneur/SMB market
- 30-40% YoY growth of no-code TAM
No-code is huge and growing, but as @edavidpeterson has written, no-code is about more than tools: it’s about a philosophy that emphasizes interoperability and customizing your software to your needs.
https://t.co/UJY6BRtXwl
Trying this on for size\u2026
— David Peterson (@edavidpeterson) January 14, 2021
\u201cNo code\u201d isn\u2019t a coherent category. It\u2019s a design philosophy.
But tools built with this philosophy in mind will be the biggest winners of the next decade.
Let me explain what I mean by way of analogy.
.@zapier enabled interoperability by building a solution to one of the intractable problems in SaaS: APIs that don’t talk to each other.
The product took off and hit $100M ARR in just 9 years, comparable to companies that have raised 100x as much money.
https://t.co/0Thk42eRpJ
Ever notice that Zapier is doing $100m+ and has no direct competition? Found their niche and crushed it \U0001f44c
— Tyler Tringas (@tylertringas) November 7, 2019
Zapier was riding an explosion in APIs that started the same year they were founded—2011.
Suddenly, every SaaS business wanted to offer its users extensibility, but not spend time figuring out what integrations to build or building them.
That’s where Zapier came in handy.
There are a *lot* of software shops in the world that would far rather have one more technical dependency than they'd like to pay for one of their 20 engineers to become the company's SPOF expert on the joys of e.g. HTTP file uploads, CSV parsing bugs, PDF generation, etc.
Every year at MicroConf I get surprised-not-surprised by the number of people I meet who are running "Does one thing reasonably well, ranks well for it, pulls down a full-time dev salary" out of a fun side project which obviates a frequent 1~5 engineer-day sprint horizontally.
"Who is the prototypical client here?"
A consulting shop delivering a $X00k engagement for an internal system, a SaaS company doing something custom for a large client or internally facing or deeply non-core to their business, etc.
(I feel like many of these businesses are good answers to the "how would you monetize OSS to make it sustainable?" fashion, since they often wrap a core OSS offering in the assorted infrastructure which makes it easily consumable.)
"But don't the customers get subscription fatigue?"
I think subscription fatigue is far more reported by people who are embarrassed to charge money for software than it is experienced by for-profit businesses, who don't seem to have gotten pay-biweekly-for-services fatigue.
On a serious note, it's interesting to observe that you can build a decent business charging $20 - $50 per month for something that any good developer can set up. This is one of those micro-saas sweet spots between "easy for me to build" and "tedious for others to build"
— Jon Yongfook (@yongfook) September 5, 2019
Every year at MicroConf I get surprised-not-surprised by the number of people I meet who are running "Does one thing reasonably well, ranks well for it, pulls down a full-time dev salary" out of a fun side project which obviates a frequent 1~5 engineer-day sprint horizontally.
"Who is the prototypical client here?"
A consulting shop delivering a $X00k engagement for an internal system, a SaaS company doing something custom for a large client or internally facing or deeply non-core to their business, etc.
(I feel like many of these businesses are good answers to the "how would you monetize OSS to make it sustainable?" fashion, since they often wrap a core OSS offering in the assorted infrastructure which makes it easily consumable.)
"But don't the customers get subscription fatigue?"
I think subscription fatigue is far more reported by people who are embarrassed to charge money for software than it is experienced by for-profit businesses, who don't seem to have gotten pay-biweekly-for-services fatigue.
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
