Revetti maintains a suite of free diagnostic tools that surface what’s quietly costing an operation. They are not lead magnets. They take 5–15 minutes each, run in the browser, and produce useful output. Run them in any order, share them with anyone, return to them when something changes.
The deepest diagnostic Revetti offers in tool form. Walks through 50 specific configuration and capability checks across an M365 or Google Workspace deployment. Output is a scored assessment with a prioritized list of improvements — the same diagnostic logic that powers the formal Workspace Audit engagement.
Identifies SaaS subscriptions in your stack that are redundant, underused, or replaceable by tools you already own. Output is a list of candidates with rationale and estimated savings.
Diagnostic for whether an M365 or Google Workspace deployment is being used at full capacity. Surfaces features the operation is paying for but not using.
A single composite score reflecting how well a workspace is configured for the operation actually being run. Useful as a benchmark you can re-run quarterly to measure progress.
Where automation is currently working, where it isn’t, and where it’s missing. Output identifies the highest-leverage automation opportunities specific to the operation.
Quantifies the cost of operational sprawl and the upside of consolidation. Produces a number that supports internal budget conversations.
The diagnostics produce useful information. Some visitors run them and act on the output independently. Some run them and bring the results to a discovery call as the starting point for an engagement conversation. Either is fine.
The tools are not gated. They are not lead-capture forms in disguise. They produce real output and don’t require an email address to deliver it. If the output suggests a structured engagement makes sense, the Engagements page describes the work; the Audit page describes the formal Workspace Audit.
If the diagnostics surface something worth acting on, a discovery call is the way to start. No pre-work — the tool output is enough.