How does adding AI change the upkeep cost?

AI APIs may add usage charges. Include setup, maintenance, subscriptions and connected services in the estimate, then check current provider rates and measure a small sample before choosing a limit.

Whose AI API key should be used?

For production apps, have the customer supply their own AI account key. Usage is billed directly to them, so cost is transparent and the builder never absorbs someone else's bill. Demos run on the builder's key with a call cap.

Does using AI send data outside Google?

Yes. Calling AI sends that text to an external server such as OpenAI or Google. Mask or exclude sensitive data like personal, contract, or medical information before sending, and keep a human approval gate on the output.

How Much Does Adding AI Cost? Estimate Usage Before You Build

A request is filtered before leaving for an external AI service; a human reviews its draft, while separate customer and builder key paths show who receives the usage bill. — Visual guideFilter unnecessary or sensitive fields before an AI call, then let a person approve the draft. Usage follows the key owner: a customer key bills the customer; a builder key is for capped demos.

Conclusion first: A small Apps Script workflow may fit within your existing account and quotas, but that does not make setup or maintenance free. An AI API can add usage charges alongside subscriptions or other connected services. For a first estimate, how about measuring a small sample with the intended model and a spending limit?

What to include in the estimate

Check the whole workflow: account subscriptions, quotas, connected services, setup and maintenance. If an AI API is involved, check its current billing terms too. A low API bill alone does not establish the total cost.

The three things that set the cost

Model, volume and frequency multiply into the monthly AI bill; the key owner decides who is billed

Takeaway

Model — check current provider rates and try a small sample before choosing.
Volume — cost scales with the number of characters processed. Longer input and longer output cost more.
Frequency — calls per day × length per call. That product is your monthly bill.

I cannot give a reliable monthly figure without the provider, model and workload. A small sample can help estimate input, output, retries and call frequency. Compare that estimate with the current billing terms before agreeing on a budget.

Whose key — the most important operational call

Calling AI needs an “API key,” and usage is billed to that key. Whose key you use decides who carries the cost.

Setup	Who pays usage	When
Customer’s key	Customer (their own AI account)	Recommended for production. Matches “build once, own it”; cost is transparent
Builder’s key	The builder	Demos and trials only. Always cap the usage

For a production app, having the customer enter their own AI account key is cleanest. Usage bills straight to them, so the builder never absorbs someone else’s costs by accident. For a public demo, run a light model with a hard call cap.

Where the data goes

Text is filtered inside your Google account, sent to an external AI server, and a person checks the draft before anything is sent

Calling AI sends that text to an outside server (OpenAI, Google, and the like). It’s the first point where data that lived only inside your Google account passes outside it.

Keep the human approval gate

Don’t auto-send or auto-execute AI output without a person checking it. Especially for customer-facing wording, amounts, and outbound email, keep a step where a human looks first. AI drafts fast; judgment and responsibility stay with a person. That one gate prevents the wrong-send accident.

Ideas to try in a small pilot

Don’t add AI where rules already work. Fixed classification or templates don’t need it.
Don’t re-call on the same input. Store a result once and reuse it (caching).
Default to a light model with a call cap. Reserve the top-tier model for the few items that need it.

Before you add it

Which AI feature — summary, translation, classification, or draft?
Expected calls per day and length per call?
Whose key — the customer’s or the builder’s?
Any sensitive data? Is this content OK to send outside?

With these answers, you can estimate the monthly usage up front.

In one line

Include setup and maintenance as well as any subscriptions, connected services and AI usage. Maybe start with a small measured sample, then agree on limits and who pays each bill before connecting real data.

Questions?

Wondering “what would my AI feature actually cost per month?” — just ask. I’d nudge you to wire it up yourself, but if you’re short on time, I also build these.