I think sales leaders should treat agent access as a line item in the CRM order form, written down before the next renewal. Two vendor documents from the past three months show why a blog post or a launch announcement cannot carry that weight.
What the two documents say
On November 17, HubSpot published a post on how it will price headless access. It sets out three tiers. Seats include enough access to do everyday work from Claude or ChatGPT at no extra cost. Agents a customer brings connect through the same APIs as other integrations, and those calls count against the API capacity already in the plan. Work done in HubSpot’s governed environment for agents, such as enriching records and personalizing outreach at scale, is paid for with credits. You can read the full text in the post itself.
On August 19, Salesforce announced an expanded Headless 360, including an MCP server that lets agents in Agentforce, Claude, ChatGPT, Cursor and other platforms discover and invoke Salesforce capabilities. The announcement describes what agents can reach and how permissions and governance carry over. It does not state what agent access costs, and it carries the usual note that pricing and packaging are subject to change.
Neither document is a contract. That is the point of this column.
Why the order form has to carry it
A seat count used to predict a CRM bill. HubSpot’s post shows a vendor splitting use into a seat tier, an API tier and a credit tier, and the line between them depends on what an agent does and where it runs. A rep summarizing open deals from Claude sits in the first. An agent enriching records across a territory sits in the third. If a company buys seats this year and deploys agents next year, the bill depends on a classification the vendor wrote in a blog post and can revise.
That classification is where your forecast lives. A sales operations team that plans for 200 seats and a handful of agents has a number. A team that adds a prospecting agent in the second quarter has a different number, and nobody agreed in advance which tier the new agent falls into. Ask for the answer in writing while you still have a renewal to bargain with.
What to ask for
- A schedule that names each agent action and the tier it belongs to: seat, API capacity or credits.
- The API capacity included in your plan, stated as a number, and what happens when third-party agents reach it.
- The audit record for agent actions, and whether it covers agents that connect through plain APIs or only those inside the governed environment.
- A notice period before the vendor moves an action from one tier to another.
The strongest counter-argument
The best objection is that HubSpot’s structure is generous and already public. Seat-included access from the tools reps use every day is a favorable starting point, and a vendor that publishes its logic invites buyers to hold it to that logic. Salesforce’s note about pricing is standard boilerplate on an announcement, and vendors of both kinds will negotiate when a renewal is on the table.
My answer is that fairness today is not a term. Pricing posts get updated; the HubSpot post itself carries an update date of November 18, a day after it ran. Salesforce says pricing and packaging are subject to change. A buyer who captures the current structure in the order form keeps a favorable reading from drifting, in a market where agent use will grow faster than anyone’s budget line for it.
The layer that decides the outcome
There is a second reason to be exact about what agents may do. Dr. Paramjit “Romi” Chopra, Founder and CEO of MIMIT Health, said in Salesforce’s announcement: “What makes those answers clinically trustworthy is the physician-curated ontology sitting between the data and the agent.” His business is healthcare, and the same logic applies to a sales org. The value of an agent in your CRM depends on the curated layer between your data and the agent: field definitions, permissions, routing rules. That layer is also where the vendor’s metering will sit. Pay attention to who owns it, and put the terms for it in the contract.
For related reading on what a pilot needs before it starts, see our column on setting a CRM data baseline before any sales agent pilot and the piece on judging a sales agent by what the approver sees at the handoff.
Source: HubSpot, “HubSpot is headless. Here’s how we’ll price it”
