Do I need a technical co-founder?
I'm starting up, and have started the process of talking to users. I'm a product-minded designer who and I'm confident of creating what people want.
I can code really shoddily, at least getting to a basic MVP with the help of ChatGPT. I take too much time to build, however, and could use the help of someone better than me at this. Of course, after a basic MVP my talents fail.
My question is, should I start looking for a technical co-founder or learn more advanced coding myself? If I do need to look for one, what point would be most suited for their entry? Right now I'm assuming after launching a pilot, but is that too late?
Also, I have not worked in a startup for a while, and have no engineers in my network that I can reach out to. How do I find engineers who are leaders and willing to work with me?
18 comments
[ 3.2 ms ] story [ 49.7 ms ] threadIdeally you need a technical co-founder. If you are starting a software company, at least 1 founder needs to be really good at creating software with actual experience.
Having said that, don't settle for anyone and keep trying. You CAN build an MVP without a technical co-founder (some yourself or with freelancers etc if you can afford it) and get 10 paying customers. But you need one if you want to build a real software company and not just a side project with a few paying customers.
"How do I find engineers who are leaders and willing to work with me"
Show. Don't tell. Get an MVP done somehow and then get 10 paying customers. Heck, get 5. Show that you are the real deal and mean business. Then you have to talk about it everywhere. Think of it as sales. You have to sell yourself/your vision/your company to someone who may have similar interests. But any good experience technical person won't join you unless you do these things first.
There are a few platforms you can use to find a potential technical cofounder. There's obviously YC's "Cofounder Matching", and then there's a newer service (might be invite only?) called Co-foundermatch.ai. I've had some success with both but found my current role through YC's co-founder matching.
Good luck :)
If tech is just a tool, one of many to support your core business - then no, you don’t require a high expertise in the core team.
All no code startsup success stories I heard are good examples of businesses without core technical advantage. Many of them are basically spreadsheets with some bells and whistles.
https://www.youtube.com/watch?v=ZpKu2wvquWg&list=PLQ-uHSnFig...
> I can code really shoddily, at least getting to a basic MVP with the help of ChatGPT.
Then launch your MVP solo, IMO. Coding is still a superpower right now, and it's a great secondary skill for any entrepreneur--I recommend you continue learning. But even aside from leveling up, launch your MVP solo. It lets you retain full control over direction, and validates the idea.
> If I do need to look for one, what point would be most suited for their entry?
After you validate the business (with paying customers). And when you cannot move the business forward alone.
> is that too late?
No.
> How do I find engineers who are leaders and willing to work with me?
The answer to this is also to validate the idea. Or build it and show it to them. Let people attach to your idea. You're also important, but the business should be the star, not you. Have your business making money, so you can pay these people good salaries.
Sure you can co-found. Sure you can go it alone. Both approaches can work, both can fail.
From my perspective, I've always had co-founders. I've found that having to convince a partner of an idea is a good way to filter out crap ideas.
Whichever way you go, employee or co-owner, it's important to find people uou can listen to, and that will listen to you. Sometimes you'll be right, sometimes they'll be right.
"How do I find engineers who are leaders and willing to work with me?"
The most efficient I've seen is just blogging. Speak about the problem from your heart. Social media works too including Instagram and TikTok.
For one thing, tech people are just flooded with offers from non-tech cofounders. So we see a lot of people who have ideas and then lose interest after the prototype is complete. After the tech cofounder spends a month or so full time building it. It helps to actually care about the problem and know enough about it for a long time.
> he was technical enough to alter and change and add to other technical designs
He could do more too.
> https://duckduckgo.com/?q=steve+jobs+atari
> Jobs was hired as Atari employee #40, as a technician fixing up and tweaking circuit board designs.
> "So, we decided to have a night shift in engineering -- he was the only one in it."
I've come across hundreds of "looking for a technical co-founder" folks; they all typically have an idea that has been done before or are overconfident about their product development skills.
Questions such as "How do we make money?", "Do you have contact with a few initial pilot customers?" etc tend to make them run away.
If you know a good market niche, feel free to send me a message or any other developer; we can generally be very rational and can recognize value very easily.
Are you building a technology company or a non-technology company?