What framework should I use to prioritize either dedicating engineering resources to build out product functionality or just using a 3rd party service?

Question

Kara Gillis · Accepted Answer

I typically advocate for using full-time engineering talent on the most innovative features, hardest problems to solve and outsource to third party services for things that I can depend on, not require a ton of updates to, and save me money.

Your dedicated engineers are there because they're your most valuable resources - keep them engaged and excited by working on the most fun challenges!

Krishna Panicker · Answer

Without full context, I will assume you are not a start up but rather a profitable business with growing revenue.

When considering whether to build, buy or partner (BBP), work with your team to put together a set of principles that are informed by your :

* vision and strategy
 * differentiated core
 * ability to deliver value to market quickly

Once you've identified the high leverage items that brings differentiated value, then work with your engineering team to model each of the 3 BBP options, and score them (doesn't matter how , just align on a framework).

1. How quickly can you prototype and validate the solution with your target customer ?
 2. What's the time to market for each option?
 3. Which one delivers the highest value ?
 4. For each option, what's the total cost of bringing it to market ?

Brandon Green · Answer

I don't have a specific framework I use for determining build vs buy, but I've typically used a series of questions to help evaluate the decision:

- What is the problem you're trying to solve by building or buying?

- How strategically critical is that solution to your business? Is it something that could create a competitive advantage, help build moat against competitors? (If so, there is probably some risk in relying on a 3rd party.)

- What benefits come from buying? Does it significantly speed up your time to market? Are there long-term benefits or capabilities that a 3rd party vendor can provide beyond what you're immediately trying to solve for? (If either is yes, that may increase the value of buying a 3rd party solution.)

More importantly, look at other examples of companies having built vs bought and how they evaluated those decisions. One thing I love about the Internet is that there are tons of examples of companies having gone through this decisioning process, and how it worked out for them. I recommend checking out things like Ben Thompson's Stratechery blog, the Acquired podcast, blogs of companies you know have bought vs built in-house, etc.

Ashwin Arun Poothatta · Answer

It is important to consider the build vs buy decision where it makes sense as teams are often focused on building everything, resulting in inefficiencies and a lack of focus. While using 3rd party services can be a strategic move to accelerate your roadmap and free up resources and time, it is important to decide if it aligns with your long-term goals and strategy. To make the decision, consider the following questions with stakeholders

* Is the functionality core to your product and will it differentiate you in the market?
 * Do you need out-of-the-box functionality or customizations?
 * Are there industry-leading services you can use?
 * Will using a 3rd party service accelerate time to market?
 * What are the implementation and maintenance costs compared to building in-house?
 * Will the 3rd party meet your user's service level expectations?

It is also wise to gather feedback from other customers of the service and the impact it had on their product and users, as these decisions require significant investment in capital, time, and effort.

Related Ask Me Anything Sessions

Atlassian Director of Product Management (Confluence), Paresh Vakhariya on Product Roadmap & Prioritization

Green Dot Principal Product Manager, Ashwin Arun Poothatta on Product Roadmap & Prioritization

Splunk Director of Product Management, Richard Shumon Product Roadmap & Prioritization

Related Questions