Angshuman Rudra
← Back
Business models№ 005
Teardown

Google Workspace Add-on Portfolio

Does a portfolio of tiny utilities beat one ambitious product?

A portfolio of small, focused Google Workspace add-ons and Chrome extensions that automate repetitive tasks for business professionals — mail merge, scheduled reports, form notifications, file auditing, document generation. Each add-on solves one specific pain point inside tools people already use every day (Gmail, Sheets, Forms, Drive). The model is indie micro-SaaS: low build cost, recurring subscription revenue, organic discovery via Google Marketplace and Chrome Web Store. Reference: Amit Agarwal (labnol.org, Google Developer Expert) has built 8+ of these and turned it into a sustainable solo business.


Problem statement

Business professionals spend hours on tasks that should be automated — mail merge in Gmail, generating contracts from Google Sheets data, scheduling spreadsheet reports, auditing who has access to shared Drive files. Native Google Workspace doesn't solve these. Third-party SaaS is overkill and expensive. A focused add-on that does one thing well, inside the tool they already have open, is the right fit.

ICP (who exactly has this problem)

  • Operations managers and executive assistants who send bulk personalized emails
  • Finance and legal teams generating repetitive documents (invoices, contracts, agreements) from spreadsheet data
  • Marketing teams scheduling recurring reports out of Google Sheets
  • IT admins auditing Google Drive access at small-to-mid companies
  • Google Workspace power users who know the platform deeply but hit its limits constantly

Market and TAM

Google Workspace has 3 billion users. Even targeting the 1-5% of business power users = 30-150M addressable users. Google Marketplace has built-in distribution — users search for add-ons inside the product. Chrome Web Store is a second distribution channel. Market is proven: Mail Merge for Gmail (Mailmeteor, GMass, Yet Another Mail Merge) all have significant paid user bases. Document automation (Portant, Autocrat) has paying customers. This is a crowded but large market where niche execution wins.

Alternatives (how people solve this today)

  • Zapier / Make — works but requires knowing what to automate and costs more
  • Dedicated SaaS tools (Mailchimp for mail merge, DocuSign for docs) — expensive, over-engineered
  • Manual work — the default for most small teams
  • Other Workspace add-ons — exist but most are poorly maintained, bad UX, or compliance-questionable

GTM angle

Google Marketplace is the primary distribution — users actively search for solutions inside Workspace. SEO is secondary (long-tail "mail merge gmail" type searches still have volume). Build one add-on, get it to 1,000 paying users, use that install base as the audience for the next one. Each add-on cross-promotes the others. The portfolio compounds — Amit Agarwal's model exactly.

How it works

  • Pick one high-frequency pain point in Google Workspace (start with mail merge or document generation — proven demand)
  • Build a Google Apps Script add-on or Chrome extension solving exactly that problem
  • Publish to Google Marketplace + Chrome Web Store
  • Charge $5-15/mo per user or a flat annual license
  • Iterate based on reviews, add one new add-on every 2-3 months
  • Each new add-on installs cross-promote the others

Riskiest assumption

Google Marketplace discovery is enough to drive installs without a marketing budget. If organic Marketplace search doesn't convert, you need SEO or paid acquisition — both cost time/money that undercut the micro-SaaS model. Validate by checking install counts and review velocity on existing competitors in the Marketplace before building.

Open questions

  • Which specific add-on to build first? Highest demand + lowest competition in Marketplace?
  • Apps Script vs. full Chrome extension — Apps Script is faster to build but has limits; extension is more powerful but harder
  • Pricing: per-user subscription vs. flat team license vs. freemium?
  • How much of this can be built with Claude Code in a single Saturday session?
  • Does this conflict with or complement the existing studio projects, or is it a separate track entirely?