3 ms·
Right, sure, there is an initial pain of building domain knowledge. But that one year of knowledge building, distribution, early customers, then dominates who h
by mikert89 1y ago
Right, sure, there is an initial pain of building domain knowledge. But that one year of knowledge building, distribution, early customers, then dominates who has control over the cap table for a decade. Why not just do this work yourself? Its some weird myth that someone capable of being a technical leader cannot also flesh out the distribution
Especially with the existence of AI, it really makes no sense and is some weird hierarchical system built by business people
- abrichr 1y ago> But that one year of knowledge building, distribution, early customers, then dominates who has control over the cap table for a decade. Can you recommend any resources for learning how to do this work yourself?
- mikert89 1y agoOne shortcut would be to: 1. pick a vertical (construction, legal, accounting, etc) 2. look at how to apply ai (compliance, voice customer service, email) 3. find sales people from a would be competitor or old school b2b saas in that area, and pay them 150$ an hour to tell you what customers are paying for 4. at the direction of how to do sales, come up with the product and either do the sales yourself without building, or pay someone to do cold calls and pitch the product 5. build the product
- mooreds 1y agoI'd recommend: - the lean startup: https://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous-Innovation/dp/0307887898 https://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous... - Amy Hoy's blog: https://stackingthebricks.com/ https://stackingthebricks.com/ - working in the domain you are interested in for a year. Go be a realtor. Go work in a lawncare business. etc. etc. - read Patrick's advice about how he found customers for Appointment reminder: https://www.kalzumeus.com/2010/05/14/unveiling-my-second-product-demo-included/ https://www.kalzumeus.com/2010/05/14/unveiling-my-second-pro... edit: added link to Patrick's piece
- mooreds 1y agoMaybe AI has changed things, but I think it takes more than one year to gain sufficient domain expertise. But your argument still has validity even if it takes 2-3 years to gain the knowledge, so let me address that. My response is: if I wanted to be an expert in <startup domain> to the point I didn't need a co-founder CEO, I would take the time, the years I mention above. But that has costs (opportunity costs if nothing else). Instead, I prefer to be an expert in software development. This gives me less control in each given startup as you point out, but more optionality across startups (and other companies)[0]. This choice also means that I give input on the hard decisions that company leadership has to make, but I don't have to make the final call. Frankly, that's more weight than I care to bear. That's a personal choice. I've watched friends be CEOs of successful startups and it's not always (nor usually, even) fun or easy. 0: I wrote more about that optionality here: https://www.mooreds.com/wordpress/archives/3445 https://www.mooreds.com/wordpress/archives/3445
- x0x0 1y agoYou're trying to have a serious discussion with someone convinced he can build deep domain knowledge in eg banks and their needs, how to sell to them, plus the associated network, in a year while also writing code. Oh, and just assumes "early customers", ie you're also going to learn how to sell. Because how hard can it be :rolleyes:
- lurk2 1y ago> Its some weird myth that someone capable of being a technical leader cannot also flesh out the distribution This idea often gets repeated here but it’s based on ZIRP from 2010s driving up developer salaries to a point where every kid with some portion of a CS degree thought he was the next Zuckerberg. “Technical” contributors became convinced they were the only contributors. Lots of stories about “idea guys” and useless upper management who Just Don’t Get It (meanwhile most guys posting things like this have never even seen a balance sheet). It’s a popular idea here because it establishes devs as the smartest guys in the room, but it doesn’t have a lot of bearing on reality. Plenty of devs have neither the aptitude nor inclination to learn the business side of things, as evidenced by some of the lifers who post here about upper management. This attitude will change as market cools off, no code and LLM output improves, and overseas contractors become more accessible. > Especially with the existence of AI, it really makes no sense and is some weird hierarchical system built by business people LLM code output can be tested as it is generated, whereas its advice on accounting and contract law can only be tested by domain experts, who you can just pay for this advice without involving the LLM.
- mikert89 1y agoycombinator, the best very early stage investors of all time hold this opinion: "If you are a technical founder, you do not need a non-technical cofounder." https://x.com/snowmaker/status/1948160642399314188 https://x.com/snowmaker/status/1948160642399314188 Its really not up for debate, at this point it is a borderline scam to work for a CEO that isnt significantly better/bringing in capital. You are basically giving them free labor
- mjr00 1y agoYou don't need a non-technical cofounder, but you do need a founder willing and capable of handling non-technical things. If nobody in your startup team wants to handle sales, marketing, finances, and business operations, you're going to end up with working software that nobody's paying for.
- bix6 1y agoJared has an (unfinished?) degree in CS and Econ so that’s a bit rich for him to say. Why’d he bother with Econ if it’s so UsELeSs?