You lead a team of engineers, and your team is responsible for building out a new customer-facing product that could have a huge impact on the trajectory of your company. Lately you've been considering whether or not rolling your own authentication system is a good idea, and after careful consideration, you've concluded that it's not in the best interests of your company. To talk to all the relevant stakeholders about this choice, you need to adapt your approach based on the size and structure of your company. You'll have to emphasize the benefits of outsourcing your auth system to each type of stakeholder, including your boss, developers, project management, product management, legal, quality assurance, UX and design, security, and infrastructure teams. By doing so, you can build a consensus among stakeholders that will help you achieve the best outcome for your company. Key points include reducing implementation time and costs, mitigating risk, allowing team members to focus on more interesting features, and ensuring compliance with data protection laws and standards certifications. Ultimately, the goal is to emphasize spending time doing new things and building new features that solve problems for customers, rather than reinventing existing functionality.