Skip to content
  • There are no suggestions because the search field is empty.

What to expect in your first week

Know what appears after each connection and use the waiting time to clean the data that matters most.

What you get

A realistic first-week sequence. Some data arrives quickly, while other views become useful only after mapping, synchronisation or wider usage coverage.

Start with accounting and spend mapping

After the accounting connection, transactions begin appearing in Spend Overview according to the platform and history you selected. The useful next step is not simply waiting for a dashboard — it is reviewing Needs Review and Unmapped items so software costs land against the right applications.

Once enough spend is mapped, you can start using the spend quick wins and savings views with more confidence.

Spend Overview showing the four transaction tabs with their counts

Spend Overview showing the four transaction tabs with their counts

Add identity when licence questions matter

Google Workspace, Microsoft Entra ID or Okta can add users and user-to-app relationships. The exact sync behaviour and activity data differ by provider, so use the connection's Sync History or Activities where available to confirm what has arrived.

Build usage coverage over time

If you use the browser extension, browser-based usage becomes more representative as the relevant users install and connect it. Do not treat partial rollout as complete evidence for the whole organisation.

Worth doing while you wait

  1. Confirm the suggestions in Needs Review. Every one sharpens a cost figure.
  2. Confirm your app list and archive what isn't real.
  3. Add renewal dates for your five largest apps.
  4. Assign owners, so findings have somewhere to go.

What you've unlocked

By the end of the first week, aim for usable data, not perfect data: the important spend mapped, the main apps confirmed, owners and renewal dates added where known, and the connections you genuinely need showing healthy syncs.