Skip to content
TRDThe Research Desk, home

01 · Automation

Business automation for the work nobody should be doing by hand.

Copying rows, rebuilding reports, sending reminders, re-typing orders. We automate the repetitive, rule-based work around your team, mostly inside the Google Workspace and tools you already pay for.

Free first conversation · No obligation · You own the code

§ 01Point of view

Automation that survives contact with a real business

  1. 01

    Fix the data before the flow

    Automations fail on messy inputs. We give every record an ID, a single home and validation before we automate what happens to it.

  2. 02

    Automate the rule, keep the decision

    Systems do the chasing, copying and calculating. People keep the approvals and judgement calls, with everything they need in front of them.

  3. 03

    Nothing fails silently

    Every job logs what it did. When something can't complete, a named person is told why and what to do.

  4. 04

    Settings, not code

    Rates, recipients, templates and deadlines live in a settings sheet or admin screen your team controls.

§ 03Trade-offs

Apps Script, no-code or custom code?

Apps Script, no-code or custom code?
CriterionGoogle Apps ScriptZapier / Make / n8nCustom application
Best forTeams whose data already lives in Google WorkspaceConnecting SaaS tools with simple, linear flowsComplex rules, many users, customer-facing access
Running costIncluded in Google WorkspacePer task or per run; grows with volumeHosting and database; predictable
LimitsExecution time and daily quotasBranching logic and error handling get awkwardHigher build effort up front
OwnershipScripts in your Google accountFlows in your platform accountCode in your repository
§ 04Proof

Case studies

§ 05Process

From brief to handover

  1. 01Stage

    Brief

    You describe the problem in your own words: a form, an email or a call. We ask about the process, not just the feature list.

    Written brief

  2. 02Stage

    Study

    We look at the real material: your sheets, current tools, sample data and the people involved. Most scope mistakes are avoided here.

    Process map

  3. 03Stage

    Scope

    You receive fixed deliverables, a timeline and a price. Nothing is charged and no code is written until you approve it.

    Scope & quotation

  4. 04Stage

    Build

    Work happens in stages with a link you can click through, not a status report. Changes are discussed against the scope, openly.

    Staging link

  5. 05Stage

    Handover

    Source code, documentation and credentials in your accounts, plus a walkthrough for the people who'll use it.

    Handover pack

§ 06FAQ

Common questions

01What should we automate first?

The task that is repeated most often, follows clear rules and causes the most damage when it's late or wrong. That's usually intake, reminders or reporting. We rank candidates by time saved and risk removed before quoting anything.

02Will automation work with our existing Google Workspace?

Yes. Most of our automation runs inside your own Google Workspace using Apps Script, so there's no new platform to license or learn.

03What if our process changes later?

Rules that change often (rates, recipients, deadlines, templates) are kept in a settings sheet or admin screen so you can adjust them without editing code.

04How long does an automation project take?

Most automations are delivered in 2–4 weeks from an approved scope. Larger multi-step workflows take longer; your scope states the timeline.

05Do we need to pay for Zapier, Make or other tools?

Not necessarily. Much of our automation runs on Google Apps Script, which is included in Google Workspace. If a paid platform is the better fit, we explain the running cost before you approve anything.

06What happens if an automation fails?

Every job logs what it did. If something can't complete, a named person is alerted with the reason, and the step can be retried or handled by hand. Nothing fails silently.

07Is it safe to give you access to our Google account?

We request only the permissions each script needs, work with the access you grant, and you can revoke it at any time. Credentials and API keys stay in your accounts.

08Will you train our team?

Yes. Handover includes a walkthrough for the people who'll use it and written documentation of every trigger, setting and schedule.

Next step

Tell us what's slowing you down.

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