How much to charge for a Google Sheets automation
How much to charge for a Google Sheets automation comes down to a floor and a ceiling you can calculate. The floor is your estimated hours times your rate. The ceiling is the yearly value of the manual work the automation removes, plus any tools it replaces. Your quote sits between the two. The typical job is a business that already runs on a spreadsheet: form responses that need sorting, a weekly report someone builds by hand, invoices or reminders sent from rows, data copied in from another app every morning.
I am not giving you a market dollar figure. A script that formats new rows and one that pulls from three APIs, cleans the data, emails a report and handles failures are different jobs. One number would be noise. Your rate and the client's numbers will get you a real one.
The pricing trap with Sheets is that the client thinks of it as free. They already have the spreadsheet, and Apps Script has no subscription bill. So they compare your quote with nothing. Your job is to move the comparison to the hours their team spends on the sheet every week. This is where Claude Code earns its place: it writes and tests the Apps Script, the data cleanup and the API calls quickly, and with Google's clasp tool you can keep the script in a local folder under version control instead of editing it in the browser.
Calculate your floor and ceiling
Run this before you name a price. Every input is yours or the client's, so you can show the working in the proposal.
The Google Sheets automation calculation
| Number | How to get it | Who supplies it |
|---|---|---|
| Floor | Your estimated hours for each line in the quote, plus a buffer you choose for edge cases and revisions, times your hourly rate | You |
| Time value per year | Hours per week spent copying, sorting, checking and sending from the sheet, times 52, times what an hour of that person's time costs | Client |
| Spend replaced | What they pay per year for tools, add-ons or contractors the automation takes over, if any | Client |
| Cost of a miss | Only if they can point to real examples: a reminder that never went out, a report built from stale data, a row copied twice | Client's own history, your judgment |
| Ceiling | Time value plus spend replaced, plus the miss line only if it is documented | Calculated |
If the floor is above the ceiling, the automation will not pay for itself in a year. Say so and offer a smaller version, such as automating only the weekly task that eats the most hours.
Check the account limits before you quote
Apps Script has no bill, but it has quotas, and they decide your design. Quotas are per user and reset 24 hours after the first request. They are also different for a consumer account such as gmail.com and a Google Workspace account. Find out which one the client has in discovery, because it changes what you can promise.
Apps Script limits that shape a Sheets automation
| Limit | Consumer account | Google Workspace account |
|---|---|---|
| Triggers total runtime | 90 min / day | 6 hr / day |
| Script runtime | 6 min / execution | 6 min / execution |
| Custom function runtime | 30 sec / execution | 30 sec / execution |
| Email recipients per day | 100 / day | 1,500 / day |
| URL Fetch calls | 20,000 / day | 100,000 / day |
| Triggers | 20 / user / script | 20 / user / script |
Two of these change the price. The 6-minute cap per run means a big job has to be split into batches that pick up where the last one stopped, which is more work than a single loop. The daily trigger runtime is the one that bites: when a triggered script runs out, it fails with the message Service using too much computer time for one day. A sheet that syncs every few minutes on a consumer account can hit 90 minutes long before the client notices anything is wrong. These limits can change without notice, so design with headroom.
Size the sheet as well. A spreadsheet holds up to 20 million cells. A log tab that gets a row on every run grows forever, so either archive old rows on a schedule or quote the archive as its own line.
The CCC Sheet Quote
Six parts of a Google Sheets automation quote
| Part | What it prices | Question to ask the client |
|---|---|---|
| Process map | Every step, every tab, every decision, written up and signed off by the owner before the build | Walk me through one row from the moment it arrives to the moment nobody touches it again |
| Scripts and triggers | The Apps Script functions, the triggers that run them, and batching where a job could pass the 6-minute cap | When does this need to happen, and how fast after the data arrives? |
| Data cleanup and connections | Formatting, deduplication, and any API calls in or out of the sheet | Show me the messiest row you got last month |
| Error handling | What each script does when a run fails, a quota runs out or an API is down, and who gets told | If this stops for a day, who notices first, and how? |
| Limits and headroom | The runtime and email estimate against the client's account limits, and the archive plan for growing tabs | Is this a Google Workspace account or a personal one? |
| Handover and tuning window | A walkthrough, notes on each script and trigger, and adjustments after the first month of real data | Who will own this once it is live? |
Error handling is your anchor line. A triggered script that fails does not announce itself on the sheet. The run is recorded on the My Executions page with a Failed status, and nobody looks there unless you build a notification. Price the alert as its own line and show the client what they will see when something breaks.
Install the triggers under the client's account
This is the ownership point most freelancers miss. Installable triggers always run under the account of the person who created them. If you create the trigger, every email the script sends goes out from your account, the runtime counts against your quota, and a teammate on the client's side cannot see the trigger at all. When you hand over and leave, the automation is still tied to you.
- Keep the spreadsheet and the script in the client's Google account, and have the client's owner create the triggers, or create them from an account the client controls.
- Write the account that owns the triggers into the proposal, so nobody finds out by accident six months later.
- Agree the date your edit access ends.
Testing has its own catch. Script executions and API requests do not fire triggers, so submitting a form response from code does not run the form's submit trigger. Test with real submissions through the form, and put that test run in your definition of done.
Always quote the tuning window
A Sheets automation meets reality in its first month of real data. Someone renames a column the script depends on, a busy week pushes the trigger runtime closer to the daily limit, or a form starts collecting a field nobody planned for. If you have not quoted for that, you fix it for free while the client wonders why they paid.
Put a fixed tuning window in the first proposal, next to the build price. Say what it covers: fixing broken runs, adjusting to renamed columns, and a check of the execution history after the first full month. Say what it does not cover: new sheets, new scripts and new processes. For ongoing work, offer a retainer. How to price a maintenance retainer covers the structure.
How to present the Google Sheets automation quote
- Lead with the outcome in the owner's words. One line on what changes, such as the Monday report sitting in everyone's inbox before anyone logs in, then the price.
- Offer three options. A starter that automates the single busiest task, a standard that adds error alerts and the full process, and a full version that covers the related sheets with a longer tuning window. Make the middle one the clear best value.
- Show your calculation. Put their own hours and tool spend in the proposal, next to the limits check, so they see the design was sized for their account.
- Itemize it. Process map, scripts and triggers, cleanup and connections, error handling, limits and headroom, then handover and the tuning window. That gives the client a line to trim instead of a reason to say no.
- Take a deposit and tie the rest to milestones, with the signed process map and a full test run as two of them. How much deposit to charge covers the schedule.
Skip hourly on the invoice, even though hours set your floor. Why I stopped charging hourly for AI builds explains why. If the client is not sure what they need, sell paid discovery first. Client discovery questions before you quote has the questions, and automating spreadsheets with Claude Code shows the build side.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How much should I charge for a Google Sheets automation?
Work out a floor from your estimated hours times your rate, and a ceiling from the manual hours it removes per year plus any tools it replaces. Quote between the two and itemize each part, including error handling and a tuning window.
Does Google Apps Script cost money?
Apps Script has no separate subscription, but it has daily quotas per user. Triggers get 90 minutes of total runtime a day on a consumer account and 6 hours on a Google Workspace account, and each run stops at 6 minutes.
Should I charge per script or per hour?
Neither. Charge a fixed price for the project, itemized by part, then a monthly retainer if the client wants ongoing changes. Your hours set your floor, but they do not belong on the invoice.
Whose Google account should the automation run under?
The client's. Installable triggers run under the account of whoever created them, so emails go out from that account and runtime counts against its quota. Have the client's account own the spreadsheet, the script and the triggers.
What happens when an Apps Script automation hits its limit?
The script throws an exception and the run fails. A triggered script that uses up its daily runtime fails with the message Service using too much computer time for one day. Build an alert so the client knows when it happens.
Can Claude Code help build a Google Sheets automation?
Claude Code can write and test the Apps Script, the data cleanup and the API calls, and with Google's clasp tool you can keep the script in a local folder under version control. You still own the process map, the client conversations and the sign-off on error handling.
Last reviewed by Duncan Rogoff on November 18, 2026


