What each setup step unlocks

What you get

A simple map of which data source supports which result, so you can reach an early useful view without treating every setup task as a prerequisite.

The ladder

Connect your accounting platform. This brings spend transactions into AppVentory. Once those transactions are mapped correctly, you can build reliable app-level cost and spend trends.

Match spend to the right apps. Confirm suggested matches and work through unmapped spend. This is what makes downstream app-level cost and savings analysis more trustworthy.

Connect your identity provider. This brings users and user-to-app relationships into the picture. Google Workspace and Microsoft Entra ID can also contribute available sign-in/activity signals; Okta is based on assigned-app and user data with manual sync.

Roll out the browser extension where appropriate. Browser-based usage can add another usage signal beyond identity-provider access. Treat extension-dependent conclusions in line with your actual rollout coverage.

What each unlocks

• Total software spend — An accounting connection
• Potential overlapping tools — A reliable app list and enough supporting data for overlap analysis
• What renews in the next 90 days — The app list, plus dates
• Spend changes worth reviewing — Enough historical spend for a useful comparison
• Reliable app-level cost — Your spend matched to apps
• Cost per person — An identity provider
• Browser-verified usage questions — Extension coverage for the users being reviewed

Start with the outcome, not the checklist

If your first goal is spend visibility, start with accounting and mapping. If the question is licences and adoption, identity and usage coverage matter more. Advisors can use the same organisation-level setup logic inside a client workspace while managing the wider portfolio from My Practice.

What you've unlocked

You can now choose the next setup step based on the question you want AppVentory to answer.