Blog / Small Business Automation

Hiring a Google Apps Script Developer: What to Expect and What to Ask

By Keyona Meeks, Founder, ReRev Labs · Oct 31, 2026 · 8 min read

The short answer: A good Google Apps Script job is small, written down and testable. Before you hire, write what starts the job, what should happen, who checks the result and what happens when it fails. Ask the developer which Google account will own the script, where secrets will be stored, what permissions it will request and what you get back when it is done. Pay against a test on a copy of your sheet, not against a promise.

By the end of this post, you'll be able to:

Write a one-page scope a developer can quote against.
Ask the questions that show whether someone knows how Apps Script behaves.
Name what you should receive at handover.
Decide whether to hire out, build it yourself or skip the script.

You have a Google Sheet or a Google Form that works, mostly. Someone on your team does a repeat step by hand: copy a row, send an email, file a PDF, chase a late answer. You have heard Google Apps Script can do it, and you do not want to learn to code. So you are thinking about hiring someone.

I sell build work, so you should know I benefit if you hire us. Most of this post is about how to hire anyone well, and some jobs are better done by you.

What does a Google Apps Script developer actually do?

They write code that runs inside your Google account and reacts to things in Sheets, Forms, Gmail, Docs and Drive. If you have not seen it, read what Google Apps Script is first. The typical jobs are small: send an email when a row changes, build a PDF from a form answer, copy data between sheets, post a message when a number crosses a line.

That is also what makes hiring hard. The code is short, so the real work is in the details around it: which account runs it, what it is allowed to touch, what happens when it fails and who can fix it later.

When should you not hire anyone?

Some jobs do not need a script, and a good developer will tell you so. Check these first:

A built-in feature covers it. Sheets has notification rules, dropdowns and conditional formatting. Forms can send you a response email. If one of those does the job, use it.
You cannot say the steps. If you cannot explain what happens, in order, to a new hire, a developer cannot code it either. Write the steps first.
The step needs judgment on every item. A person should keep making that call. A script can prepare the information for them. If you are not sure which of your steps to automate first, read what to automate first in a small business.
The real problem is a missing person. If the work is a whole role, compare options in virtual assistant vs automation.

How do you write a scope a developer can quote?

One page is enough. Use these five lines for each job:

Trigger. What starts it? A form submit, an edited cell, a time of day.
Input. Which sheet, tab and columns does it read? Give a sample with fake data.
Action. What should it do, in plain steps? Send, copy, create, mark.
Check. Who looks at the result, and how do they know it was right?
Failure. What should happen if it cannot finish? Who gets told?

If a developer quotes without asking about line 5, that is worth noting. Scripts fail quietly unless someone builds the alert.

For cost framing across a whole business, see how much small business automation costs. I do not quote prices here, because they vary by job and by person.

What should you ask before you hire?

Ask these in writing. The answers matter more than the sales pitch.

Which Google account will own the script?

The script runs as an account, and the limits depend on the account. Google's quotas page lists total trigger runtime of "90 min / day" for consumer accounts and "6 hr / day" for Google Workspace accounts, and a single run is limited to "6 min / execution." It also lists email recipients per day at "100" for consumer accounts and "1,500" for Workspace accounts, and says "All quotas are subject to elimination, reduction, or change at any time, without notice." Source: Quotas for Google Services, checked October 30, 2026.

The plain point: the script should live in an account your company owns, not in the developer's personal account. If it lives in theirs, it stops when they leave.

What permissions will it ask for?

Apps Script works out the permissions from the code. Google's authorization page says "Authorization scopes are determined automatically by scanning the script code," and that "Code that is commented out can still generate an authorization request." It also says users may "see a warning screen saying the app is unverified by Google" when a script uses sensitive scopes and has not been verified. Source: Authorization for Google Services, checked October 30, 2026.

So ask the developer to list every permission the script requests, in words you understand, and why each is needed. A script that only needs to read one sheet should not ask for all of your Drive. Expect to click through an authorization screen the first time you run it.

Where will secrets be stored?

If the script talks to another service with a key or a webhook address, the key should not sit in a cell in your sheet or inside the code. Google's Properties Service is the usual place for it: Properties Service. Ask the developer to say where each secret will live and how you change it.

How will they test it, and on what?

The answer you want: on a copy of your sheet, with sample rows, before it touches real data. Ask what they will run, what they expect to see, and how you can repeat the test yourself. Be wary of "it works on my machine" with no way for you to check.

What happens when it fails?

Ask for a failure alert to a named person, an email that says which row failed. Ask what happens if the script runs out of time. Google's quotas page lists a six-minute limit per run, so a job that loops over thousands of rows needs to be built with that in mind.

Is the code written to run fast?

Google's best-practices page says "Alternating read and write commands is slow," and advises to "read all data into an array with one command." It also says "Using JavaScript operations within your script is faster than calling other services." Source: Apps Script best practices, checked October 30, 2026. You do not have to judge the code yourself. Ask whether the developer reads a whole range at once and avoids a call per cell. A good one will know what you mean.

Who can fix it later?

Ask who maintains it after handover and what that costs, without being pushed to pay for it. The better answer is that the code is readable and documented enough that another developer could take over.

What should you get back at handover?

Ask for these in the contract:

The code, in your account. Not a copy in theirs.
A one-page handover note. What it does, what starts it, where the settings are and where the secrets live.
A list of permissions. In plain words.
The test you ran together. Sample input, expected output, who ran it.
A failure alert. Pointed at a named person on your side.
A list of what you must provide. Access, sample data, a person who can answer questions.

How do you spot a weak proposal?

Look for these:

It promises to "automate everything" without asking what starts the job.
It does not mention testing on a copy.
It asks you to share your personal password. You should share access through Google's sharing tools, not a password.
It stores keys in the sheet.
It does not say who owns the script.
It offers no way for you to check the result.

Where do marketplaces fit?

When I searched "google apps script developer for hire" on October 30, 2026, the results were mostly freelance and talent marketplace pages and a few agency blog posts. I did not review any of them for quality and I do not name them. A marketplace can be a good way to find people. The questions above work the same wherever you find someone. Ask them, and read the answers.

Where does an LLM fit in this?

Developers use AI tools to write the first draft of a script, and that is fine. The part to check is the same either way. A person should read what it does, test it on a copy, and confirm it handles the messy rows. An LLM belongs inside the script only where the input is messy, such as reading a free-text email, and a person should check that output before it goes anywhere that matters. For the rest, plain rules do the job better. My stance: AI writes the code, plain automation runs it, and an LLM shows up only where the input is messy and a person checks the result.

Where this has limits

Google changes its limits. The numbers above are from October 30, 2026 and Google says quotas can change without notice. Check the quotas page before you rely on them.
I have not hired through the marketplaces. I make no claim about their quality.
This is a question list, not a guarantee. A developer can answer every question well and still miss something. Test on a copy.
Contracts are your call. I am not a lawyer. If a contract covers ownership or liability, ask an attorney.
I do not quote prices. Cost depends on the job.

If you have a job in mind, tell us about it on /letstalk. Bring the five-line scope above and a sample sheet with fake data. Do not send passwords or login details.

Frequently asked questions

How do I find a Google Apps Script developer?

Marketplaces, agencies and referrals all work. The method matters less than the questions you ask and the test you require.

What should I ask a Google Apps Script developer before hiring?

Which account owns the script, what permissions it requests, where secrets are stored, how it will be tested, what happens on failure and who maintains it afterward.

Should the script be in my Google account or the developer's?

In yours. If it lives in theirs, it can stop working when they leave or close the account.

Why does the script show an unverified app warning?

Google says users may see that warning when a script uses sensitive scopes and has not been verified. Ask the developer to explain which scope triggers it.

Can I just use AI to write the script myself?

You can try. Test it on a copy of your sheet first and read what it does before you give it access to real data. If the job is small and low risk, this is a reasonable way to start.

What is a reasonable test before I pay?

Run the script on a copy of your sheet with sample rows, compare the result to what you expected, and trigger a failure on purpose to see the alert.

Read next: Questions to ask before you hire automation help works for any automation hire, and build vs. buy automation if you are not sure the custom script is the right spend.