Hemant Mohapatra Profile picture
Sep 19, 2019 13 tweets 11 min read Read on X
Can’t thank ace investor and dear friend @anuhariharan of @ycombinator enough to join us again for a masterclass at #EE2019 @lightspeedee, and take the cohort back to “Startup Basics” and what differentiates companies that breakout from those who don't. Thread below (1/13) 👇 ImageImage
@anuhariharan @ycombinator @lightspeedee Anu kicked off with a provocative thought - “Start by doing things that don’t scale”. Recruit your first 100 users manually. Talk to them, get direct feedback, the learning is unparalleled. This is your chance to really test the product in a closed controlled environment. (2/13)
@anuhariharan @ycombinator @lightspeedee Your first 10 hires are mission critical. All the 20-30-40 you bring after that will be exactly like them. You really need people who can roll up their sleeves and do whatever it takes. (3/13)
@anuhariharan @ycombinator @lightspeedee Knowing who to hire requires deep introspection among co-founders. Write down strengths of the founding team. What complements do you need right away? E.g. Brex’s founders spiked on engineering, particularly back-end. One of their first hires was a strong UI/ UX person. (4/13)
@anuhariharan @ycombinator @lightspeedee On hiring and firing, Anu recognised that no matter how hard you try, you will make mistakes. However, this is a skill that you need to learn and evolve in. It’s absolutely unavoidable and becomes increasingly important as you scale. (5/13)
@anuhariharan @ycombinator @lightspeedee What differentiates successful founders over time is *speed* of decision making. You might make mistakes, but course correcting is something you only learn over time. No "wrong or right" decisions, more "good or bad" decisions basis the info you have at the time (6/13)
@anuhariharan @ycombinator @lightspeedee “Co-founder relationships last 10-20-30 years, often longer than marriage.” Anu encouraged founders to write down co-founder name against the ultimate decision authority on 6-7 areas (fundraising, product roadmap, hiring, customers, sales etc.) that cause most dissonance. (7/13)
@anuhariharan @ycombinator @lightspeedee Co-founders should have informal 1:1s once a week at least. Have honest dialogues, give direct feedback. You’re each invested in success of company. Always ask “What makes the company successful, not what makes you individually successful.” (8/13)
@anuhariharan @ycombinator @lightspeedee You have to be okay saying I don’t know this, need to bring someone who does. You won’t scale until you reflect on whether “is this the best use of my time?” (9/13)
@anuhariharan @ycombinator @lightspeedee On founder stress/ health, Anu made an imp. point that nothing is worth building if it compromises sleep & eating and exercise. You are your biggest super-power - if you can't scale, nothing will. (10/13)
@anuhariharan @ycombinator @lightspeedee Using Bezos’ framework, she said “When things are going wrong, it’s never as bad as you think. When things are right, it’s never as good as you think.” (11/13)
@anuhariharan @ycombinator @lightspeedee What helps overcome stress? Co-founder relationships, coaches, writing down unanswered questions and deciding actions against each. Most often, it is the indecisiveness that causes stress. (12/13)
@anuhariharan @ycombinator @lightspeedee Finally, just saying “Do right by customer” isn't enough. It's the hard decisions you make that define company culture.” A now B$ co almost went bankrupt in early days coz they refunded an unhappy customer. 1 customer vs company: they chose the customer! Thanks @anuhariharan 🙏

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Hemant Mohapatra

Hemant Mohapatra Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @MohapatraHemant

Nov 25
One of the things we hear often about AI is how it’ll bring a productivity surge to society and have a deflationary impact on GDP. Technical revolutions, over a long enough horizon, do tend to make societies better off economically but we wanted to go deeper into what is the nature of productivity today, where does it come from, what do the productivity curves for large tech & non-tech categories look like, and then understand exactly where, and how will AI have the most impact on these productivity curves. @AbhiramTarimala and I dug into some of these core concepts in today's piece and a lot of python code & charting later, we present to you "AI - the last employee, How bigtech AI CAPEX spending will reshape future corporate cost structures" - link at the end of the 🧵:
Productivity = Automation + Specialization. Nations grow GDP/capita by automating (do more with the same people) or specializing (create higher-margin products). AI supercharges both. Taiwan going from an agrarian economy with a GDP/capita of ~150$ in the 1950s to a semiconductor powerhouse with a GDP/capita of $7000 by the 1980s is an example. Also worth noting that without automation, it’s hard to free up enough resources to move up the specialization curve. We’ll see later in the article that the same logic would apply to businesses — improving specialization & automation is directly related to productivity.Image
Our starting hypothesis was that as most orgs scale, fixed costs (FC) go up, and marginal productivity (MP) goes down. We want to be on the "genius savant" lines on FC and MP curves; instead most cos are the orange lines. A genius savant company will scale infinitely with very few people, and will maintain high productivity forever.Image
Read 10 tweets
Jul 13
~12yrs ago, I got a job @Google. Those were still early days of cloud. I joined GCP @<150M ARR & left @~4B (excld GSuite). Learned from some of the smartest ppl in tech. But we also got a LOT wrong that took yrs to fix. Much of it now public, but here’s my ring-side view👇
By 2008, Google had everything going for it w.r.t. Cloud and we should’ve been the market leaders, but we were either too early to market or too late. What did we do wrong? (1) bad timing (2) worse productization & (3) worst GTM.
We were 1st to “containers” (lxc) & container management (Borg) - since '03/04. But Docker took LXC, added cluster management, & launched 1st. Mesosphere launched DCOS. A lot of chairs were thrown around re: google losing this early battle, though K8 kinda won the war, eventually 👏
Read 14 tweets
Jul 5
So now that Nvidia has far outstripped the market cap of AMD and Intel, I thought this would be a fun story to tell. I spent 6+yrs @ AMD engg in mid to late 2000s helping design the CPU/APU/GPUs that we see today. Back then it was unimaginable for AMD to beat Intel in market-cap (we did in 2020!) and for Nvidia to beat both! In fact, AMD almost bought Nvidia but Jensen wasn’t ready to sell unless he replace Hector Ruiz of AMD as the CEO of the joint company. The world would have looked very different had that happened. Here’s the inside scoop of how & why AMD saw the GPU oppty, lost it, and then won it back in the backdrop of Nvidia’s far more insane trajectory, & lessons I still carry from those heady days:Image
After my MS, I had an offer from Intel & AMD. I chose AMD at 20% lower pay. Growing up in India, AMD was always the hacker’s choice - they allowed overclocking, were cheaper, noisier, grungier and somehow just felt like the underdog david to back against the Intel goliath!
Through the 90s, AMD was nipping @ Intel’s heels but ~2003 we were 1st to mkt w/ a 64-bit chip &, for the FIRST time, had a far superior core architecture. Oh boy, those were exciting times! Outside of SV, I haven’t seen a place where hardcore engg was so revered. Maybe NASA.
Read 18 tweets
Jul 2
Speed of execution is the moat inside which live all other moats. Speed is your best strategy. Speed is your strongest weapon. Speed has THE highest correlation to mammoth outcomes. Those who conflate speed w/ 'thoughtlessness' haven't seen world class execution @ speed. E.g.:
Many confuse speed w/ impatience. Impatience is your boss pinging you @ 9pm then calling @ 6am to check if a task is done. Speed is strategic. It is a permeated sense of urgency built w/ a shared belief that what you are doing is important & if you don’t do it, someone else will.
AMZN defines speed. Their 2015 SEC filing () is a must-read: (1) deliberate irreversible decisions (~10%?) (2) expedite all else. Founding teams need to learn how to apply judgment w/ <70% of data (<50% for early stage cos). Move fast, “disagree & commit”. shorturl.at/xDEU1

Image
Image
Read 10 tweets
Jun 8
For those of you following anything SaaS, you'll note there have been a lot of calls around 'saas is dead' lately. If you are wondering why, I wrote about this last yr here👇. This isn't just about saas but rather a 50yr macro CAPEX/OPEX cycle at play under the hood. : shorturl.at/sJ4IZhttps://medium.com/@MohapatraHemant/capex-opex-supercycles-the-dusk-of-saas-and-the-dawn-of-ai-saas-8aa5cfe74c93
Over the last 20yrs, both the cost of building and distributing software has COMPLETELY crashed. 20 years ago, it’d take a 4yr CS degree to write software, today thanks to internet anyone who wants to work hard can learn to code. In 20yrs world has gone from 5-6M software developers to 60M+ today. Second, the cost of distribution has gone to zero thanks to SaaS. I remember the days MSFT used to ship us a new MSDN CD monthly; imagine if you had to burn 60M CDs monthly as MSFT today? Software is shipped hourly, globally, all at once to everyone now.Image
Result? A Cambrian explosion in SaaS Globally. Every revenue pool is fragmented across lots of players now. This is also why even at $200-300M ARR scale, network effects of brand/WOM are becoming harder to see -- there are very few to none of "no one gets fired for buying IBM" type businesses today. Public markets can't foresee a 300M ARR business going to 1B ARR as easily as they would in the past. Ergo, multiples compression across the board.
Read 9 tweets
Feb 10, 2023
This is for SaaS & esp India-SaaS but applies more broadly as well. I’ve been investing in India-SaaS since '18 & harping abt this endlessly to anyone who’d listen. I’ll say it again: the age of “business model innovation” in SaaS is over. It’s done. What does this mean? 🧵1/20
If you don’t have a fundamental product or tech innovation at the heart of your company, you are looking at a 10yr slog ending in a $5-10M ARR plateau → a [10-20]% CAGR lifestyle biz; a sub-$50M M&A by the category leader; or a slow death to $0. What changed, you may ask? 2/20
10yrs ago, “GTM as product” still had a shot. Building a basic SaaS product was *hard*. Cloud was in relative infancy. At GCP, the 1st thing customers would ask us was ‘why should we entrust our mission critical software, infra, data to a 3rd party?” Today we laugh @ this Q. 3/20
Read 20 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(