1/ Today I prepared for talking about common mistakes startups make (founding -> growth stages) by writing it in tweet form. I ramble too much when public speaking and hoped it would make the core ideas clearer in my mind and more concise. Think it worked. Here are the tweets

2/ Earliest mistake is picking the wrong co-founders. You have to be value-aligned (don’t have conflicting personal goals) and respect each other. With both of these, any other differences are irrelevant - can be worked out. Without them everything else you do is irrelevant.
3/ If you launch, next mistake is chasing top-line vanity metrics (sign ups) instead of growing the number of users who *really* love you. @paultoo advice - better to have 10 users who depend on you than 100 who a lukewarm. This requires patience and killing your ego.
4/ If you raise a seed round, it’s tempting to ignore retention. With money, there are always ways to grow top-line (buy ads, launch a new location). Strong fundraisers can do this for multiple rounds (though investors are more savvy to this now). Eventually, the bottom falls out
5/ Once you’re growing without churn, you find you have a diverse set of customers and can’t make them all happy -it’s easy to fail trying. Commit to a long term strategy for going public and build for the users who get you there, even if you lose the others. You have to focus.
6/ With growth, retention, and focus - now you have to scale team. Two types of mistake, hiring too slow and too fast. Product focused founders likely to hire too slow (don’t want to delegate, like the details), business-minded founders likely to hire too fast.
7/ Hiring too slowly doesn’t kill you, it just caps your upside. Your competitor builds a team faster and signs up more customers with a slightly worse than yours but still good enough product. You’re left with a nice, small business.
8/ Hiring too fast kills you via bad decision making. You lose rigor in hiring process (bad people -> bad decisions), there’s no effective onboarding/setting people up for success (good people -> bad decisions), growth stalls, conflict rises (good people leave)
9/ Avoid all of these...and there's still myriad other ways you could fail so don't attach too much of your identity to the outcome of your startup :-)

More from Startups

There are some amazing founders and indie hackers that have made 🤯-worthy progress this last year.

The stuff you can do in a year is seriously astounding 👇

👉 @TransistorFM reaching $22k MRR in one year:
https://t.co/BuKmXEeEtH

I was one of their first customers and the progress @mijustin and @jonbuda have made working mostly part-time has been crazy.

Now both are full-time. Follow them on @buildyoursaas

👉 @talk2oneup reaching $10k MRR in one year: https://t.co/SOoGkKA19r

@daviswbaer joined as a co-founder and through many different marketing tactics, pricing changes, and product updates, they've managed to carve out a niche market in a really competitive industry.

👉 @hostifi_net $9k MRR in one year: https://t.co/TknroGZWoK

After getting fired from his full-time job, @_rchase_ embarked on a year focused on building products to replace his salary in a year.

The dude seriously SHIPS and even took investment from @earnestcapital


👉 @ClosetTools $11k MRR WHILE WORKING FULL-TIME AND WITH A FAMILY: https://t.co/pKQ7pFvpZY

With a strong product, continuous improvement, and SEO, @unindie has really been inspirational.

There are no excuses.
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

॥ॐ॥
अस्य श्री गायत्री ध्यान श्लोक:
(gAyatri dhyAna shlOka)
• This shloka to meditate personified form of वेदमाता गायत्री was given by Bhagwaan Brahma to Sage yAgnavalkya (याज्ञवल्क्य).

• 14th shloka of गायत्री कवचम् which is taken from वशिष्ठ संहिता, goes as follows..


• मुक्ता-विद्रुम-हेम-नील धवलच्छायैर्मुखस्त्रीक्षणै:।
muktA vidruma hEma nIla dhavalachhAyaiH mukhaistrlkShaNaiH.

• युक्तामिन्दुकला-निबद्धमुकुटां तत्वार्थवर्णात्मिकाम्॥
yuktAmindukalA nibaddha makutAm tatvArtha varNAtmikam.

• गायत्रीं वरदाभयाङ्कुश कशां शुभ्रं कपालं गदाम्।
gAyatrIm vardAbhayANkusha kashAm shubhram kapAlam gadAm.

• शंखं चक्रमथारविन्दयुगलं हस्तैर्वहन्ती भजै॥
shankham chakramathArvinda yugalam hastairvahantIm bhajE.

This shloka describes the form of वेदमाता गायत्री.

• It says, "She has five faces which shine with the colours of a Pearl 'मुक्ता', Coral 'विद्रुम', Gold 'हेम्', Sapphire 'नील्', & a Diamond 'धवलम्'.

• These five faces are symbolic of the five primordial elements called पञ्चमहाभूत:' which makes up the entire existence.

• These are the elements of SPACE, FIRE, WIND, EARTH & WATER.

• All these five faces shine with three eyes 'त्रिक्षणै:'.