I'm in early stage for my start up. Now that I have the business idea and plan together I'm ready for it to be built. I'm not a techie to build my app and site. So is it better to hire a cofounder/cto to build the app or pay a company to build it. What are pros and cons of each?
Hi Ayan, I went through this same dilemma many years ago (and technically still going through this). I'm breaking down your question into three possibilities:
CTO/Co-Founder - YES, this is 100% the best way to go. The only problem is finding someone with your same vision and drive for the company your building. Note that a freelance developer and CTO/Co-Founder are NOT the same thing. A CTO will be there from beginning to end, will be willing to negotiate his/her price in exchange for equity and you should still consider letting this equity vest over the course of a few years. Don't give someone 10% just to build an app once at a discount, and then disappear. This happened to me.
Freelance Developer - Over the course of my startup I have hired 4 freelance developers. The problem with [some] Freelancers is that not all of them are very forward thinking. They are here to do a project and then bounce. Some even bounce before the project is done (yes, this happened TWICE to me) to chase that next big client. Twice I was left with terrible and incomplete code. Trying to go after them for the remaining project or returning funds was futile. It would have cost more in legal fees than hiring a new developer to finish the code.
Development Firm - This is now the route I'm looking at. While it costs more money, development firms have repetitional risk they're concerned with. They are less likely to drop your project or develop a bad product bc as a company they have a reputation to maintain. These guys don't want a nasty review on Yelp or the Better Business Bureau, etc.
As a rule of thumb, keeping IP and talent in-house is a better strategy for building a long-term growth strategy and reflects positively on your valuation and investment worthiness.
However, many people jump the gun of forming a team and splitting co-founder equity way too early, in my option. To put things in perspective, I've been building, growing, and running startup companies since late 90's, so I've seen it all.
These days, I with every new idea that I take on, I get the team to follow a path of least resistance / maximum growth to achieve certain milestones, which, at a high-level could be outlined like this:
So here you go, first HIRE external experts to get you there faster, then RECRUIT a co-founder / CTO to build, when you know you have a chance.
I've launched about a dozen startups with this method, and dropped about a dozen more after quickly learning they were non-starters.
Hope this helps, and message me if you want details on any of the above.
Hiring a development company is beneficial, I run such app development company Agicent (www.agicent.com) and can try to tell you why:-
1. You get all expertise at once place:- You need to acknowledge that app development ain't a single guy job, you need a designer, a developer (or two) for front end, a backend developer and a supervisor to professionally execute the work.
You get this edge while working with an agency, and not with single guy.
2. A pro App team doesn't need to learn many things since they do it everyday, in fact most of the times we've reusable codes for regular things, it helps in making things cost and time effective.
3. You should be hiring (or partnering with) a CTO even when you are outsourcing work, he is the best guy to manage an team of app developers and can get most out of them and ensure things ain't going wrong. It's not only coding where you need a CTO but across many strategic and tactical decisions related to product development, monetization, marketing and what not. The vision to have a CTO is far expanded than what it looks in the begining.
4. Accountability A legally incorporated app company is hard to ditch you, more so if they are around from sometime. We live on our work, we do it "Full time" and not as a part time gig and would never do anything that makes us look unprofessional so far as we are in senses. :)
5. Easy to scale-up/ plug out You don't need to commit an year's salary to an app company, you build a product, launch, test waters. If success, then continue, else you know what I mean. Easy it is, believe me. Also, you can take professional handover from such company whenever you build your inhouse team (we never mind that I know).
We App development companies exist for a reason, and that's a real one. And yes, we don't ask you to write a review on yelp. :)
Also, its more a of a relationship-vibes based-professional association for such custom developments, its not like dealing with a shop or something. So the more you consider us our team, the more we love you back. Believe me, or ask our customers. :)
Feel free to discuss any further, my skype is sudeepbhatnagar, or e-mail to firstname.lastname@example.org.
You probably need to do both. It's imperative that you have a full-stack developer as a partner (for equity since most likely you can't afford one) to help watch over things. This person will already have a good paying job or his own gig. They will be hard to find. There are more elements to developing than you are probably aware....scripting/outlining the app functions, wireframing, graphics, developing, adding api's, determining your stack, implementing the stack and testing. Finally, you need to publish with the stores and market it....website (another development.) If you can do a lot of this work yourself, you can submit it to a variety of overseas shops (assuming you're in the US.) You can get the work done for 10-25% of the cost in the US. There are inherent problems and barriers going this route....you must be very, very explicit in what you want..notice I exaggerated it to make an important point. If not well thought out, you will be adding and changing things frequently which will up your costs. Be prepared to take twice as long and spend twice as much as you think. This will happen regardless of how exacting you are with your requirements. If fairly accurate, some will quote on a lump sum basis..others are time and materials.
I spent three years and $110,000 developing an app, two websites, two CMS and a database hoping to find someone to run with it. This can be another problem. In my case, we had a few young people that were originally partners but as time went on they lost interest. They needed immediate gratification....obviously an MVP, which we are not. It is still a viable product, but needs a CEO to move it forward.
Should you have additional questions, feel free to call. You can learn from my mistakes. Also, I can refer you to overseas shops with whom I've worked. Skype @ timothy.early1 or email@example.com
You are certainly at a very exciting time for your idea as you work to bring all that planning to life. I’ve certainly seen this debate a lot in the last 10 years as for the first time real, viable, (and in many cases more efficient) alternatives to internal technical hires are available.
A Co-Founder and CTO is certainly an attractive option in some ways. They share the burden of building the company and if chosen correctly can be a valuable asset in planning and building your app and site. However, it should be remembered that all things in the world adhere to the risk-reward paradigm—the higher the risk, the higher the reward OR the lower the risk, the lower the reward. Make no mistake, having a Co-Founder is like being married—you are together for better or worse. I am particularly fortunate to have an amazing Co-Founder but my experience is uncommon. It is risky to vet a Co-Founder for the depth and strength of relationship needed to run a company with you, and certainly this is all the more challenging when you have little time to make the decision. There is also the added risk of ensuring your new CTO is up to the job and truly has the requisite skills. All in all, a very risky move that can pay off but also hints at the majority of startups that ultimately fail because one of the founders wasn’t truly “in it to win it.”
An increasingly popular alternative is to hire a design and development firm to build your app and site for you. This trend has exploded in recent years as companies have realized that for the cost of a good CTO in salary, equity, or both buys a very talented design/dev firm. The wins of hiring a strong firm are many. As professionals, they deliver your app and site to your specifications. Said another way, your dream comes true, not a compromise of it. A good design/dev firm also has a health bench of talent so instead of a single person (as with a CTO), your project benefits from many great minds all with deep experience building and shipping projects. Delivery is also a considerable win here. A CTO with hopefully the full skill set you will need will spend a great deal of time building your app. By comparison, a professional firm will scope the timeline and cost of your app and site at the very beginning. You will have transparency on an actual delivery date which as anyone will tell you in the startup world is huge! Plus, with so many talented folks all tasked to your project I can just about guarantee that your project will be market launch ready in considerably less time.
I’m not really going to touch on freelancers because in the world of design and development, this option is frequently the costliest in time AND money. Generally, freelancers have consistency issues in sticking with a large-scale project like an app and site. And it can easily sink a startup when a freelancer disappears or fails to deliver. Additionally, with harder to define hourly rates coupled with the slower or inconsistent output, costs tend to inflate quickly and unexpectedly with most freelancers.
In short, there is a reason that so many startups and established companies are turning to quality design/dev firms to build their first or next big idea. You can’t beat having a professional team build your project and all that talent frequently comes in at a bargain (in time and money) when compared to an internal CTO or the inconsistency of freelancers. With a firm you will be riding an increasingly popular wave that is making it easier for entrepreneurs to realize their vision at a significantly higher level of quality without much of the potential downside. I’d be happy to talk with you more about this if that would be helpful.
I hope you are doing fine.
Think simple: Is this app / website your core business proccess or will it only support and optimize your operation?
Another question to assist you: Would it make sense for the spotify (for eg.) To outsource the development of spotify?
You see? If your system / app is your golden key, hire a software developer (probably offer him a minor society) and make sure to have a fair and safe contract in hands. (Never underestimate the value of a good lawyer's assistance).
If not, if the app will only assist you on collecting information and you have a specific product or service behind it, hire a company stead.
I really don't recommend to use freelancer developers, most of them have their own priorities, they will probably not focus on your project and you will probably have deadline's issues.
That's what I put on perspective to decide for my yellow brick road.
Hope to have helped.
Best of luck!
Hi Ayan, I also went through the same dilemma multiple times. I am also a tech person so I handled the situation. But some times it becomes terrible. Hiring own tech team becomes expensive. Same is the case of software companies, as for your applications you need continuous improvements, new features etc as per user feedback. Software companies charges you extra for these small things. So the total development cost becomes much more than expected.
Finally we found a bullet proof solution, that worked for me with excellent results every time. Please contact me for more details. Sure your search will end and you always get excellent results.
I think it all comes down to experience, risk and of course dollars. If you've got significant (millions) in investment, and you've done this before, you put together an executive team with the contacts you've made over the years, filling the CTO to lead the tech team. This person will not be programming - most importantly, they'll know how to find and hire the right people with the right experience and they can can align business needs with development focus.
Assuming, your budget is much lower - say self, or angel funding of $200K, half of which you'll put towards technology. In a perfect world, you'd find a full-stack developer capable of developing your backend, and your web or mobile apps... Of course they'd be designers too and be trained and passionate about UX. They'd have enough development experience to be dangerous, but not enough that they'd be afraid of the realities startup life brings. They'd work for $60K plus equity, and with other indirect costs you'll stay under budget the first year... Now, it's not to say that diamond-in-the-rough doesn't exist, but without solid referrals, direct technology understanding and experience, - and still - a hell of a lot of luck, you're walking a very fine line. And then you're hoping just one person can pull this together without the support of a team around her or him. Now I've seen this happen, but it will take much longer than you expect.
The other option is to hire a team...
Go offshore, and although the price-tag looks fantastic, you'll need to be ready to hand-hold at every stage, and that one month will turn into two, and three, and four. If you turn away for a second you're in trouble. When you do decide you've had enough, and costs have spiraled, with no-end in sight, you're gonna have a really hard time with anyone back here you hope to hire later to pick up the pieces. Again, overseas outsourcing can work out very well, but it is vital that someone on your end is managing the product, and the project closely, and attentively. I've seen this experiment go badly time and time again, so apologies to any good outsourcing firms
Now here's where my bias comes in. I run a small development team called 3Advance that works directly with non-technical founders that are ready to roll. The startup has a solid business plan and marketing strategy or budget, and they need to get their idea to market within a few months. Most importantly for you is not specifically technology knowledge, but reputation and recommendations of the dev group. If the team is proven, and you like what they've done (this should be obvious from their portfolio or site), $100K, for example goes a long way, and can be used for the specific things you need most - Design (Logo, UX, UI), Development (Backend, Web, Mobile).
In this case, your long-term plan will likely still to have your own internal team, but this can happen once you've got traction, and you've proven your business can sustain itself with revenue, or you've opened up the doors to further funding. I think it's worth saying that your team should share these same goals - your development firm should be happy to see you move to the next level and fully support the transition. This is honestly one of the most fulfilling parts of my job.
In my opinion, had I been in your position, I would not hire a cofounder/cto because I would not know how it'd turn out with that person in future, and anyways the profit margin would split; and hardly you can get the work done *your way* (which you need to, at least at this stage) by a co-founder.
I would not pay a company to build it (especially if big IT company) either, because they're too expensive to afford at this stage where idea is not validated yet (assuming) and don't know if the idea would work or how long it'd take to really go big.
I'd rather hire a freelancer with really great experience seeing his/her portfolio who'd make me a great site but won't be too expensive as a big IT company.
understand that whatever rout you take you really need to own the product and project yourself. That means before you consider hiring/partnering with anyone or any company you need to sit down and clearly describe exactly what you want to build. Start with short, written use cases and a written 'overview' for each module/function of your application then add logic/flow diagrams and screen mockups. Yes, this is a lot of work, but you will regret it if you don't do this. It is infinitely cheaper to make changes on paper/Visio/Lucidcharts now than it is to change code 6 months and thousands of dollars down the road. the process will force you to really understand, in detail, every aspect of your application. If you take the approach that you will not have an opportunity to actually speak directly to the person/company who builds your application/site (this should be your mindset, not your actual plan) and also assume that they may or may not be fluent in your same language then this will force you to be very disciplined in building your "specs". If you meet with potential cofounders they will appreciate the work you have put into clearly defining what you want them to build and you will clearly set yourself apart from the average 'non-techie' founder. If you take the cofounder rout I would argue that you need a developer, not a "CTO". this developer might grow into the CTO role eventually, but don't start off filtering for "CTO". If you take the rout of hiring a developer/freelancer or a dev company then you will need these detailed specs anyway and, again, you will save yourself a ton of time and money by having clear and complete specs. But the most important reason to spend the time to produce detailed specs is that the process will force you to really understand your application and make changes sooner rather than later. Your application will change over time, but this processes will allow you to minimize the cost of those changes. To answer your original question: You need to look not only at getting your application built, but also sustaining ongoing development and support. If you can find a technical cofounder who meets all of your criteria then i say this is the preferred rout. That's not easy. I would not forego other options waiting to find Mr/Ms right. You need to move the project forward each day. If you can't find viable cofounders in a relatively short timeframe then if you have the money, skills and the experience of product management and recruiting, hiring, managing, firing, and leading developers then i'd say hire a developer. This developer can potentially grow into your CTO assuming dev works out. Talk about this with them upfront. If they are not interested in the potential to be an employee/partner/equity holder then at least your are both on the same page going in. As Vanessa F mentions, hiring individuals/freelancers can be risky so make sure your written agreement with them gives you protections if they skip out early or produce bad code / spaghetti code. Plan for code reviews by a third party. If you don't have experience hiring and managing developers and you don't find a viable cofounder soon then your only truly viable option is to hire a dev company. Here again you will need detailed specs, a very clear understanding of exactly what needs to be built and a solid agreement that allows for code reviews, progress payments, ongoing support, etc.