Automation

Google Sheets, Document & Data Automation

If someone in your team spends the first hour of every day copying numbers between a sheet, an email and a system, that hour is a workflow. I build the collection, validation, merging and filing so the data arrives where it belongs, in the shape it should be in, without anyone retyping it.

  • Apps Script, Sheets, Airtable, n8n and Make
  • Validation before data lands, not after
  • Setup quoted on request

Who this is for

Businesses running on spreadsheets that have grown past what a spreadsheet should do: a daily sales sheet updated from three sources, a supplier invoice folder someone types into a ledger, a client sheet that is copied and renamed every month, a report that exists because one person merges five files by hand every Monday. This is one of the builds under marketing and business automation services, and it is usually the cheapest one with a visible daily payback.

It is not a database migration project. Where the real answer is a proper system rather than a better sheet, I will say so and point at internal tool and dashboard development instead of automating a structure that should not exist.

What gets automated

  • Collection. Form submissions, emailed attachments, WhatsApp-submitted photos, exports from your CRM, ad platforms and accounting software, all landing in one structured place on a schedule instead of being downloaded by hand.
  • Extraction. Invoices, receipts, purchase orders, CVs, bank statements and ID-free application forms turned into rows, with low-confidence fields flagged for a person rather than guessed. The model side of this follows the rules on AI automation services.
  • Validation. Format checks, required fields, duplicate detection on the right key, range checks on amounts and dates, and a quarantine sheet for anything that fails. Cleaning data after it lands is far more expensive than refusing it at the door.
  • Merging and reconciliation. Two sources matched on a common key with the differences reported, which is what most manual monthly work actually is.
  • Document generation. Contracts, certificates, offer letters, reports and invoices produced from a template and a row, as PDFs, filed in the right Drive folder with the right name, and emailed or sent on WhatsApp.
  • Filing and archiving. Consistent folder structures and naming, so finding last year’s document does not depend on who saved it.
  • Scheduled outputs. The Monday report built and delivered before Monday, covered further on automated marketing reports and dashboards.

What I deliberately do not automate

  • Statutory accounting entries. Data can be prepared and pushed into accounting software, but the books are maintained by the people responsible for them.
  • Silent correction of bad data. A workflow that quietly fixes what looks wrong will eventually fix something that was right. Failures are quarantined and reported.
  • Scraping sites that forbid it, or collecting personal data from sources that did not consent to it.
  • Storing identity documents and card numbers in spreadsheets. If a process needs them, they stay in a system built for them.
  • Automating a sheet nobody trusts. If the current numbers are wrong, the first job is finding out why, not scheduling them.

How a build runs

  1. Watch one real cycle. The daily or monthly routine, done by the person who does it, while I record every click. The gap between how it is described and how it is done is where the requirements actually are.
  2. Fix the structure before automating it. One header row, one record per row, no merged cells, no colour as data, no totals inside the data range. This step is boring and it is the difference between a workflow that survives and one that breaks in week three.
  3. Agree the system of record for every field: which source wins when the sheet and the CRM disagree.
  4. Build in a copy of your real data, including the messy historical rows, then run old and new side by side for a cycle and compare the outputs line by line.
  5. Add validation and alerting so failures surface immediately, with a quarantine location and a named person who clears it.
  6. Hand over with documentation, a version of the script or scenario your team can read, and training on how to add a column without breaking the workflow.

What you receive

  • The scripts, scenarios and sheets in your own Google or automation accounts, with no dependency on me.
  • A restructured, documented data layout with a data dictionary explaining every column and where it comes from.
  • Validation rules, a quarantine sheet and an alert routine with a named owner.
  • Version history and a backup routine, so a bad run can be rolled back.
  • Documentation, a recorded handover and optional monthly support for changes as the process evolves.

Pricing pointer

Setup is quoted on request; a single sheet workflow, for example form to validated sheet to generated PDF, sits at the lower end of the range. Multi-source reconciliation with document extraction, generation and filing sits higher, and restructuring a badly built existing sheet is often a third of the work. Maintenance is quoted on request; Airtable or similar subscriptions are paid in your own name. Where the work spans many tools rather than many files, see workflow automation.

Next step

Send the spreadsheet, or a screenshot if it holds sensitive data, and tell me what a person does to it each day. I will come back within four business hours with what can be removed entirely, what should be restructured first and a fixed price.

Frequently asked questions

Do you use Apps Script or a tool like Zapier?

Whichever is cheaper to run and easier for your team to maintain. Apps Script is free, fast and ideal for work that stays inside Google Workspace. n8n, Make or Zapier make sense when several outside services are involved or when a non-developer needs to see the logic. Many builds use both, with Apps Script doing the sheet work and a platform handling the connections.

Can it read scanned invoices and PDFs?

Yes, with the caveat that accuracy depends on scan quality and layout consistency. Fields the extraction is not confident about are flagged for a person rather than guessed, and the workflow is tested on a sample of your real documents, including the worst ones, before anyone relies on it. Handwriting remains unreliable.

Our spreadsheet is a mess. Is that a problem?

It is the normal starting point and part of the job. Merged cells, colour used as data, totals inside the data range and several tables on one tab all have to go before automation is dependable. Restructuring is done on a copy, with the old sheet left intact until the new one has run correctly for a full cycle.

What happens when someone edits the sheet by hand?

Sheets stay editable, because forbidding that never works. What changes is that automated ranges are protected, edits to structural rows raise a warning, and the workflow validates rather than assumes. Where a manual edit would genuinely break things, that column is moved out of reach and exposed through a form instead.

Can it push data into our accounting or CRM system?

Yes, where the system has an API or accepts a structured import. The workflow prepares and validates the data and either writes it or produces a file for a person to review and import. For accounting, I default to preparing rather than posting, because the people responsible for the books should be the ones entering them.

How long does a build take?

A single-sheet workflow goes live in about a week. Multi-source reconciliation with extraction and document generation takes three to five weeks, most of it spent on data structure and on testing the historical rows that do not follow today's rules.

Ready to talk about your project?

A free 30-minute call, a straight answer about what would move the numbers, and a written proposal within 48 hours if we are a fit.