Sagun Garg

3 x Founder/CTO (15+yrs), 2 x CTO Advisor, 3 x EIR, 9+ Polyglot Programmer, ex-Deloitte, B-Tech(CS).

[3 x Startups] [GitHub] [X/Twitter] [Blog] [Google Scholar]
Written by Sagun Garg
on 

November19: Y Combinator Startup School Notes

MVP Basics for a StartUp

SeriesMVP: Episode 1

QUESTIONS ?

  • Are you solving for a Problem of a User ?
  • Are you your own User? 
  • Is your MVP Embarrassing enough (optimise for speed) Does some value stick with a user ?
  • Are you optimising for a Niche early on non-scalable with your MVP?
  • Are you solving Non-scaling but manually ?

DON’T

  • Don’t build product before defining the problem of a user 
  • Don’t build for a mysterious set of users
  • Don’t iterate problem and market(fall in love with problem statement on the solution) but iterate only on the solution
  • Don’t build heavy MVP (keep it lean landing page + spreadsheet)
  • Don’t solve for everyone 

SERIESMVP: Episode2

  1. Iterations of MVP: Be prepared to throw away your solutions during iterations. Hold the problem and market hard and close to your chest, be very flexible with the solution

  2. Stages of Iteration
    • 1st MVP: Use Problem Statement(Solve for a User) + Gut feel Solution(Don’t Listen Users for Solution)
    • 2nd MVP: Problem Statement +. Market (Hold on to This) + Solution (Listen to Early users Feedback)
    • 3rd MVP: MVSP Vs MVLP: Minimum Viable (Shitty vs Lovable) Product
  3. Product + Early Users for an established industry is a better way to lead the MVP without caring much for business model (because it is an established industry hence optimise for growth. Business model is much easier to discover. But if it is a new playbook then market sizing, goto market and business model need to be emphasised before the product early on)

bitcoin-principles

high-standards

nexchanges

startup

founder-cto

entrepreneurship

books

blogs

bitcoin,

ethereum,

chainlink,

polkadot,

solana

ycombinator

notes

startups

ycombinator-other-ideas

application-pattern

design-pattern

automated-testing

fuzzing-engine

python

vulnerability-research

security-analysis

polyglot

programming

webassembly

AI-ML

crypto-vcs

longetivity

ownership

property-rights

tokens

protocols

bitcoin

ethereum

chainlink

polkadot

smart-contracts

defi

blockchain

skills

roles

poems

mentorship

pitching

founders

operator

vcs

crypto

pantera-capital

bitcoin-physics

moonstream

proof-of-work

power-projection

token

native-asset

filecoin

proof-of-x

freedom-tech

confiscation

censorship

permissionless

decentralized

lightning

method-of-accounting

amm

damm

liquidity-pools

gpt4

llm

chatgpt

gpt3

ai-ml

estate

planning

multi-sig

miniscript

spending-conditions

btc

multsig-decay

inheritance-planning

btc-contracting-key-setup

btc-expanding-key-setup

decay

inheritance

physics

saylor

thermodynamics

casa

multis-ig

bitcoin-wallet

bitcoincore

release

technical

improvements

Libitcoin

mempool

BIP324

timelocks

bitcoin-smartcontracts

ordinals

wallets

nft-bitcoin

smtp

email-servers

procotol-design

decentralised

communication

enterprise-custody

frost

roast

musig2

multsig

bip

taproot

future

wealth

private-banking

deflation

hyberbitcoinization

wealth-banking

AI/ML

mindset

bootstrap

unlearn

artificialintelligence

ai/ml

enterprise

custody

witness

signing

learners

visual

auditory

kinesthetic

microstrategy

berkeshire-hathway

accumulation

privacy

bonds

risk-profile

michael-saylor

OG

investor

custody-types

TabConf6

bdk

day1

day2

day3

multisig

self-custody

utxo

pow

store-of-value

mstr

degen

mstu

mstx

hedgefund

options

moneyness

call

put

strike_price

market_price