Make Workspace do the admin.

More of your operations than most owners suspect. Real examples from the pattern book: intake forms that create tracked jobs; Sheets acting as the operational database for quotes, jobs, assets and time; Docs generating quotes, contracts and reports from live data; Gmail routing and answering the repetitive mail; Calendar handling bookings, crew scheduling and reminders; Drive filing everything to a convention automatically. Individually they are conveniences. Wired together, they are a business system — the diagram above is not aspirational, it is Tuesday.

Google’s built-in automation layer — JavaScript that runs inside your Workspace account, on Google’s infrastructure, with native access to Sheets, Docs, Gmail, Drive, Forms and Calendar. It is what turns “six separate apps” into “one connected system”: the form submission that generates the quote, the sheet edit that emails the update, the Friday trigger that builds the report. It costs nothing extra to run, lives in your account under your permissions, and — because it is plain JavaScript — any competent developer can maintain what we build. No black boxes.

Sometimes dedicated software wins, and we say so — full accounting, regulated recordkeeping and heavy multi-user products are not Sheets jobs. But a striking share of small-business software spend buys things Workspace already does: another subscription for forms, another for approvals, another for asset tracking, each with its own login, its own per-seat fee, its own training curve, your data on its servers. Building on Workspace means no new licences, no new logins, everyone already trained, and you own the system outright. The honest comparison is on this page’s cost-of-ownership band — and where a dedicated product genuinely earns its fee, our recommendation says buy it.

Different layer. Zapier and Make are excellent third-party bridges between separate products, billed per task, running on their servers. Apps Script lives inside Workspace: it reaches deeper into Sheets, Docs and Gmail logic, handles custom rules those platforms cannot express, runs at no per-task cost, and keeps data inside your Google account. When your workflow spans outside products, we use the right bridge — sometimes that is n8n or a direct API. When the workflow is Workspace-to-Workspace, which for many small businesses is most of it, native is faster, cheaper and more private.

It runs under Google’s own permission model, which is the safest place available: every script has an owner, every scope (what it may touch) is explicit and reviewable, and access can be revoked in one click. We deploy with the narrowest permissions each workflow needs — the quote generator touches templates and the quotes folder, not your whole Drive — test against copies before touching live data, and hand over code you can read and audit. Nothing leaves your account for a third-party server, which is an argument Workspace-native automation wins over almost every alternative.

Nothing dramatic, by design. The scripts live in your account, not ours; the documentation explains what runs when in plain English; the code is standard JavaScript any developer can pick up. This is a deliberate contrast with the industry pattern of automations that die with their consultant. If we stopped working together tomorrow, every workflow keeps running, and your next developer inherits a documented system rather than an archaeology project.

You own it; we configure what the project needs and hand back the keys. Where an engagement touches domain administration — user provisioning, group policies, sharing defaults, retention — we set it up with you, document what was chosen and why, and make sure an owner-side admin understands the panel. We are happy to stay on call for admin questions, but Workspace tenancy is like your domain name: it should never live in a vendor’s hands, including ours.

Real ones, and we design around or away from them. Apps Script has daily quotas (emails sent, runtime) that a normal small business never meets but a mass-mailing scheme would. Sheets is a superb operational database into the tens of thousands of rows, and the wrong tool at hundreds of thousands. Heavy simultaneous editing of one record set, regulated books of record, and customer-facing apps with accounts all belong in purpose-built software. Part of the service is telling you which side of those lines your workflow sits on before anything is built.

Small, sharp and expandable. We walk one process with whoever runs it, build against a copy of your real Sheets and Drive, deploy with tight scopes, watch the first live runs beside you, and hand over the documentation. Typical first projects: intake-to-quote, job tracking with a per-person view, document generation, or the Monday report that builds itself. Most clients then add a second and third workflow to the same backbone — the system grows by accretion, each piece paying for itself before the next.

Usually. Half our Workspace enquiries start with “the person who built our sheets left”. We audit what exists, document what it actually does (often the first documentation it has ever had), repair what is fragile, and either stabilise or rebuild depending on what the audit shows. Undocumented automation is technical debt with a friendly face; the rescue engagement converts it into something owned, understood and maintainable.

For real business use, yes — Business Starter or above. Paid plans bring the shared drives, admin controls, and higher execution limits that reliable workflows lean on, plus your own domain on mail. Some patterns technically run on free personal accounts, but building business operations on a personal Gmail is a governance problem waiting for a bad day. If you are on the fence about tiers, we will tell you exactly which features the proposed workflows need and which tier carries them.

Genuinely, within its lane. Apps Script can serve small internal web apps — a crew job board, an approval console, a stock-take screen — living at a URL, gated to your domain logins, reading and writing your Sheets. For internal tools used by a handful of people, this is dramatically cheaper than commercial platforms and needs no new accounts. The lane has edges: it is not for customer-facing products or heavy concurrent use, and we will say when your idea has outgrown it. But “a small screen for the team, built on data we already have” is a weekly request here, and Workspace answers it well.

Same discipline, specific venue. Process Automation is platform-agnostic — n8n, APIs, whatever the stack needs. This page is the Workspace-native specialisation of it, for businesses whose operations already live in Google’s tools, where staying native is cheaper, more private and easier to own. In practice we often mix them: Workspace-native for the internal spine, a bridge where an outside system must join in. Start from whichever page matches where your data lives; the first-call conversation is the same honest one.

Fixed per workflow, like our other automation work — and typically at the affordable end of it, because the platform costs nothing extra to run and the integration surface is native. No per-task fees ever accrue; there is no subscription to us unless you want the optional care arrangement. The honest total cost of a Workspace system is the build fee plus the licences you already pay Google — which is precisely why we keep recommending it to businesses that already live there.