Uses

Tools of the trade.

Everything I use to run client projects — no affiliate links, nothing I don’t touch weekly. Every item here earned its place by shipping real work.

01 — Where client systems actually live

Automation stack

My production workhorse for Workspace automation — developed locally in VS Code via clasp, versioned in git, deployed through CI.

Sheets as a database, Gmail as a mail engine, Drive as a file pipeline. Most "expensive SaaS" needs are three formulas and a trigger away.

For teams that must own their workflows visually. I pick per project — my rule of thumb lives in a blog post.

The glue for real-time triggers and scheduled scrapes inside Manifest V3 extensions.

02 — Daily drivers

One editor for Apps Script, Svelte and PHP — the clasp + Vite combo makes Workspace code feel like real engineering.

What this site and my client portals are built with. Prerendered, fast, and a joy to refactor.

For client codebases that already run on them (ERP dashboards, US startup work). The framework is the client’s choice; the quality bar is mine.

Still the fastest path for classic CRUD backends — restaurant management systems and job portals in production.

03 — Boring on purpose

Every client deployable lives here — global edge, no servers to babysit, free tier that outlasts most side projects.

CLASP deployments, linting and build checks run on every push. If it deploys manually, it will break on vacation.

Auth/realtime for portals; plain MySQL where the client’s host already runs it. Databases are a utility, not a religion.

04 — The unglamorous layer

Every discovery call books itself — the free audit link you see all over this site.

590+ orders on Fiverr taught me scoping discipline; Upwork clients taught me documentation. Both still feed the pipeline.

My CRM, project tracker and invoicing ledger. The automation engineer’s dirty secret: the best tool is the one the client can read.