1/ Recently, I learned about the concept of ‘struggle porn’. This refers to the fetish of sacrificing nearly everything (health, relationships, time) for your startup. I fear that this label is creating more harm than good.

2/ @nateliason wrote a fabulous article about this topic, which first introduced me to this concept. Everyone should read it: https://t.co/eyyZkPXlED
3/ @alexisohanian also recently spoke about struggle porn, though referring to it as ‘hustle porn.’ (as the co-founder of @hustlefundvc, obviously I take issue with this pejorative definition of ‘hustle’, but that’s another topic) https://t.co/XnDT8Ly7UK
4/ Struggling in itself isn’t necessarily bad. Let’s be real here--if you’re going to start a startup, you will struggle. Founders should expect to work harder generally than employees. You will be challenged in many ways and also be super rewarded in others. This is normal.
5/ However, if you are over-indexing on hard work without clear purpose and degrading your mental health/relationships in the process--then this is very bad and we obviously should not celebrate this behavior.
6/ But when we start to say that struggling means that you are doing something wrong, or that struggling in itself is shameful--then that is dangerous. It may actually prevent more founders from openly talking about their struggles.
7/ I’m constantly working to earn a deep and authentic relationship with our fund’s founders. When they struggle, we want to know so we can try to help. We don’t want founders to internalize these mental challenges, but instead be open about them.
8/ Instead of discouraging founders from the Struggle, we should just recognize that it’s a natural part of the startup journey. As VCs, our job is to provide support and not judge when our founders need real help.
9/ Final note, getting back to what I think is the heart of struggle porn: If you’re sharing your own ‘struggle journey’ just to brag insincerely about how hard you’re working--then you are an asshole. You are not helping anyone.

More from Startups

.@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.
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.

You May Also Like