July 22nd, 2024

Why technical cofounders reject you

The article explains why technical co-founders may decline partnership offers due to unrealistic founder requirements. It emphasizes execution over ideas, mutual risk-taking, and attracting co-founders with potential and independence.

Read original articleLink Icon
Why technical cofounders reject you

The article discusses reasons why technical co-founders might reject partnership offers. It highlights unrealistic requirements set by some founders, emphasizing the importance of execution over unique ideas. The author stresses the need for business founders to bring value to the table, understand the risk imbalance, and manage their expectations realistically. Additionally, it addresses the misconception around bootstrapping and the necessity for business founders to take equal risks as technical counterparts. The article advises on how to attract a technical co-founder by demonstrating the potential for success and personal capability to drive the project forward independently. It concludes by emphasizing the competitive landscape for technical talent and the need for founders to offer compelling reasons for collaboration.

Related

Link Icon 19 comments
By @iamleppert - 3 months
"I might be biased but most cofounders who want to bootstrap was because they were afraid to do actual work. Raising funding requires hard rejections which they want to avoid as much as possible."

This. I worked with a guy who tried to raise money, couldn't take all the rejections, never prepared for any of his meetings (didn't remember the names of people he met), and didn't understand the market he was operating in or what his product should or would do. After that "failed", he "pivoted" (his words) to "bootstrapping" which actually meant just not paying people. In his words, we would be paid when the product had sales.

After people stopped showing up for work, he shifted the blame to the economy and "investor headwinds". Then he "pivoted" again to "crowdfunding". "Move fast and break stuff" he'd say when he would visit me a few times a week in the office.

Eventually, at one of his visits he found that I wasn't there anymore either. This was followed by threatening phone calls and emails from his laywer/father.

This guy had a big career at Fortune 500 and 100 companies and big tech before trying to start his own company. Guess the same skills that make one successful in corporate america don't translate into starting a real business.

By @mooreds - 3 months
I wrote something similar in 2021 [0].

Lots of great opinion in the original piece. It's hard to pick just one piece of advice to amplify, but if you made me pick just one, it is that the risks are asymmetrical for each co-founder. The tech work is front-loaded because it is difficult to sell before something is built. I know at least one tech friend who slaved over a product that the other co-founders couldn't (or wouldn't) sell after it was built.

How can you avoid this as a non-tech co-founder? There's lots you can do to prove out the market:

* talk to potential customers

* build a no-code solution that solves part of the problem

* take people's money for a pre-sale

Yes, this is work, but so is the rest of a startup. De-risk the tech co-founder's role and you'll have a lot more success.

0: https://www.mooreds.com/wordpress/archives/3445

By @softfalcon - 3 months
It all comes down to "doing the work"... which is the key to "executing on the idea".

There are countless folks who like to have ideas and imagine a dream scenario where other people labour to bring those ideas to life. I meet them regularly, some of them were at one point my friends.

Folks will always try and talk their way into a free lunch. Make sure you're not the one paying for it.

By @zug_zug - 3 months
shrug I meet that checklist, but of course I'd only be interested in a non-technical cofounder who passed a similarly comprehensive checklist (e.g. proven career in sales, major connections with potential clients, strong understanding of market position and competitors, already has created mockups that people are interested in purchasing).
By @blueyes - 3 months
The irony here is that business co-founders actually have at their disposal more and better tools to test a business idea without need of a technical co-founder than ever before in history. The smart ones always sold before they built, maybe with a landing page. Now they can also test simple apps while having essentially no coding skills themselves. Obv this does not work in hardware and multiple other domains where complexity grows. But the business co-founders asking for technical co-founders for an app are actually signalling that they are either poorly informed or simply don't want to build with the skills they already have.
By @ldjkfkdsjnv - 3 months
I have a suspicion that hacker news down ranks articles like this. Its dangerous for their business model. And nothing could be more true than:

"The business cofounder essentially gets more leverage the more work the technical cofounder does -- because now there is sunk-cost and a psychological shackle. The technical cofounder just wants to be done with the build-out so the business can proceed and make money -- but the business cofounder has every incentive to expand the MVP more and more since they are putting in no effort (possibly have not quit their job either) and wants more and more before the system can be sold."

Its a very good deal for non technical cofounders! And usually they end up running more of the business than the tech guy. The tech guy is stuck in front of a computer banging out code. The non technical cofounder is out wining and dining customers, doing "partnerships", etc. They become the face of the business. Which does matter, and it takes a psychological toll on you, watching them essentially take your hard work, and use it.

By @mihaic - 3 months
Great article and I strongly agree with 95% of it. The only thing I'd like to add nuance though is on the "ideas are worthless" rehash. I think the pendulum has struck a bit too far, and at some point actually there's more merit than normally acknowledged to deep thinking about all the implications of an idea. Take this advice only after you can execute though.
By @smarri - 3 months
I came to the conclusion, personally, that a non technical co-founder should spend the time to become technical. I'm sure it's not needed in all cases, but for me, it was the right path.
By @neilv - 3 months
Some good advice, but be careful with how the final word will be interpreted:

> You should prove to the other party that this is happening and the train is departing. They can have a ticket to the ride if they join you right now.

"Prove" will be interpreted as "persuade", so...

Sounds like advising the hypothetical startup CEO that they don't need the technical co-founder, that it's all about the CEO, that even the rest of the founding team is just disposable commodities, riding the CEO's glorious coattails. (This kind of thinking isn't unusual.)

Or advising the startup CEO to be a BS-ing salesperson towards their own co-founders, considering that the CEO's magical success is actually far from certain, but you're advising them to fake that till they make that. Even fake it towards the people with whom it should be in the CEO's interest to be most honest, so they can solve problems together effectively. Unless the CEO thinks those people would never deal with the CEO, if they knew the truth of what they actually brought to the table. (This also happens.)

But if you just want an untrustworthy technical cofounder, then the above interpretations are fine, since maybe being pathological is good self-defense, in that particular team.

By @jatins - 3 months
Well written and relatable.

I think Twitter/X has done and continues to do a lot of damage to startup ecosystem. You often meet non-technical folks slinging around buzz words like "let's think from first principles" or "gotta sell shovels" without actually having on ground experience of building or selling things because some AI influencer had a recent thread on it.

By @JohnBrookz - 3 months
I was a non technical founder idealist. Then my friends told me I lacked the skills to be a business and a technical founder.

It was honest and useful. I dropped out of nursing school, went to business school and taught myself how to write code. I worked at some F500 companies for a few years (still there sadly).

But last week I launched my first product with a cofounder and it’s probably the best one on the market. My “technical founder” is much more technical than me but I’ve filled out a little of both gaps.

If you’re a non technical founder I can’t take you seriously. Unless you’re a walking pile of cash with a top hat, no sane technical founder would risk it.

By @jacknews - 3 months
It's easy to dismiss ideas as worthless etc if you never have any good ones. Of course anything obvious like 'uber for X' is worthless.

And sure, success is 90% perspiration, but that's also wasted without the matching 10% inspiration.

As for the argument that people would resent 20% 'idea equity' - they already give up much more than that to 'founder equity'. Did Bezos build Amazon? Or Musk Space-X, Tesla etc? They own those companies, and orchestrate them to some extent, but the workers, hired managers, etc, actually built them. Yet the vast majority of the spoils still go to the owner/founder.

By @jmathai - 3 months
If you are actually good at sales then you’ll have no problems getting a technical cofounder.

The imbalance in my experience is that there are more technical cofounders out there than great sales people looking to start a business.

A non-technical cofounder is not just someone with an MBA who has ideas. But those will struggle convincing someone they should give them sweat equity for building product.

By @masherm - 3 months
No good technical cofounder would work for free - why would anyone expect them to when they get paid 300k+ working at a FAANG?
By @jl2718 - 3 months
Mostly because there is a MASSIVE oversupply of people that can’t and won’t do anything useful, and insist that their technical incompetence makes them uniquely qualified to be in charge of everybody else that is doing the work.

But at some point, that’s exactly how it has to work out, because CEO is a poorly-understood role that is only discoverable through natural selection among legions of technical bozos. One of those crazy idiots can make you rational experts a billionaire, but most of them will waste your time, and you probably can’t tell the difference.

By @karmakaze - 3 months
I don't find that list so off-putting. The only ones I would reject/change:

- has business acumen -- they're looking for a technical co-founder, right?

- works for free -- for a written share of the company, not free

By @AndrewKemendo - 3 months
I’m hopefully in the final “nerd meets money” job I’ll ever have and my argument is going to be that no technical person should ever take a deal from a non-technical person. The reality, however, is that most of us are not in financial positions to be able to refuse it. I think we need to collectively figure out how to support each other so we can tell capitalist narcissists to go away.

I’ve been in every possible part of these deals and In the absolute best possible case you are going to betray your own technical vision and get 1/1000th of the value that you create as output. That’s absolutely best case.

Non-technical work, fundraising, sales etc is all fictional bulshit in hopes of managing the greater fool trick with the public market being the ultimate fool. Psychopathic wannabe dictators play the role of intermediary between capital and labor such that they are on one hand trying to pretend that they give a shit about their employees and their welfare and on the other hand tell their investors how much they’re gonna fuck everybody over in language that is specifically crafted to not sound like that exactly what is happening - with a massive legal apparatus that is built to prioritize the rights of capital over labor in every single case.

The only reason that works is because structurally in the world that we live in today, all of the people with money generally have no functional skills and so they need to coopt people with skills, with unfair contracts, in order to do what they want to do.

Capitalists need us technologists and technical labor, who know how to build an implement stuff in order to make their money. If they knew how to make stuff, they wouldn’t be asking for a “technical cofounder”

If all that somebody does is bring money to the table then you can bet that that’s all they’re going to be able to bring. And you can also expect that they’re going to demand the majority of the value that is created by you because of the fact of the way finance and money works in the world.

If that’s the life you wanna lead, with the idea that you too can be a lazy capitalist stealing the value from others, then as a technologist I’m not sure what to tell you.

I’ve yet to encounter a technical person with any care for their craft who had a overall positive experience selling out to capitalists.

I think WhatsApp is the perfect example here in that it was intended to be a tool for freedom. Now a multi billion dollar corporation spies on their multibillion users for money.