Free AI cost audit
See Where Your AI Money Goes, And What You Can Cut Without Hurting Quality.
A vendor-neutral review of the models, prompts and usage behind your AI features, and the AI inside the SaaS tools you pay for. You get a written report like the one below: every finding with its saving, effort and risk to quality.
- 5 working daysfrom receiving your data
- No API keysno code, no production access
- Yours to keepwhether or not you hire us
The sample report
Read The Report Before You Ask For Yours
This is the report you will receive, filled in for Example SaaS Co., a fictional company. Every figure is invented to show the format, so it is not a result or a forecast.
Not a SaaS company? Retail reports break down the same way: Shopify and app add-ons, helpdesk AI charged per resolution, product-description tools and search AI.
AI cost and quality audit
Where Example SaaS Co.'s AI money goes, and what to change
Data reviewed: billing and usage exports, June to August 2026, a list of 11 AI tools and plans, and 25 redacted prompts.
Illustrative sample. Example SaaS Co. is a fictional company and every figure here is invented to show the format. Provis has not yet completed client audits, so none of this is a result.
Contents
What is in this report
- 1Cover and scope1
- 2Contents2
- 3Executive summary3
- 4Where the money goes4
- 5Findings register5
- 6Finding F1 in full6
- 7Prompt recommendations7
- 8Model routing and caching plan8
- 9Keep, and what not to do9
- 10Your data, and the 30-day plan10
- 11Method, limits and confidence11
Executive summary
One page for your CFO
Monthly AI spend
Saving range
Quality risk
The short version. Most of the spend sits in two features: support ticket tagging and the in-app assistant. Both run on a larger model than they need for part of their work, and both resend the same instructions on every call.
Top three actions
| Action | Saving / month | Effort |
|---|---|---|
| Move ticket tagging to a smaller model (F1) | $2,100–2,600 | Low |
| Cache the assistant's system prompt (F2) | $900–1,200 | Low |
| Send fewer retrieved chunks to search answers (F3) | $700–1,000 | Medium |
Saving by finding (midpoint of each range, per month)
Spend breakdown
Where the money goes
Monthly average, June to August 2026, by feature and tool. API costs are volume times each provider's published price on the audit date.
By provider
By environment
Findings register
Six findings, ranked by saving
| # | Finding | Saving / month | Effort | Quality risk | Who |
|---|---|---|---|---|---|
| F1 | Ticket tagging runs on a large model; a smaller one matches it | $2,100 to $2,600 | Low | Low | Your team |
| F2 | The same 1,900-token system prompt is sent on every chat call | $900 to $1,200 | Low | None | Your team |
| F3 | Search answers send 12 retrieved chunks; 5 cover 97% of answers | $700 to $1,000 | Medium | Low | Us |
| F4 | Two tools summarise the same helpdesk tickets | $450 to $500 | Low | None | Vendor |
| F5 | 14 of 60 staff AI seats unused for 60+ days | $400 to $430 | Low | None | Your team |
| F6 | Timeouts retry the whole chain, doubling some calls | $350 to $600 | Medium | None | Us |
Confidence for each finding is on page 11. Savings are ranges because they depend on volume, which changes month to month.
Finding F1
Ticket tagging runs on a large model; a smaller one matches it
Evidence
The change
Saving
Quality check
| Effort | Quality risk | Confidence | Who | Roll back |
|---|---|---|---|---|
| Low 1 day | Low | High | Your team | One config value |
Monthly cost of tagging
How to read a finding
- 1Evidence from your own exportsToken counts and volumes, not estimates.
- 2One specific changeWhat to switch, and what to keep as a fallback.
- 3Savings as a rangeBecause volume moves month to month.
- 4Quality tested on your dataYour past inputs re-run before we recommend anything.
- 5You can check it yourselfA small test before you move all traffic.
Prompt recommendations
Prompt changes, costliest first
Assistant system prompt (F2). 1,900 tokens sent on every call, including 600 tokens of examples the model no longer needs.
Search answers (F3). Retrieve 12 chunks, then send the top 5 by relevance score.
Ticket tagging (F1). Return the tag only, not a sentence of explanation: 40 output tokens become 6.
Routing and caching
Which task goes to which model
| Task | Today | Recommended | Why |
|---|---|---|---|
| Ticket tagging | Large model | Small model, large as fallback | 196/200 same tags |
| Assistant answers | Large model | Keep large model | Quality dropped on the small one |
| Search answers | Mid model | Keep, send fewer chunks | Context is the cost, not the model |
| Staging tests | Large model | Small model or a local open model | No users see staging |
Caching. Cache the assistant's system prompt and the search instructions. About 70% of input tokens on those calls repeat word for word.
Batching. Re-embed the help centre nightly in one batch instead of on every edit.
Open models. At this volume, hosting your own model costs more than it saves. Revisit above roughly 4 times today's tagging volume.
Keep, and what not to do
What earns its cost
| Keep | Why |
|---|---|
| Search answers | Users who search with it find answers faster. Keep the feature; F3 only trims the chunks it sends. |
| Assistant on the large model | Answer quality dropped on the smaller model in the sample test. |
| Helpdesk AI add-on | Drop the duplicate summariser instead (F4). |
What we recommend you don't do
Not covered by this audit
| Code review or security testing | Not part of the audit; we did not see your code. |
| Production systems | No access was given or needed. |
| Vendor contract negotiation | We note renewal dates; you negotiate. |
If your spend is already sensible, your report will say so.
Your data
What we received, and when it is deleted
| Received | Used for |
|---|---|
| Billing and usage exports, June–August | Spend breakdown, findings |
| List of 11 AI tools and plans | Seats and duplicate tools |
| 25 prompts, customer data removed | Prompt recommendations |
Not received, not needed: API keys, passwords, source code, production or admin access, customer data, PHI. Files are deleted within 30 days of this report, sooner on request.
30-day plan
| Week | Do | Who |
|---|---|---|
| 1 | Cache prompts (F2); remove unused seats (F5) | Your team |
| 2 | 10% of tagging on the small model (F1) | Your team |
| 3 | Fewer chunks for search (F3); fix retries (F6) | Us |
| 4 | All tagging moved if agreement holds; drop duplicate summariser (F4) | Your team, vendor |
Method, limits and confidence
How the numbers were worked out
Cost. Token volume from your usage exports times each provider's published price on the audit date. Tool costs from your invoices. The calculation sheet shows every formula.
Quality. Before recommending a cheaper option, we re-run a sample of your own past inputs on it and compare the results. Where quality drops, we say so and recommend keeping the current setup.
| Finding | Confidence | Based on |
|---|---|---|
| F1 | High | 200-ticket re-run |
| F2 | High | Token counts |
| F3 | Medium | 50-question re-run |
| F4, F5 | High | Invoices, seat logs |
| F6 | Medium | Error logs, one month |
Limits. Three months of data; seasonal peaks may differ. Savings assume today's prices and volume. We did not review code or production systems.
What's inside this audit?
- An executive summary with the savings at stake
- Where your AI money goes, by feature and model
- A findings register: saving, effort and quality risk
- Prompt, model-routing and caching changes
- What to keep, and what not to touch
- Your 30-day plan, with method and limits
Document details
- Pages
- 11
- Format
- Last updated
- October 2026
Audit terms
What We Need,
And What We Never Ask For
We need billing exports, a list of your AI tools and a few cleaned sample prompts. We never ask for keys, source code, admin access or customer data.
for your AI spend
We need
- Billing or usage exports from your AI providers
- A list of your AI tools and plans
- A few sample prompts, with customer data removed
We never ask for
- API keys or passwords
- Source code
- Production or admin access
- Customer data or PHI
-
NDA on request.
We sign your NDA before you share anything.
-
Deleted within 30 days.
Your files are deleted within 30 days of the report, sooner if you ask.
-
Vendor-neutral.
We take no commission from any AI tool or provider we recommend.
-
Honest findings.
If your spend is already sensible, the report will say so.
How to redact a prompt. Replace names, emails, phone numbers, order or patient IDs and anything else that identifies a person with placeholders such as [NAME], [EMAIL] or [ORDER-ID]. Keep the instructions and the structure: that is what we review.
Who runs it
Engineers Who
Build And Run AI
A new service, from a team that runs AI in production: on OpenAI, Anthropic, open models on Ollama, Qdrant, n8n and PostgreSQL.
-
Agents MCP server on a live ordering platform
Live in TrueWholesale

-
Product search AI SearchBot for online stores
Live in ProvisCommerce.ai

-
Chat and voice Price and coupon assistant across 1,500+ stores
Live in Gyanee.ai

-
Generative AI Branded social posts from one line
Live in Chitra

Provis Technologies AI Integration services are phenomenal. We have been witnessing growth after the AI automation they have put into our business.
Clutch5.0 · 12 reviews
Google4.6 · 36 reviews
UpworkTop Rated200+ projectssince 2012
Frequently Asked Questions
Questions Before You Request The Audit
What to ask before you share your AI spend with us.
Still unsure? Ask us on WhatsApp or send us your question.
Some teams will want help putting the fixes in place, and the audit is how they get to know us. Whether you hire us is up to you: the report is yours either way.
No. Billing or usage exports, a list of your AI tools and plans, and a few sample prompts with customer data removed are enough. We never ask for API keys, passwords, source code, production or admin access, customer data or PHI.
Each finding states its risk to output quality, so you can see the trade-off before changing anything. Where quality would drop, the report says so.
No. We are vendor-neutral and take no commission from any AI tool or provider we recommend.
A 30-minute call to walk you through it. If you want help with the fixes, we quote that separately. There is no obligation.
- 1We confirm what to sendA short email listing the exports we need, and your NDA if you want one first.
- 2You share the exportsBilling or usage exports, your tool list and a few redacted prompts.
- 3Your report, in 5 working daysFrom the day we receive your data.
- 4A 30-minute walkthroughThe findings, explained. The report is yours to keep.
Rather pick a time yourself?
Book a 30-min call with Vivek SharmaCEO & Founder, Provis Technologies
Contact Us