Choose a relevant source
Use your company's supported admin reporting. Vaze brings the available account, key, seat and usage information into one place.
Company AI readiness audit
A practical review of the AI you already use.
Connect a company AI provider. See useful findings, decide what to improve first and keep a review you can share with your team.
Start your AI reviewStart with one provider you administer. Check the setup you need.
Useful data, then a clear next step.
Focus on what matters first
Review key access, seat assignments and cost checks. Use the provider's activity reports to decide where adoption needs attention.
Keep the review useful
Download a dated review you can keep. Share it with the right people, record follow-up in Vaze and refresh the data for your next review.
Fictional example · Illustrative findings and team-authored plan
From a finding to an improvement plan.
Northwind Example Ltd connects OpenAI API and GitHub Copilot. The review starts with what those sources report; the team adds the context and chooses the follow-up.
One active API key has organisation-wide scope
The key can reach more than one project. Its owner and dependent services need checking before a change.
First: confirm its use
Jordan will identify the owner and dependencies by 12 October, then prepare the appropriate scope or retirement decision through the approved process.
Four Copilot seats have no reported activity in the review window
The seats are a review candidate. The team checks reporting coverage, current need and billing terms.
Next: speak to the seat owners
Sam will confirm by 15 October whether people need help adopting the tool or whether an assignment can be reduced at the right billing point.
Who owns billing alerts and the AI policy?
The team names the responsible people and confirms its rules for company AI use.
Then: set a review date
Jo will check the alert recipient, link the approved policy and set the next team review for 5 November.
These names and findings are fictional. The example plan shows decisions a company could make; it is not a customer result or a screenshot of a completed audit.
Start with the provider your company uses.
Choose the exact product and ask a company administrator to help if needed. Signing in to Vaze with Google or Microsoft is separate from connecting a reporting source.
OpenAI API, Anthropic Console and OpenRouter
For company API accounts: use the platform's organisation/admin or management reporting credential shown in Connector setup. OpenAI API data is separate from ChatGPT subscriptions; Anthropic Console is separate from Claude Team or Enterprise. Key and usage fields vary by provider.
Prepare your API account access →GitHub Copilot and Microsoft 365 Copilot
For supported company plans and admin reporting: GitHub requires the organisation grant shown in setup; Microsoft 365 requires a company administrator's reporting permissions. Available activity depends on the plan, reporting settings and window. Personal subscriptions are different products.
Review access and billing before removing a seat →ChatGPT Enterprise, Claude Enterprise and Cursor teams
Workspace analytics needs an eligible workspace/team and the appropriate admin reporting access. Use the exact setup instructions in Vaze. Enterprise reporting keys differ from API platform keys; Cursor setup explains its broad Admin key before you connect it.
What workspace administrators can see →Google Workspace and bundled AI
Workspace reporting and licence inventory use administrator-authorised access. A licence or bundled entitlement tells you what is available; it does not by itself establish whether someone uses AI. Check the available feature activity alongside your company's own tool records.
Explore the supported reporting sources →A little company context goes a long way.
Connected data does the first pass. Add the owner of a tool or key, the policy it follows and the person responsible for the next step when those details are needed.
Who owns this tool?Which company policy applies?
Keep your approved tools register and company AI policy alongside the review.
What should an AI readiness audit tell you?
For a company already using AI, a useful operational review links current account data to a decision: what to inspect, who needs to act and what to check next time. Start with our practical AI tool audit guide if you are assembling the wider company picture.
Scope and sharing
The review covers the supported sources you connect and the information those sources expose. Keep each dated review in your own approved storage and share it only with authorised people. Refreshing the review replaces the current preview; downloading a review does not send it.
A key's last use does not show when it was rotated, and a quiet seat does not establish that a colleague has left. This is an operational review, not certification, comprehensive discovery or automatic remediation.
Start with one useful AI review.
Connect an authorised company source, review the findings and choose a next step.
Start your AI review