Welcome back to Good Better Best.

Each week, we break down real product, packaging, and pricing moves from leading SaaS and AI companies and share the ideas worth stealing.

This week, Google formally introduced Workspace Studio across all plans. This update is particularly interesting for us. As Workspace customers, we’re considering moving some of our AI workflows there. The question we’re asking (and have been asking regularly lately) is whether or not it makes sense to move any of our AI workflows out of Claude. Below I broke down Google’s packaging strategy, and how we’re thinking about it.

Let’s get to it.

PS. Next Monday, I’ll be joining Dor Sasson, CEO of Stigg, for an AMA to go deep on SaaS packaging. Sign up here.

Last week we observed 100+ changes. The highlights:

Check out more updates on PricingSaaS →

Here’s what was top of mind in Pulse this week:

🔥 Hot Companies

🚨 Hot Topics

Google launched Workspace Studio back in December, but formally introduced it on the pricing page this week:

Workspace Studio allows you to use Gemini to create automated workflows across your apps in minutes. The UI is really nice. You can create a prompt describing what you want to do, then Gemini will build a step-by-step “Flow” to execute the action. For each step, you can customize it to your liking.

This morning, I created two flows that I’m excited to test: one for email follow up, the other for daily news briefings. Here’s what it looks like:

The interesting thing is I already have similar workflows set up in Claude. Because I use Claude so much, I expect the email drafts from Claude will be more tailored to my voice than Gemini. However, Gemini has context to my full inbox, and should be able to use that to draft emails in my voice. We shall see.

The more interesting thing here is that if I use Google for these flows, it gives me tokens back in Claude to use on more interesting work.

This is the tradeoff that has become a constant question for us at PricingSaaS. We run the entire business out of Claude. We’ve built agents that execute all sorts of jobs for our data product and content operation. The image below is of PricingSaaS Mission Control, where we coordinate tasks across our (growing) team of 7 agents.

Given how core these workflows are to the business, the more menial workflows we have to do throughout the day (e.g., email follow up, content calendar admin) feel trivial by comparison. If we can offload those tasks to another product, especially at low cost — there’s serious value there.

Which brings me to how Google is pricing Workspace Studio.

Currently, Google is offering Workspace Studio in every plan at no additional cost. This makes it a no-brainer to test, and gives Google a chance to capture some of our AI workflows. My guess is that Google will continue to bundle this functionality into Workspace going forward, and any increase to the price will go to the subscription fee.

Since Google is one of the few companies directly competing with Claude, it doesn’t make sense for them to position around Claude token preservation, but maybe that’s an opportunity for other companies? Notion immediately comes to mind. I’d imagine using Custom Agents in Notion at $10 per 1,000 credits is cheaper than running those workflows out of Claude, which we’re doing today.

But here’s where I’m stuck. This week, Claude announced higher usage limits for all paid plans:

This announcement makes me question the switching cost of moving these agents into Notion (or Google for that matter). If Claude’s token pricing is close enough, is it worth the time to learn a new agentic workflow tool? For now, I plan to hold tight, and will reassess next time we bump up against our Claude limits.

This post is a bit stream of consciousness, and I don’t have a perfect answer here. I’m genuinely curious how others are thinking about this, and incorporating these tools into their own workflows. All I know is Claude has rapidly become our center of gravity, and it’s forcing us to regularly question our willingness to pay for everything else.

Thanks for reading! If you’re working on monetization and want to learn more about how we help, book time here.

Until next time,

Rob