Skip to content

The pros and cons of outsourcing product development

I discuss when outsourcing product development can help an early stage company move faster, access skills it lacks and keep customers seeing progress whilst the internal team focuses elsewhere. I also share why key product work should move in-house as the business grows, covering cultural fit, quality trade-offs and the risk of technical debt.

Key takeaways

  • Outsourcing can help small teams access proven skills, move quickly and reduce delivery pressure in the early stages.
  • External teams may not share the same cultural commitment or long-term product focus as an in-house team.
  • Fast, cost-conscious delivery can create fragile architecture and technical debt if quality and strategy are not managed carefully.

Topics

  • Product Development
  • Startup Growth
  • Team Management
  • Engineering

Transcript

Wow, right, yeah, that's a big topic. Okay, so I guess let's start with the advantages, especially in the early days. I'm like, I think it's actually quite advantageous to do this because growing a team when you're very small with limited budget, it takes a lot of time. Often maybe there may not be certain technical skills in-house. You might not attract a certain level of talent or whatever it might be. So I think being able to, like, outsource some of your product build to another company who has those skills, who can kind of easily ramp up a team, or relatively easily ramp up a team and tackle it, and who's also, you know, that team is kind of proven. Like, it's not the first time they've ever built a product, right? Whereas for a founder, it might kind of be. You never know, like, what their background is. So generally speaking, they can kind of apply a proven methodology, a proven team, and get to work fast and deliver. They're also accountable, right? Like, so you've suddenly got this extra bit of accountability, like one throat to choke, as they say. Like, if it's not working, you're like, right, come on, you know, to do that. And whilst you're also having to do a load of other things in the early stages, such as selling to customers and things like that. So I think it kind of spreads your risk a bit, increases the accountability a bit more widely. Yeah, and like, you know, there's a lot of talent out there in the world, and it might be that you're also outsourcing. To a team in a country that you have no personal exposure to, right? So in our case, we actually used a team in Ukraine for about two years in the early days. And the main thing we did there is we were actually rebuilding our main platform with our own engineering team, and that the Ukrainian team were building kind of like integrations and add-ons to our existing platform so that to our customers it felt like we were still innovating on the platform whilst our core main team were rebuilding our new one. I don't think they would have been able to do that without that outsourced team taking care of it. So I think there's some good stuff there, right? Ultimately, I'd say though, as you get bigger, you shouldn't be outsourcing, like, key parts of your product. I think it does need to come in-house. I think the part of the disadvantages then would be the people who are recruited by that outsourced company, they weren't really recruited because they believe in ScreenCloud. They were recruited because they wanted to make money developing software for customers and then they'll find out which customer they're working on when they get there. So there's a little bit of a cultural misalignment, which is that developer hasn't necessarily fully opted into you. I think they do try and match, you know, against interest and stuff like that, but the reality is they also need to get to work, right? So that's one issue you have. And I think when we had that Ukrainian team, for example, you know, we actually quite—they were actually a pretty good team. I remember one guy once asked one of the developers, like, Oh yeah, so why did you become a developer? And he's like, Well, you know, actually my interest is really in acting, but I need to make money, so I just became a developer. And he's like, Oh, okay. And actually, if you think about it, where he's from, he's like, I need to make money. That makes money. It's not my passion, but I'm smart and I can do it. And you're like, Okay, that's fine. There's nothing wrong with that. But ultimately, like, that isn't going to—he's not going to be going home at night thinking, What can we do? How can we make this better in the future? And there's another thing about outsourcing, which is like, everyone probably knows this triangle, okay? You've got speed, cost, and quality. Pick two. Now, I would say outsourcing companies probably skew towards cost and speed, and that's probably because customers, especially ones who haven't done lots of product development before, they are the two things they care about. I want it done quickly, and I don't want to spend a fortune. And so you're going to get high-velocity product coming out of them, but they're not going to take that time to step back and think about the longer-term perspectives. And this is what we found after a couple of years of doing this, is that suddenly we had this, like, a lot of code, a lot of stuff had been pushed out, but it was quite fragile. It hadn't really been architected right, hadn't really been thought right. And whereas subsequently bringing all of that back in-house, this is the responsibilities of VPs who've been here or worked their way up to VP for like five years, just thinking about screens, only screens, not any other technology. And so I think it's not, again, it's not their fault. They're just responding to the market. But, and, you know, as a customer, it's great to see product shipping, shipping, shipping, but then two years down the road, you've got a lot of technical debt. You haven't really been very strategic, and I think that can be a real problem. I'm sure all of this can be figured out, but this is what my experience is.