If your finance team has started asking harder questions about your CRM and AI tool spend, you’re not alone. AI CRM billing models are changing fast, and two developments from October 2026 make it clear that the era of flat, predictable SaaS subscriptions is giving way to something messier – and potentially more expensive – if you’re not paying attention.

The first signal came from HubSpot. The second came from a company most GTM teams still haven’t heard of: Bending Spoons.

HubSpot’s New AI Spend Controls: What Changed and Why It Matters

HubSpot has rolled out a set of billing guardrails specifically designed to reduce budget anxiety around AI agents. The changes are concrete and worth understanding in detail:

• Spend caps on AI credits – customers can now set a ceiling on credit consumption, so an autonomous agent doesn’t quietly run up a bill over a weekend.
• Seat-to-credit swapping – teams can trade unused seats for credits, giving ops leaders more flexibility in how they allocate spend across the stack.
• Pay-as-you-go or flat-rate billing – rather than forcing everyone into a single pricing model, HubSpot is letting customers choose the structure that matches their usage patterns.

These aren’t minor tweaks. They reflect a real tension that’s been building for the past 18 months: companies want to use AI agents in their sales pipeline and customer workflows, but the consumption-based pricing that powers those agents introduces a new kind of financial risk. A flat monthly seat fee is predictable. An AI agent that runs hundreds of tasks per day is not.

For RevOps teams specifically, this matters because AI tool costs are increasingly coming out of the same budget envelope as CRM licences. Spend caps give finance a guardrail; seat-to-credit flexibility gives ops teams a lever. That combination is genuinely useful.

Why AI CRM Billing Models Are Getting More Complex

The shift toward credit-based and consumption-based pricing isn’t unique to HubSpot – it’s a structural change across the category. The reason is simple: AI agents do more per unit of time than a human rep using a traditional CRM, so charging purely per seat undersells the product’s value and underprices the vendor’s costs.

This creates a real problem for go-to-market planning. When your CRM was just a place to log calls and track deals, your monthly cost was basically fixed. Now, if you’re running AI-powered outreach sequences, automated lead scoring, and agent-driven follow-up, usage can spike dramatically during a product launch or a big quarter-end push. That variability has to go somewhere in the pricing model.

The guardrails HubSpot introduced are a direct response to that variability. Smart move. Other vendors will follow.

The Bending Spoons Factor: What $1.08 Billion in ARR Acquisitions Signal

Here’s where things get strategically interesting for anyone thinking about long-term CRM vendor risk.

Bending Spoons – an Italian software company valued at roughly $34 billion – acquired both Airtable and Miro within a 37-day window. The numbers are striking:

Bending Spoons paid 2.7x ARR for Airtable and 2.3x ARR for Miro, totalling $1.08 billion in acquired Annual Recurring Revenue (ARR) for approximately $2.64 billion in enterprise value – signed 37 days apart.

Bending Spoons’ own organic growth sits at around 3%. Its headline 126% growth figure is almost entirely acquisition-driven. That context matters enormously. It tells you this is a company that buys revenue, optimises margins aggressively, and moves on to the next target. Both Airtable and Miro are tools GTM and sales teams use regularly – Airtable for campaign tracking and project coordination, Miro for sales process visualisation and collaborative GTM planning.

What happens to product roadmaps, integrations, and pricing structures when a cost-optimisation-focused acquirer takes over? That’s a question your RevOps team should be asking right now, not after the next price change lands in your inbox.

What This Means for Your CRM and GTM Stack Decisions

These two stories aren’t unrelated. Both point to the same underlying shift: the economics of SaaS tooling are being renegotiated, and the teams that plan ahead will be better positioned than those who don’t.

A few practical considerations for GTM and sales operations leaders:

• Audit your credit exposure now. If you’re using any AI-enabled CRM features – whether in HubSpot, Salesforce, or another platform – find out how consumption is measured and what your ceiling looks like. HubSpot’s new caps are a good prompt to do this across your entire stack.
• Map your tool dependency on recently acquired products. If Airtable or Miro sits inside your go-to-market workflow, it’s worth having a contingency. Not panic – just a plan.
• Revisit your Ideal Customer Profile for tools, not just customers. The same logic you apply when qualifying a prospect – stability, fit, long-term value – applies to evaluating vendors. A tool that fits today might not fit in 18 months if ownership or pricing changes fundamentally.
• Watch Net Revenue Retention signals in vendor earnings reports. A vendor with strong NRR is investing in keeping customers happy. One leaning entirely on acquisitions for growth may be optimising elsewhere.

For a broader look at the tools in this space, the CRM Tools Directory is a useful reference when you’re evaluating alternatives or benchmarking your current stack.

How AI Billing Models Affect Sales Forecasting and Budget Planning

There’s a downstream effect here that doesn’t get enough attention: variable AI billing makes sales forecasting and budget planning harder. Not impossible – but harder.

When your CRM costs are fixed per seat, finance can model them cleanly. When those costs fluctuate based on agent activity – number of emails sent, leads enriched, meetings booked by an AI SDR – your monthly spend becomes a variable tied to pipeline activity. In a big month, costs go up. In a quiet month, they come down. That’s not inherently bad, but it requires a different kind of tracking discipline.

The best RevOps teams will build a usage-to-pipeline correlation model: essentially, how much does it cost in AI credits to move a lead from initial contact to qualified opportunity? Once you know that number, you can budget AI spend the same way you budget Customer Acquisition Cost – as a function of expected pipeline volume, not as a fixed overhead line.

That framing also helps internally. Finance is far more comfortable approving AI tool spend when it’s tied to pipeline output than when it’s presented as a technology cost with no clear return attached.

The Deeper Question: Ownership, Stability, and Tool Trust

Bending Spoons’ acquisition strategy raises a question the SaaS industry doesn’t like to sit with: does it matter who owns your CRM or GTM tooling, as long as the product works?

The honest answer is: sometimes, yes. Ownership affects roadmap priorities, support investment, integration stability, and pricing strategy. A company focused on margin expansion after an acquisition may pull back on the product features that made the tool attractive in the first place. That’s not speculation – it’s a documented pattern in software M&A.

This doesn’t mean you should immediately replace every tool that gets acquired. It means you should pay attention. Check the CRM News feed regularly and watch for changes in support SLAs, pricing announcements, and integration roadmaps. Those are the early signals that an acquisition is moving from “business as usual” to “cost rationalisation mode.”

For teams that rely heavily on collaborative tools sitting adjacent to their core CRM – project tracking, whiteboarding, workflow automation – the Bending Spoons situation is a useful reminder to keep your integration architecture flexible. The less tightly coupled your stack, the easier it is to swap a component when you need to.

One Concrete Action to Take Before Year-End

If you take one thing from these two stories, make it this: run a vendor risk and billing audit before Q1 2027 planning locks in.

That audit should cover three questions. First, which tools in your GTM stack now use consumption or credit-based billing, and do you have caps in place? Second, which tools have changed ownership in the last 12 months, and have pricing or roadmap priorities shifted? Third, what’s your actual cost per qualified opportunity when you include AI tool usage – and does finance know that number?

The CRM Guides section has practical resources on stack auditing and vendor evaluation if you want a structured framework to work through. For deeper metric tracking across your revenue function, the article on CRM Metrics and KPIs: 25 Numbers Every Revenue Team Should Track is worth bookmarking as you build out that picture.

The teams that treat AI billing and vendor stability as strategic considerations – not just IT procurement details – will have a cleaner, more defensible GTM operation going into next year. That’s the actual advantage right now. Subscribe to the CRM Daily Newsletter to stay across developments like these as they happen.