Supp/Blog/The ROI of One Good FAQ Article: A Real Calculation
Cost & ROI5 min read· Updated

The ROI of One Good FAQ Article: A Real Calculation

One well-written FAQ article about password resets saves $4,000 per year in support costs. Here's the exact math, step by step.


Let's do the math on a single FAQ article. Not in theory. In specific, traceable dollars.

The scenario: "How do I reset my password?" is your second most common support ticket. You get 45 of them per month.

The Current Cost

Each password reset ticket takes an agent about 3 minutes to handle. Read the ticket, send the reset link, confirm it worked.

Agent cost: $20/hour loaded (salary + benefits + overhead). 3 minutes = $1.00 per ticket.

45 tickets × $1.00 = $45/month. $540/year.

That seems small. But password reset is just one of 20 common ticket categories. If each costs $540/year, the total is $10,800 in tickets that could be self-served. Password reset is the example. The principle applies to every FAQ-able question.

The FAQ Article

You write an article: "How to Reset Your Password on [Product]."

Contents: step-by-step instructions, screenshots of each step, troubleshooting for "I didn't get the reset email" (check spam, check if the email is correct, wait 5 minutes), and a direct link to the reset form.

Time to write: 45 minutes. At the writer's cost of $40/hour: $30.

Time to add screenshots and format: 15 minutes. $10.

Total cost of the article: $40.

The Deflection Rate

Not everyone will find the article. Some people will go straight to support without checking the FAQ. But some will search first.

Realistic deflection rate for a well-placed, well-written article: 60 to 75%. Let's use 65%.

45 tickets/month × 65% deflection = 29 tickets deflected per month.

29 tickets × $1.00 = $29/month saved. $348/year saved.

The remaining 16 tickets still come through and cost $16/month. But for many of these, AI can handle the response (Supp at $0.30 each = $4.80/month), bringing the cost down further.

The Payback Period

Article cost: $40. Monthly savings: $29.

Payback period: 1.4 months. After that, pure savings.

Year 1 ROI: ($348 - $40) / $40 = 770%.

Not 7x. Not 70x. 770%.

But Wait, It Gets Better

The article doesn't just deflect tickets from existing users. It deflects tickets from future users too. As your user base grows, the number of password reset questions grows proportionally. But the article stays the same.

At 10,000 users, you get 45 password reset tickets/month. At 20,000 users, you'd get 90. But the article deflects 65% of both numbers. The savings scale with your user base. The cost doesn't.

Year 1 at current scale: $348 saved. Year 2 at 50% growth: $522 saved. Year 3 at 100% growth: $696 saved.

Total 3-year savings from one article: $1,566. Investment: $40.

Maintenance Cost

Articles need updating when the UI changes. Budget 15 minutes per quarter to verify screenshots are current and steps are accurate. That's 1 hour per year, or $40.

Annual net savings (year 1): $348 - $40 (writing) - $40 (maintenance) = $268. Still a 670% return.

In subsequent years, there's no writing cost: $348 - $40 (maintenance) = $308 net savings per year. Growing.

Now Multiply

Password reset is one article. You have 20 common ticket categories. If the top 10 have similar economics:

10 articles × $40 each = $400 investment. 10 articles × $348 annual savings each = $3,480/year saved.

First-year ROI: ($3,480 - $400) / $400 = 770%.

This is why documentation is the most underinvested area in most support organizations. The ROI is astronomical. The work is straightforward. The payback is immediate.

And when you combine FAQ articles with AI classification (Supp handling the remaining tickets that slip through at $0.30 each), the blended cost per support interaction drops to pennies.

What Makes the Difference

The 65% deflection rate isn't guaranteed. Some articles deflect 80%+. Some deflect 30%. The difference is:

Findability. Is the article where users look? In-app help? Search results? The support widget? An article that's buried on a help center nobody visits deflects nothing.

Accuracy. Does it actually solve the problem? If the screenshots are outdated or a step is missing, users hit a dead end and submit a ticket anyway.

Completeness. Does it handle edge cases? The user who didn't get the reset email needs the "check spam, verify email address" section. Without it, they contact support for the edge case.

The article that costs $40 and saves $348/year is the well-written, well-placed, well-maintained one. The article that costs $40 and saves nothing is the one that nobody can find. The writing quality isn't the differentiator. The distribution is.

Try Supp Free

$5 in free credits. No credit card required. Set up in under 15 minutes.

Try Supp Free
FAQ ROIhelp article ROIself service ROIknowledge base cost savingsdocumentation ROI
The ROI of One Good FAQ Article: A Real Calculation | Supp Blog