Live data from Hacker News

You do need a technical co-founder [video]

ycombinator.com

371–380 of 381 posts

Re: You do need a technical co-founder [video]

#371
post #25

Earlier quoted context omitted.

Your cofounder in a new startup isn't your manager.

The point is you can act like whatever you want, and so can everybody else, and often that means they'll be idiots, often in consequential ways. That's life.

The point is if you act like an employee, you will be treated as an employee.

Starting a company is not easy. If you stand around and only do tech, then you're not a founder, you are an employee. If you have to ask "what needs to be done next?" you are not a founder, you are an employee.

If you call someone your manager, then you are an employee.

Re: You do need a technical co-founder [video]

#372

Earlier quoted context omitted.

>> 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 al…

https://news.ycombinator.com/item?id=14070135 Prior discussion on 80 hours a week.

I 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.

Re: You do need a technical co-founder [video]

#373
post #342

Earlier quoted context omitted.

I have substantially less exposure to this space than you seem to, but even when trying to start projects with friends, this holds true. So often, I get pitched by pals who think the idea is what they've done, and at that point, it's up to me to "code up." What I would love to hear is, "I've been talking with these three businesses already, and they seem interested." or even, "I'm really worried about the sales and m…

How do you even find these people? I somehow managed to surround myself with highly technical individuals who are only interested climbing a corporate ladder, not any kind of serious entrepreneurship.

"Business co-founders" are usually finding me (not the other way around.) They are approaching me on linked in cold, or on linked in referred thru someone, or at Meetups (pre-pandemic) or thru community organizations.

Re: You do need a technical co-founder [video]

#374
I 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.

Re: You do need a technical co-founder [video]

#375

Even 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 nontech…

May I ask what a non-technical founder should look for in a technical co-founder? I have two customers for slightly different businesses. The deals are made, I am building MVP's myself and JVing with established tech companies to get products to market. I have a supply chain with a 30% cost advantage with customers. and I have a hardware software system that significantly improves hire businesses that has customers a…

> May I ask what a non-technical founder should look for in a technical co-founder?

Breadth of expertise, ability to learn quickly, open minded when it comes to technology. Loves to work with clients and solve their problems more than they love the tech.

The B2B and PostGIS part caught my eye. I'm technical, but leading both the business and the technical sides of my spatial analytics company. I would be happy to share at least some of my technical knowledge. From infrastructure, DevOps, through database and data layer, and all the way to the frontend - I've been doing this for years and there could be a thing or two that may be useful to you.

On the other hand, I can always do better when it comes to B2B sales, so I am looking to learn too. Maybe we can have a chat sometimes.

Would like to connect?

Re: You do need a technical co-founder [video]

#376
post #184

As 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 le…

>> 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.

It 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.

Re: You do need a technical co-founder [video]

#377

I'd argue the other side of the this: you don't need a non technical cofounder.

Agreed, I think it depends on the technical complexity of the product & model.

Declaring it an absolute requirement feels a bit like an exclusive club without real merit or consideration. I say this as a former exec at a YC company founded by a pair of eng degrees that couldn't build a thing (not even a prototype).

Re: You do need a technical co-founder [video]

#378
post #238
post #183

Earlier quoted context omitted.

Honestly as a technical guy: You come off as greedy. As a technical founder, I face the EXACT same risks. What if the business guy can't drum up money? What if he can't sell the damn pen. Most companies fail, the strongest firms will have strong business and technical people. If you want to stand on one leg. Go for it. You'll piss your money away overseas. When you need someone to help you get across that line... the…

I just mitigate as much risk as I can, as early as I can, and it's worked so far. Tech is littered with hundreds of companies that died because of personality conflicts - which can be readily mitigated with an MSA and SOW. As I note in my original comment, my approach can absolutely be utilized by technical founders.

No contract can save you from what you don't know, and don't understand.

Different points of view, if they can stay respectful. Can be a great strength.

I see the world in terms of risk. If X will help me derisk something. Even if it isn't totally EV+ it can be a good play, because risk of ruin is real. Especially with large amounts of money, and small numbers of trials.

25% less to have a 10% better chance at making 75m vs 100m? Probably worth it a that level. Because 75m or 100m is life changing money for 99.99% of people at least. The amount won't matter as much as your chance of getting to it.

Re: You do need a technical co-founder [video]

#379

Earlier quoted context omitted.

>> 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. I get calls weekly from people seeking technical co-founders. The biggest thing most CTO candidates dont realize is the power they have -- unless the "business co-founder" is actually bringing something to the table. I'd LOVE…

The worst example of this is the "founding engineer" role. I get a lot of these offers, and it just feels like a scam every single time. Founders often sell that as some incredible opportunity, zero-to-one, full codebase ownership, huge scope, no eng team, etc, etc. All of that for an amazing 1% equity. So yeah, the expectation is that I will build the whole project, drive product decisions, help hiring the rest of t…

It's the same with YC: at the end of the day even the founders will end up owning only a small fraction of the company. The difference is that the VCs dilute you over time, not up front, to get the maximum amount of work out of you.

Re: You do need a technical co-founder [video]

#380
post #4

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. 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…

Great comment! I am dropping that as a quote on my blog as others need to read this.
Post reply on HN