1/ Throughout my startup career, I’ve seen many founders have an aversion to sales. This is a mistake that can kill your startup.
More from Justin Kan
I just gave a talk to the W2021 YC batch. It's my favorite startup audience to talk to. Here are some of the highlights:
Finding product market fit is the critical thing to do in a startup.
Everything else: demo day, what investors you get, how much you raise, what press covers you -- it is all window dressing.
Many founders don’t want to talk to their customers because it makes them vulnerable, because it's hard work, because it's scary. Creating a tight feedback loop with customers is the one thing that will help you discover PMF.
If a customer isn't one of your cofounders, try to create a customer panel that allows as tight of a loop as possible. Call them daily. Put them in your Slack.
My Twitch cofounder Emmett Shear has a great analogy on PMF here: it's like rolling a boulder downhill.
Finding product market fit is the critical thing to do in a startup.
Everything else: demo day, what investors you get, how much you raise, what press covers you -- it is all window dressing.
Many founders don’t want to talk to their customers because it makes them vulnerable, because it's hard work, because it's scary. Creating a tight feedback loop with customers is the one thing that will help you discover PMF.
If a customer isn't one of your cofounders, try to create a customer panel that allows as tight of a loop as possible. Call them daily. Put them in your Slack.
My Twitch cofounder Emmett Shear has a great analogy on PMF here: it's like rolling a boulder downhill.
1/ What is \u201cproduct/market fit\u201d? I\u2019m not sure I can give you a definition. But maybe I can share what the subjective difference is in how it feels when you have it and when you don\u2019t. Founding a startup is deciding to take on the burden of Sisyphus: pushing a boulder up a hill.
— Emmett Shear (@eshear) July 27, 2019
More from Startups
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.
