Hackernoon logoTechnically Speaking, Not Having a Technical Cofounder Is Not the End of the World by@rtslabs

Technically Speaking, Not Having a Technical Cofounder Is Not the End of the World

Ken Green Hacker Noon profile picture

Ken Green

Technically Speaking, Not Having a Technical Cofounder Is Not the End of the World

Photo credit: Tumisu/Pixabay

So you have an idea.

A great tech idea!

An idea that keeps you up all night working through the who, what, where, when, and how.

Sadly, you don’t know how to code, and all the developers you know are either working for someone else or are working on their own projects. Or they’re prohibitively expensive, and you lack startup funds.

This is a conundrum many entrepreneurs (or wantrepreneurs) face when they’ve stumbled upon an idea for a new app or new software.

So what you do? Are investors going to take you seriously without a technical cofounder? Do you really want to found a company on your own? Which of these paths do you choose to go down?

  1. Spend time and energy trying to recruit a technical cofounder.
  2. Learn to code and do it yourself.
  3. Hire a team that knows how to code and can build your product.
  4. Outsource the work and focus on building the business.

These are all viable options, and the right one is going to depend on your background, your product, and your resources. While it might be hard at first to figure out which option is going to be best for you, the good news is that not having a technical cofounder is not the end of the world. Because as you can see, you do have options.

Don’t waste time and energy trying to recruit a technical cofounder

Here’s the thing about recruiting a business partner. You wouldn’t marry someone after a first or even a second date. So why would you recruit a business partner that way? While being a sole founder is challenging, if you’re going to start a business with someone, it should be with someone you’ve had some sort of life experience with.

It’s more than not really knowing the person though. There are several problems with trying to recruit a technical cofounder:

  1. How do you recruit someone to help lead your company in an area in which you lack skills when you don’t know enough to vet their skill set? This person is going to be your cofounder, making the vetting process that much more risky.
  2. A recruited cofounder has less of an ideological commitment to the startup because the two of you didn’t come up with the idea together. It’s not their idea or a shared idea — it’s yours. This makes them more of a hired gun with less buy-in — which means they’re also less likely to take a decrease in pay for the good of the company when the chips are down.
  3. Have you heard of this scenario before? Idea guy/gal convinces coder to leave their job behind and come work for their amazing startup. (If you’re a tech person, it’s likely already happened to you.) The problem is that it can be hard to woo someone with the skills you’re looking for — if they’re that good. Most talented developers are not going to risk everything to work with you. They most likely have offers or already work for big companies that pay well, have nap rooms, and offer benefits. That’s hard to compete with.
  4. “Developer” does not necessarily mean “cofounder”. Just because a developer has talent and can build what you need doesn’t mean this person is a good candidate to be your cofounder.
  5. It takes a lot of time and energy to recruit a cofounder,and there’s no guarantee you’ll find one. You could be using that time and energy to move forward with your idea instead.

Keep moving

You still don’t have a technical cofounder, but you’ve still got a great idea. Here’s something else to consider: The best app in the world is worthless if you don’t build a marketing strategy for taking it to market and making sales. While you don’t have anyone to build your product, you should be pushing as far as you can with what you do have.

Start by getting your vision down on paper. Use a tool like Lean Canvas, and map out your value proposition and potential customer profiles. The more you understand the problem you are solving and the people you want to reach, the better.

Once you’ve got your lean canvas and value propositions, start interviewing potential customers to test your idea. This is what it takes to be a startup. The technical stuff comes later. If you start building a product before you really understand your customer’s needs, you are going to waste a lot of time building something that may not be the right solution.

Outsource vs. hire

Here’s the big question: who is going to build your product? The challenge with hiring a developer or team of developers is that, like finding a technical cofounder, it’s going to be hard to properly vet the right person and hard to convince talented developers to come work for you. Another challenge with hiring is that the recruiting and training process can be arduous. While it’s important to spend time building that thing you want to build, as a founder there are so many other things you need to focus on.

Outsourcing the work to an agency may seem like an expensive option, but it could actually be your best option. Think about it. There’s no recruiting, training, or managing of employees involved. When you work with an agency that has experience doing the work you want to have done, there’s less to manage. Yes, it’s going to cost you, but it holds you accountable to take your business serious and it ensures you have time to focus on the other parts of your business.

Another thing to think about is that as expensive as hiring an agency might be, could it still be financially advantageous? The money you pay an agency is a pure write-off — a business expense. That’s going to be cheaper than paying benefits and taxes on employees in some cases, depending on the amount of work you need to have done.

Alex Turnbull, founder of Groove HQ, outsourced the building of his app and tells it like this: “I didn’t have to recruit. I didn’t have to train any employees. And while I worked very closely with the MojoTech team, I didn’t have to manage anyone directly; I could focus on what was most important to me: contributing directly to the creation of the product.”

One downside to outsourcing is that when you do hire a team of developers, it’s harder to build up the team spirit and culture that would have been built creating the first lines of code and launching the product. There’s something to be said for the ownership your team feels when they build the product from day one.

Not having a developer on your team who was there for the build can also be challenging, as it could take time searching through someone else’s code to find bugs and fix problems.

Start with a small ship

Whether you outsource or hire, one thing’s for sure: you need to start with a small ship and make sure it floats before you build a bigger ship. It’s very important to start with an MVP (minimal viable product), and then test and build from there. Taking an agile approach to building your product is the best way to ensure you keep costs low and build something the market will love.

You should also take a research-driven approach to growing. Make sure you have a strong support person or team who knows how to collect feedback, prioritize feature requests and bug reports, and ultimately learn about your users’ wants and needs.

Learn to code

You don’t need to be the next Mark Zuckerberg, but you should have some grasp of how coding and software development work, including some of the language your developers are coding in. At some point, you are going to need to hire developers or choose an agency to build your product (or *gasp* build your MVP on your own). As a sole founder, all the decisions start and stop with you. You need to know a little more than what you know now, so you make sound decisions and communicate with and manage your team in the most effective way possible.

Learning to code is not out of the realm of possibilities. There are free programs like Codecademy that can get you where you need to be.

Appreciate yourself and what you bring to the table

Finally, don’t take the skills you have for granted. Just because you can’t code and don’t have a technical cofounder doesn’t mean you’re doomed. You had the idea. Do the research, do the work, make the contacts, and nail your business development strategy. While it’s nice to have a cofounder, you know what’s even nicer? Owning 100% of your company.

We’ll leave you with this important nugget of advice from Alex Turnbull: “But the most important thing you can do, no matter which approach you take, is start.

Hacker Noon is how hackers start their afternoons. We’re a part of the @AMIfamily. We are now accepting submissions and happy to discuss advertising &sponsorship opportunities.
To learn more, read our about page, like/message us on Facebook, or simply, tweet/DM @HackerNoon.
If you enjoyed this story, we recommend reading our latest tech stories and trending tech stories. Until next time, don’t take the realities of the world for granted!


Join Hacker Noon

Create your free account to unlock your custom reading experience.