Can technical founders handle business tasks like sales and fundraising?

Yes, technical founders can handle business tasks. These tasks require general intelligence, which technical individuals possess. While having specific industry expertise can help, a technical founder can learn or adopt these responsibilities with enough drive and willingness.

What's the difference between having the ability and the appetite for business tasks?

The ability to do tasks is about possessing the skills, while appetite is about having the willingness and enthusiasm to do them. A technical founder may be capable of sales, but lacks the 'appetite' for it. It's crucial for a founder to have both, or to ensure someone on the team strongly does.

Are there successful companies founded solely by technical people?

Yes, there are many prominent examples. Companies like Google, NVIDIA, and Microsoft were all founded by individuals with technical backgrounds, demonstrating that a separate business co-founder is not always essential for massive success.

When might industry expertise be more valuable than a business co-founder?

When selling into specific industries like legal or medical, a founder with direct experience (e.g., a lawyer or doctor) can be highly beneficial. Their understanding of the customer's language and needs can be more critical than general business acumen.

What does investor feedback about needing a business co-founder really mean?

Often, this feedback points to a perceived deficiency in the technical founder's 'appetite' or quality in handling business aspects like sales or company setup. It's less about lacking skills and more about a lack of drive or commitment to those non-coding responsibilities.

Why is having any co-founder, even without specific business skills, important?

The core reason cited is the sheer difficulty of the startup journey. Having a co-founder provides essential emotional support and a partner to navigate the challenges with, regardless of their specific skill set.

Key Moments

Do Technical Founders Need Business Co-Founders?

Y Combinator

Science & Technology5 min read11 min video

Jan 11, 2024|166,596 views|3,666|210

YC Y Combinator yt:cc=on

Save to Pod

Key Moments

TL;DR

Technical founders don't inherently need a business co-founder; the key is having someone with the 'appetite' to handle non-coding tasks, regardless of their background.

Key Insights

Every company requires tasks beyond coding, such as incorporation, payroll, customer interaction, hiring, sales, fundraising, and customer support, which can be handled by any founder.

The crucial factor is not technical vs. non-technical expertise, but the 'appetite' and willingness to adopt and excel at these essential business tasks, rather than begrudgingly doing them or making excuses.

Some of the world's most valuable companies, including Google, NVIDIA, and Microsoft at their inception, were founded solely by technical individuals, demonstrating that a business co-founder is not a prerequisite for success.

If a technical founder is solving their own technical problem, especially in areas like developer tools, the need for a separate business co-founder diminishes significantly, as their technical background provides the necessary insight.

Investor or advisor feedback suggesting a technical founder needs a business co-founder might, in reality, be a polite way of pointing out a deficiency in the founder's appetite or execution quality for business-related tasks.

Defining the need for non-technical expertise

The question of whether technical founders require a business co-founder is a complex one, often debated by investors and advisors. While the answer to 'does every startup need one person who can't code' is a definitive no, the underlying discussion revolves around the necessity of non-technical skills within the founding team. The core argument presented is not that technical founders are incapable of handling business tasks, but that the *willingness* and *appetite* to perform these tasks are paramount. Many essential business functions, such as legal incorporation, payroll, tax filings, customer communication, sales, fundraising, and customer support, do not require coding proficiency. Technical founders are just as capable of performing these 'smart generalist tasks' as anyone else, provided they have the drive and dedication.

The critical role of 'appetite' over background

The distinction between having the *ability* to perform non-coding tasks and having the *appetite* for them is highlighted as extremely important. A technical founder might be able to reply to emails or engage in sales, but the crucial question is whether they have the desire and vigor to do these tasks exceptionally well. Michael Seibel emphasizes that founders must adopt these responsibilities with excitement and a drive to be the best, rather than grudgingly or viewing the work as beneath them. This 'appetite' is the driving force that ensures these essential business functions are not neglected. It suggests that if a technical founder possesses this drive, they can effectively manage the business side, even without a dedicated business co-founder. Conversely, if they lack this appetite, merely adding a business co-founder might not solve the underlying issue if they aren't willing to engage either.

Historical examples of purely technical founding teams

The argument against the absolute necessity of a business co-founder is strongly supported by examining successful, high-value companies. Google, founded by Larry Page and Sergey Brin, and Microsoft, founded by Bill Gates and Paul Allen, both began with purely technical founders. NVIDIA, a company at the forefront of GPU technology, was founded by individuals with deep technical expertise in electrical engineering, who arguably possessed the vision and understanding essential to create the company. While the CEO of NVIDIA may not spend his days coding, his background as a trained engineer was instrumental. Similarly, within the Y Combinator portfolio, companies like Stripe and Dropbox demonstrate that technical founding teams can achieve massive success without a traditional business co-founder. This track record suggests that the 'one business person + one tech person = startup win' formula is not a guaranteed or essential path to success.

Technical founders solving their own problems

When a technical founder is building a product to solve a problem they personally experience, particularly in technical domains like developer tools, the need for a separate business co-founder becomes even less apparent. In such cases, the founder's deep understanding of the technical nuances and the target market's specific pain points often suffices. Their technical background provides them with the insight required not only to build the product but also to effectively communicate its value, engage with potential customers within a technical community, and potentially even handle fundraising. It’s argued that a non-technical business co-founder might not possess the same level of insight or credibility in these highly technical niches.

Interpreting investor feedback on co-founder needs

Dalton Caldwell and Michael Seibel suggest that when investors or advisors recommend a technical founder get a business co-founder, it may not always be a literal prescription for a skill gap. Instead, it could be a delicate way of highlighting a deficiency in that founder's demonstrated willingness or effectiveness in handling crucial business tasks. If a technical founder expresses a strong aversion to sales, marketing, or customer outreach, or if their efforts in these areas are subpar, the advice to seek a business co-founder might be a response to this perceived lack of 'appetite' or execution. The underlying message could be: 'You seem unwilling or unable to do the vital non-coding work; perhaps someone else should.'

Situational benefits of domain expertise, not generic business skills

While generally arguing against the necessity of a business co-founder, the discussion acknowledges that specific domain expertise can be highly beneficial. For instance, if a startup is developing legal software, having a founder with a law degree who understands the legal industry and how to sell to attorneys can be a significant advantage. Similarly, a company targeting doctors and hospitals might benefit from a founder with medical experience. This is distinct from generic business or MBA qualifications; it's about deep, relevant industry knowledge that complements the technical vision. However, even in these cases, the emphasis remains on the individual's willingness to engage and excel, rather than just their credential.

Co-founder necessity for emotional and logistical support

Beyond specific skill sets, the fundamental argument for having a co-founder, regardless of their background, is the sheer difficulty and demanding nature of the startup journey. The process is incredibly challenging, and having another person to navigate it with provides crucial emotional support. This isn't about needing someone to teach you business skills they learned in school, but rather about shared experience, accountability, and a partner to face the inevitable hardships. The presence of a co-founder can make the arduous path of building a company more manageable and less isolating.

Mentioned in This Episode

●Companies

●Organizations

Common Questions

No, not all startups absolutely require a business co-founder. While many tasks outside of coding need to be done, a technical founder often has the general intelligence to handle them. The key is having someone on the founding team with the 'appetite' to do these tasks well.

Topics

Mindset & Self-Improvement Technology & Innovation Business & Entrepreneurship Startup Strategy Business Development Startup Founding Founder Psychology Co-founder Dynamics Technical Founders

Mentioned in this video

Companies

Microsoft

Mentioned as another example of a valuable company that started with two technical founders, supporting the argument that a business co-founder is not a strict requirement.

Google

Cited as an example of a highly valuable company founded by two technical founders, suggesting that a dedicated business co-founder is not always essential.

NVIDIA

A company founded entirely by technical engineers, highlighting that a business co-founder isn't always necessary, especially when solving a technical problem.

Dropbox

Presented as another example from the YC portfolio, founded by technical individuals, fitting the pattern of companies that may not have required a dedicated business co-founder.

Facebook

Acknowledged as a complex case regarding co-founder roles, but Zuckerberg is identified as a technical founder, fitting the pattern of technically founded successful companies.

Stripe

Cited as a prominent example from the YC portfolio that was founded by technical individuals, supporting the idea that a business co-founder is not essential for success.

Organizations

Mentioned in the context of its portfolio companies like Stripe and Dropbox, which are often technically founded, reinforcing the theme that business co-founders are not always necessary.