BC STARTUPS
Saved by @zmbnski

1/ The first 18 months of starting a company is often life or death. I must've made 5 different companies that each failed within 9 mo. 😭 Each time the company failed I figured out what I could do better. Eventually startup #6 got to $40K/mo by month 18. Here’s what I learned...

 2/ Stay focused! Ignore things that are a waste of time: meetups & conferences, meetings with no clear agenda, fundraising if you're not fundraising, reading lots of tech media articles, etc. Every week should feel like significant progress in the first year.
3/ Your first 5 hires will be the difference between life or death. Choose carefully. Be picky. Many of the things we do at the company still are a result of those early hires' legacy. Have fun as a tight knit team. It will change & evolve as you get bigger so enjoy this moment.
4/ Growth may be flat for the first 9 months. It's gonna be okay. Almost every company has experienced this: Airbnb had to sell cereal in-between, Slack failed as a gaming company first, Tesla sold only 147 cars after 6 years! You probably won't be an overnight success either.
5/ In the beginning, do customer support yourself. You will learn a lot about why your product sucks. I did 5,000+ support tickets when it was the two of us. Delight customers & fix things fast while you learn. It will help you build an amazing intuition about your customers.
6/ If your competitor made something your customers love: remove your ego & build it. But, make sure you understand why. Don't blindly copy things either. Learn why first. This was invaluable for me & helped us win critical battles over the years. Nobody cares who built it first.
7/ Positioning matters. Spend time figuring out how to explain your product. If it's easy to do, figure out how to explain why it's different as simply as possible. If not, keep experimenting. We bombed this in the first year. It can often be the diff between success & failure.
8/ Your mantra should be: "Be scrappy." Save money. Don't waste. Ignore status. Focus on building. Make people think you're bigger than you are. Do things the larger company won't do because they move slow. You don't need ping pong tables to win, you need grit & resourcefulness.
9/ Pick roles as co-founders to divide & conquer. You both can't be in charge of all engineering, product, design, & business decisions. This often blows up companies! Debate vigorously but make a call. Opt to test ideas vs throw them away though--especially if it's cheap to do.
10/ Truth is, you're going to be using your gut a lot because you lack data. To compensate: talk to customers, meet people who will play a devil's advocate, & understand the tech from 1st principles. Meet people live tho. It will make a meaningful difference in what you'll learn.
11/ Research the history of your market. It will help you identify old & long-standing assumptions, challenging obstacles you too will face, and critical features it took old players a decade to realize to build. I failed to do this until we were 6 years in & it hurt us.
12/ If you have bad customer retention, you're probably not ready to scale the company. Fix that first, then focus on growth. The #1 reason I've seen 100s of companies fail is by becoming addicted to a clever distribution strategy before their product was good. It's a trap!
13/ If this is your 1st time, consider something like @ycombinator. Having a crew of ppl to commiserate w/ in the early days can help you overcome existential moments. During the '09 recession, we all struggled to raise money. Going through it together made us more resilient. 💪
14/ Stay laser focused on solving a narrow set of problems. I failed to do this around the 18 mo mark & got behind because shiny new things excited me. It hurt us & we lost customers. We spent the next 2 years focused on 3-4 major things & significantly surpassed our competitors.
15/ Finally, realize that this is one of the most exciting phases: building the company from scratch. Figuring out what works & what doesn't. Building things that haven't existed. You're starting to cement your company culture too. Have fun, excerise, & take a pic of the team 📸.
If you haven't read it already, here are lessons I learned when becoming "CEO" for the first time: https://t.co/m77U25VDbg

More from Startups

Hiten Shah
Hiten Shah
@hnshah
Startup life can be summed up in three steps:

1. Find problem
2. Fix problem
3. Go back to step 1

Works for every thing you need to do in a startup.

Growth is determined by a combination of how fast you can go through the steps successfully and how long you can keep at it.

Finding the right problem to solve starts with understanding your customers.

Nobody says I wish I talked to less customers.

There aren’t any hacks or shortcuts to this.

Go talk to your customers.

Fixing problems in a startup isn’t usually straightforward.

You don’t have time, money or people to throw at the problem.

You have to go deep, dig for the details and think very creatively about solutions.

Then experiment like there is no tomorrow.

You can’t grow a startup without a fundamental understanding of how to problem solve really fast.

This skill comes from practicing jumping into the unknown.

You don’t usually get time to prepare for what’s coming next.

You’ll have to learn how to figure it out along the way.

Startup people have to become comfortable with the discomfort of uncertainty and the unknown.

This is why I say, nobody knows what they are doing.

We’re all just jumping from problem to problem expecting to figure things out.

Hopefully our past helps us not crash and burn.
STARTUPS
Justin Jackson
Justin Jackson
@mijustin
Yesterday, I wrote about how easy it is to sell ice cream on a crowded beach: https://t.co/a9z2ZTixb7

Today, I’m at the local fair.

There are hundreds of vendors.

But there are also huge crowds who are hot and thirsty; lots of demand for cold drinks!

Go where the crowds are!


Again, this is just a metaphor!

But it’s a good reminder:

🍋 If you have a lemonade stand, it’s better to go somewhere hot, where there are a lot of thirsty people.

💻 If you want to make software, it’s better to go where there are a bunch of potential customers.

BTW - targeting a good market doesn’t mean you’ll automatically win!

There are a TON of factors that influence a business’ success (or failure).

But choosing a market that has a lot of demand (and good channels) is essential for future success.

In business, nothing is guaranteed.

You might be in a good market today, but tomorrow it could fall apart.

Markets are fickle.

Some days they want 🍦, other days they want 🥤.

The economy can go up, or it can crash.

A good competitor can come in and grab market share.

But this reinforces the point:

“Business is already hard, why make it harder?” – @asmartbear

Why try to enter a niche where there’s no demonstrable demand?

Why try to serve a total addressable market of 500, when you could go after 500,000 potential customers?
STARTUPS
Advertisement
Patrick McKenzie
Patrick McKenzie
@patio11
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.
STARTUPS
Justin Kan
Justin Kan
@justinkan
With @ycombinator #demoday kicking off, @atrium gathered advice from past YC founders.

.@jaltma from @latticeHQ says “Don’t confuse investor interest with product-market fit. You’re about to be on the receiving end of a lot of hype and FOMO - use it to your advantage by taking the money and then keep your burn and ego low.”

.@typesfast from @flexport says “I like to remind myself that even Bruce Springsteen still gets nervous before his concerts. Remember that, and then try to focus on what investors want: First, not to be bored. Second, to get rich(er).”

.@collinmathilde from @frontapp says “Leverage your data to tell a story about what the business has achieved and where it is going. Metrics are necessary, but they are too often shared without a narrative arc.”

.@drusenko from @weebly says “Make it relevant. Investors can live in their own world, so try to find an angle that they can relate to.”
STARTUPS
Brainhub
Brainhub
@brainhubeu
“Every time you write a new code, you should do so reluctantly, under duress, because you completely exhausted all your other options.” - Jeff Atwood @codinghorror

Hence the growing popularity of the no-code software.

A quick thread 👇


1/

NO-CODE IS EATING THE WORLD

The concept isn't new (remember Microsoft FrontPage?) but the capabilities that the no-code and low-code tools offer today change the way individuals and businesses approach building digital products.

WHY IT'S INTERESTING? 👇

2/

No-code tools let you build things without writing code. Websites, mobile apps, online stores – all that (and a lot more!) can be built without any prior coding experience.

3/

Even though the “no-code” label is often an oversell (many platforms are "just" low-code and still require some low programming effort), the capabilities offered are game-changing, especially at the first stages of product development.

4/

Key no-code platforms:

•@Shopify: e-commerce
•@canva: design
•@airtable: databases
•@webflow: web development
•@zapier: process automation
•@bubble: mobile app development
STARTUPS

You May Also Like

Stephen Fasenfeld \U0001f600
Stephen Fasenfeld 😀...
@fasenfeld
1. “Who Are Ireland’s Members Of The World Economic Forum Implementing The Great Reset In 2021 ? 🧵1/28

🕵️🔎 Politicians, Musicians, Clergy, Bankers, Journalists, Human Rights, Artificial Intelligence, Sustainability, Corporations & Agriculture


2. In previous threads I have looked at 🇮🇪 key players in the Trilateral Commission as well as 🇮🇪 people who have attended the Bilderberger meetings. I also looked at the 🇮🇪 in the Young Global Leaders which is a site run by the WEF. You will see a lot of crossover between them.

3. The purpose of this thread is to compile all the Irish members into one thread for ease of access and reading rather than having to dive through the WEF site. This is by no means definitive and I will be adding more over time when they pop out of the woodwork.

4. Ireland’s WEF members are drawn from all walks of life but can be split into 2 separate areas. The WEF calls the first category “people” and the 2nd one “agenda contributors”. In total Ireland has a minimum of 61 members. Some of the names will be familiar and others will not

5. In this thread I’m just going to concentrate on the 21 people (there are probably a lot more). There are also 40 “agenda contributors” which I will cover in a separate thread. The agenda contributors are those who write articles or do research for the WEF site.
ECONOMY
James Felton
James Felton
@JimMFelton
Butt plugs were originally sold as a miracle cure for headaches, acne, and insanity

Thread, article here and h/t: @qikipedia :
https://t.co/Ts84xnmWKJ


For a long time, medicine was pre-occupied with the question "can this be solved by putting something in the butt?"

Take, for example, tobacco smoke enemas, in which 18th Century physicians saw drowning victims and attempted to de-deadify them by blowing tobacco smoke up their rectums with a pipe.


Despite having no medical benefit whatsoever, the practice was popular, and enema kits lined the Thames like lifebelts, ready to be used as one final humiliation for somebody who was crap at swimming.

This practice ended sometime after 1800 when it became apparent that it didn't really work, given how the anus famously isn't really connected to the lungs, but doctors weren't quite finished with having a poke around in the old anus to see what happens just yet.
TECH
Advertisement
\uc2e0\ub150\uc758\uc0ac\ub098\uc774
신념의사나이...
@Belposto_korea
What does Gold- Backed mean?
The Chinese Elders have been accumulating gold for hundreds of years. They are gold-rich. Some of their gold was loaned to the Central Banking System so that it could fund the rebuilding of Europe after the many war-torn years from World Wars I and II

BTW they never returned it but used it to start their financial empire to enslave humanity. This is the Central Bank Banking System./2

Maybe this is why one of the conditions to use their gold for the QFS is the demise and full disclosure of the Central Bank banking system before the RV can take place./3

The Elders have caves of hidden gold and are now using it to gold-back the currencies in the QFS for every country in the world. It is important to understand that the QFS and the money it is about to release is all brand-new currency./4

It was designed by the Alliance to fund the new financial system that will reset all Currencies of the world to Gold-Backed currency./5
SOCIETY
\u092c\u094d\u0930\u093e\u0939\u094d\u092e\u0923\u094b\u0902 \u0915\u093e \u0907\u0924\u093f\u0939\u093e\u0938\U0001f441\ufe0f\U0001f441\ufe0f
ब्राह्मणों का इतिहास👁️...
@BRAHMIN_0052
MOHIYAL_BRAHMIN_KING
RAJA_PORUS
King_Porus_History

1)King Porus was a famous Indian king, his real name was #Purushotama. He belonged to PURU tribe mentioned in #RIG_VEDA, the Ancient books of India.


2) Porus ruled the Punjab region and expanded his kingdom between the Jhelum River and Chenab River in the Indian Subcontinent. He was a legendary warrior and more war skills. He made the army most powerful with war skills. Even Alexander had also made difficulty to defeat Porus.

3)Word of Mouth Oral tradition in #Mohyal_Brahmin families since ancient times has kept the Great Saga of their Great Elder known to them as Maharaja “ #Puru” alive.

4) When #Alexander the Great invaded India in 326 BC he was challenged near Taxila by a mere chieftain of the Area. He was King #Porus, a #Vaid_Mohyal. After his encounter with Porus, Alexander met with more resistance near Multan where the forces were predominantly #Mohyal.

5)The Bali rulers of Multan fiercely engaged with Alexander's army in skirmishes in which many senior Generals died. Later during the long and bitter fighting in #Multan, Alexander got hurt by an arrow which pierced his chest ,
RELIGION
Nicolas
Nicolas
@necolas
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.
TECH