Back to Your Feed
4 Answers

Kara Gillis
Splunk Sr. Director of Product Management • October 31
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 y......Read More
603 Views

Krishna Panicker
Airbase VP Product • March 8
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......Read More
345 Views

Brandon Green
Buffer Staff Product Manager • August 16
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 somethin......Read More
290 Views

Ashwin Arun Poothatta
Green Dot Principal Product Manager • April 4
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 im......Read More
410 Views
Related Ask Me Anything Sessions

Atlassian Director of Product Management (Confluence), Paresh Vakhariya on Product Roadmap & Prioritization
June 22 @ 10:00AM PST

Green Dot Principal Product Manager, Ashwin Arun Poothatta on Product Roadmap & Prioritization
April 4 @ 10:00AM PST

Splunk Director of Product Management, Richard Shumon Product Roadmap & Prioritization
January 10 @ 10:00AM PST
Related Questions
We’re pivoting our product, and it’s difficult to plan the roadmap too far out. How do we reset expectations on what product communicates?When does it make sense to make your roadmap publically available, and what do you include (vs your internal roadmap)How do you handle exec input in the roadmap, and convey a point of view while also accommodating?Which stakeholders have input into your roadmap, and how to balance giving them influence vs control?How do you determine how much of your roadmap should be focused on existing customers vs prospects?How does your product team usually work with your product marketing team with building the roadmap?