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.
Spreadsheet functions and menu actions that put complex logic one click away from the people who need it.
Internal portals and forms served from Apps Script, with Google sign-in and role checks, at no extra hosting cost.
Gmail parsing and templated sending, Drive filing, Calendar scheduling and Docs generation, coordinated from one codebase.
Time-driven and event-driven triggers with locking, retries and resumable batches for long-running work.
Editor add-ons for Sheets and Docs when the same tool is needed across many files or teams.
Audit and restructure of existing scripts: remove duplication, fix quota issues and document what each part does.
We develop locally with clasp and TypeScript where it makes sense, so every change is tracked and reversible.
Batch reads and writes, caching and continuation tokens keep jobs within execution limits as data grows.
Errors are caught, logged and emailed to a named owner instead of disappearing into the execution log.
When a requirement is beyond what Apps Script does well, we say so early and propose the smallest external component that solves it.
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.
Per-execution time limits, daily quotas on emails and URL fetches, and no long-running processes. Most business workloads fit comfortably when the code is written for those limits; we flag early when one doesn't.
For modest traffic and internal or known users, yes, and we have built multi-role portals on it. For public-facing products with heavy traffic we recommend a hosted web application instead.
For larger projects, yes: we develop locally with clasp and TypeScript, keep the code in version control, and deploy to Apps Script. Small scripts can be written directly in the editor if that suits your team better.
Yes. Apps Script web apps can use Google sign-in and check roles from a sheet or database, so different users see different screens and data.
Usually. Timeouts are most often caused by reading and writing one cell at a time or processing everything in one run. Batching, caching and splitting long jobs into resumable steps normally solves it.
Yes. You get commented code plus a written guide to every trigger, setting and scheduled job, and what to do if one fails.
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