Almost every business is technology-enabled in some way these days. Hair salons do their scheduling online, powerline workers train in VR, and pharmacists use AI systems to check for contraindications. There are very few businesses out there that could not be made more efficient and profitable — or provide better services for their customers — through technology.

In most situations, buying software and customizing it makes the best sense. You need a word processor and an accounting system, but it would show boldness to the point of lunacy to build one yourself. Quickbooks and Microsoft Word are worth the few hundred dollars a year. They might not be perfect, but the cost to build and maintain your dream accounting software could run into the millions.

However, in many situations, businesses invent new ways to improve their internal operations or their customer experience. While a comparable off-the-shelf solutions may exist to fit those needs, a custom built product is likely the only way to deliver the required features and processes the company is looking for. Features like these become competitive advantages. Organizations want to own the intellectual property behind their competitive advantages. You don’t want to license these types of systems if your competitors can license them just as easily.

That leaves companies with one choice: Build your own custom software. But the question is whether you should try and build your business-changing application in-house or outsource it to a development agency.

Cost vs. Time

Most decisions in the professional space come down to the project management triangle. If you want to build software of any decent quality, you can pick two of the three corners to move: cost, time, and scope (the number and robustness of features the project has). If you want fast and cheap, you have to shrink the scope. If you want robust and cheap, you’ll have to wait a long time.

The decision to hire an agency or build a team hinges on these three corners. In business applications, scope is usually the non-negotiable — the requirements are the requirements. Building a team takes a lot of time and costs money. Hiring an agency will drastically reduce the ramp up time by comparison, but potentially cost more. If you are worried about quality, remember that you get what you pay for.

Management Structure

Deciding to build out your own development team is not for the faint of heart, but it can have serious benefits.

To build a basic, but healthy and functioning, software team you will need the following:

  • A CTO or CIO to handle strategy and management.
  • A Director of Engineering to manage the team, build out processes, etc.
  • A Software Architect to design the system. (This can be a senior developer for small teams.)
  • A couple of DevOps engineers to manage the environments.
  • At least one QA expert. (No, developers can’t check the work themselves, I’ve tried.)
  • Developers, including full-stack, frontend, and backend developers if you’re building out a product. A good mix of senior, mid-level, and junior developers would be my recommendation to make the team robust.
  • A product owner. Preferably someone with management experience
  • A scrum master (if you’re following Scrum/Agile).
  • UX expert. I cannot understate this role enough! (They can be outsourced if you have to, but are much better to have on the team.)
  • A visual designer. Depending on the product you are building, this is the one optional role.

This is the biggest reason to hire an agency. If you want something built well, you really need a team that looks like something similar to this. Depending on your budget and experience, it could take years to put a team like this together.

However, if you have highly technical and experienced upper management there are benefits to in-house teams.

But We Are a Lean Startup

That’s great! Then you don’t need any of the stuff I listed above. But if you are purely a technology startup, then you (I’m guessing you’re a founder), need to be building the tech yourself, or at least have a co-founder building the tech. As the company scales, you can bring on additional help and you will almost certainly start looking like the organize above.

How Long Does It Take To Build a Team?

It depends on if you’re talking about a good team, or just any team. Building an organization from scratch takes time. You need to recruit, hire people, onboard them, manage them, weed out the good, let go of the bad, hire replacements for those let go, etc. You also need to invent, document, and enforce the systems and processes that will lead to the best outcomes. You will need to build a culture of caring, accountability, and quality. So, basically it will take a long, long time. This is a lot easier to do if you have a top rated CTO or a Director of Engineering in place already. Someone who has gone through this process before will be able to get you up and running much more quickly. They will also be able to oversee all stages of the team building from recruiting to delivery.

Recuiting may be the hardest piece of all of this. Good developers don’t want to join companies without histories of good development practices. So if you don’t have someone for new hires to look up to, you’re going to be stuck with coders who are just looking for a job, and they don’t write good code.

In-House vs Outsourced — Conclusion

Unless you are going to go with the lowest bidder, there probably isn’t that much difference between a good internal team and a good agency. Well-run development studios partner closely with their clients and eventually start to act as part of the same company. The developers in agencies like this feel as much ownership in what they are building as full-time employees would — sometimes more.

Price is not going to be dissimilar either. Once you count things like benefits, office space, management scaffolding, training, hardware and software tools, payroll, HR, etc., etc., etc., it’s unlikely that in-house could be done cheaper than even the large agencies.

The real difference comes down to the level of control you want over the team and the type of product you’re building. If you are a small technology startup you would be crazy to hire a big agency unless your product needed to be really good from day one. If you plan on becoming a technology company, you might want try a hybrid of agency and in-house. Finally, if you are a small- to medium-sized company whose existing products or services are not predominantly tech-focused or delivered, I would suggest not doing development in-house.

Previous ArticleNext Article
I help companies turn their technical ideas into reality.

CEO @Sourcetoad and @OnDeck

Founder of Thankscrate and Data and Sons

Author of Herding Cats and Coders

Fan of judo, squash, whiskey, aggressive inline, and temperamental British sports cars.

Leave a Reply

The Internet Doesn’t Have Enough Love In It (And How We Can Fix It Easily)

I’ve been thinking about all the wrong things when it comes to AI writing code.

Everyone else seems to be too. Job displacement. Security vulnerabilities. The ten-times-faster developer who now bills the same and delivers four times as much. These are real conversations worth having, just not the one I want to have right now.

The one I want to have is about teaching a six-year-old multiplication.

Here’s what I mean. Imagine you’ve been sitting with your kid every night for two weeks trying to explain multiplication. You’ve tried drawing rows of dots. You’ve tried songs (don’t judge me). You’ve tried the “just think of it as groups of things” approach that works for literally every other math concept but, mysteriously, not for your kid. Then one night, something clicks. You found the explanation, YOUR explanation, the one that worked for your actual kid with your actual kid’s brain, and it finally, beautifully, clicks.

Now imagine you could spend a Saturday morning turning that into a small web app. Not a startup. Not a SaaS platform. No login. No backend. No one’s going to hack it (there’s nothing to hack). Just a little thing that walks through multiplication the exact way you figured out it works, step by step, the way you’d explain it. You send it to the WhatsApp group for your kid’s class. Some of those other parents, also quietly losing their minds over multiplication, try it. And it helps.

You just made the world a tiny bit better. That’s it. That’s the whole thing.

Claude Code exists now, and a handful of other tools like it, and the reason I think this matters isn’t productivity. It’s access. The barrier between “I have an idea for something that could help people” and “I have a thing that helps people” used to require knowing how to code, or hiring someone who does, or talking a developer friend into your project over enough beers that their guilt exceeded their better judgment. Now it’s a Saturday morning and a good description of what you want to build.

The internet already has beautiful things in it that were built out of love. Free coding education for kids. Open-source video editors. Someone’s incredibly detailed home-brewing app with no monetization plan whatsoever. Artists making interactive experiences because they wanted to see if they could. These things exist because someone cared more about making the thing than making money from the thing. I think that ratio is about to shift dramatically in favor of the people who just want to make something good.

I’m not saying we should all stop paying for Salesforce (we should probably keep paying for Salesforce, there’s a reason that thing costs what it costs). I’m saying the category of software that was previously not worth building because it wasn’t commercial enough to justify the cost, that category just got a lot more interesting.

What’s in that category? Things like:

  • An app that helps beginning judo students understand the concepts behind a throw, not just the mechanics, because judo is where I learned confidence and discipline and I want other kids to find that
  • A private family memory vault (not Instagram, not Facebook, not anything with an algorithm deciding what matters), just a place where the people who love my son can send photos and stories somewhere safe, for him to open when he’s older (Maybe I’ll turn this into something?)
  • A system that reminds companies to send their employees gifts on the days that actually matter to them, because I know from running a company that it fills the cup of the person giving just as much as the person receiving (Thankscrate, if you’re curious, and yes, that one is turning into something real, but that is genuinely not why I built it)

None of those were commercial ideas first. They were just things I cared about.

I think the most interesting software that gets built in the next few years won’t come from developers moving faster. It’ll come from people who previously had no path from “I care about this” to “I built something about this,” and now they do. Parents. Coaches. Teachers. The person in your office who could explain that one complicated process better than anyone and has always secretly wanted to turn it into something.

The stakes are low. The bar to launch is low. The cost is low. The only thing required is that you actually give a damn about what you’re building.

So… What do you give a damn about?

Go build it. I still sometimes have to count on my fingers, but I’m told the app helps.