15 ms·
You do need a technical co-founder [video]
- jjtheblunt 3y agoThere have been multiple ads/posts recently from companies citing YC__ looking for a technical cofounder. So, is this post correlated?
- doctorpangloss 3y agoMaybe. Those posts offer preposterously low equity, so I wonder whom it is supposed to attract. Suckers? Y Combinator sincerely wants people to succeed, I don’t think it’s reactionary or myopic like that. That said, to fill whatever hundreds of spots nowadays, they’ve exhausted Math 55, it graduates all of 12 people every year. They’re dipping into a far greater supply of nepo babies than ever before. Those jagoffs can’t do anything - not programming, let alone sales - so whom is this advice really for? Those companies will “succeed” anyway, I mean they won’t fail. You can make a ton of money as a technical cofounder, but for the minimally intellectually stimulating problems of some moron's meaningless app, for that moron to get all the glory? Just to polish life off by marrying your subordinate and sending the kids to Day School? And shoveling all that money right back into meaningless angel investments? This is a stylized comment of course, but it's just to say, yeah, you need a technical co-founder, really easy for Y Combinator to say. I too would like extremely talented people to give everything and take nothing.
- deleted 3y ago[deleted]
- jjtheblunt 3y agoWhat’s Math 55?
- esafak 3y agohttps://en.wikipedia.org/wiki/Math_55 https://en.wikipedia.org/wiki/Math_55
- BadCookie 3y agoDo you mean the “founding engineer” jobs? It can be misleading, but those are not founder roles. They are regular employee roles where the “founding” part of the title is just an honorary indication that the person joined the company early. YC won’t count someone as a founder unless they have at least 10% equity in the company. Founding engineers are typically getting 2% or less (from what I understand).
- jjtheblunt 3y agoYep that’s what i noticed and the thresholds i did not know. Thanks for explaining.
- TuringNYC 3y agoFounding Engineer = Engineer making under-market salary for tiny sliver of equity who can be laid off anytime because the company is fledgling, works 70hrs a week, puts in major % of work a founder would contribute, but has little upside. To be honest, for someone who cant land market salaries (e.g. non typical background), who finds a good team, this might be a good opportunity.
- hackitup7 3y agoI'd take the even stronger stance that additional technical cofounders seems to deliver increasing rather than diminishing returns.
- redm 3y agoThe inverse side of this is, that depending on the business, you may need another type of co-founder as well. Two technical co-founders aren't the right fit for every business.
- timeagain 3y agoCan’t be bothered to watch the whole video at work so I apologize if this is in TFV. If you can’t find one technically minded person who believes enough in your vision to drop everything and help you make it, that is not a good sign for your vision.
- michaelje 3y agoOr a technical audience is not the market
- anamexis 3y agoThat doesn't seem relevant. A co-founder isn't part of your market or audience.
- notahacker 3y agoThat's why the willingness of a software developer to drop everything to work with you might not necessarily signal anything wrong with your vision. If you can't find a single software developer who believes in your plan for better APIs or project management tools or consumer internet apps, it's a pretty good heuristic that your vision or ability to sell it sucks, or that you add less value than the dozen other people that talked to them about chatbots for X this week. Any prospective technical co-founder has a huge amount of insight into those markets. On the other hand, unwillingness of software developers to believe that the dullest sounding CRUD app going will be very exciting to grey suited men controlling a little known niche (probably precisely because hardly anyone's writing software for it) doesn't actually mean there isn't a market there.
- esafak 3y agoYour product could be boring and useless except to a niche audience, but still a great business opportunity. In that case, people will only work on it for the money, and that is fine. Some ideas are simply harder to sell to potential employees: “We’re making the world a better place through paxos algorithms for consensus protocols.” “We’re making the world a better place though software defined data centers for cloud computing.” “We’re making the world a better place through canonical data models to communicate between end points.” “We’re making the world a better place through scalable, fault tolerant distributed databases with acid transactions.” https://www.youtube.com/watch?v=B8C5sjjhsso https://www.youtube.com/watch?v=B8C5sjjhsso
- atoav 3y agoThis is what I constantly tell my students: The hard part about doing a tech product for the most part isn't the what beginners think makes tech hard — the hard part is wrangling systemic complexity in a good, sustainable and reliable way. Many non-tech people e.g. look at programmers and think the hard part is knowing what this garble of weird text means. But this is the easy part. And if you are a person who would think it is hard, you probably don't know about all the demons out there that will come to haunt you if you don't build a foundation that helps you actively keeping them away.
- sonicanatidae 3y ago>This is what I constantly tell my students: The hard part about doing a tech >product for the most part isn't the what beginners think makes tech hard — the >hard part is wrangling systemic complexity in a good, sustainable and reliable >way. I teach the same thing, seemingly every day to my teams. It doesn't work, until it works reliably, within reason. High-5 from the doers to the teachers! (Both are needed) For the record, my partner teaches at a major university, just not tech. ;)
- sebmellen 3y agoMore people need to read https://grugbrain.dev/ https://grugbrain.dev/
- jeremyjh 3y agoI really wish I'd read this 25 years ago, but probably I wouldn't have believed any of it.
- geiagal 3y agoI wonder what portion of Hacker News users aren't technical. I thought this headline meant a technical founder needs a technical co-founder even.
- gumballindie 3y agoJudging by how many believe procedural text generators are viable programmers, i’d say a lot of hn users arent technical.
- AndrewKemendo 3y agoI'd venture to say the majority are non technical
- deleted 3y ago[deleted]
- CodeCompost 3y agoYeah and then the non-technical co-founder treats you like you're worthless because you're "just a programmer"
- redm 3y agoThat may be more of a personality conflict. There's no more important choice than who you co-found with, and both parties should have high regard for each other's value to the business.
- distortionfield 3y agoOf course that’s how it _should_ be. After working at enough startups in very early and/or founder roles, I can tell you it’s more common than not to get treated like a second class citizen when the “business” dinners come.
- deleted 3y ago[deleted]
- distortionfield 3y agoA tale as old as time. Gotta love the classic spin on the same trope of “the C suite drives the sales tho” to justify their insane salaries and bonuses. like they’d have anything to sell in the first place.
- robertlagrant 3y agoYes, you need to make and sell things. They're both difficult.
- distortionfield 3y agoI’m not diminishing the effort and skill necessary to be a good salesperson. I am, however, commenting on how often that turns into engineers being kept “in the back” when the paperwork starts.
- jjtheblunt 3y ago(Title is altered, changes meaning: explanatory "Why you need..." is more enticing than the assertion "You do need...")
- deleted 3y ago[deleted]
- biomcgary 3y agoI think the amount of technical expertise needed varies by field. I work in a small biotech startup. In this space, you aren't going to get anywhere without deep technical knowledge.
- jensneuse 3y agoThe inverse is also true. As a technical founder, and maybe even an introvert like me, you should definitely look for a non-technical co-founder who can help you with networking, etc... I found my dream co-founder through YC Co-founder match and what can I say, it's going great. We're focusing on enterprise GraphQL/API solutions (https://wundergraph.com https://wundergraph.com) and I benefit from the networking and communication abilities of Stefan, while I answer all technical questions. Tldr, I highly recommend to team up with people who complement your skills.
- malux85 3y agoIt’s great to hear of a YC Co-Founder success, I’m looking for a non-technical cofounder now so I’ll give this a shot
- Tactical45 3y agoYou hit the nail on the head with complimentary piece - and extending that to personality as well. You need a mix of technical skills (engineering, product, marketing, etc) but also personalities (which manifest in different behaviors which are all useful & compliment each other - eg bias for action and hitting targets vs careful analysis).
- jensneuse 3y agoI'm very strong in logical analysis and strategic thinking. My problem though is that I have a natural tendency to not talk to people. Ask me a question and I'm happy to answer, but I don't like to initiate conversations. Stefan is the opposite. Everybody loves him. He can talk to everyone and he's very creative in finding leads and building connections with other companies. But he's a really bad developer. Together, we're a really strong team. I'd say without him, I would still not have a strong network.
- ryandrake 3y agoHonest question: Why can't this person be employee #(single digit), SVP of sales or something, hired during product development? Why the need to elevate to co-founder? Does an introverted technical founder really need an extraverted non-tech networking expert from day one?
- tracerbulletx 3y agoHaving started a small business I respect greatly the skills of great sales people and fund raisers and people who are great with people. But I don't respect them when they think they can start a business where they don't take what they actually make seriously and think the product will just work its self out if they sell hard enough.
- threeseed 3y agoHistory has shown them to be right. There are many terrible products in this world that were successful only because of good sales and marketing. And vice versa.
- jeremyjh 3y agoHow many of those are from single-product startups? I know some are, but not most that I can think of.
- deleted 3y ago[deleted]
- cmrdporcupine 3y agoIt's just survivorship bias though. There's also boatloads of startups that had crap product and just died right away, and we don't talk about them.
- debacle 3y ago> There are many terrible products in this world that were successful only because of good sales and marketing. And vice versa. Name one.
- mplewis 3y agoTesla cars
- cmrdporcupine 3y ago
- ofirg 3y ago"but based on the thousands of companies YC has funded over the years, companies lacking a technical co-founder underperform" which could mean soon-to-be-underperforming companies fail to attract technical co-founders
- lnsru 3y agoI am developer who spend 2 decades developing things. First decade it was hardware and now I moved to software. I can always guess which idea from “idea person” will work and which is not technically feasible. In my limited experience the “idea persons” are not really listening why stuff does not work. Sometimes simple laws of physics are ignored.
- ofirg 3y agoto dream is to be mad. so that tracks.
- brynbryn 3y agoThe original title on this (which was there when I started this post) was infuriating - but it is still bad. Is it speaking to the 'true' co-founder who is above the technical one? Maybe the other co-founder who is an 'idea innovator' could up-skill a little and stop pretending that you can build a business by putting on a power suit and making presentations with upturned hands and studied pauses?
- sebastianconcpt 3y agoVery timely for a conversation I'm having this week. Thanks for bringing this up.
- oooyay 3y agoI like Michael's take that the real value in a founder is their ability to recruit the right team. What I don't think was said explicitly here is that typically technical people are progressively marginalized as the business grows. We get some harrowing stories where that doesn't happen, but I don't think that's the standard story. Like they allude to, it's a story of what the people who handle the money and investments value. Context: Michael is a non-technical founder from Justin.tv and Twitch.
- michaelmior 3y agoI'm confused what is harrowing (acutely distressing or painful as Merriam-Webster says) about stories where technical people are not marginalized.
- oooyay 3y agoTypically stories I hear where technical people maintained equity it was through a lot of maneuvering. It wasn't given to them by the merits of their accomplishments.
- michaelmior 3y agoFair point. That makes sense :)
- bomewish 3y agoI was also puzzled. Thanks for asking and thanks for clarifying.
- deleted 3y ago[deleted]
- choppaface 3y ago> typically technical people are progressively marginalized as the business grows I know three YC technical co-founders who were ousted by their CEOs, and a justintv alumn who got nothing from the follow-on exits. When YC says “you need a technical co-founder” they mean it like you need a disposable lawyer. The essay here is about targeting growth and flipping, not high-performance teamwork.
- anovikov 3y agoThat's explainable, Dunning-Kruger effect. Whole custom development industry is based on it. Otherwise it will never exist as there are whole agencies with 20-30 year history that never seen a tiny bit of what they produced working in production: everything is a throwaway paid for by these would-be founders. It's like clouds: AWS exists because enough stupid people don't understand available hosting options and can't make simple cost calculations. This will never change simply because no one makes money if it does. If those people started looking for a tech-cofounder, then two options: - they never find one, thus give up on the idea, the money they spend/waste on it will never be spent, thus GDP from this final consumption (which nearly all of custom development is: final consumption, a hobby), will not be created. - they find someone who will pretend or will falsely believe to be technical. essentially same guy as the original one. and he will waste some time and money with freelancers, become convinced they are all fraud (because this is what happens when you ask for idiotic stuff to be built on impossible budgets - everyone except scammers, decline), then hire some agencies, and waste some money on them, aaaaand it's gone! How do you explain to people who are not capable of starting a business, that they shouldn't start one? Bigger question: WHY would you do it? Why not just benefit from them?
- robocat 3y agoUsing Dunning-Kruger as an explaination is a very Dunning-Kruger thing to do: https://news.ycombinator.com/item?id=38415252 https://news.ycombinator.com/item?id=38415252
- gnicholas 3y agoThis is generally true. I had a technical cofounder for the first 4 years or so, but once our tools were built it was less clear what his ongoing role would be. This is because at that point, our focus turned to licensing our (patented) technology to businesses. We still have B2C customers who use the tools that he originally built (and which have been updated by contractors after he left), but now the vast majority of our revenue comes from our B2B licensing. We are pretty unique in this regard, since most startups aren't able to generate much revenue from licensing in this way. Specifically, when we work with our licensees, we provide a JS library that they plug into their own platform. We don't need engineers to do integration work, or provide support. My technical cofounder provided a lot of value in getting us to where we are, for sure. But needing a technical cofounder to launch doesn't necessarily mean you need one all the way along.
- m_a_g 3y agoAnd your client's needs won't change ever? The product won't need anything done on it until vacuum decay? Finally, someone made a proper JS library.
- gnicholas 3y agoThe clients don't want us mucking around in their code, which is why they have their devs do the work. There are some cases where having a dev on our end could help unblock their devs, but these are pretty rare cases. In general, it's very easy for folks to use our tech, and I'm able (thanks to a couple years of CS back in the day) to help out with the vast majority of questions that come up. In terms of changes, there aren't any material changes. We've had licensees up and running for 7 years without changing any code.
- bob88jg 3y agoWhat so the person who "provided a lot of value in getting us to where we are" got ditched in the end? Is that your story? Use people and then chuck them to the curb once everything u need has been extracted?
- 3y ago
- deleted 3y ago[deleted]
- DelaneyM 3y agoCorollary: you do not need a non-technical co-founder. My advice to engineers is that it's nearly always easier to learn business/sales than to learn to like a co-founder, especially the type generally drawn to being a "business" founder. It is good to have a co-founder in general though, get one of those if you can. Just don't worry about finding complementary skills, bias entirely towards someone you can work with.
- Eumenes 3y agoI generally agree but if you're developing a product for a niche industry and that non-technical co-founder has a shit ton of insight and connections, it will 1000% open doors. Then again, perhaps you can partner with those folks in other ways vs giving away 50% equity.
- edgyquant 3y agoBy that logic the person with that domain knowledge can partner with technical folks for less than 50% equity. Which is what normally happens in my experience
- gnicholas 3y agoThis is more likely to be true where you are selling to other technical people. But it becomes much less likely to be true when you are selling B2C, or to non-technical businesspeople. And of course, the ability of a technical person to learn sales varies quite a bit. Some technical folks pick it up easily, but others do not (or find important non-technical bits like fundraising and sales to be very distasteful/annoying).
- notahacker 3y agoAnd of course the reverse is true. Some "business people" can pick up a huge amount about UX, client priorities, process automation and what is and isn't technically possible and make useful product management contributions even if they never touch the codebase, and some simply aren't interested in that level of implementation detail even if they're really good at selling the big picture and someone really needs to get a handle on that side of the business.
- amelius 3y agoThe first non-founder employees of a company usually end up with the worst deal financially. Take that into account if you're the technical guy working for the startup.
- esafak 3y agoDepends on what you mean by founder. Pre-funding employees can get sweet nominal-cost restricted stock awards.
- TuringNYC 3y ago>> Depends on what you mean by founder. Pre-funding employees can get sweet nominal-cost restricted stock awards. So basically, lottery tickets that you get to cash out in 7yrs if you are lucky. You are better off working at market rates, and buying Nasdaq options with your pay difference.
- esafak 3y agoI suppose you started your company expecting to make a loss relative to buying options, and you tell prospective hires the same thing? You're skipping the part about early hires having outsized impact over the fate of the company and the value of their equity.
- TuringNYC 3y agoFair point. The risks are huge. Makes sense if you've got 30% of the cap table. The risk is worth it. Esp if you are founder and on the board directing the company and fending off risks. Not sure it makes sense if you've got 0.5% equity. Definitely does not make sense if you are being given X,000 shares and have no access to the cap table. Any engineer who thinks they can value a fraction with a numerator and no denominator is fooling themselves. Startup employees -- if you were given 50,000 shares but told you arent allowed to see the cap table, please UPVOTE/DOWNVOTE accordingly if you think the pay-cut to market was worth the money you got at the IPO.
- 3y ago
- hoistbypetard 3y agoI never thought that was an open question (given the space we're talking about)... The one that seemed more open and therefore more interesting: do you need a non-technical co-founder?
- Belomolo 3y agoMost modern companies ARE tech / it companies but either don't know it or don't accept it. It's easy to run services on the internet when you don't know what you are doing wrong...
- kragen 3y agothose companies will happily outsource the development of their core competitive advantages to another company who does appreciate its value; they will then sell it to their competitors
- 23B1 3y agoThis is dated. There's no rules to founding your own company. As a non-technical founder I can A) Get a technical cofounder which takes me weeks to find, dilutes my ownership, and with whom I have no recourse if their work is sub-par (or we end up just not liking/trusting/vibing with each other) or B) Build an MVP with any number of offshoring partners in a matter of weeks and for far cheaper (money, time, opportunity cost). If I don't like the work, we can modify the contract, or I can quickly pivot to another team. This is also true for technical founders as well, to be clear. You can probably do a lot of the business stuff by outsourcing. You can worry about gelling a team once you've got to 1.
- nurple 3y agoHeh, good luck. As a tech cofounder, I attempted to do just this and I have extensive development and management experience. It was a nightmare, EVERY SINGLE offshoring company tried to play us as a group that didn't know their stuff, and when put to the iron they couldn't produce anything that would stand up--technically--against a mild sneeze. If I hadn't been there, my other founders would have gotten up to their eyeballs in offshore dev debt and would have a giant hairball that even the most experienced tech people would be unable or unwilling to make additional progress against once the offshore team stops delivering. So, good luck trying to lead an offshore team that's only interested in absorbing as much money from you as possible before moving onto the next sucker. If you don't think a tech cofounder is worth their ask, then you deserve to get exactly what you pay for.
- kragen 3y agoi'm interested to hear what kinds of things they did and what you did in response. there are probably a lot of good stories there
- TuringNYC 3y agoI'm not the GP, but I know many of the tricks to watch out for: - Offshore partner delivers software, but you dont have any code. Successive rounds of updates become more expensive. You cant walk away because you have none of the code. (Business co-founder has no idea and goes to new partner with binaries expecting updates to be delivered, then gets told they need to start from scratch) - Offshore partner delivers software and code, but not the code corresponding to the software. You try to switch partners, but realize you start from zero, because you dont have the code - Offshore partner delivers software and correct code, but only for the app/UI. Only they retain code for the backend. - Offshre partner delivers code for UI and backend, but not the right code, UI is secretly pointing to a different backend with different code - Offshore partner delivers correct code all around, but only they have the build scripts, dependencies, and cloud images required to run it. - Offshore partner delivers everything, but only they have the data required to start up the system. New partner spends as much time figuring things out and eventually wants to re-code the whole system. For each of the above, business co-founder goes thru the rounds two or three times. Each time, they spend 20 or 30k and each time they walk away with binaries they cant do much with. Eventually they give up, or find a technical co-founder.
- hiddencost 3y agoI'd argue the other side of the this: you don't need a non technical cofounder.
- gkoberger 3y agoDisagree, and I say this as a technical founder with no cofounder. Once things start to take off, a majority of the things you deal with are non-technical. There’s so much that goes into building a company, and you really need someone who understands how businesses work and can run G2M. Sure, you can hire for it… but you’ll almost never find someone as invested in it as the founder, and it’s just as important as the product.
- geniium 3y agoI love the format with the topics on the side, well done YC! Downside: they are too much looking around , probably a lot of people around or screens with prompters. Disturbing me
- vlod 3y agoAssuming you've just seen this for the first time, it's worth watching ALL of the Dalton+Michael videos. Have fun!
- opportune 3y agoEven this article IMO subtly demonstrates the mindset that leads nontechnical founders to not think they need a technical cofounder, by phrasing the search for one as “recruiting” as if they were a subordinate or code monkey. It should be a partner relationship, not a subordinate relationship. This mindset that technical cofounders are essentially “coders” (a term I hate) is very prevalent among inexperienced nontechnical founders. I know I’m preaching to the choir here but a lot of technical people have deep industry/business/product knowledge and have social skills. It is very frustrating when some Ivy League 25 year old PM/management consultant tries to pitch you on their vision while treating you like an idiot savant they can easily take advantage of.
- welfare 3y agoCompletely agree, I'm waiting for the article on "Why you need a business-oriented co-founder and how technical founders can recruit one"...
- thelittlenag 3y ago+1 on that!
- debacle 3y agoThe problem is that you don't. "Business" has been systematized in many ways, and more and more your "business" is just someone else's software.
- jdminhbg 3y ago> There are two reasons founders resist going out and recruiting users individually. One is a combination of shyness and laziness. They'd rather sit at home writing code than go out and talk to a bunch of strangers and probably be rejected by most of them. But for a startup to succeed, at least one founder (usually the CEO) will have to spend a lot of time on sales and marketing. [2] http://paulgraham.com/ds.html http://paulgraham.com/ds.html
- aleph_minus_one 3y ago
- jschveibinz 3y agoI'd like add to this conversation this two other important facts: 1) you (or your partner) do need domain experience and expertise. If you want open a bakery, or even try to automate a bakery, you really need at least some commercial baking experience. I see so many folks pitching a product in an area where they have zero experience. 2) you (or your partner) do need some organizational and/or business management experience. Business-whether it is software, hardware, or selling bakegoods-is about working with people and working with money. Learn about it and do some of it before starting uour own company.
- TuringNYC 3y ago>> 1) you (or your partner) do need domain experience and expertise. If you want open a bakery, or even try to automate a bakery, you really need at least some commercial baking experience. I see so many folks pitching a product in an area where they have zero experience. I'd love to deep-dive into your example. Lets say this is the case. Suppose you are the technical co-founder coding for 80hrs/wk. Does the baker also work 80hrs/wk? Can you just hire a baker as a consultant for 5hrs/month? Is that worth giving away 50% of the quity? Are they just providing some domain expertise you can buy a la carte, or are they bring in sales and critical relationships? Are they just another baker, or President of the National Baker's Association who will get you front-row exposure to thousands of bakers?
- jschveibinz 3y agohttps://news.ycombinator.com/item?id=14070135 https://news.ycombinator.com/item?id=14070135 Prior discussion on 80 hours a week.
- TuringNYC 3y agoI agree with the discussion that this isnt typical for programmers (employees) but I think for founders it is very different. A successful founder has to put in so much. Even when you arent working, you are often working -- that might mean lunch with a potential investor gatekeeper or a soft pitch to a prior colleague who might refer you to a client. Or working the room at a conference. Or speaking to a lawyer on the phone even when you're at the playground with your children...because otherwise you might lose some critical client sale in the redlining process. I dont think I've ever worked as much as when I was a founder. There is also the sheer leverage you have over the business and outcome. Every hour invested can mean so much.
- thelittlenag 3y agoAnd here what we need is a business co-founder who can help us crack the nut of getting traction. Sigh.
- vlod 3y agoI think the old manta at here and at YC: "Make something that people want" probably answers that. A lot of us here have been guilty of building vitamins rather than painkillers. I speculate lack of traction is an indicator of that.
- ilc 3y agoAs a technical founder/early person in my past: If you don't know why you need a technical founder. That is EXACTLY why you need one. It is the same reason why if as a technical founder, I didn't know why I needed a non-technical founder. I'd probably be making a major error. To those saying they waste equity: If you truly have a failed company, with a bad founder, buy them out or kill the firm, it happens. You've learned some key lessons. If the founders you need cost you 75% of your equity and you make a unicorn.... Were they worth it? Who cares. You got your fuck you money.
- TuringNYC 3y ago>> If the founders you need cost you 75% of your equity and you make a unicorn.... Were they worth it? Who cares. You got your fuck you money. How many times does it end at the technologist owning 25%? I've seen tons of friends swindled and ending up with nothing and successive rounds of business hires walk away with the value.
- ilc 3y agoIt does help to have SOME finance background when doing all this. I will not deny that people are gonna get screwed. The question is how to minimize the damages.
- hartator 3y agoOr you do not need non-technical founders. Sales people selling themselves more than anything.
- syrusakbary 3y agoI'm a technical founder working in a deep-tech startup. If I am completely honest, I think the recommendation of having a technical cofounder while useful for startups in the past might not be as useful for the startups of the future. Why? I strongly believe AI will cause a paradigm shift, and I'll adventure stating that AI will make non-technical people be able to do more and more with less. Which will make the requirements for differentiation in the tech side even harder to accomplish (very few people reaching the god-tech realms), but at the same time it would make the bases reachable for almost anyone. Basically, a more polarized order where less people will have access to "technical founders" that can differentiate themselves enough outside of the AI realms. I'd love to get more thoughts on this!
- WendyTheWillow 3y agoHaving used LLMs to solve tech problems, I would not trust the current state, or even GPT5, to reliably solve anything other than the most trivial of trivialities. Is the idea that in 2025, AWS will have an AI console where a non-technical founder types in what they want their site to do, and the LLM takes care of the rest? Register domains, build out the database/backend/auth/frontend, etc.? I really can't see it happening in 2025, or 2035, without some pretty big leaps forward, the kinds of leaps that may never be possible.
- danenania 3y ago"Is the idea that in 2025, AWS will have an AI console where a non-technical founder types in what they want their site to do, and the LLM takes care of the rest? Register domains, build out the database/backend/auth/frontend, etc.?" Even when this AI exists, the non-technical founder will ask it for the wrong things.
- TuringNYC 3y agoLOL? Why do we even need the business co-founder? Let the LLM create the idea also and keep 100% percent of the equity for the FAANGs that created the LLM
- vlod 3y ago
- m348e912 3y agoAs someone who would be interested in being a technical co-founder (complete with my own seed money), I wonder if when they say technical co-founder, they mean programmer who can build a MVP or someone who can build a technical team and help solve technical problems.
- TuringNYC 3y agoThey are speaking about non-technical founders who are seeking technical co-founders
- happydev 3y agoWhen I met my current cofounder he was paying $5,000/month to a dev agency in Eastern Europe that was ripping him off with slow progress, inflated hours, and very poor quality code. Their developer was brand new to the tech stack and made many glaring mistakes. As a non-technical founder he had no way to judge the quality of their work, he was completely at their mercy and they took advantage of him. I do not know how non-technical cofounders expect to avoid this type of situation.
- gnicholas 3y agoFor sure. I'm a non-technical startup CEO but did two years of CS in college. Also, my product is on the simple side, from a technical perspective. These two facts have definitely helped as I've overseen dev work and brainstormed new product ideas. If you've never done any coding, it's hard to know what is relatively easy versus relatively hard. I'm still not perfect, but at least I don't make the completely uninformed mistakes that I would make if I'd not done a little 'hello world'-ing of my own.
- quickthrower2 3y agoThe skill here though is the general skill of hiring people to do a job you can’t do yourself. This is a very useful life skill. Have you ever hired an electrician or builder? It is like that. So if you hire a company to build something think of a way to keep them in check. You could hire an independent person to review their work (like hiring a seperate project manager and architect to work with the builder) Or you learn the trade a bit and ask lots of hard questions. That fly by night outfit would crumble on asking basic questions because they are not cut out for it. Their happy paths is suckers. As a coder I got sucked into cheap labour coders and never again. Too much skummy stuff going on.
- corry 3y agoFor many (most?) startups, for many (most?) MVPs, in many (most?) domains -- yes, with a million caveats -- the "non-technical cofounder" can likely figure it out what's needed to hack together a simple product, get a handful of real users using it, and then go from there. In my case, all I had done was make HTML/CSS websites with a bit of PHP. But I didn't let "I need a technical cofounder" and "I'm just the business guy" stop me from figuring out how to build v0.1 myself and get it out. I had never touched a server before. I had never built a web app with a MVC stack before. I had zero experience with command-line prior. I didn't have any formal technical training. But I just started coding and built it myself, and from there was able to attract a great technical cofounder and early team. And 10 years later, we sold it for $100M. I'm not saying this to brag. I'm proud that "I figured it out" with duct tape but I realize that I had the good luck that it all worked out. But I worry that other guys like I was are sitting there thinking 'Shit, everyone says I need a technical cofounder'. Well, maybe not. Go try to build it yourself. Especially in the age of co-pilot and decades of StackOverflow - for most apps, you can figure it out. No one take this the wrong way. I'm just trying to potentially inspire some bright person out there to try it themselves, and building the first simple version yourself might be the missing step in attracting a REAL technical person or at least validate your hypothesis.
- deleted 3y ago[deleted]
- quickthrower2 3y agoThis is going to age as well as supermarket cheddar. In a year the explosion of nocode and AI driven tools will allow lots of non-technical founders to build great startups. Especially the X for Y ones. No you can’t build a Google, Instagram or Dropbox that way but you can build a business to the point where you can hire a CTO. You can get started without a tech cofounder for many things. All the Uber for X type stuff like Airbnb or that YC one with cleaners for hire a while back are examples.
- selcuka 3y ago> In a year the explosion of nocode and AI driven tools will allow lots of non-technical founders to build great startups. Corollary: In two years of time, the inflation of No/Low Code + AI startups will lead to massive competition, and only those who has an actual technical cofounder will survive.
- quickthrower2 3y agoFor tech companies yes. A lot of startups aren’t really tech companies but “we use tech” companies. Those will buy off the shelf solutions from the tech startups or from big tech.
- exabrial 3y agoLol why are tech skills so talked down on? How about a non idiot business and accounting savvy co founder with a great vision and a solid product idea with a firm understanding why previous attempts failed, but also with the maturity to admit when they were wrong about their calls? Loool Come on man.
- spacetimeuser5 3y agoCan I offer intravenous DMT, ketamine or at least psilocybin (in various frameworks) for a technical co-founder, especially in such fields as bio/neurotech, AIxchemistryxhardware, as this may necessitate from the methodology of quantum mechanics?
- tristenharr 3y agoI love getting approached by friends and family and having to do my best to gently let them down on their “million dollar ideas” they “need my help building”. It’s not that they are all bad ideas. I just stopped putting any value at all in “ideas” a while ago. Ideas are a dime a dozen, even trillion dollar ideas. (Here’s an idea, lets invent teleportation, it took me ~3 seconds to come up with a trillion dollar idea!) I think there are three things that matter so much more than the idea. Team, execution, and traction. You need the right team, and putting together the right team is the most difficult thing to do, because a good startup team needs to be able to cover the largest amount of surface area in terms of “stuff we can do ourselves”. There’s a lot of different “departments” in a company, and at the early stage it’s the founders covering all of them. If you want me to play Frontend Dev, DBA, Product Manager, Architect, Backend Dev, Tech support, and Tech recruiter I’m ok with that so long as you can play Accountant, Fundraiser, Spokesperson, Secretary, Lawyer, and customer support. You also need execution. I won’t say the execution has to be great across the board, but ideally it’ll be great in a few core areas key to your idea (I.e. your special sauce), while being “good enough” across all the “departments” you juggle to convince people you know what your doing. This is where I think lots of people fail. People have this false notion that they can do the things they are most comfortable/good at and somebody else will soon come along to handle the other stuff. (Well we can just hire somebody for that they say — with what money I ask?) Execution means understanding that no job is below you because at the end of the day it is solely on you if it gets done or not and oftentimes there is nobody else to do it. The monthly update emails don’t get sent unless you send em. The employees don’t get paid unless you pay em. (They tend to get bitchy about that if you forget to do it on time too.) The product doesn’t get built unless you build it, and the customers don’t get acquired unless you acquire them. That brings me to the last thing, which is traction. If I had a dollar for every-time someone has tried to get me to go in on building their “New take on social media, it’ll be the next big thing!” I’d probably be able to self-fund my next venture by now. If you have “the best thing ever” but nobody’s using it, it isn’t “the best thing ever”. It’s kind of like Schrödinger's cat. Your product is both the best thing ever, and a piece of garbage until somebody opens the box and uses it, upon which you find out which it is. You don’t need traction at first but eventually you need traction or your venture will become a exercise in masochism as you slowly slide towards bankruptcy trying to get enough traction to save you the company from entering a death spiral.