Mintlify Analytics Adds Savings to Show Time and Money Docs Teams Save

Why Mintlify built Savings

According to Mintlify, documentation teams often struggle to show how their work translates into business results without the right metrics. The company points to its own State of Knowledge report, in which 47% of teams said they have not measured the impact of their documentation.

Mintlify Analytics already covers Traffic, Assistant, Search, Automations, User engagement, and Feedback. Savings builds on that data to answer a different question: what value Mintlify brings to a team, including teammates who do not use the product directly. Neha Halebeed, who wrote the announcement for Mintlify, says numbers that back up the positive feedback from users make it easier to report on and support the platform.

The Savings section shows the time saved from automations and assistant usage, as well as money saved from assistant conversations.

How the numbers are calculated

Mintlify describes the money calculation as the simpler of the two. It uses an industry-standard cost of $12 per deflected assistant conversation. A conversation counts as deflected when the assistant answers the question and it does not turn into a support query, which would have cost the team time and therefore money.

Time saved required more thought, according to the company, because there is no standard in the market right now. Mintlify invites other teams to use its reasoning and make it the standard.

• For every merged pull request created by an automation, Mintlify evaluates the lines of code generated by the PR.
• It then places the PR in a t-shirt size bucket: small, medium, or large.
• Based on the bucket, it assigns a rough time savings.

Mintlify says it chose buckets over a per-line figure because a line-by-line approach would not give a picture that anyone on a team could easily decipher. Buckets, it argues, let people quickly gather the impact of the time saved.

Only automations that are merged count toward time saved. If a PR is not merged, the company says, it was not able to save the team time.

What comes next

Mintlify says it plans to convert time saved into money saved as it learns how accurate the valuation feels to customers. That conversion would be based on the time an equivalent action would take, factoring in the agentic era and review time.

The company is also building Attribution analytics, which would let teams see the value their Mintlify site brings to the team and to customers. Mintlify is asking users what they would like to see in Analytics next and directs feedback to its roadmap.

For documentation teams, Savings offers a way to put figures behind the value of their work, using a stated method that they can inspect. The time estimates are rough by design, and Mintlify itself describes them as a valuation it will refine based on customer feedback.