SharePoint and Teams

<p>Just saying, but I would actually look at what their carbon based workflow is before I try and recommend changing things.</p><p>Teams sort of dumbs down SharePoint, which is not necessarily a bad thing if they are using SharePoint as a network share, but if they have spent some time organizing it, then you are messing around with something familiar to them. Usually, that ends badly.</p><p>How do they handle documents? Is SharePoint just a place to archive them or are they using it to allow multiple people to access and/or edit the documents. How is their SharePoint tenant set up…multiple site collections, multiple sites, a single collection with one root site?</p><p>How open is the organization to change? How sophisticated is the user base?</p><p>What are their needs regarding data security and retention? Can you implement that in Teams, considering the Team members can have fairly broad permissions?</p><p>Teams is a good product, and if they have Office365 subscriptions, then it is there. You might want to propose a trial run on an upcoming project, so they are starting with a clean slate, and can compare it to current processes. That may be all you need to do to sell it. </p><p>As "TheJoeFin" suggested, PowerApps and Flow are good tools. They work with SharePoint and Teams, so whichever way you go, they are likely part of the future.</p><p>…and tequila is always a good idea.</p>