In this episode we chat with Brent Sanders and Roman Beylin on due diligence when it comes to technology. This discussion is everything a first-time (or tenth-time) seller needs to know when it comes to managing your exit strategy with technical diligence.Some of the top things a first-time buyer should take away from this session:Why proper documentation right from the beginning is keyWhat licenses really mean and how you may need to upgrade your software dependencies and packages The rubric for what a buyer is looking for: code, testing infrastructure, source and product management, how team works, service set upThe key licensing questions you need to be clear about with your companyWhy folks that work with brokers tend to leave it up to the buyer to be diligent rather than be proactive in being diligentThe role attorneys and fractional CTO’s have in technical diligence and who else you need to talk to in your business to get startedWhy centralizing access control and single passwords are essentialUnderstanding legacy code and why you need to be prepared to go places that haven’t been touched in a whileThe most common things that business owners get wrong with the transition Why agencies often aren’t necessary and how to avoid a walking dead portfolio companyAt what point in the M&A it makes sense to bring on someone to help with technical due diligenceThe importance of diligent password managementWhy it’s important to keep your software updated constantly to minimize risk and mitigate future issuesIf you’re looking for a smooth transition, this episode on technical diligence is not one you’ll want to miss. Tune in to get all the details to manage your exit smoothly.Related episodes:Who's Your Buyer? A Look Into the Most Common Types of Buyers in a Business AcquisitionDon't Spill the Bean. Why Confidentiality Matters when You're Planning an ExitLinks:VerneHQDueDilioFastCTOKeywords:Due diligence in technology, passwords, technology, tech, licensing