How Larridin and Viva Insights compare
We’re comparing the two on coverage and on how each one values AI work. Details as of 16th November 2026 based on Microsoft’s documentation. “Not shown” means we found no public evidence either way.
| What matters | Larridin | Viva Insights |
|---|---|---|
| Coverage | 5,000+ business apps, including Microsoft 365 Copilot | Microsoft 365 Copilot, the agents inside it and GitHub credits[1] |
| AI spend | Billed spend in one ledger: seats, cloud and API usage, coding tools and agents, mapped to owners and cost centers | Copilot Credits and GitHub AI Credits[1] |
| Time and value | Human-equivalent hours from a predictive model, estimated for each AI session by type of work and complexity; a conservative, modeled floor | “Assisted hours”: a fixed 6 minutes per Copilot action, valued at $72 an hour by default[2] |
| Types of tasks | Each AI session classified into 105 standard work activities | Copilot actions by app and feature[2] |
| Share of work touched by AI | By workflow (Workflow Intelligence) | Not shown |
| AI fluency | Scored from prompt structure and depth across AI tools; prompt text isn’t stored | Power, habitual and novice users, based on Copilot action counts[2] |
| Agents | Agents traced to an owner, with alerts for agents whose owner is gone; coding-agent effectiveness and cost | Agents inside Microsoft 365 Copilot, and agents registered in Agent 365[3] |
| Engineering | Engineering Output and coding-agent effectiveness (Larridin Developer Intelligence) | Not shown |
| AI adoption | Tools in use, daily and occasional users, approved and unapproved AI | Copilot adoption by app, team and manager[2] |
| Data collection | Browser extension, desktop agent, and billing and API integrations | Microsoft 365 telemetry already in the tenant[4] |
| What to know | Needs an extension or agent for usage and fluency data | Doesn’t measure AI tools outside Microsoft |
How each tool estimates time saved
Viva Insights counts Copilot actions. Each search, summary or creation action is credited with 6 minutes, and a summarized meeting adds its length. Those hours are multiplied by an hourly rate, $72 by default, to give “assisted value.” Microsoft calls these figures broad approximations.[2] A one-line email reply and a full report draft both count as 6 minutes.
Larridin’s predictive model starts from the work. It matches each AI session to one of 105 standard work activities from the U.S. Department of Labor’s O*NET taxonomy, with a complexity level, and estimates the time a competent professional would need to do the same work without AI. Because it estimates each session from the work done, it predicts time saved more accurately than a fixed estimate per action. The result is a conservative, modeled floor: “at least X hours.”
The same estimates show which tasks people hand to AI and what share of each workflow AI touches, plus how much work time AI adds for each team. Next to billed spend, that gives a CFO the cost of AI work by team.
What Viva Insights does well
Viva Insights has a very detailed first party view of Microsoft 365 Copilot. It tracks Copilot usage across the Office apps (in Teams, in Excel etc). The Copilot Dashboard is included as part of the Microsoft 365 Business and Enterprise plans.[2]
With 50 or more Copilot or Viva licences it adds agent dashboards and external benchmarks (each drawn from at least 20 companies).[2][3] The privacy controls are quite mature: the advanced analysis reports and the senior-leader views in the Copilot Dashboard don’t show results for groups of fewer than 5 people by default, and an admin can raise that minimum.[5]
What data Larridin collects
Larridin’s browser extension monitors activity on AI tools to determine whether it’s work account usage or personal account usage and to assess AI fluency. Prompt and conversation history is not stored. There is no keystroke or screenshot recording. The spend is derived from billing and API integrations (Microsoft 365 Copilot seats and credits etc).[6] Personal accounts and unapproved tools will show as usage with no spend. SOC 2 reports are available at trust.larridin.com.[7]
Recommendations by role
CIO: Choose Larridin to see every AI tool and every AI dollar across the company in one place. Viva Insights covers Microsoft 365 Copilot and the agents inside it.
CFO: Choose Larridin to tie billed AI spend to owners and cost centers and compare it with what AI produced. Viva Insights values Copilot with a fixed time estimate per action.
CTO: Choose Larridin Developer Intelligence to measure what engineers and coding agents ship and to lower model cost with the Larridin Router. Viva Insights doesn’t measure engineering output.
Head of AI: Choose Larridin to see how well people use AI and which tasks they hand to it, across every tool. Viva Insights shows Copilot usage levels.
CHRO: Larridin measures AI use and its impact across teams. It isn’t built for employee engagement surveys.
Running both
Many Microsoft 365 companies keep Viva Insights, since it is already in the tenant. Larridin adds the AI tools outside Microsoft and puts billed spend for all of them next to a per-session estimate of value. Start with the teams that use the most AI outside Copilot.
Questions to test in a pilot
- Can the tool show AI use outside Microsoft 365, such as ChatGPT or Cursor?
- Can it show last month’s billed AI spend by cost center across every vendor?
- How does it estimate time saved: one fixed value per action, or per piece of work?
- Which types of tasks do people use AI for, and what share of each workflow does AI touch?
Proof
One customer had three AI tools with similar adoption (about 73-79%), but one of them had fewer than 1 in 10 users active on a given day and was roughly 7.7x less engaged than the top tool, which made it the first seat count to review at renewal.
The median engineer draws $213 a week in billed AI coding spend (invoiced spend, among engineers who merged code and drew billed spend, four weeks to August 2, 2026). It is a conservative floor, because usage on flat-fee plans never appears on a metered bill. Source: Larridin AI coding spend benchmark.[8]
Questions buyers ask
What is the main difference between Larridin and Viva Insights?
Viva Insights has a fixed rate per action for Microsoft 365 Copilot. Larridin covers all the AI tools and puts a value on each session based on the work that’s actually done.
Is Larridin a better fit than Viva Insights for measuring AI ROI?
Yes. Larridin links the AI spend to the work that AI does across 5,000+ business apps (including Copilot). Viva Insights is entirely within Microsoft 365 and Copilot is valued at 6 minutes per action.
What is Copilot Analytics?
Microsoft’s reports on Microsoft 365 Copilot are split between the Microsoft 365 admin center and Viva Insights. The key ones are the Copilot Dashboard, the Agent Dashboard and the Consumption Dashboard (for credits).
Does Viva Insights measure ChatGPT, Claude or Cursor?
No, its view stops at Microsoft 365 Copilot and the agents within it.
How are Viva Insights “assisted hours” calculated?
Each Copilot search, summary or creation counts as 6 minutes plus the length of the meetings that you’ve summarised. That’s the broad approximation that Microsoft use.
How does Larridin estimate time saved?
Larridin’s predictive model matches each AI session to a standard work activity and a complexity level, hence it is able to predict time saved more accurately than a simple fixed estimate per action. It reports a conservative, modeled floor in human equivalent hours.
Does Larridin measure AI fluency?
Yes. The score is derived from the prompt structure and depth across the various AI tools. The prompt text itself is not stored.
Does Larridin measure Microsoft 365 Copilot?
Yes. Copilot seats and credits are in the same ledger as every other AI tool, with usage alongside.
Can I use Larridin and Viva Insights together?
Yes. Many teams keep it for the Microsoft 365 detail and add Larridin for every AI tool and billed spend.
How do I start with Larridin?
Ask for a pilot plan. We’ll scope a pilot around the AI ROI question that your leadership is asking.
Sources
Bracketed numbers in the page copy, for example [2], match the numbered sources below. Each marker links to the source.
Microsoft sources, checked November 16, 2026:
- Microsoft Learn: Copilot Analytics introduction: learn.microsoft.com/en-us/viva/insights/copilot-analytics-introduction
- Microsoft Learn: Copilot Dashboard: learn.microsoft.com/en-us/viva/insights/org-team-insights/copilot-dashboard
- Microsoft Learn: Agent Dashboard: learn.microsoft.com/en-us/viva/insights/org-team-insights/agent-dashboard
- Microsoft Viva Insights product page: microsoft.com/en-us/microsoft-viva/insights
- Microsoft Learn: Viva Insights privacy: learn.microsoft.com/en-us/viva/insights/advanced/privacy/privacy
Larridin sources:
- Larridin: Microsoft 365 Copilot license management: larridin.com/integrations/microsoft-copilot-license-management
- Larridin Trust Center: trust.larridin.com
- Larridin AI coding spend benchmark, August 2026: larridin.com/data/ai-coding-spend-benchmark