The tracker is not the hard part. Opening it is.
This started on a coaching call. I was pushing a husband-and-wife team to track their contacts, and we got past whether they should and into how. They suggested a Google Sheet, which is a good instinct — a sheet gives you the history.
But pulling up a sheet every single day is exactly the step that gets skipped. So I suggested a Google Form instead: the form arrives in your email, you enter your contacts, and the entry lands in the sheet on its own. You never go to the sheet to log. It comes to you.
They asked how to build it. I was going to record one Loom for the two of them. Then I figured everybody could use it, so here it is instead.
What I asked Claude for
I described the people, the goal and the emails I wanted. That was the whole input.
I have a husband and wife team committed to 100 contacts a week. Build me a Google Apps Script that sets up a Google Form they fill in each day, a Google Sheet that stores the entries, and a dashboard with a leaderboard showing contacts this week, this month, this quarter and this year against their annual goal. Email each of them every morning with where they stand, email a reminder in the evening if the day has not been logged yet, and send a weekly accountability summary that copies their coach. Before you build anything, tell me what else you would recommend to make it better.
Ask what it would add before it builds
Left alone, Claude will try to build something that proves how smart it is. So I stopped it first and asked what else it would recommend — anything that would make this better. It came back with a few suggestions, I locked a couple of them in, and then I told it to write the code.
What came back was a couple hundred lines of code, none of which I can read. That is fine. My job was to copy it and follow the instructions it gave me.
Where the code goes
- Start a new Google Sheet in your own Drive and name it. Mine is the Jencks Contacts Tracker.
- Open Extensions, then Apps Script. Let the editor finish loading.
- Delete the code that is already there and paste in what Claude gave you.
- Save, then run. It opens on a function called setup, which is the one you want.
- Approve the permissions prompt. Apps Script asks for authorization the first time you run it. Review permissions and approve — that is what lets it email you.
Then you go back to the sheet and watch it build itself.
What it built
A contact target for each person. A leaderboard showing how many contacts each of us has made this month, this week, this quarter and this year, plus progress toward the annual goal. A weekly history. And a chart that graphs performance over time.
It also connected a Google Form to the sheet, so a form entry lands in the sheet and flows straight onto the dashboard.
In the video I seed the sheet with sample entries so the dashboard and the emails have something to show — a target of 50 each, a couple of months of made-up contacts. Those numbers are demo data, not anyone’s real production.
The emails are the part that works
Every morning: good morning, here is the date, here is where you are on contacts this week, here is where your teammate is. One link, straight to the form. That is the whole interaction.
At 6 p.m., if the day has not been logged, another email says so. And once a week, an accountability summary goes out with where you landed — set to copy the coach, which is the part I would not skip.
Build it in your own Drive
I built the demo with Kristi and me as the agents rather than putting that team’s numbers tracker in my Google Drive. The concept is identical either way, but the file has to live where you live — that is what lets it email you.
What you focus on expands
If accountability is where you keep slipping, this is the fix, and it is that easy. Go to Claude, ask for the Apps Script, and put the triggers in place so the reminders and the leaderboard stay in front of you instead of depending on your memory.
Make it a great day, and take it and run.
Three builds that run without you.
Before you build your own.
Do I need to know how to code?
No. Merrill did not read the couple hundred lines Claude produced. You copy it, paste it into Apps Script, save, and run the setup function. The instructions for where it goes come back along with the code.
Why a Google Form instead of just the sheet?
Because opening a sheet is the step that gets skipped. The form link arrives in your email, you tap it and enter the number. The sheet still keeps the history and the dashboard still reads from it, but logging no longer depends on you remembering to go there.
Where does this need to live?
In your own Google Drive. That is what lets it email you, and it keeps your numbers in your own hands. Merrill built the demo with himself and Kristi as the agents rather than putting a team tracker in his Drive.
What does it send, and to whom?
A morning email with where you stand on contacts for the week and where your teammate stands, a reminder at 6 p.m. if the day has not been logged, and a weekly accountability summary. Merrill set the weekly one to copy the coach.
Tell Google you want Kristi’s builds first
Add kristijencks.com as a preferred source and Google highlights new Claude for Agents builds and Take It and Run articles in your Top Stories and AI results.