Build vs. Buy: The enterprise software conundrum
summary
Thomson Reuters needs faster time to market for Checkpoint Edge and finds its legacy QA won’t scale with a cloud‑native, microservice architecture, so the team buys BrowserStack after a vendor assessment and runs a one‑month POC to validate browser/device coverage and integration. The integration requires switching to Robot Framework. Building in‑house repeatedly turns weekend hacks into months of hidden costs, adds technical debt and maintenance burden, and loses opportunity to focus engineers on core AI/ML product work.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:05Build vs buy dilemma
- 4:33Factors favoring buying
- 9:47Budget and cost considerations
- 11:51Timelines and ROI
- 13:18Opportunity cost analysis
- 16:24Quality compromises
- 18:11Technical debt risks
- 21:37Factors forcing building
- 22:39Data security concerns
- 24:03Security and compliance
- 25:29Comprehensive solutions
- 26:54Market risk assessment
- 29:19Talent and skill alignment
- 31:05Thomson Reuters framework
- 33:34Architecture fit
- 35:19DevOps tool selection
- 36:44Closing thoughts
- 37:07Q&A session
related talks
32mBuild vs. Buy in the Midst of Armageddon
05mChallenges of building a test infrastructure around a cross-platform Desktop
40mSecurity Automation in the agile SDLC - Real World Cases
28mWhy You Shouldn't Run Business Applications with a Build Tool
41mCross browser and device platforms are ripe for disruption
36mHow to build continuous security and embed it in your product
19mBusiness Impact Delivery Using Test Automation
38mScaling Automated Testing & Architecture from Startup to Enterprise