Salesforce's three tiers meet a five percent upgrade rate
Core, Advanced and Max list at $195, $395 and $550 with named credit pools, and five percent of Sales and Service users have moved up so far.
Salesforce / Product coverage
Salesforce Platform
Source-linked reporting organized by product, platform, and the topics that connect them.
Latest coverage
Salesforce's named agents are only as safe as your permissions
Rebecca Wettemann's read on Salesforce's named agent roster turns on one condition an admin can test, that permissions are correct today.
Salesforce names six trust layers and two need proof
Salesforce's newsroom post lists six trusted capabilities behind its agent platform. Trusted agency and trusted actions are the two an architect has to test.
Salesforce names a headless meter and leaves the price blank
Salesforce's August 31 rate card carries a Headless Platform Interaction usage type priced TBA, and the two narrower rows it replaced are gone.
Certinia's agent count and the move to fixed-bid work
Certinia went from 10 packaged agents in April to 24, and the bigger change is Salesforce-native firms quoting fixed bids instead of hours.
Buyers expect headless Salesforce access to cost more, not less
Buyer research on 20 interviews found most already reach Salesforce outside its UI, and three quarters of those modelling it expect to pay more.
Tottenham cut 35 systems to one, and identity was the hard part
Tottenham Hotspur consolidated about 35 fan-facing systems onto Salesforce. The harder work is the one Rob Pickering names in passing: identity across touch points.
Salesforce's outage started with an internal login service
Salesforce says requests stalled on an internal login service. Authentication is the dependency most continuity plans never wrote down.
Salesforce says every job now has a builder component
Salesforce Ben reports almost 20,000 staff are in roles that did not exist a year ago, and that every role now screens for a builder component.
The TSA number inside Salesforce's Missionforce year one
Salesforce says TSA's Ace agent resolves 96% of roughly 100,000 monthly traveler conversations without escalation. That rate deserves a second look.
Salesforce's Koa puts CRM reasoning inside the model
Salesforce claims three times fewer errors on CRM actions for Koa. That figure comes from Salesforce's own CRM benchmark, not an independent one.
Salesforce's Agentic Work Unit is a budgeting problem
Salesforce bills agent work in Agentic Work Units, and one business outcome can consume wildly different numbers of them. Your renewal needs a forecast.
Siemens' Agentforce rollout is a governance test, not a win
Siemens is routing 2,500 monthly leads across 132 countries through two Agentforce agents, and the real test is quality control at that scale.
Claudeforce's 37 skills turn a preview into a permissions problem
Salesforce put a number on Claudeforce at Dreamforce 2026, 37 sales skills running through an MCP server in Claude, and that number is a permissions question first.
AIforce claims to replace the UI. The admin's work just relocates.
Salesforce framed AIforce at Dreamforce 2026 as AI replacing the CRM interface. For the admin who built what's underneath it, the question is where that logic goes next.
Job-ready Agentforce agents need a defined handoff between jobs
Salesforce's job-ready Agentforce agents each own one function. When orchestration passes work between them, your team must define what crosses and who owns it.
Salesforce's Trusted Context is the real boundary for agents
Salesforce's six-part enterprise AI model lists Trusted Context first. Our read: what an agent can see and understand is the limit of what it may do.
What an Agentforce agent needs before it can run for weeks
Salesforce's new long-horizon runtime lets Agentforce agents pursue goals for weeks. These are the run-level controls the post leaves for you to ask about.
What Salesforce's AI Control Plane needs to explain one action
Salesforce's AI Control Plane will observe agent behaviour and outcomes. Explaining a single action needs a per-call record the post never describes.
Winter ’27 longer-running agents need a named lifecycle owner
Salesforce says Winter ’27 agents run whole workflows across channels. A run that lasts days outlives your change window, so someone must own it.
Winter '27 puts governed CRM data under every agent
Salesforce's Winter '27 post rests autonomous workflows on governed CRM data. Here is what governed has to mean before an agent runs a case end to end.
Winter ’27 cross-channel agents redefine a closed case
Salesforce says Winter ’27 agents carry a case across voice, Slack, and email. Closed now means every channel is settled, and your status field can't say that.
Winter ’27 gives you six weeks, so build the calendar today
Salesforce’s Winter ’27 post is dated August 31 and goes live October 12. Here is how to turn its fifteen items into owners, sandbox dates, and a freeze.
Claudeforce prebuilt skills carry someone else's sales process
Salesforce in Claude ships 37 prebuilt sales skills. Each one encodes a definition of deal health and pipeline review that your org may not share.
Claudeforce should leave permission ownership inside Salesforce
Salesforce says an admin connects Salesforce in Claude once and permissions are managed centrally. Whose identity each action runs under is the question to ask.
Claudeforce solves the read path and leaves you the write path
Salesforce in Claude reads CRM and Slack data through one admin connection. Governing the writes, where business rules and side effects live, is the hard part.
What Claudeforce has to preserve when sellers work in Claude
Salesforce says Claudeforce routes actions through its rules. Here is what the trust boundary must still carry when a seller never opens Salesforce.
What the Claudeforce open beta asks of a Salesforce team
Salesforce says Claudeforce moves from select pilots to open beta in September 2026. What a Salesforce team should settle before sellers connect Claude to CRM.
Analysis and architecture
Designing a Salesforce sharing model that still scales
Salesforce sharing only ever adds access, and the platform stores the result. How to set the baseline, the hierarchy and the rules so growth stays affordable.
Why Salesforce Release Updates break things, and who owns them
Seasonal releases mostly add capability. Release Updates change platform behaviour your configuration already depends on, and enforcement arrives either way.
The integration owner role is better than it sounds
An integration belongs to neither system team, so it goes unowned. What the owner role really involves, and why it is a stronger career position than it looks.
Salesforce Data Cloud earns its place next to the action
Data that drives segmentation, routing or an agent belongs next to the action. Data that only feeds a report is a second copy you pay to keep.
Movers break the identity lifecycle across business apps
Provisioning is the easy part. Transfers add access and almost never remove it, and every application keeps entitlement in a model of its own.
Six release cycles and the dates you cannot move
Winter '27 lands October 12, the Release Planner retires November 15, Brazil is arriving and 2026R2 is already live. Six vendors, one team calendar.
Salesforce seasonal releases and your sandbox preview window
Winter '27 is generally available October 12, 2026. If your test sandbox was never on a preview instance, refreshing it is the only way onto one.
The Service Cloud Case decisions you cannot undo later
Record types or separate objects, contacts who exist nowhere, entitlements you may not need. The Case model choices that fix what you can report on for years.
Service accounts are the least governed identity you run
Integration accounts miss every joiner and leaver process. Give each one a named owner, a readable name, narrow scopes and a rehearsed rotation.
Identity architecture when you run two Salesforce orgs
When a company runs more than one Salesforce org, single sign on is the easy part. The gap audits find sits in deprovisioning across two login domains.
Why the Salesforce single-org debate has no clean answer
A decision framework for splitting a Salesforce org, and an honest look at what the split really costs once you're running two systems instead of one.
The real difference between a connector and an integration
A connector gets a record from one system to another. An integration owns what happens when the record gets rejected, and most sync projects fail without that part.
Related guides
How two departments agree on one number and keep agreeing
Two correct figures for the same measure differ on timing, population or attribution. Find which one, write the definition down, then name an owner.
A Salesforce sandbox estate you can test a release in
Preview status belongs to the instance rather than a setting, so the sandbox you test a seasonal release in has to be planned months before the notes land.
What Agentforce actually is, and where it stops
Agentforce agents are handed a job rather than a script, bounded by topics and instructions, and they see exactly what the user they run as can see.
How to run a Salesforce permission audit that sticks
A working method for auditing Salesforce profiles and permission sets, and removing the access you find without breaking someone's Monday.
Negotiating a multi-year SaaS renewal
Before a three-year SaaS renewal call, pull your own usage data, read the vendor timeline pressure for what it is, and decide what discount is worth the lock-in.
Small integration contracts for Salesforce and ServiceNow
Name the business event, send only fields the receiver acts on, version when meaning changes, and write down what happens to duplicates.