Who this is for
Businesses whose real operating system is a set of spreadsheets: quotations, stock, attendance, project trackers, client lists. If someone on your team spends hours each week copying between sheets, formatting a report or chasing an approval by email, that work can usually be automated inside the tools they already know. This sits within marketing and business automation and is often the cheapest answer to a problem that looks like it needs new software.
The advantage over Zapier or Make is cost: Apps Script runs inside your Workspace at no extra charge and with no per-task pricing, which for a Nepali business avoiding a USD subscription is frequently the deciding factor. The disadvantage is that it needs writing and maintaining, so it should be documented well enough that another developer can pick it up.
What I build with it
- Reports that build themselves. Data pulled from Google Ads, GA4, Search Console or Meta into a Sheet on a schedule, then formatted and emailed or pushed to a dashboard: see reporting automation.
- Form-driven workflows. A Google Form submission that creates a record, notifies the right person, generates a document and schedules a follow-up.
- Quotation and document generation. A row in a Sheet becoming a formatted PDF quotation or invoice from a template, emailed automatically: see sales and quotation automation.
- Approval flows. A request that emails an approver, records the response, and moves the item forward or back with an audit trail.
- Data cleaning and consolidation. Several sheets merged, deduplicated and normalised on a schedule instead of by hand.
- Gmail automation. Labelling, routing, canned replies to categories of enquiry, and extraction of data from structured emails into a sheet.
- Reminders and escalations. Overdue tasks, expiring documents, renewals due, chased automatically.
- Internal tools. A Sheet with a custom menu and sidebar becomes a usable application for a team that already lives in spreadsheets: see internal tools and dashboards.
The limits worth knowing
- Execution quotas. Apps Script has daily runtime and trigger limits, generous for most business use and a real ceiling for heavy data processing.
- Not a database. Sheets handle thousands of rows comfortably and hundreds of thousands badly. Past that point the answer is a proper database, and I will say so.
- It is code. Someone must be able to maintain it. Everything I write is commented and documented, and where a no-code platform would serve you better long-term, I recommend that instead: see n8n.
- Google authorisation is required, and scripts that access data need explicit permission, which is worth understanding before deployment in a business with strict data rules.
How a build runs
- Watch the manual process and time it, since the business case is the hours it consumes.
- Decide the platform honestly. Apps Script where it fits, n8n or Make where the flow spans many external services.
- Build in a copy of your live sheets, never against production data.
- Error handling and notification, so a failure is visible rather than silent.
- Deploy, with the trigger schedule documented.
- Handover including commented code, a written explanation and a walkthrough with whoever will own it.
What you receive
- Working scripts inside your own Google Workspace.
- Commented source code that you own.
- Error handling with notifications.
- Written documentation of what each script does and when it runs.
- A walkthrough with your team.
Build pricing is on request; see packages. There is no platform subscription: it runs inside the Workspace you already pay for.
Next step
Describe the spreadsheet task that eats the most time on the contact page. Those are usually the quickest builds with the clearest return.
