Am I Paying More Just for Mail Merge?

PMM Mindset · April 2026

Most teams pay for the tier. Few teams audit what the tier actually unlocks.

Google Workspace Business Standard costs $14/user/month. Business Starter costs $7. That gap adds up fast across a 50-person org - roughly $4,200 per year.

One feature buried in that upgrade: Gmail mail merge. Native multi-send with personalization fields, built directly into the compose window. No third-party extension. No BCC hacks. No Mailchimp workaround for a simple client update.

The workflow is clean. Build an HTML email with inlined CSS, open it in Chrome, copy the rendered output into Gmail compose, add merge fields, and send. Every recipient gets a personalized message - no forwarding artifacts, no "undisclosed recipients" in the header.

That is a real capability. But here is the question PMMs should ask about every SaaS tier, not just Google's: is the team actually using the features that justify the price?

The Tier Utilization Problem

SaaS companies design pricing tiers to maximize upgrade incentive. They bundle high-value features with table-stakes improvements and bet that one compelling capability - mail merge, advanced analytics, SSO - pulls the entire organization up a tier.

It works. Openview's 2025 SaaS benchmarking data shows tier upgrades account for 35-40% of net revenue retention at PLG companies. The upgrade motion depends on perceived value, not verified usage.

That creates a gap. The buyer upgrades for one feature. The vendor counts on stickiness. The team never audits whether the other bundled capabilities see any use.

PMMs who work on pricing and packaging see this pattern constantly - from the vendor side. Fewer apply it to their own tool stack.

A Framework for Tier Audits

Before the next renewal, run a simple audit. Three questions per tool, scored honestly.

Question 1: Which tier-specific features does the team use weekly? Not "has access to." Not "used once during onboarding." Weekly active usage. If mail merge is the only Business Standard feature the team touches, that is a $4,200/year mail merge tool.

Question 2: Can those features be replaced at a lower tier or with a cheaper tool? Gmail mail merge replaces third-party tools like GMass or Mailmeteor. But if the team was already using one of those on the Starter tier, the upgrade added cost without removing the old tool. Net savings: zero.

Question 3: What is the per-feature cost of staying on the current tier? Divide the tier delta by the number of tier-specific features in active use. If the answer is uncomfortable, the tier is not earning its place.

Why This Matters for PMMs

This is not just a procurement exercise. It is a positioning lesson.

Every PMM building a pricing page should ask: will buyers audit this tier the way we just audited ours? Because sophisticated buyers will. And when they do, bundles that hide one premium feature behind a wall of unused capabilities look like margin extraction, not value delivery.

The companies winning on PLG beyond the free tier understand this. Tier upgrades that stick are the ones where usage expands across multiple features post-upgrade - not the ones where a single feature pulled the buyer up and nothing else stuck.

Product-led companies track feature adoption by tier as a retention signal. PMMs should track the same metric on their own tools as a spend discipline.

The Mail Merge Test

Google's mail merge is a clean example because it is a single, visible feature with a clear tier boundary. Apply the same logic to every tool in the stack:

Tool	Current Tier	Tier-Specific Feature Used	Weekly Active?	Replacement Available?
Google Workspace	Business Standard	Mail merge, 2TB storage	Mail merge: Yes. 2TB: No.	GMass ($20/mo) for merge only
Notion	Team	Permissions, guests	Guests: Yes. Permissions: Rarely.	Free tier + manual sharing
Figma	Professional	Dev mode, branching	Dev mode: Yes. Branching: No.	—
Slack	Pro	History, integrations	Both: Yes.	Tier justified.

The table forces specificity. "We need the paid tier" becomes "we need these two features, and here is what they cost us relative to alternatives."

The Series Ahead

This is the first in a series examining the question every operator and PMM should ask at renewal time: am I paying for this, and am I using it?

Upcoming posts will apply the same tier audit framework to specific tool categories - AI coding assistants, CRM platforms, infrastructure spend. The goal is not cost-cutting for its own sake. It is building the discipline of evaluating build-buy-prompt decisions with the same rigor applied to customer-facing pricing.

Every SaaS vendor designs tiers to maximize revenue. Every buyer should audit tiers to maximize value. The gap between those two incentives is where wasted spend lives.

Next step: Run the three-question audit on your top five tools this week. If even one tier cannot justify itself, you have found budget to reallocate - or a pricing page lesson to bring back to your own product.

PMM Mindset helps marketing leaders sharpen GTM, pricing, and positioning decisions. Book a workshop ->