01 · Automation
Free first conversation · No obligation · You own the code
Sound familiar? Tell us which one on WhatsApp (opens in a new tab) and we'll suggest where to start.
Triggers that move, validate and route rows between sheets and teams: on edit, on form submit or on a schedule.
Summary views built from protected source data, with filters for owners and managers instead of copies for each person.
Formatted PDF or email reports generated and sent on a schedule, to the right people, with the right numbers.
Google Forms or web forms that create records, assign owners, send confirmations and notify the team.
Invoices, quotations, certificates and letters produced from sheet rows as branded PDFs, saved to Drive and emailed.
Pull from and push to Stripe, Shopify, HubSpot, WhatsApp, accounting software or any REST API.
Automations run inside your own Google Workspace. We request only the OAuth scopes each script needs, and API keys are stored in your project's properties, not in ours.
Apps Script has execution time limits and daily quotas. We batch reads and writes, use locks where two people can trigger the same job, and design long jobs to resume rather than fail halfway.
We normalise the sheet first (one row per record, stable IDs, protected ranges) so the automation has something reliable to work on.
Every job writes to a log sheet: what it did, when, and what it skipped. When something looks wrong, you can check without calling us.
Typical stack
01 · Education & research
The Research Desk (our own operations)
The Research Desk coordinates clients, specialists, deadlines and invoices every day. We turned the Google Sheets workbook behind it into an automated system with team, client and admin portals, without moving the data off Google Workspace.
No. If Sheets is working for your team, we automate around it. When a workload genuinely outgrows it (concurrent editors, row counts, permissions), we will tell you and show what a move to a database would involve.
You do. Scripts live in your Google account, and you receive commented source code and a written handover explaining every trigger and setting.
Yes. We start with a short audit of the existing scripts and triggers, then fix, refactor or rebuild depending on what we find.
It depends on how often the task runs and how long it takes by hand. During the study stage we list each manual step with its frequency, so you can see the time involved before you approve anything. We don't quote savings we haven't measured.
Yes, if it's designed for it. We read data by header name rather than fixed column letters, validate inputs, and protect the ranges that scripts depend on, so normal day-to-day edits don't break anything.
We work inside your Google account with the access you grant, request only the permissions each script needs, and you can revoke our access at any time. We're happy to work on a copy of the sheet first if you prefer.
Yes. Common examples are Stripe, Shopify, HubSpot, WhatsApp, accounting software, Gmail and any service with a REST API. Data can flow in on a schedule, when something happens, or both ways.
Yes. Recipients, templates, rates, deadlines and similar values live in a settings tab, so your team can adjust them without touching code.
After a short study of your process we send a written scope with fixed deliverables, timeline and price. Nothing is charged before you approve it; payment is typically 50% to start and 50% on delivery.
You do. Code, accounts and documentation are handed over in your name once the project is paid.
Next step
Tell us the process that eats your team's time. We'll reply with what we'd automate first, how, and roughly what it would cost to run.
Free first conversation · No obligation · NDA on request