Back to Blog Home

Measuring the ROI of an AI-Powered Company Brain

Two professionals shaking hands over a desk with a laptop and documents

To take a defensible ROI case for a company brain to the CFO, count only the dollars that move. Hours saved are capacity, not savings, so present them as capacity unless a budget line changes. With illustrative numbers, 2 hours a week for 100 employees at a fully loaded $50 an hour is $10,000 a week, or $520,000 a year. Pick one workflow whose baseline already sits in a system, subtract what wrong answers and upkeep cost, and treat any figure from a vendor calculator as a hypothesis.

Hours are capacity, and dollars need a budget line

The usual calculation multiplies hours saved by an hourly cost, as in the example above. That figure is the value of freed capacity and an upper bound at best, because a salary does not shrink when someone searches less. We recommend presenting it as capacity and counting dollars only where a budget line moves: a hire or contractor you no longer need, a paid queue that shrinks, or a ramp-up that shortens for a role with a measurable output. Say what the freed hours will be used for, and expect the CFO to ask.

The same discipline applies to estimates you did not make yourself. A vendor's calculator is a seller's hypothesis. Espresso AI's sign-up page, for example, leads with a "Get a savings estimate" button for Snowflake and Databricks spend. Whatever the product, an estimate from a seller is a starting hypothesis, and the baseline in your own systems is the number you can defend.

Pick a workflow whose baseline sits in a system

Choose the one or two workflows where the brain intervenes and where the "before" number can be pulled from a system of record, then record four weeks of it before launch. Surveys and self-reported search time are useful as color, but they are estimates that can be argued with, so let them back a number and never be the number.

GroupBaseline to pullWhere it lives
New engineersDays from start date to first merged pull request, and mentoring hours per hireGit host, calendar
Support and successAverage handling time, and escalations to senior agentsHelpdesk
SalesDays from start date to first qualified meeting or first closed dealCRM
HR and operationsRoutine requests per week and time to close themInternal ticketing
EveryoneQuestions posted in the help channel and sent to named experts, for the topics the brain coversChat export

Count interruptions at the source: the questions that still reach a person on the topics the brain covers, per week, before and after. A thumbs-up on an answer measures whether it looked right and does not show that a person was spared, so do not call it a deflection rate. Define each workflow by the task it completes, the way Stripe's documentation is organized around jobs such as accepting payments online or selling subscriptions, so that every metric counts a task finished and not a document opened.

Subtract what wrong answers and upkeep cost

Most ROI models list benefits and stop. Two costs belong in the calculation. The first is upkeep. AWS's explanation of RAG says retraining a model on your own data is expensive and that retrieval is the cheaper way to give it new information, which puts the running cost in the retrieval pipeline and in keeping the pages current: the same page treats stale source data as ongoing work, with documents and their embeddings updated on a schedule or in real time. Count the owners' review hours as the main cost line next to the license.

The second is wrong answers. Subtract their cost: price one wrong answer per topic, such as the refund honored by mistake, the access granted too early or the hour of rework. Multiply by the wrong-answer rate on a fixed test set and by the number of questions you expect, then subtract the result, with the license and the upkeep, from the benefit. If a topic's errors cost more than its answers save, take that topic out of the assistant's scope. An ROI model that leaves out this term will look better on paper than the assistant performs.

Track from day one

Do not wait until the end of the year. Review the questions the assistant could not answer every week with the page owners, because each one is a page to write or fix, and the documentation team's time is spent against a ranked list and not against guesswork. Show leadership a one-page monthly view of three numbers, the human-handled volume, the ramp-up time and the wrong-answer rate, next to the cost, and re-baseline when the company's strategy changes what the brain is for.

Two failures erase the return. If the assistant gives outdated information, people go back to asking colleagues, so answer only from current, owned pages and show the source with every answer. If it ignores permissions and leaks HR or executive material, the damage outweighs any productivity gain, so it must never use a document the person asking cannot open.

Take one workflow to a six-month review

Pick one workflow from the table, pull four weeks of its baseline, price one wrong answer on its most common topic, and run a pilot with a small, measurable team. After six months, compare the current numbers with the baseline, convert hours into dollars only where a budget line moved, subtract the license, the upkeep and the cost of wrong answers, and put the result in front of leadership with the assumptions written out.

Topics

Related posts

Your team’s knowledge, answered in Slack

Add the Kipwise Agent. It answers from your pages with the source, and asks before it changes anything. 7-day trial, no card needed.