Zendesk's pricing is famous for the 'paywall around innovations' pattern: CSAT, SLA, multilingual, advanced AI, and other staples land in higher tiers, and add-ons hit 15-35% of total cost. Teams pay for Suite Growth when their actual feature usage maps to a competitor's mid-tier at half the price. The product reads a Zendesk billing CSV and 30-day usage snapshot, then outputs a tier-fit analysis with side-by-side equivalent plans on Front, Help Scout, Plain, and Kustomer.
builder note Position this as a 'we save you money, take a cut of the first year savings' service, not a $99/mo subscription. CFO buyers love contingent-fee structures, and the analysis itself is mostly a CSV diff. The risk is that Zendesk responds with retention discounts and your customer renews anyway, which is also fine because they paid you to find that out.
landscape (3 existing solutions)
The 'too-high-tier-for-actual-usage' problem applies to Zendesk specifically but the pattern is general (Intercom, Salesforce, HubSpot). Anchor on Zendesk because the complaints are loudest and the add-on tax is most documented. Expand later.
sources (3)
zendesksaas-spendcustomer-supporttier-analysisdowngrade
Salesforce shipped CRM directly into Slackbot in March 2026 with 30 AI features, but it's bundled into Slack Business+ at $15+/user/mo, and the SSO tax pushes a typical 10-person team's effective rate higher. SMBs that wanted chat-native CRM are now stuck choosing between paying Salesforce-tier money for a Slack add-on, hand-rolling a CRM in a Notion DB, or running a real CRM their team won't open. The product is a sub-$5/user chat-native CRM that lives inside Slack, Discord, or Teams as a bot, with a tiny web UI for the admin who actually opens a CRM.
builder note The Salesforce launch is the gift. Use 'the SMB version of Slack CRM' in every headline. Don't try to be Salesforce-feature-complete, target the three jobs (log a deal, log a contact, schedule a follow-up) that 80% of SMB CRM use is. Make it work in Discord and Teams too. Most SMBs aren't on Slack, that's a Salesforce blind spot.
landscape (3 existing solutions)
Salesforce just validated that chat-native CRM is the future and then priced SMBs out of it. The opening is a sub-$5/user product positioned explicitly as 'the SMB version of Slack-native CRM' that works inside whatever chat tool the team already pays for.
Salesforce Slack-native CRM (Slackbot) Locked behind Business+ and the SSO upgrade. SMB-prohibitive for the team it claims to target. The 3-10 person shops cited as the use case can't afford the floor. Pipedrive / HubSpot Free / Folk Web-app first, Slack integration is a notification feed. The actual CRM work still happens in the other tab, which is the original SMB complaint. Spreadsheets and Notion DBs Free, but no Slack-native command syntax for 'log this convo as a deal,' no auto-update from email, no follow-up reminders that arrive where the team already lives. sources (4)
crmslackdiscordsmbchat-native
Zapier's per-task pricing with AI-step multipliers makes a 5-step workflow running 100x/day cost $73/mo vs. ~$10 on Make. The known inflection point hits around 2,000 tasks/month. Make is the technical answer but the UX is fiddly enough that small ops teams refuse it. Self-hosted n8n means running a server, which the same teams refuse. The product is a flat-fee SaaS with Zapier-quality UX, capped by workflow count instead of task count, with explicit support for AI-orchestration steps as first-class citizens.
builder note Don't compete on apps. Compete on the 'migrate-from-Zapier' button. Build one tool that imports a Zapier export, maps it 1:1, and shows the bill delta on day one. The integration catalog gap closes itself over six months if the migration UX is good. Anchor pricing at $99/mo flat, not per task.
landscape (4 existing solutions)
Make is the technical winner and Zapier is the UX winner. Nobody has both at the post-Zapier-but-pre-n8n price tier with explicit AI-step pricing. The wedge is the 2,000-tasks-per-month team that already knows it has outgrown Zapier and is sick of the migration friction.
Make.com Cheapest per-task answer. Module-graph UX punishes ops people who came from Zapier. Adoption stalls at the team-of-five threshold. n8n self-hosted Best price but requires running a server, version upgrades, and Docker. Same teams that wouldn't run their own GitHub Actions runner won't run this. Activepieces, Pipedream Closer to Zapier UX but smaller app catalogs. The 2k-tasks-per-month Zapier customer has 30+ integrations they need, and these tools don't have them all. Lindy Agent-shaped, not workflow-shaped. Different mental model. Doesn't directly replace 'when X happens in Salesforce, post to Slack, update HubSpot, file a Linear ticket.' sources (4)
other https://www.lindy.ai/blog/zapier-pricing "The moment you start optimizing task counts instead of workflow quality, you've outgrown it. For a lot of teams, that inflection point hits right around 2,000+ tasks/month" 2026-04-22 zapier-alternativeworkflow-automationai-orchestrationflat-feeops
Standard SaaS contracts price by seats. They have no language for per-agent attribution, usage ceilings, audit rights, or customer-side budget caps that hard-stop the vendor's meter before the vendor's meter hard-stops them. Procurement teams about to sign the next batch of renewals at ServiceNow, Workday, HubSpot, Salesforce, and SAP need a productized template kit: redline-ready clauses, a vendor-question checklist ('what is your roadmap for agent metering?'), and a benchmark table of what other companies have negotiated.
builder note Sell this as a one-time PDF + Notion template pack, not a SaaS. Procurement people will pay $499 for a doc that prevents a $50K mistake on the next renewal. The trap is trying to be the legal tool itself. Be the boring, lawyer-reviewed checklist that gets emailed around as the standard.
landscape (3 existing solutions)
Multiple major analysts within the last two weeks have explicitly prescribed exactly this product (cloud-style committed-spend clauses for SaaS). The first credible template pack with named procurement leaders endorsing it becomes the de-facto reference. Distribution: FinOps Foundation, ProcureCon, CFO podcasts.
Vendr / Tropic / Sastrify advisory Help you negotiate seat-shaped contracts. Their playbook is still pre-tollgate. The agent-action clauses don't exist in their template library yet. sources (4)
procurementsaas-contractsfinopsai-agentstollgate
Notion's $10-per-1000-credits markup on Custom Agents is roughly 4-6x the underlying model cost for the same Claude/GPT calls. Plus and Free users are locked out entirely. Teams that already pay for Claude or OpenAI tokens want an open-source runner that reads from and writes to Notion (or its competitors) on a schedule, uses their own API keys, supports the same 'Monday morning status doc' patterns, and ships as a single binary or Docker compose with a tiny web UI. Predictable monthly cost: the LLM bill itself.
builder note Don't make it a 'Notion alternative.' Make it an 'agent runner that respects Notion as the canonical store.' The customer is buying back predictable cost, not new features. Ship Docker compose, MIT license, a clean web UI, and one killer recipe (the weekly status doc) prebuilt. The audience is exactly the people running the audit-and-kill console from signal #1.
landscape (3 existing solutions)
Two flavors exist today: workflow tools that can sort of fake it (n8n) and vendor replacements that just relocate the markup (Notis, Taskade). No focused 'BYO-key Custom Agent runner that targets Notion as a system of record' exists. The opening is narrow: anchor on Notion, expand to Confluence/Coda/ClickUp later.
Notis SaaS replacement, still a vendor markup. Doesn't solve the underlying complaint about per-credit billing, just changes the meter. n8n / Activepieces / Pipedream with Notion API Workflow tools that can call the Notion API, but they aren't 'agent-shaped.' You build the prompt-and-write loop yourself, including the credit-style controls. Wide gap between 'can be done' and 'works out of the box like Notion Custom Agents.' Taskade Genesis / Tana Force you off Notion to use them. The customer want isn't 'leave Notion,' it's 'stay in Notion but run agents on my own dime.' sources (4)
notionopen-sourceself-hostedai-agentsbyo-key
Airtable bills the workspace owner per-user when an invitee accepts a workspace invite, with no in-UI warning. Users have reported $2,000+ surprise bills inside the first month after a team-wide invite blast. The product is a thin middleware: route invites through an approval queue, show the projected monthly delta before any seat is created, optionally swap to limited-permission collaborator roles by default, and email finance when the budget threshold is about to break.
builder note Don't try to convince Airtable to fix this, they won't. The wedge is the proxy invite link. Easy to demo in a Loom, easy to viral-share in r/sysadmin and r/Airtable. Charge by seats-prevented-per-month, not per-user, because the buyer is the admin, not the team.
landscape (3 existing solutions)
The pain is well-documented but no one has built the gatekeeper. The interesting wedge is OAuth-into-Airtable + an invite proxy URL the admin shares instead of the native invite link. Same pattern would extend to other surprise-seat vendors.
Airtable native admin panel Shows seat count after the fact. No 'before-accept' preview, no auto-conversion to lighter roles, no budget guardrail. sources (3)
airtablesaas-spendseat-licensingguardrailsops
Intercom charges $0.99 per Fin resolution but a known community-confirmed bug counts AI handoffs to humans as resolved anyway. HubSpot moved Breeze Customer Agent to $0.50 per resolved conversation and Prospecting Agent to $1 per lead on April 14, with no public spec for what counts as 'resolved' vs. 'closed' vs. 'escalated.' Customers running both vendors need a third-party shadow logger that records every conversation, classifies it independently, flags miscounted resolutions, and emits a credit-back-request packet the support team can submit without opening a ticket war.
builder note The hidden moat is the conversation-classification taxonomy itself. Whoever publishes a clean spec for 'resolution vs. handoff vs. escalation vs. abandon' becomes the de-facto standard, the same way OpenTelemetry became the trace spec. Skip seat pricing, charge per disputed dollar recovered.
landscape (3 existing solutions)
Two of the biggest customer-facing AI agent vendors just shipped per-resolution pricing within a four-week window. Neither has a customer-friendly definition or dispute flow. Mid-market support teams running Fin + Breeze together are the natural buyer for a vendor-agnostic auditor.
HubSpot Breeze usage console Brand new, no shipping disputes tooling yet, no public 'what counts as resolved' spec. Customers are flying blind on the unit definition. sources (4)
customer-supportoutcome-based-pricingintercom-finhubspot-breezeaudit
Atlassian is rolling Loom workspaces into its billing system. Every Creator Lite seat (previously free, limited recording) auto-upgrades to a paid Creator seat on the integration date, with only a brief grace period to deactivate users before the charge lands. One team reported a 100x jump because 14 inactive members became 14 paid seats. The product is a guided migrator: snapshot every recording, preserve view-URLs via a redirect layer, update Slack/Confluence/Jira embeds, and land the team on Tella, Vidyard, Bubbles, or self-hosted Cap before the next billing cycle.
builder note The hidden margin is the redirect layer. Loom share URLs are sprinkled across Slack, Notion, Confluence, and email threads dating back years. The team that ships a free 90-day URL forwarder gets the brand recognition, then upsells the actual migration. Don't try to be a video product. Be a migration concierge whose deliverable is 'your old share links still work for 90 days.'
landscape (3 existing solutions)
Atlassian provides the on-ramp, alternatives provide the destination, nobody provides the bridge. Migration windows are short and tied to each workspace's integration date, so the pain is acute and time-boxed. Plenty of teams will pay for a concierge service that finishes the move in a weekend.
Manual download from Loom workspace Single-video MP4 download exists. Bulk export is per-recording, share URLs break, no embed rewrite, no team-transfer flow. Admins are clicking thousands of times. sources (5)
loomatlassianmigrationscreen-recordingsaas-acquisition
ServiceNow's Action Fabric meters every outside-agent action through their MCP server. Workday's CEO publicly endorsed agent metering. HubSpot moved Breeze Customer Agent to per-resolution, Prospecting Agent to per-lead. SAP is blocking unauthorized agents. Datadog capped agent traffic on its MCP. Each vendor will ship its own unit, its own meter, its own definition. No FinOps tool today sees agent activity across these vendors, and finance teams will hear about the spend in retrospect, the way they heard about AWS in 2014. The product is a single-pane view with per-agent attribution, anomaly alerts, and a Reserved-Instance-style commit advisor.
builder note The trap is trying to be Datadog for agents from day one. Start with ServiceNow Action Fabric only (it has a real API, the meter exists, and the customer pain is concrete), prove per-agent attribution and a cap rule, then add Workday and HubSpot. Finout will eventually ship this, but they're a few quarters off the architecture rewrite they admit in their own essay. Window is real.
landscape (3 existing solutions)
Multiple sources within the last two weeks explicitly call out the visibility gap. AWS shipped Cost Explorer four years after charging meaningful money. SaaS tollgates have a similar window opening now, and whoever builds the cross-vendor view first owns the FinOps category one layer up.
Finout / Cloudability / CloudZero Built for AWS/GCP/Azure-shaped bills. Don't ingest ServiceNow Action Fabric, Workday HCM agent meters, or HubSpot per-resolution invoices yet. Finout themselves admit the visibility tool gap. sources (6)
finopssaas-tollgateai-agentsservicenowworkday
Notion flipped Custom Agents to paid metering on May 4 ($10 per 1,000 credits, 30 to 60 credits per run). Workspaces that piled up beta agents on autopilot now need a one-shot tool that ranks every agent by 30-day spend, last decision impact, and trigger frequency, then bulk-kills, demotes, or downshifts cadence before the first month closes. Bonus mode: emit a workspace-wide cap and per-agent caps with diff preview, since Notion's own controls landed late and don't show projected cost.
builder note Don't build another Notion replacement. The non-obvious play is a 30-day, scoped-token, no-DB audit tool: paste an admin token, get a ranked kill list and a one-click cap. Most workspaces will use this once and never again, which is fine, charge $19 and move on. The trap is overscope: building it as a SaaS with seats and a dashboard means you miss the panic window.
landscape (3 existing solutions)
Vendor controls landed on May 5, a day after billing began, with no projected-cost preview. The available 'help' is blog explainers and replacement vendors. No one is shipping a focused, in-workspace audit-and-kill console for the 30-day decision window admins are sitting in right now.
Notion native credit dashboard Shows credits consumed but not last decision impact, frequency-vs-need analysis, or bulk kill. Forces admins to open every agent one by one. sources (5)
notionai-agentsfinopssaas-pricingworkflow