Should I hire a CTO or a dev shop?

My answer is always: it depends. So I want to outline some of the challenges and drawbacks here.

When to Hire a CTO

In almost every scenario I recommend startups find a technical co-founder who can spend all of their time building and managing their software. I make this recommendation for a few reasons:

  1. It’s important to have someone who can speak about technical assets.
  2. Having someone from the get-go to retain the technical knowledge is incredibly important.
  3. They add value to the team.
  4. They add a lot of credibility when pitching investors.
  5. In-house engineers produce higher quality code (in general, not always the case).

Although they can be hard to find, technical co-founders can make or break software businesses.

When to Go The Dev Shop Route

The only scenario in which I actually recommend working with a dev shop is when you already have someone technical on your team. In these instances you have some leverage that can ensure quality of code. When engineers at a dev shop know that you have in-house engineering talent that will be conducting code review they feel pressure to produce quality code.

On the contrary, code quality will suffer if they know that you do not have any in-house engineers. Likewise, they know that the project will no longer be their responsibility in a few months time. Why does this matter? Code quality is very important because without quality code:

  1. Routine maintenance becomes difficult and costly.
  2. Changes and improvements are more time consuming.
  3. Down the road when your business is growing your software most likely won’t scale to support your needs.

If you have an engineer who can work with the dev shop and monitor their work, then working with a dev shop is a great way to complement your in-house resources so that you can build and iterate faster.

An Example

I recently brought on an offshore engineer. Before we kicked off the engagement I was incredibly skeptical and had very low expectations. However, with proper product management and daily code reviews we have seen incredible results at less than 1/10th of the cost of working with our own engineers.

TLDR
Make sure you have engineering talent and if you need more resources temporarily or cost effectively then consider complementing your team with a dev shop.

Was this article helpful?
0 out of 0 found this helpful


      This website and all posts and content are intended for educational purposes only and for no other purposes. This website does not and is not intended to provide legal, financial or tax related advice. Although we take great care to make sure that all of our information is accurate and useful for it intended educational purposes, if you have a specific issue for which you need actionable advice, please come to the Martin Trust Center in person to speak to one of our Entrepreneurs in Residence (EIR) or consult a licensed attorney or other professional. Despite the backgrounds and qualifications of our staff, mentors, lecturers, authors, EIRs and speakers no attorney-client, advisor, or other confidential/privileged relationship exists or will be formed between you and the Martin Trust Center or the Massachusetts Institute of Technology. Under no circumstances should any content be relied upon in making any decisions that could have any financial or legal impact(s).
Have more questions? Submit a request

Comments

Powered by Zendesk