Another quarter, another SaaS audit where we discover we're paying for ghosts. I've just finished what feels like the annual ritual of purging unused seats from our Grammarly Business account, and I'm left wondering why this process is still so manual and opaque. It’s a perfect little microcosm of the wider sales stack problem: we buy for the theoretical peak, then hemorrhage cash on the long tail of inactivity.
You'd think a tool built on data and suggestions would make this easier for admins. Instead, we get a dashboard that's more about aggregate writing stats than actionable financial hygiene. So, for anyone else tired of paying for colleagues who left six months ago or for that one team that tried it for a week and silently reverted to their chaotic Google Docs ways, here's the painfully manual walkthrough I followed.
First, the reconnaissance. Don't just look at the 'Last Active' column in the **Admin panel > Team members**. It's a start, but it's famously generous. Grammarly seems to consider opening the extension pop-up as 'activity.' You need to cross-reference.
* Pull your most recent billing invoice to confirm your total paid seats.
* In the Admin panel, sort by 'Last Active.' I set a arbitrary but harsh cutoff: anyone inactive for over 90 days is immediately suspect.
* The critical step: export the user list via **Settings > Export team data**. This CSV gives you a slightly more granular, though still limited, view.
* Now, the manual labor. Correlate this list with your actual org directory (Slack/HRIS/Google Workspace). This is where you find the departed, the rebranded (looking at you, folks who changed names post-marriage and created a new account), and the simply disengaged.
The cleanup is straightforward, albeit one-by-one. Select a user > click 'Remove from team.' The system will piously inform you their work will be preserved should they ever be re-invited. Lovely.
The real irony, and my core contention, is the lack of proactive tooling here. For a platform that nags me about my tone and comma splices, where are the admin alerts?
* A weekly digest flagging seats with zero document edits for 30 days.
* A bulk removal tool.
* A simple integration hook to deprovision seats when an email is deactivated in our core IDP.
* Even a predictive forecast: "Based on activity trends, you could reduce your license count by X next cycle."
Without these, the 'Business' in Grammarly Business feels less like a partnership and more like a gym membership model—banking on our inertia. We implement this ritual for CRM, for project management tools, and now, apparently, for our grammar checker. The savings aren't trivial; for us, it was reclaiming 15% of our seats. That's a non-trivial chunk of change to reallocate to tools people are actually using.
Maybe next quarter they'll surprise me. Until then, mark your calendars for another manual scavenger hunt.
🤷
Completely agree on the last activity column being misleading. I've found it can show activity for months after someone has offboarded, likely from cached sessions or background pings from installed extensions.
You need to export the detailed usage report and filter for actual writing events - keystrokes or corrections - not just app opens. Even then, the data lag can be up to 48 hours, so you're never auditing the current state.
This is why we treat it like an infrastructure lifecycle policy now. We have a Lambda that pulls the Grammarly API weekly, correlates it with our HRIS deprovisioning feed, and auto-revokes licenses after 30 days of no substantive usage. The manual admin panel is just for exception handling.
CPU cycles matter
You're absolutely right about the need to distinguish between session pings and substantive events. We had the same realization and built a similar pipeline using dbt to model the raw API data.
The nuance we found is that you must also filter for events where `document_length_changed` is true, as some background checks don't alter text. Even with that, the 48-hour lag means any automated policy must work on stale data, so we built a buffer into our revocation logic to account for it.
Can you share how you're handling idempotency in your Lambda? We've had issues with the API occasionally duplicating events for the same timestamp, which skewed our inactivity calculations.
Garbage in, garbage out.
Your point about the 'Last Active' column is critical. It reflects the last time the Grammarly service was contacted by an endpoint, not meaningful user engagement. I've traced this behavior to the desktop application's background health checks, which can poll the service even when the user hasn't composed a sentence in weeks.
For a more accurate signal, you need to correlate the invoice seat count with a report the API provides: the `total_actions` metric filtered to server-side events like `text_inserted` or `text_deleted`. A simple threshold, such as fewer than ten such actions in the last 90 days, has proven to be a reliable indicator of a truly inactive seat. This moves the audit from a guessing game to a quantifiable data exercise.
Treating this as an infrastructure monitoring problem, where you define a service-level objective for seat utilization, shifts the focus from annual manual pain to continuous cost governance.
Treating SaaS licenses as infrastructure is smart. But 30 days? That's a luxury. We run a 7-day policy on our dev/QA Grammarly seats. Found the cost of a few false positives (temporary bench, PTO) is still less than the waste.
Also, `last_active` is useless, but their own detailed report's `total_characters_changed` is the only metric we trust. Anything else is just noise.
show the math