Wanted to sanity check a view with you: MCP matters product-wise, but not as a standalone pricing unit. My take is SaaS companies shouldn’t monetize MCP itself. It’s a connectivity layer, and customers don’t buy “protocol access” - they buy the value it unlocks. So the monetization likely shows up in: - premium AI layers — paid add-ons / tiers with custom agents, integrations, context, admin controls, or workflow automation - usage-based pricing — credits, actions, outcomes - seat expansion / plan upgrades - pull-through to core product usage So my thesis is: don’t monetize the protocol; monetize the value created through it. Curious what others are seeing: - what usage patterns are real? - how are you packaging it? - what are customers actually paying for?

We just shipped our first public PricingSaaS Skill. It's called Pulse Market Map Over the past couple weeks, hundreds of people have used the PricingSaaS MCP to do research, and one of the most common use cases is competitive intelligence. With Pulse Market Map, you can do competitive research that used to take hours (or days) in minutes. Here's how it works: ▶ PricingSaaS MCP is the intelligence layer — it connects your AI tool directly to the pricing data we're tracking across thousands of SaaS companies. ▶ Pulse Skills are the action layer -- they sit on top of the data and provide instructions for specific, executable workflows to make it immediately actionable. Pulse Market Map takes any SaaS category and generates a full competitive landscape report in minutes: → Every major player, segmented by tier → Pricing models and packaging details → Key patterns across the market → Strategic insights you can actually use You can install the Skill here: https://lnkd.in/ekbiep7J I also recorded a step-by-step tutorial to make setup easier. Would love to hear what you build with it — drop your results in the thread. And if anything feels off, please tell me. This is the first of many Skills and your feedback shapes what we build next 💪🏻

https://www.clay.com/blog/introducing-clays-new-pricing

Pricing is one of the hardest things to get right as a business owner. Most of us start too cheap.Some go too expensive too fast.Others realize later they were undercharging for years. Looking back, my biggest lesson with pricing has been how much it affects who you attract, how profitable you are, and how seriously customers take you. So I’m curious from other operators here: What pricing mistake taught you the biggest lesson in business? Could be: • Charging too little• Raising prices too late• Not charging for something you should have• Overpricing early 👇 Drop your experience in the comments.

Hey all 👋 We launched the PricingSaaS MCP beta last week and the feedback + experiments so far have been 🔥 One thing we’re seeing quickly is that people start with:“Cool, I can connect tools to pricing data…” Then the next question becomes: “What can I do with it?” That’s where Claude Skills come in. If you’re new to them, the simple mental model is: - MCP = tools - Skills = recipes PricingSaaS MCP gives you data + knowledge tools, and Skills let you chain those tools into repeatable workflows — so you can basically run analyses or reports on demand. Example: I built and ran pricingsaas-report-builder skill on Slack’s pricing → https://share.pricingsaas.com/1772731424/slack-pricing-report-2026-03.html I’ve attached the pricingsaas-report-builder Skill to this post—feel free to grab it, try it, and remix it. Curious: - Are you using Claude Skills yet? - What kinds of Skills are you building (or wish existed)? Would love to see what people are experimenting with. 🚀