Loading...
Answers
MenuIs it OK not to have CTO co-founder?
We are a marketplace for freelance developers codingninjas.co. In the beginning we've managed to do an MVP without a developer in a team. We've tested, pivoted few times and managed to get to a solution we want to scale. And some revenue...
Is it OK to stay without CTO co-founder and just to hire one?
Answers
In my last two start ups I have invested heavier into my team than i have in the past and it has paid off big.
Hiring an expert in their position has proven to be one of my most successful and stress free action in business. I will add this to my best practices.
If you want to learn more about what I've learned and some resources on where to look, schedule a call now while my rates are discounted for the next 24 hours.
If your product or service considers technology as a competitive advantage compared to other marketplaces , yes it is better to have a CTO who can leverage technology to build capabilities. E.g if you are buyer-seller matching is based on machine learning backed algorithms, you need to retain the tech guy. Does not mean he/she has to be a CTO. You could use equity power too.
If you business is just another market place and the your execution power is the differentiation, then you could live with a agency/freelance company
My co-founder and I are not programmers. I have a design/marketing background and he has a business/sales background.
We hired a skilled developer to work on the product and after he proved himself and we were approaching PM-fit we promoted him to CTO and gave vested stock options.
Some candidates may want the title right away, or stock options right away, but in any case you don't *need* a CTO co-founder as long as you have a very good lead developer hired.
Any skilled, experienced programmer who believes in what they're building will treat the product like their baby, give them the title and mentorship to grow along with the company and you can do well without a technical co-founder.
Based on what I have been observing in a number of cases, generally speaking, it really depends on what the startup is doing or proposing to do.
When the required technologies/competences can be easily found in the market, it is highly possible to survive without CTOs and/or co-founders without specific experience/competence. When the new Technologies are being developed as part of the activity of the startup than it is highly recommended to involve people with specific experience/competence (and vision, enthusiasm, capacity to integrate new solutions, etc...), since the earliest stages of development.
In both cases it is highly necessary to invest time and attention in the careful definition of requirements and specifications for the work that (external) development teams will be asked to implement.... this means that if no CTO at least someone with a clear functional view must be present (internally).
In your specific case, I suppose that to be really original creating a "marketplace for freelance developers" you really need to involve asap very skilled and very creative developers who, at same time, have the capacity to specifiy and describe their "dreaming marketplace". whether they need to be co-founders or not is largely a matter of "relationships" and "sharing of risk"...
If the answer to the following 3 questions is "yes", you should get a CTO. If answered "no" to at least 2 of them, you could probably manage with a freelancer or part time employee.
1. Is there a lot of (technological) work needed (the "Work")?
2. Is the Work ongoing (for at least 1 year)?
3. Do you need someone with a unique talent to do the Work (versus the fact that many programmers can do such work)?
Despite the above, if you're looking to raise capital (with Venture Capital firms), you should consider getting a CTO co-founder or full time employee as VC's are reluctant to fund startups/ventures that don't have a CTO as part of the team.
If you do decide to take on a CTO, make sure that you use a reverse-vesting mechanism (there's information on this online but I'm happy to help).
I've successfully helped over 300 entrepreneurs and I'd be happy to help you as well. Good luck
Related Questions
-
How to deal with co-founders that aren't pulling their weight?
I feel your pain — I've been there several times in a couple of my companies. Each situation ended up being unique, and had to be handled differently. I think there are a few things to consider before you make your decision: -- 1. What is in your cofounder's way? Is you cofounder being held up by a lack of clarity? Lack of motivation? Lack of autonomy? One of my past cofounders was very good at getting the job done, but didn't naturally have the skill to lay out tasks in a manageable way. To get around this, I worked with the whole team (4 people) to write up process documentation that removed the need to "figure out what to do next" that was tripping up this cofounder. -- 2. What job was your cofounder brought on to complete? And is it being completed? One of my companies brought on a cofounder simply to give us a marketing platform — he had a huge online audience — but he did nothing else. At first, this caused tension; once we had specifically laid out who was on the team and for what purpose, it was easier to identify where responsibilities lay. -- 3. Is your cofounder capable of doing the job? One of the more painful ordeals I've gone through in business is bringing on a good friend, then realizing that — despite his talent and intelligence — he just wasn't able to perform the job I'd hired him for. His skills were better suited for a different job: he needs hands-on management; he works better with repetitive tasks that don't require big-picture thinking; he lacks assertiveness and confidence, which were critical for the management-level role he'd been hired to do. After I tried to clear everything in his way, it became clear the company couldn't survive if he remained on the team. I had to lay him off. -- 4. Do you just simply not like the way this cofounder works? In one of my startups, there was a cofounder who I didn't know all that well, but he had amazing industry contacts and domain knowledge. However, once we started working together it became clear that we had VERY different working styles. He drove me completely nuts with (what seemed to me to be) a very ADHD-style of planning, with projects starting and being dropped and then coming out of nowhere with a call at 21:00 to discuss something critical that would be forgotten tomorrow. I'm sure I drove him nuts, too. So eventually we ended up selling that company — it was that or shutter it — because we knew there wasn't a chance we'd be successful if we continued as we were. -- Working with other people is tricky in general. Our instinct is to assume that we're the best workers on the planet and everyone else is incompetent, an idiot, a slacker, or all of the above. Usually it's a combination of an organizational-level lack of clarity, poor communication, no processes, and (sometimes) plain ol' we-don't-see-eye-to-eye-on-things-ness. Hopefully that helps. Feel free to get in touch if you'd like to hear specifics on my situations, or if you'd like any help devising a strategy for resolving your cofounder trouble. Good luck!JL
-
In a startup with a globally-spread remote team, does it still make sense to incorporate in U.S./Delaware vs. somewhere overseas?
Delaware C-Corp I usually Delaware is the best choice for any startup looking for fundraising with a US focus. However, if you are a remote and global team, an overseas or foreign corporation or US tax purposes might make sense. You'd have to talk to an advisor who can dive into your situation, but it would be more difficult for the US owner come tax time, as he'd likely have to file form 5471 to the IRS for any controlled foreign corporation, and form 90-22.1 for any foreign bank accounts. There are a lot of other concerns I didn't hear you raise that entrepreneurs usually have and ask me about, namely banking and merchant accounts/ payment processors. In terms of accepting online payments, any US corporation or LLC is far and away the best option for a company. It's difficult to suggest without knowing more about the company but you might explore Delaware, Wyoming, Hong Kong and other offshore jurisdictions for your legal entity. Each tend to have positives and negatives and there is no one size fits all solution. I do write about issues of incorporation quite regularly on my website FlagTheory.com - so you can read those articles for free, or we can schedule a call - Clarity.fm/incorporation when you have specific questions. Thank you and hope this was helpful!EJ
-
Need some advice on how to build a team, and determining what kind of talent I need?
A great team looks like this - 2 full stack engineers. They can manage servers, security, build features and code front end JS/interactions. - 1 visual designer focused on product, information architecture, UX and flows. - 1 front end developer who can take designs and built out killer interactions and can wireup any back end code to the UI The CEO can manage product + customer development and everyone on the team does support. That's 5 people and can accomplish a lot!DM
-
Where do I find a co-founder to join my team?
1) Look up local universities and email the chairperson of whichever programs relate to the type of cofounder you need (i.e. electrical engineering, marketing, etc.). You could even possibly go there in person and put up a sign on a bulletin board. 2) There may be relevant Meetups in your area, go there and network with attendees (www.meetup.com). 3) If you're specifically looking for engineers, look up local 'hacker' / maker spaces that may exist in your area (see here: https://wiki.hackerspaces.org/List_of_Hacker_Spaces). Send me a message if you want to discuss more options and how to access them, all the best, LeeLV
-
What is your advice for building a team of like-minded individuals to help start your business?
I'm a feelance CFO and I work actively with early stage companies. I've been at this for almost 30 years. Some of my current and recent clients wrestle actively with this very questions. My advice is to have the tough conversations right up front, early in the team building process. This usually consists of answering questions like, "who's in charge and what does that really mean," "who gets how much of the company and when and in exchange for what," "what are you, you and you really bringing to the table in terms of skills and cash," and "who is really in a life situation that will allow them to sustain their commitment to the business?" Any team that can get through these questions can get through the trials of surviving startup. I'm happy to talk with you directly about these issues and, in particular, to help look at them through a strategic financial planning lens.HD
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.