Before Stitchflow, everything was just manual and opaque. We were doing onboarding, offboarding, auditing, and everything else either through Okta or logging into each app manually. We had no visibility. Two people with the same title would have totally different permissions across apps like Salesforce, Copper, Jira. And worse, sometimes folks who left two months ago still had access somewhere. We'd literally had to click into apps to see who still works here! Stitchflow gave us a single pane of glass. We can see the correlations we need; user x has a Salesforce account but isn’t in Okta or user y hasn’t logged into Zendesk as an agent in 30 days - why. It surfaced stuff we didn’t even know to look for. During our domain migration and SSO rollout, it helped us catch legacy users and duplicates before they became a problem. That kind of digging would have taken us forever.

Before Stitchflow, we were buried in spreadsheets. Just getting the right data meant pulling from multiple sources—Okta, various systems, other data sources—and then spending hours trying to merge everything into something useful. It was death by a 1000 cuts before renewals. Now, with Stitchflow, we can instantly access what we need without the manual overhead. One of the biggest wins was automating Slack cleanup. Our team managed to archive about 60% of inactive Slack channels, which has been a huge improvement for organization and usability. People always say there are too many Slack channels, and with Stitchflow, we finally had an easy way to fix that. It’s just a simple point-and-click process now.

Before Stitchflow, everything was spreadsheets and manual audits—just going back and making sure people actually got deprovisioned. We have hundreds of SaaS accounts, and it was all on us to track who had access to what. There were always gaps, things getting missed. Now, with Stitchflow, we can actually see how users are provisioned across different applications. It helps us cut down the manual work, and we're not bouncing between different tools trying to piece things together. We’re also working on using it to define our departmental and sub-departmental provisioning, so we know exactly what access someone should have when they start.