Salesforce insight for growing B2B teams

Salesforce's AI Coworker Now Costs $50 a Seat. Should You Hire It?

Tue, 10 Nov 2026 13:11:49 GMT

For two years, Salesforce has been selling the idea of AI agents. Last week, it started selling you a coworker. On November 4, Salesforce reported that Agentforce Coworker — the "digital teammate" it launched globally this summer — has passed 185,000 users, with usage up 21-fold in three months. More interesting for mid-market teams: it now has a flat price of $50 per user per month, and over the next few weeks it's showing up where your people actually work — Microsoft Teams, iOS, and dedicated Mac and Windows apps. The AI coworker just stopped being a keynote concept and became a line item you can actually evaluate. Here's what was announced, what it really costs, and how to decide whether your team should "hire" one.

1. What Agentforce Coworker Actually Is

If Agentforce is the platform for building AI agents, Coworker is the colleague who manages them for you. Instead of your team learning which agent handles which task, an employee hands Coworker a business request in plain language — "check on the Acme renewal, it feels shaky" — and Coworker breaks it into steps, pulls the relevant Salesforce records and connected data, coordinates the right agents and workflows behind the scenes, and comes back with results and recommended actions for a human to review.

Salesforce's own example is exactly that renewal scenario: Coworker gathers service history, flags unresolved cases, and drafts the follow-up communications — work a rep would otherwise assemble by hand across five tabs. James Nakashima, Salesforce's SVP of Product Management, summed up the positioning: the goal is "one Coworker that brings the right agents together to get work done," rather than a growing roster of agents your users have to learn to manage.

Two design choices matter for anyone responsible for an org. First, Coworker operates under each employee's existing permissions, sharing rules, and access controls — it can't see anything the user couldn't see. Second, approval and audit capabilities are available for supported operations, so autonomous doesn't have to mean unsupervised. Both points cut two ways, as we'll get to below.

2. What's New in the November Announcement

The headline numbers — 185,000+ users, 21x usage growth in three months — tell you adoption is real, at least among early movers like Fulton Bank (20+ use cases rolled out to roughly 3,000 users) and The Adecco Group (expanding Coworker across 40 countries). But the substance for planning purposes is the rollout calendar.

Available now

Google Workspace and Microsoft 365 connections — Coworker can combine email, calendar, and files with Salesforce data, which is what turns "summarize this account" into a genuinely useful meeting brief or renewal plan.
Skills — reusable workflows your team builds once and anyone can run, so your best rep's renewal-check routine becomes everyone's.
Conversation History — tasks can be picked up where you left off across supported platforms and devices.
The $50 per-user, per-month pricing option — turned on through your Salesforce account executive.

Rolling out in November 2026

Coworker in Microsoft Teams — generally available.
A dedicated iOS app and Mac and Windows desktop apps .
A Coworker MCP server , using the Model Context Protocol to connect Coworker to external systems.
A free trial for Flex Credits customers .

Expected in December 2026

Daily Digest — a morning summary of top priorities.
Scheduled tasks — recurring work that runs on its own cadence.
Coworker inside the Field Service, Consumer Goods Cloud, and Life Sciences Cloud mobile apps .

The usual caveat applies, and Salesforce says it plainly: pricing and packaging are subject to change, availability varies by region, and purchasing decisions should be based on features that have actually shipped — not on a December roadmap.

3. The Pricing Question: Flat Seat or Metered Usage?

Regular readers will remember our recent look at Flex Credits, Salesforce's consumption-based model for metering agentic work. The $50 Coworker seat is the other philosophy: a flat, predictable, per-user price — adopt it team by team, budget it like any other license, and stop watching a credit meter.

Which model wins depends on usage patterns, and this is where mid-market teams should do actual math rather than take either option by default:

Flat seats favor heavy, habitual users. If your sales and service teams will lean on Coworker daily — briefs before every call, renewal checks, drafted follow-ups — a fixed $50 per user is easy to model and likely cheaper than paying per action.
Consumption favors experiments and spiky usage. If you're still finding out whether anyone will use this, metered usage (and the free trial for Flex Credits customers coming this month) lets you test without committing seat licenses to people who may never open it.
The real cost isn't the license either way. At $50 per user, a 50-person deployment is $30,000 a year. That's visible and manageable. The hidden costs are the ones that determine whether you get anything for it: data quality, integration setup, and governance. More on that below.

A sensible mid-market path: trial on consumption with one team, measure what people actually delegate to it, then convert the proven users to seats. Buying 200 seats on launch enthusiasm is how AI line items end up in next year's cost-cutting review.

4. Why This Matters Specifically for Mid-Market B2B

Most Agentforce news to date has skewed enterprise — big builds, big services engagements. Coworker's November announcement is arguably the first time the AI-coworker pitch has been packaged in a shape mid-market companies can realistically buy: a flat price, no agent-building project required to start, and delivery inside tools (Teams, mobile, desktop) your team already lives in.

There's also an encouraging signal for companies with heavily customized orgs. One of Salesforce's featured customers, BACA Systems, enabled Coworker in an environment with 1,300 custom objects and reports it now answers questions that previously took 45 to 60 minutes of manual digging. Mid-market orgs are often the most customized relative to their admin headcount — if Coworker genuinely handles messy, customized environments, that's where the time savings concentrate.

But the same two design choices we flagged earlier deserve a hard look before you switch anything on:

Coworker inherits your permissions model — including its flaws. "It only sees what the user sees" is reassuring exactly in proportion to how clean your sharing rules are. Years of accumulated profiles, permission sets, and org-wide defaults set to "let's fix that later" become the operating boundaries of an AI that surfaces information fast and conversationally. Over-shared data that nobody stumbled into before gets a lot easier to find.
Coworker inherits your data quality, too. A digital teammate that confidently summarizes stale opportunities, duplicate accounts, and half-filled fields doesn't make your team faster — it makes them confidently wrong. The 185,000 users in the press release are, presumably, mostly in orgs that did the groundwork.

5. A 7-Step Checklist Before You Turn It On

If Coworker is on your radar for Q1 planning, work through this sequence first:

Audit sharing rules and permissions. Review org-wide defaults, role hierarchy, and permission sets for your pilot team. Fix over-sharing before an AI makes it searchable in plain English.
Pick one high-frequency workflow. Renewal checks, pre-call briefs, case triage summaries — choose a task your team does weekly and define what "Coworker does it well" looks like.
Clean the data that workflow touches. Not the whole org — just the objects and fields your pilot use case depends on. Stage completeness, close dates, contact roles, case status hygiene.
Decide seat vs. consumption deliberately. Use the Flex Credits trial if it fits, measure real usage for 30–60 days, then license the users who've built the habit.
Set approval boundaries. Use the available approval and audit capabilities to require human review on anything customer-facing — drafted emails get read before they're sent.
Plan the Teams/mobile rollout, not just the Salesforce one. The November apps mean Coworker will live where your team chats. Decide who gets it, and brief them, before it simply appears.
Measure time saved, not messages sent. Usage stats flatter every tool. Track the metric that justified the pilot — minutes to a meeting brief, time to triage a case — and compare against your baseline.

The Bottom Line

Salesforce's AI coworker now has a price tag, an app store presence, and a seat at the table in Teams. For mid-market B2B companies, that makes this the right quarter to evaluate it seriously — and the wrong quarter to buy it impulsively. The teams that will get real value in 2027 are the ones spending the next 60 days on unglamorous groundwork: permissions, data hygiene, and one well-chosen pilot workflow with a number attached.

Not sure whether your org is ready for a digital teammate? That's exactly what our free 2-minute org health check at 360quantumsolutions.com is for — or book a consultation and we'll map your Coworker readiness, fixed fee, no surprises. Your Salesforce should be your #1 sales tool. Let's make it one.

Your Reports Are About to Explain Themselves: Salesforce Closes Loops

Tue, 03 Nov 2026 13:09:42 GMT

While most of us were watching the World Series and planning for the holidays, Salesforce quietly closed another acquisition. On November 2, the company completed its purchase of Loops, an AI analytics startup whose whole pitch is that you shouldn't have to dig through dashboards to find out why a number changed. Loops is being folded into Tableau, and it's the clearest signal yet of where Salesforce reporting is headed: away from static dashboards, toward analytics that watch your metrics for you, explain what moved and why, and suggest what to do about it.

That sounds like a feature announcement for data teams at big enterprises. It isn't. If you run a mid-market B2B company, you probably don't have a data analyst on staff — which makes you exactly the kind of customer this shift is aimed at. Here's what actually happened, what "agentic analytics" means in plain English, and what to do now so your org is ready when these capabilities land in your reports.

1. What Actually Happened

The facts first. Salesforce signed a definitive agreement to acquire Loops on October 12, 2026, and completed the deal on November 2. Terms weren't disclosed — this is a tuck-in acquisition, not a Braze-sized bet — and Loops' technology and team are being absorbed into Tableau, the analytics platform Salesforce has owned since 2019.

Loops built an analytics agent called Scout. Instead of waiting for you to open a dashboard, Scout monitors your key metrics continuously, flags trends and anomalies, runs root-cause analysis to rank the likeliest explanations for why a metric moved, and recommends actions in response. It delivers all of this where people actually work — email, Slack, Microsoft Teams — and users can chat with it about their data without building a dashboard first.

If that sounds familiar, it should. Tableau repositioned itself around "agentic analytics" earlier this year with Tableau Next, and Tableau Pulse already tracks metrics and sends insight digests to email and Slack. What Pulse doesn't do is tell you why a number changed or what to do about it. That's the gap Loops fills — the difference between "pipeline coverage dropped 18% this week" and "pipeline coverage dropped 18%, driven mostly by stalled deals in your manufacturing segment, and here are the three likeliest causes, ranked."

2. What "Agentic Analytics" Means in Plain English

Strip away the branding and the shift is simple. Traditional reporting is pull-based: someone builds a dashboard, someone else remembers to check it, and when a number looks off, a human goes spelunking through filters to figure out what happened. Every step depends on a person noticing, caring, and having time.

Agentic analytics flips that to push-based. Software agents watch the metrics you've told them matter. When something meaningful changes, they notify you, explain the drivers, and propose next steps. The dashboard doesn't disappear — but it stops being the front door. For a 15-person sales team with no RevOps analyst, that's not an incremental improvement. It's the difference between finding out about a problem in the Monday pipeline review and finding out three weeks later in the quarterly business review.

This isn't an isolated move, either. The new Agentforce editions Salesforce announced in September — Core, Advanced, and Max, at $195, $395, and $550 per user per month — all list "embedded agentic analytics" as a bundled capability, alongside Agentforce and Slack. Salesforce is clearly betting that watching-and-explaining becomes a standard part of the CRM, not a separate BI product you buy later.

3. Why Mid-Market Teams Should Care

Enterprise companies have analysts whose job is to answer "why did this number move?" Mid-market companies mostly don't. When the VP of Sales asks why win rates dipped in Q3, the answer usually comes from whoever has the best memory and the most Salesforce patience — which means the answer is often a guess dressed up as analysis.

That's why this category of tooling matters more below the enterprise than inside it. Root-cause analysis on tap is essentially analyst capacity you don't have to hire. Alerts that find you in Slack fit how lean teams actually operate. And because it's being built into the platform you already own, the realistic path for most mid-market orgs is that this shows up inside Salesforce and Tableau over the coming releases rather than as a separate tool to evaluate.

Now the honest caveats, because there are real ones:

Integration timing is unknown. Salesforce hasn't said when Loops' capabilities will surface inside Tableau, or how they'll be reconciled with Pulse's existing metric monitoring. Tuck-in acquisitions can take several release cycles to show up in the product.
Packaging is unknown. As of the close, Salesforce hasn't confirmed whether Scout-style capabilities will be a standard Tableau feature or a paid add-on. Given the direction of recent pricing moves — Flex Credits, consumption-based agent billing — assume there's a meter involved until told otherwise.
It only works on data worth analyzing. This is the big one, and it gets its own section.

4. The Catch: An AI Analyst Can Only Explain Clean Data

Here's the uncomfortable truth behind every agentic analytics demo: the agent is only as good as the fields it reads. Root-cause analysis works by slicing a metric across dimensions — segment, stage, owner, source, region — and ranking which slice explains the change. If your opportunity stages are used inconsistently, if half your deals have no close date discipline, if "Lead Source" has 47 values and six of them are variations of "web," the agent will do its ranking anyway. It will just rank noise.

And unlike a human analyst, an AI agent delivers noise confidently, at scale, straight into your executives' Slack. A bad dashboard gets ignored; a bad automated insight gets believed. That's why the right response to this acquisition isn't "wait and see" — it's to spend the next couple of quarters making your org the kind of place where automated analysis produces truth instead of plausible-sounding fiction.

5. Six Steps to Get Your Org Agent-Ready

None of this requires buying anything. It's the same hygiene work that makes every Salesforce AI feature — Agentforce included — actually deliver, applied with analytics in mind.

Pick your ten metrics. Agentic analytics starts with "tell the agent what matters." If your leadership team can't agree on the ten numbers that define the health of the business — pipeline coverage, win rate, average cycle length, net retention, and so on — settle that argument now, on paper, before an agent starts monitoring the wrong things.
Define each metric once. "Win rate" calculated three different ways across three dashboards is a human annoyance today; it becomes an agent feeding contradictory alerts tomorrow. Write down the formula, the filters, and the source report for each key metric, and retire the duplicates.
Audit the fields that drive those metrics. For each of your ten metrics, list the fields it depends on — stage, amount, close date, segment, source — and check completeness and consistency on each. A simple report of "opportunities missing X" per field tells you where root-cause analysis will break first.
Fix picklists before they become dimensions. Free-text fields and bloated picklists are where automated slicing goes to die. Consolidate values, convert free text to picklists where it matters, and enforce them with validation rules so the cleanup sticks.
Inventory and prune your reports. Most orgs more than three years old have hundreds of reports, most unused. Archive aggressively. When agentic features arrive, you want them pointed at a small set of trusted sources, not inheriting a decade of conflicting folders.
Decide who owns the alerts. An insight delivered to nobody is a dashboard with extra steps. For each key metric, name the person who acts when the agent flags a change — and agree on what "act" means. This is a 30-minute leadership conversation that doubles the value of everything above.

6. The Bottom Line

The Loops acquisition is small in dollars but clear in direction: Salesforce wants your CRM to tell you what's happening in your business before you think to ask. For mid-market teams without analyst headcount, that's genuinely good news — the leverage lands disproportionately on companies your size. But the capability will arrive on Salesforce's timeline, at Salesforce's price, and it will only be as smart as the data in your org on the day it switches on.

The teams that win this transition are the ones whose pipeline data is already trustworthy — the rest will be paying for an AI analyst that's better at surfacing their data-quality problems than anything useful about their business. If you're not sure which camp your org falls in, start with our free 2-minute org health check at 360quantumsolutions.com , or book a consultation and we'll walk your key metrics and the fields behind them in a 5-day org audit — fixed fee, no surprises, and you'll know exactly where you stand before the agents start talking.

Your AI Agents Are About to Show Up on Your Salesforce Bill

Tue, 27 Oct 2026 13:26:45 GMT

For the past year, the smartest trick in the AI playbook has been free: connect an AI agent — Claude, ChatGPT, or a custom-built assistant — to your Salesforce org and let it read records, update opportunities, and answer questions without anyone thinking twice about the cost. That era is ending. Salesforce announced this month that MCP and API calls made by registered third-party AI agents will soon consume Flex Credits, the same consumption currency that powers Agentforce. In plain English: every time an outside AI agent touches your org, a meter will run.

The announcement landed hard enough that Salesforce has already opened direct talks with partners over the billing concerns it raised. For mid-market B2B teams — who are often the most enthusiastic adopters of "connect an AI to the CRM" workflows precisely because they lack big-company budgets — this is worth understanding now, before the meter switches on. Here's what was announced, what it's likely to cost, and a practical plan to get ahead of it.

1. What Salesforce Actually Announced

The change is part of Salesforce's Headless Toolkit strategy, and it has three moving parts worth separating.

First, the metering itself. Successful MCP (Model Context Protocol) calls and direct API calls made by registered third-party agents will each count as a "Headless Platform Interaction," and each interaction will consume Flex Credits. This isn't limited to MCP traffic — direct API calls that Salesforce classifies as agentic are included too. Traditional API integrations (your middleware, your ETL jobs, your connected apps driven by humans and scheduled jobs) keep their current pricing and security arrangements.

Second, a new identity model. Alongside the metering, Salesforce introduced an Agentic Identity framework: AI agents get their own credentials and permission sets rather than borrowing a human user's login. MCP clients and API-based agents will eventually need to reconfigure to use OAuth credentials tied to that agentic identity. Whatever you think of the billing, this part is a clear win — most orgs connecting AI tools today are doing it through a user's credentials, which makes agent activity hard to audit and easy to over-permission.

Third, the timing and scope. Agentic usage is not currently metered, and Salesforce has committed to giving customers 30 days' notice before metering begins. The metering applies only to active production orgs — sandboxes, scratch orgs, and Developer Edition orgs are excluded, so experimentation stays free. The crucial missing detail: the Flex Credit multiplier per interaction has not been published, which means nobody can calculate their actual exposure yet.

2. Flex Credits 101: The Currency Behind the Meter

If your team hasn't dealt with Flex Credits yet, here's the short version. Flex Credits are Salesforce's consumption currency for agentic features, introduced in 2025 when Agentforce moved away from flat $2-per-conversation pricing. The published rate card: $500 buys 100,000 Flex Credits — about half a cent per credit — and a standard Agentforce action (updating a record, answering a question) consumes 20 credits, or roughly $0.10. Customers on Enterprise Edition and above receive 100,000 Flex Credits at no cost through Salesforce Foundations, which is a meaningful on-ramp for a mid-market org.

What's new is the direction of travel. Flex Credits began as the way you pay for Salesforce's own agents doing work inside your org. This announcement extends the same currency to outside agents reaching in. If your sales team uses an AI assistant that pulls account history before calls, or your ops team built a workflow where an LLM reconciles records over the API, those interactions are the ones headed for the meter — and you may end up paying twice for the same workflow: once to your AI provider for the model, and once to Salesforce for the access.

Why Salesforce is doing this now

The volume argument is real. Agentic traffic behaves differently from human traffic: an agent asked one question might make a dozen API calls to answer it, and agent adoption is compounding — this month's 10K Ecosystem Report shows Agentforce-related job listings up 63% year over year. From Salesforce's perspective, unmetered agentic access is a growing cost with no revenue attached, and it competes with Agentforce itself. From a customer's perspective, it changes the economics of every AI workflow that touches CRM data. Both things are true, which is why partner conversations got heated enough for Salesforce to open formal talks.

3. Why Mid-Market Teams Should Care More Than Most

Enterprise customers have vendor management teams who will model this, negotiate custom terms, and set consumption guardrails. Mid-market teams often don't — and they share three traits that make this change land harder.

They adopted fast. Connecting an off-the-shelf AI assistant to Salesforce via MCP has been one of the cheapest ways to get real AI value, so mid-market orgs did it early and informally — often without an inventory of what's connected.

Their agents are chatty. Workflows built quickly tend to be inefficient: agents that re-query the same records, poll for changes, or pull whole object histories when they need three fields. Nobody optimized, because calls were free. Per-interaction pricing punishes exactly this pattern.

And their budgets are already set. Most mid-market teams are locking 2027 budgets right now. A consumption line item with an unpublished rate, arriving on 30 days' notice, is the kind of surprise that turns a CFO against an AI program that was otherwise working.

4. A Six-Step Plan to Get Ahead of the Meter

You can't calculate your exposure until Salesforce publishes the multiplier. But you can do everything else now, and teams that do will be negotiating from knowledge instead of reacting to an invoice.

Inventory every AI integration touching your org. List every tool, assistant, or custom agent with API or MCP access to production — including the unofficial ones individual reps set up. If you can't name what's connected, you can't predict what gets metered.
Baseline your agentic call volume. Use Event Monitoring or API usage logs to measure how many calls your AI integrations make in a typical week. This number times the eventual multiplier is your bill; knowing it early turns the 30-day notice into an actual planning window.
Move agents onto their own identities. Don't wait for the deadline to adopt the Agentic Identity framework. Separate credentials per agent gives you auditability and least-privilege permissions today, and makes your usage data clean when metering starts.
Make chatty agents efficient. Batch queries, cache reference data that rarely changes, retrieve only the fields a task needs, and replace polling with event-driven triggers where possible. Cutting calls in half cuts the future bill in half — and makes your integrations faster besides.
Set up the Digital Wallet before you need it. Salesforce's Digital Wallet supports usage tagging and threshold alerts for Flex Credits. Configure alerts now, while your consumption is just Agentforce, so runaway usage pings an admin instead of surfacing on an invoice.
Put it on the agenda at renewal. If your contract renews in the next two quarters, raise agentic metering explicitly. Salesforce is actively negotiating with partners over this change, which means terms are softer now than they will be once the model hardens. Ask about included allowances, pre-committed discounts, and whether your Foundations credits apply.

5. What We Still Don't Know

Honesty matters more than confidence here, so three open questions. The multiplier: until Salesforce publishes how many Flex Credits one headless interaction consumes, every cost estimate is a guess — treat any vendor's projected number with suspicion. The start date: "not currently metered, 30 days' notice" is all anyone has. And the free tier question: Salesforce previously indicated some basic MCP capabilities were included with Enterprise Edition, and it hasn't yet said whether those stay free once metering begins. The partner talks now underway may reshape any of these answers, which is exactly why the preparation steps above are worth more than premature conclusions.

The Bottom Line

Metered agentic access isn't a reason to slow down on AI — the workflows that justified themselves at zero marginal cost mostly still justify themselves at a dime per action. But "mostly" is doing real work in that sentence, and the teams that come out ahead will be the ones who know their call volumes, run efficient agents, and negotiated with data in hand. The ones who get hurt will be the ones who discover their integration inventory on an invoice.

If you're not sure what's connected to your org — or whether your Salesforce foundation is ready for an agentic 2027 — that's exactly what we do. Start with our free 2-minute org health check at 360quantumsolutions.com , or book a consultation with a certified consultant (no PM layers, fixed-fee, on-time guarantee). Your Salesforce should be your #1 sales tool. Let's make it one.

Salesforce Buys Braze: What It Means for Mid-Market B2B Teams

Tue, 20 Oct 2026 13:17:21 GMT

This morning, October 20, 2026, Salesforce announced a definitive agreement to acquire Braze — the real-time customer engagement platform behind the push notifications, in-app messages, and lifecycle emails of brands like Instacart, Venmo, and Canva — for roughly $5.66 billion in enterprise value. It's Salesforce's biggest marketing acquisition since ExactTarget in 2013, and it lands squarely in the middle of budget season, just as mid-market teams are deciding what their 2027 stack looks like. If your company runs Marketing Cloud, runs Braze, or was about to pick between them, this deal changes your calculus. Here's what was actually announced, why it happened, and what to do about it — in plain English.

What Was Actually Announced

The facts, straight from the announcement: Salesforce will pay $47.50 per share in cash for Braze — about a 58% premium over Braze's prior closing price — for a total enterprise value of roughly $5.66 billion. The deal still needs Braze shareholder approval and regulatory clearance, and it isn't expected to close until Salesforce's fiscal year 2028, which runs from February 2027 through January 2028. In other words: nothing merges tomorrow. Braze operates independently until the deal closes, likely well into 2027.

What Salesforce is buying is substantial. Braze serves around 2,770 customers and powers trillions of messages and journey actions a year across mobile push, in-app, email, SMS, and WhatsApp. Its core strength is an event-streaming architecture: customer profiles update in real time as people tap, browse, and buy, and journeys adjust on the fly rather than waiting for an overnight batch job. Its AI layer, BrazeAI, optimizes content, offers, channels, and send timing.

One more data point worth noting: Salesforce's own shares dipped about 3% on the news. Investors are asking the same question you should — what does this mean for the products customers already pay for?

Why Salesforce Wants Braze

Salesforce's stated rationale is that marketers increasingly need agentic AI — tools that understand customers, make decisions, and act in real time. That's consistent with everything the company has shipped and said this year, from the Agentforce push to the Dreamforce "Agentic Enterprise" messaging. An AI agent that decides the next best message is only useful if something can actually deliver that message in the moment, on the channel the customer is actually using. That delivery layer is exactly what Braze does well.

There's also an honest product-history angle here. Marketing Cloud Engagement traces its lineage to the 2013 ExactTarget acquisition, and it was built in an email-first, campaign-and-batch era. Salesforce has been modernizing it — rebuilding marketing on its core platform and wiring it into Data Cloud (now branded Data 360) — but mobile-first, event-driven engagement has been the gap. Braze was built natively for that world. Salesforce says Braze will strengthen Marketing Cloud's cross-channel personalization and plug into Data 360, Customer 360, and Agentforce, with marketing connected to commerce, sales, and service.

What Salesforce has not announced is any specific product roadmap, migration plan, or timeline for how Braze and Marketing Cloud fit together. The language is intentionally general: "open, composable," "deeper mobile and in-app capabilities," "more intelligent personalization." Treat everything beyond that as speculation — including from consultants.

If You're a Marketing Cloud Customer

First, the reassuring part: nothing about your org changes this week, this quarter, or almost certainly this fiscal year. The deal won't close until at least 2027, and enterprise software integrations take years after that. Your renewal terms, your SLAs, and your roadmap commitments stand.

The strategic part needs more attention. When a vendor spends $5.7 billion on a product that overlaps with one you own, the overlapping product's long-term direction gets re-examined — that's not cynicism, it's how portfolio rationalization works. Over the next 12–24 months, expect clearer signals about where Salesforce steers net-new investment: into Marketing Cloud Engagement as it exists today, or into a Braze-powered engagement layer. Neither outcome is bad for you if you see it coming. Both are expensive if you don't.

The questions to put to your account executive

You don't need to renegotiate anything yet, but you should get answers on the record: What is the committed roadmap for the Marketing Cloud products we license? Will Braze be sold as a separate SKU, folded into existing editions, or positioned as the successor engagement layer? And what protections exist in our renewal if packaging changes mid-term? Vague answers are themselves information — they tell you to keep your architecture flexible.

If You Run Braze — or Were Evaluating It

Braze customers arguably got good news. The product now sits inside the largest CRM vendor on the planet, with Salesforce publicly committing to Braze's customer and partner community and to continued investment. The practical risks are the standard post-acquisition ones: pricing and packaging usually get restructured once a product enters the Salesforce catalog, and roadmap priorities shift toward the acquirer's platform — expect deeper, earlier integration with Data 360 and Agentforce, and slower investment in integrations with Salesforce's competitors.

If you were mid-evaluation between Braze and Marketing Cloud, the deal simplifies one thing and complicates another. Long term, the two are converging into one vendor's story. Short term — the next 12 to 18 months — they remain separate products with separate contracts, and you now have negotiating leverage with both sales teams, who each have something to prove while the deal is pending.

Five Moves for Mid-Market Teams to Make Now

Inventory your engagement stack. List every tool that sends a customer-facing message — Marketing Cloud, Braze, Pardot/Account Engagement, a standalone SMS tool, transactional email from your app. Note contract end dates and annual spend. Most mid-market orgs are surprised by how many overlapping senders they're paying for, and consolidation decisions over the next two years will favor teams who know their own footprint.
Check your renewal dates against the deal timeline. The acquisition is expected to close in Salesforce's fiscal 2028. If your Marketing Cloud or Braze renewal lands in 2027, you'll be negotiating during peak uncertainty — which can work in your favor if you start the conversation early and ask the roadmap questions above in writing.
Get your data model ready either way. Every plausible outcome of this deal runs through clean, unified customer data — Braze's event streams and Agentforce's decisions are only as good as the profiles underneath them. Duplicate contacts, inconsistent consent fields, and disconnected engagement history will hurt you in any future architecture. This is the work that pays off regardless of what Salesforce announces next.
Don't pause necessary projects. Deal announcements create a reflex to freeze spending "until things are clearer." For a deal that won't close for a year or more, that's usually the wrong call. If your lifecycle email program or lead routing is broken today, fixing it generates returns long before any integration ships.
Write down your decision triggers. Agree internally, now, on what would actually change your plans: a formal end-of-sale notice, a migration incentive, a pricing change above a threshold. Then stop re-litigating the question every time a headline drops. A one-page position saves a dozen meetings.

The Bigger Pattern: Salesforce Is Assembling the Agentic Stack

Braze doesn't stand alone. It follows the roughly $8 billion Informatica acquisition — data management and governance — and two years of relentless Agentforce investment. The through-line is clear: Salesforce is buying the pieces of an end-to-end loop where unified data (Data 360 and Informatica) feeds AI decisions (Agentforce) that trigger real-time action across every channel (Braze). Whether that vision lands on schedule or not, it tells you where the platform's gravity is heading — and mid-market teams that keep their data clean and their architecture simple will be able to adopt the useful parts without a painful rebuild.

The companies that come out ahead of platform shifts like this one aren't the ones that react fastest to press releases. They're the ones whose orgs are healthy enough to have options. If you're not sure where yours stands, start with our free 2-minute org health check at 360quantumsolutions.com — or book a consultation and we'll walk through what this deal means for your specific stack. Fixed fee, direct access to certified consultants, and a straight answer about what's worth doing now versus later.

Agentforce Is Now On by Default: A Governance Playbook for Mid-Market Teams

Tue, 13 Oct 2026 13:35:04 GMT

Sometime in the past few weeks, a switch flipped in your Salesforce org — and nobody on your team touched it. With the Winter '27 release, Salesforce began enabling Agentforce by default in every eligible org. Existing customers have been auto-enabled on a rolling basis since early September, new orgs get it the moment they're created, and the dedicated on/off toggle is being retired from Setup later in the release cycle. If your company runs Enterprise Edition or above with Foundations, Agentforce is almost certainly live in your org right now.

That's not a reason to panic. It is a reason to spend an hour this week understanding what changed, who in your org can now do what, and whether your permission model is ready for software that can act on its own. This post covers what Salesforce actually announced, why "enabled" doesn't mean "deployed," the risks that deserve real attention, and a seven-step governance audit any mid-market admin can run before Friday.

1. What Actually Changed

Here are the facts, stripped of the headlines. As part of Winter '27 — which finished rolling out to production orgs in October — Salesforce now enables Agentforce automatically in orgs that have access to it through their edition and licensing. Per Salesforce's release documentation and reporting from Salesforce Ben, that covers Lightning Experience orgs with Foundations on Enterprise, Performance, Unlimited, and Developer Editions, plus orgs on Agentforce 1 Edition. Auto-enablement for existing orgs began the first week of September 2026, and new orgs are enabled at creation.

The part that raised eyebrows: the Agentforce toggle on the Agentforce Agents page in Setup is being removed later in Winter '27. There's no dedicated decline checkbox. Salesforce says enablement comes at no additional cost and changes nothing about billing.

Two controls do remain, and they matter. Admins can still switch off the underlying Einstein setting on the Einstein Setup page, which disables the AI layer platform-wide. And individual agents can be activated or deactivated one by one in Agentforce Builder. So you haven't lost control of your org — you've lost the convenience of a single, obvious switch, and gained a capability you didn't schedule.

2. Enabled Is Not the Same as Deployed

Before anyone forwards this post to your CISO with alarm bells attached, one clarification: auto-enablement does not mean AI agents are now making decisions in your live workflows. No agent talks to a customer, edits a record, or triggers an action until someone in your org builds it, tests it, and activates it.

What enablement actually does is make the machinery available. Agentforce sections appear in Setup. Users who hold the right permissions can open Agentforce Builder and start creating. Think of it less like a robot showing up to work in your office, and more like a fully stocked workshop appearing overnight in a building where you haven't yet decided who gets a key.

That framing points directly at the real issue. The question isn't "is Agentforce dangerous?" It's "who in my org holds a key to the workshop, and what could they build without anyone reviewing it?"

3. The Risks Worth Taking Seriously

Permission debt comes due

Most mid-market orgs carry years of accumulated permission sprawl: profiles cloned from profiles, permission sets granted for a project that ended in 2023, org-wide defaults set to Public Read/Write because it was faster during go-live. Human users rarely exercise the full extent of what they're technically allowed to touch. An agent running under a user context will use whatever access it has, consistently and at machine speed. Agents inherit your permission debt — and then they spend it.

Shadow agents

Anyone holding the Manage AI Agents permission can build and deploy agents. If that permission is sitting inside a broad permission set — or if your admins never audited who has it, because until September it didn't matter — you've got a path for well-meaning employees to stand up AI automation with no change request, no security review, and no entry in your release log. That's the same shadow-IT pattern that gave us rogue spreadsheets and unsanctioned SaaS, now with write access to your CRM.

A bigger attack surface

Agents that read fields the outside world can write to are a genuine security consideration. The cautionary tale is ForcedLeak, a vulnerability chain disclosed by researchers at Noma Labs in 2025 and rated CVSS 9.4: it used prompt injection through the Web-to-Lead Description field — which accepts up to 42,000 characters — to manipulate agent behavior. Salesforce patched that specific vector in September 2025 with Trusted URLs Enforcement, but the underlying lesson stands. Any field that external users fill in and agents later read — lead descriptions, case comments, form submissions — is a place where instructions can hide.

Abandonment is the quiet cost

Gartner projects that over 40% of agentic AI projects will be abandoned by the end of 2027, with insufficient oversight cited as a primary cause. The orgs that end up on the wrong side of that number won't be the ones that moved slowest — they'll be the ones that moved without a plan. Default enablement makes it easier than ever to start without one.

4. The Seven-Step Governance Audit

Here's the practical part. Each step takes minutes, not days, and together they turn an unscheduled platform change into a deliberate decision.

Confirm your org's status. Go to Setup and search for Agentforce Agents. If the section is there and enabled, you're in the rollout. Note the date — your auditors may ask when this capability appeared.
Audit the Manage AI Agents permission. Run a report on every user, profile, and permission set that grants it. Strip it from anyone who doesn't have an explicit reason to build agents. This single step eliminates most of the shadow-agent risk.
Make the Einstein decision deliberately. If your company isn't ready for any generative AI in the org — for compliance, contractual, or readiness reasons — the Einstein Setup page still gives you a platform-wide off switch. Use it consciously or leave it on consciously; either is defensible, but drifting isn't.
Review the access any future agent would inherit. Check org-wide defaults on sensitive objects, sharing rules left over from old team structures, and connected app OAuth scopes. Apply least privilege now, before the first agent goes live — it's far harder to claw back afterward.
Map your externally writable fields. List the fields that web forms, portals, and email-to-case can write and that an agent might someday read. That list is your prompt-injection surface, and it belongs in your security documentation.
Update your change-management policy. Add AI agents to the same approval workflow you use for flows and integrations: a named owner, a documented purpose, a test plan, and a deactivation path for every agent that reaches production.
Write down your posture. One paragraph: "We have reviewed Agentforce enablement, our position is X, the next review is scheduled for Y." When a board member or customer asks what you're doing about AI governance, you'll have an answer that took thirty seconds to find.

5. Opt Out, Hold, or Lean In?

After the audit, you have three honest options. Opting out via the Einstein setting suits orgs with hard compliance constraints or serious unresolved permission debt — just calendar a review date so the decision doesn't fossilize. Holding — enabled but with tightened permissions and no active agents — is the right default for most mid-market teams: you keep the runway without the risk. Leaning in makes sense if you have a well-bounded use case, clean data, and someone accountable for the result; started deliberately, a first agent pilot is a reasonable Q4 project rather than a leap of faith.

The only wrong move is not choosing. Salesforce has made Agentforce present in your org; whether it becomes an asset or an audit finding is decided by what you do next.

The Bottom Line

Default enablement is Salesforce signaling, unambiguously, that agents are now a standard part of the platform rather than an add-on. You don't have to share that enthusiasm this quarter — but you do have to govern it. An hour of permission auditing this week beats an uncomfortable discovery during next year's security review.

If you'd rather have expert eyes on it, that's what we do. 360 Quantum Solutions has spent 16+ years in the Salesforce ecosystem helping mid-market B2B teams keep their orgs secure, tidy, and actually useful to sales. Start with our free 2-minute org health check at 360quantumsolutions.com , or book a 5-day org audit and we'll map your permission debt, your Agentforce readiness, and your cleanup plan — fixed fee, no scope creep, no surprises.

The Q4 Salesforce Playbook: Close 2026 Strong, Plan 2027 Smart

Wed, 07 Oct 2026 13:34:25 GMT

Q4 started last week. For most mid-market B2B companies, that means the next twelve weeks decide whether 2026 ends as a good year or a great one — and whether 2027 starts with a plan or a scramble. There's a second deadline hiding in the calendar too: the final wave of Salesforce's Winter '27 release reaches remaining production orgs on October 10, so by the end of this week, every org is running the new release. This is the quarter where your CRM either earns its keep or quietly costs you deals. Here's a practical playbook — what to clean up, what to put in front of leadership, and what to set in motion now so January doesn't start from zero.

1. Why Q4 Is Different Inside Your CRM

In Q1, an inflated pipeline is an inconvenience. In Q4, it's a liability. Every stale opportunity still sitting in "Negotiation" from July makes your year-end forecast less believable, and year-end forecasts get more scrutiny than any other number your team produces — from the CEO, the board, and whoever is building next year's budget on top of them.

Q4 is also when buying behavior shifts. Your prospects are spending what's left of this year's budget, deferring what they can to next year's, and going quiet for two weeks in late December. A pipeline review process that works fine in May will mislead you in November unless the underlying data is clean. That's why this playbook starts with hygiene, not strategy: the strategy conversations only work if the numbers underneath them are real.

2. Week One: Run a Pipeline Hygiene Sweep

Before you forecast anything, spend a few focused hours making the pipeline tell the truth. This is unglamorous work, and it's the single highest-leverage thing a sales leader can do in early October. Work through it in this order:

Close dates in the past. Build a list view of open opportunities with a close date before today. Every one of them is either a deal that needs a new date, a deal that should be marked closed-lost, or a conversation someone is avoiding. Clear the list.
Stage-age mismatches. Flag opportunities that have sat in the same stage far longer than your typical cycle. A "Proposal" that hasn't moved in 90 days isn't a proposal — it's a maybe. Requalify it or close it out.
Missing next steps. Any open deal expected to close this quarter should have a concrete next step and a date. If the field is blank, the deal plan probably is too.
Amount and stage sanity checks. Look for placeholder amounts, blank amounts on late-stage deals, and deals sitting in early stages with signature-ready numbers. These distort every roll-up report built on top of them.
Single-threaded deals. For your top ten Q4 opportunities, check how many contacts are actually attached and engaged. December is vacation season; a deal that depends on one person's inbox is a deal that slips to February.

None of this requires new tools. List views, a report on opportunity field history, and an honest hour with each rep will get you there.

3. Give Leadership a Forecast They Can Trust

Once the pipeline is honest, make it visible. The goal is a small set of dashboards that answer the questions leadership will ask every week between now and December 31 — without anyone exporting to a spreadsheet.

The three views that matter in Q4

Coverage. Open pipeline closing this quarter versus the remaining target. If coverage is thin in October, you still have time to act; discovering it in December is just bad news.
Movement. What changed since last week — deals that advanced, slipped, grew, shrank, or died. Opportunity field history and snapshot reporting make this straightforward, and it turns Monday pipeline calls from status recitals into decision meetings.
Commit versus best case. Keep the categories ruthless. A commit list that holds up builds credibility with the board; one that quietly loses a third of its deals every quarter costs you the benefit of the doubt in next year's planning.

If your team is maintaining the "real" forecast in a spreadsheet because nobody trusts the CRM version, that's not a process quirk — it's a signal that your Salesforce org needs attention. Fixing it is usually a configuration and adoption problem, not a software problem.

4. Put Winter '27 to Work While It's Fresh

With the October 10 wave, Winter '27 is live everywhere. Most teams let release features sit unused for months; Q4 is a good moment to be deliberate instead, because small admin wins compound during your busiest selling season.

Three practical moves: first, have your admin read the release notes with your Q4 priorities in mind — flow and reporting improvements tend to pay off fastest for sales teams. Second, review the release updates queue in Setup; some updates come with enforcement deadlines, and it's far cheaper to test them now than to discover them broken in January. Third, pick one or two features that remove manual steps from your pipeline process — then actually roll them out, announce them, and check adoption two weeks later.

5. The Year-End Operational Cleanup

December is also housekeeping season, and an hour of admin work now can save real money and real headaches:

Audit users and licenses before renewal conversations. Deactivate departed users, reclaim unused licenses, and walk into your Salesforce renewal knowing exactly what you use.
Check data and file storage. Storage overages are a silent line item. Archive what you don't need before it becomes a renewal surprise.
Review integrations and scheduled jobs. Year-end is when billing systems, ERPs, and marketing platforms all run their own closing processes. Confirm your integrations are healthy before everyone needs them at once.
Document what changed this year. New fields, flows, and processes added in 2026 should be written down somewhere a new hire could find. Undocumented customization is how orgs drift into the "nobody knows why this exists" state.

6. Start Your 2027 Plan Now, Not in January

Budget season is happening right now in most mid-market companies. If Salesforce improvements aren't in the 2027 plan by December, they'll spend next year competing for leftover budget. Three questions to answer before year-end:

What did the CRM cost you this year? Not the license fee — the workarounds. Deals that slipped because of process gaps, hours lost to manual data entry, reports rebuilt in spreadsheets. That's your real business case for investment.
What's the one process to fix first? Resist the ten-item wishlist. Pick the single workflow — lead routing, quoting, renewals, forecasting — where friction costs you the most, and scope that.
Is your data ready for what's next? Whatever your 2027 roadmap holds — AI agents, a new territory model, an acquisition — it will be built on the data you have in January. Every AI initiative in the Salesforce ecosystem, from Agentforce on down, returns exactly what your data quality allows. Cleaning up in Q4 is the least glamorous and most valuable AI preparation there is.

An honest org assessment belongs at the start of that planning, not after the budget is set. Knowing what's solid, what's fragile, and what's simply unused in your current org turns the 2027 conversation from guesswork into a plan.

Your Q4 Checklist, In One Place

Clear every past-due close date and stale-stage deal by mid-October.
Stand up coverage, movement, and commit dashboards leadership actually opens.
Review Winter '27 release updates and adopt one or two time-saving features.
Audit users, licenses, storage, and integrations before renewal season.
Document this year's org changes.
Get your 2027 Salesforce priorities into the budget before December.

Close the Year with Confidence

None of this requires a big project. It requires a clean org, a few honest reports, and a plan that starts before the new year does. If you'd like a second set of eyes, start with our free 2-minute org health check at 360quantumsolutions.com — or book a 5-day org audit and walk into 2027 knowing exactly where your org stands. Fixed fee, direct access to certified consultants, and no surprises in January. Your Salesforce should be your #1 sales tool. Q4 is a very good time to make it one.

Salesforce's 7 Job-Ready AI Agents: A Mid-Market Hiring Guide

Tue, 15 Sep 2026 13:15:16 GMT

Last Thursday, four days before Dreamforce opened its doors, Salesforce announced a batch of new hires. None of them are human. The September 11 announcement introduced seven named, "job-ready" AI agents — Casey, Paige, Carter, Hunter, Marshall, Piper, and Fin — each built to take on a specific role, from answering support calls to building sales pipeline. It's the clearest signal yet of where Salesforce is taking Agentforce: away from "here's a toolkit, go build an agent" and toward "here's an employee, go onboard it."

For mid-market B2B teams, that shift matters. The biggest barrier to AI agents so far hasn't been ambition — it's been the build. Pre-configured agents with names, job descriptions, and reference customers change the buying decision from a development project into something closer to a hiring decision. So let's treat it like one. Here's who's on the candidate slate, which roles are worth interviewing for a mid-market B2B org, and the questions to ask before you sign an offer letter.

What Salesforce Actually Announced

The September 11 release introduces seven agents, each aimed at a defined job function. Per Salesforce's announcement, the lineup looks like this:

Casey — Help Agent. Customer service across voice, SMS, WhatsApp, and web chat. Generally available now.
Piper — Inbound Pipeline Generation Agent. Engages and qualifies inbound leads. Generally available now.
Hunter — Outbound Sales Agent. Pipeline building and seller collaboration. In pilot now, with general availability slated for November 2026.
Fin — Customer Agent. Handles complex, multi-step customer experience workflows across channels. Generally available now.
Paige — IT & HR Service Agent. Fields employee requests through Slack and service portals. Generally available now.
Carter — Shopper Agent. Product discovery and in-chat checkout for commerce. Generally available now.
Marshall — Supply Chain Agent. Orchestrates back-office and supply chain processes. Generally available now.

Under the hood, the announcement leans on four platform capabilities: a long-horizon runtime that lets agents work on tasks spanning days or weeks with memory and durable execution, multi-agent orchestration so agents can hand work to each other, AI Skills for teaching agents your company's specific processes, and an Agent Optimizer for tuning performance over time. Salesforce also shared a scale number worth noting: 7 billion "Agentic Work Units" delivered to date, 3.2 billion of them in the most recent quarter alone.

Why "Job-Ready" Is the Word That Matters

The framing isn't just marketing. It targets the single biggest complaint we hear from mid-market teams about AI projects: time to value. Analyst firm Futurum, covering the announcement, points to research showing 55.1% of buyers cite faster time-to-value as the thing that gives them budget confidence. A custom agent build means months of scoping, prompt engineering, testing, and tuning before anyone sees a result. A pre-configured agent ships with the skills, data model, and guardrails for its job already in place — you configure and connect rather than construct.

Salesforce's proof points are early customers with striking numbers: Engine reporting 50% of chat inquiries fully resolved, HR platform Perk attributing 60% of its sales pipeline to Hunter, Asana citing a 45-day average Piper deployment with 4x conversation volume, and Anthropic reporting 79% of support conversations resolved autonomously by Fin. Those are vendor-published figures from reference customers, so read them the way you'd read any glowing job reference — real, but curated. The honest open question, which Futurum also flags, is whether 50–90% resolution rates replicate across the broader install base, where data hygiene and process discipline vary widely. That question gets answered in orgs like yours over the next two quarters.

The Mid-Market B2B Shortlist: Interview These Three First

Not all seven roles belong on a mid-market B2B org chart. Carter is built for consumer commerce, and Marshall assumes supply chain operations running through Salesforce. For a typical B2B company running Sales Cloud and Service Cloud, three candidates deserve a first-round interview.

1. Piper — because inbound leads are perishable

Speed-to-lead is one of the oldest problems in B2B sales, and it's brutally measurable: inbound inquiries that wait hours for a response convert at a fraction of the rate of those answered in minutes. Piper's job — engage every inbound lead immediately, qualify it, and route it — is exactly the work that falls through the cracks when your SDR team is small or nonexistent. If your web-to-lead flow currently feeds a queue someone checks twice a day, this is the highest-leverage role on the slate.

2. Casey or Fin — because support scales badly

Support volume grows with your customer base; support headcount grows with budget approvals. Casey (the Help Agent, which we covered when its pay-per-resolution pricing launched) handles the front line across chat, voice, and messaging. Fin is the heavier-duty option for multi-step workflows — think order changes, renewals gone sideways, entitlement questions that touch three systems. Most mid-market teams should start with Casey's scope and graduate to Fin's, not the reverse.

3. Hunter — worth a screening call, not an offer yet

An outbound agent that builds pipeline and coordinates with sellers is the most tantalizing role for revenue leaders — and the one still in pilot, with GA slated for November. Outbound is also where AI missteps are most visible to prospects who've never met you. Watch the pilot results, ask for B2B reference customers at Dreamforce, and plan a controlled trial for Q1 2027 rather than a quota-carrying deployment this year.

Paige, the IT and HR service agent, is a legitimate fourth candidate if your internal helpdesk runs through Slack and drowns in password resets — but for most mid-market teams the revenue-facing roles come first.

The Interview Questions: What to Check Before You "Hire"

You wouldn't hire a salesperson without an interview and a reference check. The same discipline applies here. Five questions to answer before any of these agents gets an offer:

Is your data ready to onboard them? A job-ready agent still learns your business from your org. If your knowledge articles are stale, your lead routing rules contradict each other, or duplicate accounts are everywhere, the agent inherits all of it — at machine speed. Fix the org first.
What does it cost at your volume? Casey launched with per-resolution pricing, and Salesforce is increasingly metering agent work through consumption. Before committing, model your actual monthly case and lead volumes against the pricing you're quoted, including the months where volume spikes. "Agentic Work Units" at scale is a real line item; make finance a stakeholder on day one.
Where does the human handoff happen? The difference between a good agent deployment and a support disaster is a cleanly designed escalation path. Define which conversations the agent must hand off, to whom, with what context — and test it before go-live, not after.
How will you measure the 90-day review? Set the agent's success metrics the way you'd set a new hire's ramp targets: resolution rate, lead response time, conversion on agent-touched leads, CSAT on agent-handled cases. Baseline those numbers now, before deployment, or you'll never know what changed.
How much orchestration lock-in are you taking on? Multi-agent orchestration is genuinely useful — and it deepens platform commitment. That's not a reason to avoid it; it's a reason to make the choice deliberately, with eyes open about switching costs later.

Watching from Dreamforce Week

Dreamforce 2026 runs today through September 17, and this agent portfolio will be all over the keynotes — expect live demos, more customer numbers, and likely additional announcements layered on top. If you're following along from your desk, the practical move is to collect claims now and validate them against your own org's reality afterward. The vendors' best week of the year is precisely the week to keep your evaluation discipline.

The Bottom Line

Salesforce packaging agents as named, job-ready hires is a real shift, and for mid-market B2B teams it lowers the barrier that has kept agentic AI in the "next year" column: the build. But job-ready doesn't mean org-ready. These agents will be exactly as good as the data, processes, and escalation paths they're onboarded into — which means the highest-ROI move this quarter may be getting your org into shape to hire them well.

That's a fast thing to find out. Run the free 2-minute org health check at 360quantumsolutions.com, or book a 5-day org audit and we'll tell you — with 16+ years in the Salesforce ecosystem behind it and a fixed fee in front of it — exactly what stands between your org and its first AI hire.

Salesforce Winter '27 Goes Live: What Mid-Market B2B Teams Get

Tue, 08 Sep 2026 13:23:42 GMT

Your Salesforce org is about to change — whether you log in to watch it happen or not. The Winter '27 release begins rolling out to production orgs across three upgrade weekends, with most instances updating on October 3 or October 10, 2026. Back in August we walked through how to use the sandbox preview window to get ready. Now the release notes are final, the feature list is public, and the question has shifted from "how do I prepare?" to "what exactly am I getting?" Here's the plain-English rundown for mid-market B2B teams: the changes that happen to you automatically, the ones worth switching on, and a short action plan to close out before go-live weekend.

1. First Things First: Know Your Go-Live Date

Salesforce rolls out major releases in waves. A small set of instances received Winter '27 on August 29, but the bulk of production orgs upgrade over the weekends of October 3 and October 10, 2026. Your exact date depends on the instance hosting your org — not on your company size or edition.

Finding your date takes two minutes: look up your instance in Salesforce Trust (status.salesforce.com), or check the box in Setup under Company Information. Put the date on your team calendar. Releases land over a weekend, so the practical implication is simple: the Monday after your upgrade weekend, your users log in to Winter '27, and any behavior change that ships enabled will already be live.

One quirk of timing worth noting: Dreamforce runs September 15–17, and the announcements coming out of San Francisco will dominate every Salesforce conversation for weeks. Don't let the keynote noise distract you from the release that is actually landing in your org two or three weeks later. Agentforce roadmap slides are interesting; a permissions change that breaks a workflow on a Monday morning is urgent.

2. The Changes That Happen Whether You're Ready or Not

Every release carries a handful of release updates — security and platform changes Salesforce enforces on a schedule, not on your preference. Winter '27 has several that deserve a spot on your test plan.

Profile filtering tightens who can see what

Once enforced, users without the View All Profiles permission can only see their own profile information. That's a sensible least-privilege default, but if you have custom components, reports, or integrations that reference other users' profile data, they may quietly stop returning what they used to. Test anything user-management-related in your preview sandbox before go-live.

Setup Audit Trail gets its own permission

Access to the Setup Audit Trail is moving behind a dedicated View Setup Audit Trail permission. If your ops team, auditors, or a managed package rely on reading the audit trail, make sure the right permission sets grant it explicitly.

The OAuth username-password flow is being retired

This is the one most likely to bite mid-market teams. The OAuth 2.0 username-password flow for connected apps — a favorite shortcut for older integrations, middleware scripts, and quick internal tools — is on its way out. If anything in your stack authenticates to Salesforce by posting a username and password to the token endpoint, it needs to migrate to a supported flow. Inventory your integrations now; the ones built by a contractor three years ago are exactly the ones nobody remembers until they fail.

Bulk email updates require verified domains

If your admins perform bulk updates to user email addresses, you'll need Authorized Email Domains or DKIM configured for verification support. Mostly relevant during migrations and re-orgs — but that's precisely when you least want a surprise.

3. Quiet Wins for Admins and Sales Ops

Not everything in Winter '27 is homework. Several features are the kind of small, daily-friction fixes that make your org more pleasant to live in — the ones worth actively turning on rather than discovering by accident next year.

Preview records from reports (beta). Users can open a record preview in a sidebar without leaving the report. Fewer tabs, less context-switching — your pipeline-review meetings will feel it immediately.
Keep manual shares when transferring records. Historically, reassigning a record wiped its manual shares. A new setting preserves them — a real improvement for B2B teams that share key accounts across sales, service, and success.
More flexible inline editing in list views. New settings let users edit fields that aren't on the page layout and edit in list views with multiple record types. List views get closer to the lightweight workspace reps actually want.
Field history tracking on the User object (GA). Track up to 20 fields on User records — long requested for security reviews and compliance, and useful the next time someone asks "who changed that role?"
Joined reports show common rows only (beta). A new option displays only the records that appear in every block of a joined report — handy for questions like "which open opportunities also have open cases?"
Reports and dashboards in LWR Experience Cloud sites (beta). If you run a partner or customer portal on the newer LWR framework, you can finally embed Lightning reports and dashboards directly.

4. Flow Builder Grows Up a Little More

Automation is where mid-market orgs quietly accumulate risk — dozens of flows, built across years by different hands. Winter '27 brings a wave of Flow improvements aimed at exactly that problem.

Flow Tags let you organize flows with custom tags grouped into categories, so "which flows touch Opportunities?" stops being an archaeology project. A new unified Test Mode (beta) supports repeatable test runs with saved input values — a meaningful upgrade over debugging from scratch every time. Edit history and version comparison improvements show what changed between versions, save by save. And an unused resources filter flags variables nothing references, which makes cleanup realistic instead of aspirational.

Two additions matter beyond convenience. Bulk screen flows can now process multiple records selected from a list view — think mass-updating a batch of renewals in one guided flow instead of one record at a time. And a new user-context enforcement option ensures a flow runs with the running user's permissions regardless of how it was invoked — worth reviewing anywhere your flows touch sensitive data, since it closes a gap between what a user can do and what a flow does on their behalf.

Builders also get validation help: Flow Builder now warns when a Create Records element is missing required fields and checks for values that exceed field length limits before you save — the sort of guardrails that catch errors in the build, not in production.

5. Your Pre-Go-Live Checklist

If you did nothing during the sandbox preview window, there's still time to run an abbreviated version of the playbook. Here's a focused week of work:

Confirm your upgrade date on Salesforce Trust and tell your team. Ten minutes.
Open the Release Updates page in Setup and review everything with an enforcement date. Profile filtering and the audit trail permission belong at the top of the list.
Inventory your integrations for the username-password OAuth flow. Check connected app login history to find anything still using it, and plan migrations for what you find.
Test your top five business-critical flows in a Winter '27 sandbox — quote approval, lead routing, renewal processing, whatever would generate a Monday-morning fire drill if it broke.
Pick two or three quick wins to enable — record previews in reports, flexible inline editing, keeping manual shares — and tell users about them. A release your reps notice as an improvement builds trust in the platform (and in you).
Schedule a 30-minute post-release check for the Monday after your upgrade weekend: review error emails, spot-check automations, ask team leads what looks off.

The Bottom Line

Winter '27 isn't a flashy release, and that's fine — the flashy announcements will be on the Dreamforce stage next week. What this release delivers is steady platform hygiene: tighter default security, better tooling for the automations you already depend on, and a stack of small usability wins your team will feel daily. The teams that get burned by releases are rarely surprised by the features; they're surprised by the enforcements they never tested.

If you're not sure where your org stands — which release updates are pending, which integrations are on borrowed time, which flows would fail a test run — that's exactly what our free 2-minute org health check at 360quantumsolutions.com is for. And if the check turns up more than you want to tackle solo, our 5-day org audit gives you a prioritized, fixed-fee roadmap before go-live weekend arrives. Your Salesforce should be your #1 sales tool. Let's make it one.

Claudeforce: What Salesforce + Anthropic Means for Mid-Market B2B

Tue, 01 Sep 2026 13:42:30 GMT

Salesforce made two announcements on August 26 — record second-quarter earnings, and an expanded partnership with Anthropic called Claudeforce. The earnings got the headlines for a day. The partnership is the one that will change how your team actually works. If your company runs on Salesforce and your reps already keep an AI assistant open in a second browser tab, this news is about you: those two worlds are being wired together, officially, starting this month.

As with most platform announcements, the press release mixes things you can use soon with things that are still roadmap. Here is a plain-English breakdown of what was announced, why Salesforce did it now, what it means for mid-market B2B teams specifically, what is still unknown — and five practical things to do about it in September.

1. What Was Actually Announced

Claudeforce is not a single product. It is three integrations moving in both directions between Salesforce and Anthropic's Claude.

Salesforce in Claude

A plugin that puts your CRM inside the Claude assistant itself. It ships with 37 prebuilt sales skills — meeting prep, deal-health reviews, pipeline reviews — and can generate interactive dashboards from live Salesforce data. Two details matter for smaller teams. First, setup is centralized: an admin authenticates once, and sellers get access without per-user configuration. Second, your business rules and permissions are enforced through Salesforce — the assistant sees what the user is allowed to see, not more. It is with select pilot customers now, with an open beta expected in September 2026 and additional skills planned for late 2026.

Claude inside Salesforce

Claude becomes an available reasoning model for the Atlas Reasoning Engine — the decision-making layer behind Agentforce — and the default model powering Agentforce Vibes and Agentforce Coworker. It is also available in Agent Builder, and for regulated industries it can run via Amazon Bedrock inside the Salesforce Trust Boundary, meaning the model operates within Salesforce's security perimeter rather than shipping your data out to a third party.

Claude across Slack

Claude becomes the default model for Slack, powering an enhanced Slackbot. Salesforce says its own internal Slackbot deployment generated 8.1 million hours of annualized productivity gains, roughly doubling quarter over quarter. That is a vendor's own number about its own workforce — treat it as directional, not a promise — but the direction is clear: Slack is becoming an AI surface, not just a chat tool.

2. Why Salesforce Did This Now

The timing was not an accident. Claudeforce landed the same day as Salesforce's Q2 fiscal 2027 earnings: $11.3 billion in revenue, up 11% year over year, with Agentforce annual recurring revenue passing $1.5 billion — up more than 240% — and Agentforce plus Data 360 combined approaching $3.9 billion in ARR.

Behind those numbers sits the question the industry has been calling the "SaaSpocalypse": if AI assistants can reason over your data and take actions directly, do you still need traditional software interfaces at all? Marc Benioff's answer — "the UI is the AI" — is telling. Rather than betting that users will keep living inside CRM screens, Salesforce is putting its data and workflows wherever the user already is: in Claude, in Slack, in an agent. For customers, that is mostly good news. It means the vendor is competing on where work actually happens instead of forcing work back into its own tabs.

3. What It Means for Mid-Market B2B Teams

Enterprise announcements often take years to trickle down. This one is unusually relevant to mid-market teams from day one, for three reasons.

It attacks the adoption problem, not the feature problem. The perennial mid-market complaint is not that Salesforce lacks capability — it is that reps will not live in it. Notes go stale, pipeline reviews run on gut feel, and the org becomes an expensive system of record instead of a sales tool. An assistant that preps meetings and flags deal risks in the tool a rep already has open is a different adoption equation than another dashboard nobody logs into.

It lowers the cost of "good AI" inside Agentforce. Until now, getting frontier-model reasoning into a Salesforce agent meant custom integration work. Making Claude a first-class model option in Agent Builder means smaller teams get the reasoning quality without the plumbing project.

Governance comes along for the ride. The most underrated line in the announcement is that business rules are enforced through Salesforce. Mid-market companies rarely have an AI governance team; inheriting your existing permission model is the practical alternative. The catch: that only helps if your permission model is actually right — more on that below.

4. What We Don't Know Yet

Being honest about the gaps is part of reading any platform announcement well. As of today, Salesforce has not disclosed pricing or licensing for Salesforce in Claude — no word on per-seat versus consumption pricing, and no confirmation of which Salesforce editions will qualify. The productivity statistics come from Salesforce's own internal use, not customer deployments. And the whole thing is at pilot stage: open beta is "expected" in September, and the fuller skills catalog is a late-2026 roadmap item.

The practical translation: this is worth preparing for now, but not worth budgeting around yet. Do not sign anything, and do not pause an automation roadmap that is already working while you wait.

5. Five Things to Do in September

Whether or not you touch the beta, the preparation is the same — and none of it is wasted, because it is the same preparation Agentforce, Data Cloud, and every other AI feature on the platform demands.

Get your data AI-ready. An assistant reasoning over your org is only as good as the org. Duplicate accounts, stale stages, and empty required fields do not just annoy admins anymore — they now produce confident, wrong AI answers in front of your reps. Start with the objects your sales process actually runs on: Accounts, Opportunities, Activities.
Audit your permission and sharing model. "The assistant sees what the user sees" is only reassuring if users see the right things. Years of accumulated profiles, permission sets, and org-wide defaults deserve a review before an AI starts surfacing everything a login can technically reach.
Inventory the AI your team already uses. Most sales teams are already pasting CRM data into some assistant unofficially. Knowing where that happens tells you exactly which official integration will deliver value first — and which shadow-AI habits to retire.
Ask about the open beta before Dreamforce. Dreamforce runs September 15–17, and Claudeforce will dominate the agenda. Going in with a specific question — "when does the open beta reach our edition, and what will it cost?" — beats absorbing two hours of keynote and coming home with a slogan.
Keep shipping the fundamentals. Clean automation, a trustworthy pipeline, adoption your managers believe in — every one of these compounds the value of whatever AI layer arrives next. Teams that treat 2026 as a waiting room will start from behind.

The Bottom Line

Claudeforce is the clearest signal yet of where CRM is heading: the system of record stays, but the interface follows the user. For mid-market B2B teams, the winners will not be the ones who adopt the newest assistant first — they will be the ones whose org is clean, governed, and adopted enough for any assistant to be useful. That part does not ship in a press release; it is work you can start this week.

If you would like an objective read on whether your org is ready for what is coming, start with our free 2-minute org health check at 360quantumsolutions.com — or book a consultation and we will walk through it with you. Fixed-fee, no PM layers, and a go-live date we actually keep. Your Salesforce should be your #1 sales tool. Let's make it one.

The Agentforce ROI Gap: How Mid-Market Teams Land on the Right Side

Tue, 25 Aug 2026 13:31:36 GMT

Here are two facts, both published within the last few months, that don't seem to belong in the same universe. Salesforce reports that Agentforce has passed $1.2 billion in annual recurring revenue, growing 205% year over year. And in a TD Cowen survey of Salesforce partners across the US, Europe, and Asia, reported this week by Salesforce Ben, exactly zero respondents said Agentforce influenced their recent bookings. Not few. Zero.

Both numbers are real. Understanding how they can both be true is the most useful thing a mid-market B2B leader can do before signing — or renewing — an AI line item this year. Because the gap between those two numbers is where budgets go to disappear, and where a small group of disciplined teams is quietly getting results while everyone else runs pilots.

In this post, we'll unpack what the numbers actually say, why the ROI gap exists, and give you a six-step plan for ending up on the right side of it — plus the questions worth asking at Dreamforce next month.

Two Scoreboards, Two Very Different Stories

On Salesforce's scoreboard, agentic AI is a runaway success. The company's Q1 FY27 results (May 2026) put Agentforce and Data 360 combined ARR at nearly $3.4 billion, up more than 200% year over year, with 3.8 billion "agentic work units" delivered in the quarter. Over half of Agentforce and Data 360 bookings came from existing customers — companies coming back for more, not just trying it once.

On the ecosystem's scoreboard, the picture is cooler. The TD Cowen partner survey reported on August 24 found that while 33% of partners observed buying and trial activity, and 56% expect interest to grow as the product matures, not a single respondent named Agentforce as a driver of recent bookings. Salesforce Ben's Dreamforce preview the same week argued the conference now "has one job": stop demonstrating what agents could do and start proving what they have done in production, with real deployment costs, governance frameworks, and honest failure stories.

How do you reconcile a product selling at billion-dollar scale with a partner channel that isn't feeling it? Simple: licenses are being bought faster than value is being realized. Companies are paying for agentic AI. Far fewer have wired it into their business deeply enough to point at a number that moved. That's not a scandal — it's the normal shape of an early technology cycle. But it has a very practical implication: the ROI isn't in the product; it's in the implementation discipline.

Why the Gap Exists

Having spent 16+ years in the Salesforce ecosystem, we've watched this movie before — with Communities, with Einstein, with CPQ. The failure patterns behind the Agentforce ROI gap are familiar, and they're avoidable.

Pilots that never leave the lab

The most common Agentforce deployment in 2026 is a proof of concept that answered questions in a sandbox, impressed a steering committee, and then stalled. Pilots stall because nobody scoped the harder second half: connecting the agent to real knowledge, real records, and real escalation paths. A demo takes weeks. Production takes commitment — data access, guardrails, and a human handoff process someone actually owns.

Use cases chosen for demo appeal, not economics

"An agent that can answer anything about our business" demos beautifully and returns nothing, because it has no baseline to beat. The use cases generating real returns are narrow and high-volume: password resets, order status, quote follow-ups, case triage. Boring wins. Boring is measurable.

No baseline, so no proof

Many teams switched on an agent without first recording what the process cost before. If you don't know your current cost per resolved case or your rep's hours per week spent on status queries, you mathematically cannot demonstrate ROI later — even if the agent is performing well. The gap between "it seems helpful" and "it returned 3x" is usually just a missing baseline.

Data and process debt, unpaid

An agent grounded in a knowledge base that was last updated in 2023, reading records with duplicate accounts and empty fields, will confidently automate confusion. Salesforce Ben's coverage notes that the underlying blockers — disconnected processes, technical debt, siloed data — don't disappear because an agent sits on top of them. Agents amplify whatever org hygiene you already have, in either direction.

The Mid-Market Advantage Nobody Talks About

Here's the counterintuitive part: mid-market B2B companies are better positioned to close this gap than the enterprises headlining keynotes. You have fewer systems to integrate, fewer committees between a decision and a deployment, and processes simple enough that one well-chosen agent can touch a meaningful percentage of total workload. An enterprise needs eighteen months of alignment to ship what you can ship in a quarter — if you pick the right target and measure it honestly.

The mid-market risk runs the other way: smaller teams have less slack to absorb a science project. A stalled pilot that's a rounding error for an enterprise is real money for a 200-person company. Which is exactly why the discipline below matters more for you, not less.

A Six-Step Plan for Landing on the Right Side of the Gap

This is the sequence we recommend to any mid-market team evaluating or restarting an Agentforce initiative this quarter.

Pick one narrow, high-volume use case. One. Look for a task that happens at least 50 times a week, follows a repeatable pattern, and has a clear "done" state — case deflection, order status, meeting scheduling, quote chasing. Resist the platform-wide vision until the first number is on the board.
Record the baseline before you build anything. Measure today's cost: volume per week, minutes per instance, loaded hourly cost of the people doing it, current resolution rate, current response time. Two weeks of honest measurement is enough. This step is what separates provable ROI from vibes.
Fix the data the agent will actually touch — and only that. You don't need a two-year data quality program. You need the knowledge articles, record types, and fields inside your one use case to be current and deduplicated. Scope the cleanup to the agent's blast radius.
Define success and kill criteria in writing. For example: "60% autonomous resolution at equal-or-better CSAT within 90 days of production, or we stop." A kill criterion isn't pessimism — it's what makes a green light credible, and it's the single best defense against pilot purgatory.
Go to production with a human handoff, not a bigger pilot. A small, live deployment serving real customers teaches you more in three weeks than three more months of sandbox testing. Make sure every conversation has an explicit escalation path to a named team, and review the transcripts weekly.
Report cost per outcome, monthly, to whoever owns the budget. Agentforce's consumption-style pricing means costs scale with usage — so track dollars per resolved conversation against your baseline human cost, not license spend in isolation. If the number is good, scale to use case two. If it isn't, your kill criteria already told you what to do.

Taking This Lens to Dreamforce

Dreamforce 2026 runs September 15–17 in San Francisco, and the pressure is on Salesforce to show production proof rather than demo polish. Whether you attend or just follow the announcements, evaluate everything through the gap: for any customer story on stage, ask what the baseline was, what it cost to implement, how long from kickoff to production, and what happened to CSAT after go-live. Sessions that answer those questions are worth your time. Sessions that don't are marketing.

And if history is a guide, expect new products and new pricing to be announced. The plan above doesn't change: one use case, one baseline, one number.

The Bottom Line

The Agentforce ROI gap is real, but it isn't a verdict on the technology — it's a verdict on how most companies are deploying it. The winners in the survey data's next edition will be the teams that picked narrow use cases, measured before they built, cleaned only the data that mattered, and shipped to production with clear success criteria. None of that requires enterprise budgets. It requires discipline — which is free — and an org that's structurally ready, which is checkable.

That second part is where we can help. 360 Quantum Solutions offers a free 2-minute org health check at 360quantumsolutions.com, and a fixed-fee 5-day org audit that tells you exactly whether your data, automation, and processes are ready to support an agent — before you spend a dollar on one. No PM layers, no scope creep, just a certified consultant and a straight answer. If you'd rather be on the right side of the gap, let's talk.

Dreamforce 2026 Preview: What Mid-Market B2B Teams Should Watch

Tue, 18 Aug 2026 13:24:29 GMT

Dreamforce 2026 is four weeks away. From September 15–17, Salesforce takes over the Moscone Center in San Francisco under a banner that tells you exactly where the company's head is at: "The Agentic Enterprise." And Salesforce isn't waiting for the keynote — it has already started teasing what's coming, with a wave of pre-Dreamforce product updates landing this week.

Here's the thing, though. Most mid-market B2B teams won't be flying to San Francisco, and frankly, most don't need to. The full conference pass runs $1,899 at the current "last chance" rate ($2,299 regular), and the announcements that will actually change your roadmap can be evaluated from your desk — for free. What you do need is a filter: a way to separate the announcements that matter for a 50-to-500-person B2B company from the enterprise showcase content that doesn't.

This is that filter. What's likely coming, what to watch, the questions to ask of every announcement, and how to get real value out of Dreamforce week without leaving the office.

1. The Setup: Where Salesforce Stands Going Into Dreamforce

Context matters, because it shapes what Salesforce will emphasize on stage. Agentforce is the company's biggest bet in a decade, and Salesforce has said it passed $1 billion in annual recurring revenue earlier this year. Q2 earnings land in early September — right before the conference — and analysts will be watching for proof that agentic AI is translating into durable revenue, not just pilots.

That means Dreamforce 2026 will be heavy on customer proof points: real deployments, resolution numbers, ROI stories. For you, that's actually useful. The 2024 and 2025 events were about what Agentforce could do. This year, the more interesting content will be what it's actually doing in production at companies your size — and what it costs. Pay attention to the case-study sessions and community roundtables (there are 240+ of those), not just the main stage.

2. "The Agentic Enterprise" — Translated for Companies That Aren't Enterprises

Salesforce's theme this year describes a business where AI agents handle defined chunks of work — qualifying inbound leads, resolving support cases, chasing overdue invoices — while people supervise, handle exceptions, and do the work that needs judgment.

If you're a mid-market B2B company, don't dismiss this as enterprise theater. The economics of agents arguably favor you more than they favor the Fortune 500. A 200-person company can't hire its way out of a support backlog or a slow quote process; an enterprise can. Outcome-based pricing — like the $2 pay-per-resolution model Salesforce introduced with Agentforce Help Agent — lowers the entry cost to something a mid-market budget can absorb without a capital request.

The catch, as always, is readiness. Agents are only as good as the data and processes underneath them. An org with duplicate accounts, stale contacts, and undocumented process quirks will produce an agent with the same problems, at higher speed. More on that at the end.

3. What's Likely to Be Announced (Based on What Salesforce Has Teased)

Salesforce has been previewing announcements ahead of the event, and the clearest signals this week center on the Headless Experience Layer (HXL) and the Multi-Agent Framework inside Agentforce 360. Based on reporting from Salesforce Ben this week, here's what's expected to reach general availability at or around Dreamforce:

HXL Widget Builder — pitched as removing the coding side of agentic development, letting teams assemble agent-powered experiences without a developer for every change.
HXL Channels — currently in beta, these let agents show up where people already work: Lightning, Slack, Microsoft Teams, ChatGPT, and Claude, with Gemini support planned.
Vibe enhancements — updates to Salesforce's AI-assisted building tools.
Micro-Frontends — a scalability play for teams running multiple UI frameworks.

Multi-Framework React has already hit general availability, which lets teams bring existing React applications into Agentforce 360, and Angular support is heading into beta.

Why the headless push matters to you

Strip away the jargon and the strategy is simple: Salesforce wants its agents working in front of your customers and employees wherever they are — your website, your customer portal, Slack, Teams, even inside other AI assistants — not just inside a Salesforce screen. For B2B companies, that's the difference between "we bought an AI tool" and "our customers can get an accurate order status at 11pm without emailing anyone." The usual caveat applies: these are forward-looking plans and Salesforce can change them, so treat everything as tentative until it's in the release notes.

4. How to Get Real Value Without Flying to San Francisco

Salesforce streams Dreamforce free on Salesforce+, with 400+ virtual sessions running September 15–18. The trap is treating it like background TV. Here's a plan that takes one person about four hours across the week:

Register for Salesforce+ now. It's free, and you can build a session agenda in advance instead of browsing live.
Pick five sessions, maximum. One keynote, two sessions matching your 2027 roadmap (say, Sales Cloud plus your data strategy), and two customer stories from companies your size or your industry. More than five and none of them get watched.
Assign owners. If your admin watches the admin track and your sales ops lead watches the Sales Cloud sessions, nobody sits through 1,600 breakouts and everything relevant gets covered.
Watch "True to the Core" if you watch nothing else. It's the Q&A where Salesforce executives answer unscripted questions from customers — reliably the most honest hour of the event, especially on roadmap and pricing.
Write a one-page debrief. Three announcements that could affect your org, one thing to test in a sandbox, one question for your account executive or partner. That page is the deliverable; everything else is entertainment.

5. The Watchlist: Five Questions to Ask of Every Announcement

Keynote demos are built to look effortless. Before anything from Dreamforce lands on your roadmap, run it through these five questions:

Is it GA, beta, or pilot? "Announced" and "available" are different things in the Salesforce world, sometimes by a year or more. Only GA features belong in your near-term plans.
What does it require? Many headline features quietly assume Data Cloud, specific editions, or add-on licenses. Ask what the real prerequisite stack is before you get excited.
How is it priced? Per user, per conversation, per resolution, or consumption credits? The pricing model determines whether a feature is a rounding error or a budget line for a mid-market org.
Who maintains it? An agent isn't a set-and-forget purchase. Someone has to own its instructions, monitor its answers, and update it when your business changes. If you can't name that person, you're not ready to buy.
What's being retired to make room? Big pushes forward usually come with quiet deprecations. Listen for end-of-life dates on features you actually use — they matter more than the shiny new ones.

6. Don't Let Dreamforce Distract You From Winter '27

One practical warning: Dreamforce lands in the middle of release season. Winter '27 sandbox previews open around August 29, and production upgrades roll out in the weeks around the conference. It's easy to spend September absorbed in announcement coverage while the release that will actually change your org next month goes untested.

Do the boring thing first. Confirm which release weekend your org is on, get your sandbox on the preview, and smoke-test your critical flows, integrations, and email deliverability settings. The Dreamforce keynote will be on demand forever; your release window won't move for anyone.

The Bottom Line

Dreamforce 2026 will be a three-day argument that the agentic enterprise has arrived. For mid-market B2B teams, the right response is neither cynicism nor a blank check — it's a short watchlist, five hard questions, and an honest look at whether your own org is ready for what's coming. The companies that get value from the agent era won't be the ones who watched the most keynotes; they'll be the ones whose data, processes, and org foundations were solid before they switched anything on.

Not sure where your org stands? That's exactly what we're here for. Start with our free 2-minute org health check at 360quantumsolutions.com, or book a consultation and we'll take a deeper look — our 5-day org audit tells you precisely what to fix before you bring agents anywhere near your customers. Fixed fee, direct access to certified consultants, and an on-time go-live guarantee. Your Salesforce should be your #1 sales tool. Let's make it one.

The 2026 Salesforce Breach Wave: Is Your Org's Front Door Open?

Tue, 11 Aug 2026 14:03:48 GMT

On August 4, Brinks Home — a company whose entire business is keeping intruders out — confirmed that attackers had stolen roughly 4.9 million customer records from its Salesforce environment. The breach was detected on July 20, and it's only the latest entry in a list that has been growing all year. If your company runs Salesforce and has any kind of public-facing portal, community, or help center, this story is about you — even if you've never heard of the attackers involved. Here's what has actually been happening in 2026, why it's a configuration problem rather than a platform problem, and a practical checklist you can work through this week to make sure your org isn't next.

1. What's Actually Happening: The 2026 Breach Wave in Brief

The attacks trace back largely to one group, ShinyHunters, which spent 2026 systematically scanning the internet for misconfigured Salesforce Experience Cloud sites — the public communities, portals, and help centers thousands of companies run on top of their orgs. The year opened with Grubhub confirming a breach in January. By March, the group claimed to have compromised roughly 100 high-profile companies, with broader estimates putting the total between 300 and 400 organizations. The victims since then read like a cross-section of the economy: LexisNexis (3.9 million records), Canadian grocery giant Loblaw (a claimed 75 million records), Hallmark (7.9 million), home security provider ADT (over 10 million), and now Brinks Home.

The response from regulators was unusually fast. On March 7, Salesforce announced it was "tracking an increase in threat actor activity" targeting misconfigured public-facing sites, and FINRA issued a cybersecurity alert the same week urging member firms to review guest user permissions and treat any exposed data as compromised. Stolen data hasn't just been sold — it's being used to fuel targeted phishing, voice phishing (vishing), and extortion campaigns against the affected companies' employees and customers.

This follows the 2025 campaigns that hit Salesforce customers through social engineering and compromised third-party app integrations. The playbook keeps evolving, but the pattern is consistent: attackers aren't breaking into Salesforce. They're walking through doors that customers left open.

2. The Uncomfortable Truth: It's Not Salesforce, It's the Settings

Salesforce has been blunt about this: "this issue is not due to any vulnerability inherent to our platform." And the technical details back that up. The attackers used a modified version of an open-source scanning tool to probe publicly accessible Experience Cloud endpoints, looking for guest user profiles with overly generous permissions. Where they found one, they could query data through standard APIs — in some cases using a quirk of query sorting to page past the usual 2,000-record limit and extract entire databases.

Nothing in that chain is an exploit in the traditional sense. Every step uses functionality working exactly as designed. The vulnerability is the configuration: a guest user profile that can read Contact records it shouldn't, org-wide defaults left at Public Read Only for external users, API access enabled for anonymous visitors who never needed it.

This is the cloud's shared responsibility model in action. Salesforce secures the platform; you secure your configuration. It's the same reason a deadbolt manufacturer isn't liable when someone leaves the door unlocked. The good news buried in that uncomfortable truth: because the problem is configuration, the fix is also configuration. You don't need to buy anything. You need to audit.

3. Why Mid-Market Orgs Are Prime Targets

It's tempting to read the headlines — Loblaw, ADT, LexisNexis — and conclude this is an enterprise problem. The opposite is closer to the truth. These attacks are automated mass scans. The attackers aren't choosing targets by revenue; they're harvesting every misconfigured site their tools can find. A 200-person distributor's customer portal shows up in the same scan results as a Fortune 500's.

Mid-market orgs are often more exposed, for three familiar reasons. First, many portals were built years ago — by a consultant long gone or an admin two admins ago — and haven't had a security review since. Second, most mid-market teams run lean: one admin wearing five hats, with no dedicated security function watching sharing settings. Third, there's a widespread assumption that "Salesforce handles security," which is true for the infrastructure and false for your data model. If you launched an Experience Cloud site before guest user security tightening became a priority, and no one has revisited it, there's a real chance your guest profile can see more than you think.

4. The Lockdown Checklist: 10 Steps to Close the Front Door

Here's the practical part. Most of these steps take minutes to check, and together they address the exact weaknesses being exploited right now. Work through them in order.

Inventory every public-facing site. In Setup, go to All Sites and list every Experience Cloud site, Salesforce Site, and portal — including ones marked inactive or built for long-dead projects. You can't secure what you don't know exists, and attackers' scanners don't care whether you remember the site.
Audit each guest user profile. For every site, open the guest user profile and review object and field permissions. The standard is minimum necessary: if the portal only needs to create Cases, the guest user shouldn't be able to read Contacts, Accounts, or custom objects holding customer data.
Set external org-wide defaults to Private. Sharing settings for external users should start from Private, with access granted back deliberately. Public Read Only defaults for external users are exactly what this campaign feeds on.
Review sharing rules that grant guest access. Guest user sharing rules are the only supported way to open records to unauthenticated visitors — so each one should be individually justified. Delete any rule nobody can explain.
Remove API access from guest users. Salesforce's own guidance during this campaign: disable public APIs in guest user permissions unless you have a specific, current business reason. Anonymous visitors rarely need programmatic access to anything.
Uncheck Portal User Visibility and Site User Visibility. These sharing settings quietly widen who external users can see. Salesforce specifically flagged both in its hardening recommendations this year.
Disable self-registration if you don't use it. Every self-registration page is an account-creation endpoint exposed to the internet. If it isn't serving a live business process, turn it off.
Run Security Health Check. The free tool in Setup scores your org against Salesforce's baseline and flags high-risk settings — session security, password policies, and more. It takes two minutes to run and gives you a prioritized punch list.
Audit connected apps and integration users. The 2025 wave of attacks came in through third-party integrations and stolen OAuth tokens. Review every connected app, remove ones no longer in use, scope integration user permissions tightly, and enforce MFA everywhere it isn't already on.
Brief your team on vishing. Stolen data is being used to make phone-based social engineering frighteningly convincing. Make sure anyone with admin access knows that "IT support" calling to install a connected app or reset credentials is the attack, not the fix.

What If You Find a Problem?

If your audit turns up a guest profile with broad read access on a public site, assume the worst until proven otherwise. Tighten the configuration immediately, then check guest user activity against your logs. If data was exposed, treat it as compromised — that means heightened monitoring for phishing and extortion attempts, and a conversation with counsel about disclosure obligations in your industry. FINRA's alert made exactly this point for financial firms, and the logic applies broadly.

5. Make It a Habit, Not a Fire Drill

The orgs that came through 2026 unscathed aren't the ones that never made a configuration mistake — they're the ones with a rhythm for catching mistakes early. The simplest version: put a recurring security review on the calendar tied to Salesforce's three release cycles per year. Each release changes defaults, adds enforcements, and occasionally resurfaces old settings. Reviewing guest access, sharing defaults, connected apps, and Health Check scores three times a year turns a potential headline into a 90-minute routine.

It's also worth asking a harder question: who owns Salesforce security at your company? If the honest answer is "nobody, specifically," that's the real finding of this year's breach wave — and it's fixable without hiring anyone.

Conclusion

The 2026 breach wave is a story about configuration debt, and mid-market companies carry more of it per admin than anyone. The attacks are automated, indiscriminate, and ongoing — but every door they walk through is one a customer can close, today, with settings they already own. Work the ten-step checklist above this week, put the review on a schedule, and you'll be better protected than most of the companies in the headlines were.

Not sure what your org would show if someone scanned it tomorrow? That's exactly what our free 2-minute org health check is for — and if you want certified eyes on the full picture, our fixed-fee 5-day org audit covers guest access, sharing, connected apps, and everything else in this article. Start at 360quantumsolutions.com . Your Salesforce should be your #1 sales tool — not your biggest exposure.

Salesforce Winter '27: Your Sandbox Preview Playbook

Tue, 04 Aug 2026 13:30:58 GMT

Summer '26 has barely settled into your org, and the next release is already on the calendar. Ecosystem preview coverage points to the Salesforce Winter '27 sandbox preview opening around August 29, 2026, with production upgrades following across release weekends into October. That gives most teams about four working weeks to get ready — four weeks that happen to collide with Dreamforce (September 15–17) and the start of Q4 planning. For a mid-market team where "the Salesforce admin" is one person with three other jobs, that collision is exactly how release testing quietly falls off the list. This is the playbook for making sure it doesn't: the dates that matter, the changes worth testing first, and a four-week plan that fits around a real workload.

1. The Winter '27 Timeline, in Plain English

Salesforce ships three major releases a year — Spring, Summer, and Winter — and every one of them lands in your org whether you tested it or not. There is no "skip this version" button. The only real choice you get is whether you meet the release in a sandbox first or in production on a Monday morning.

The cycle works the same way each time. A few weeks before production upgrades begin, Salesforce opens a sandbox preview : sandboxes sitting on designated preview instances are upgraded to the new release early, so you can test your configuration, code, and integrations against it. For Winter '27, that preview window is expected to open around August 29, 2026 , with production instances upgrading on staggered release weekends through the fall — most orgs in October. Your exact upgrade date depends on your instance; check the Trust status site (status.salesforce.com) for the date attached to yours, and treat the official release notes and Sandbox Preview Guide as the source of truth once they're published.

The detail that catches teams out every cycle is the refresh cutoff . Whether a sandbox gets the preview depends on which instance it's on when the window opens — and that's determined by when you last refreshed it. Refresh at the wrong time and the sandbox you were counting on for testing stays on Summer '26 until your production org upgrades, which defeats the point. When Salesforce publishes the Winter '27 Sandbox Preview Guide, check every sandbox you care about against it the same week.

2. Why This Cycle Is Harder Than Usual for Mid-Market Teams

Two things make Winter '27 preparation awkward. The first is the calendar. The preview opens at the end of August, Dreamforce runs September 15–17, and Q4 kicks off with pipeline reviews, budget conversations, and — for many B2B companies — the busiest selling season of the year. Enterprise customers have release management teams to absorb that. Mid-market customers usually have one admin, and every one of those events competes for the same person's time.

The second is the direction recent releases have taken. As we covered in our Summer '26 breakdown, Salesforce has been steadily shifting from "here are new features you can opt into" toward "here are security and platform standards we are now enforcing." Enforcements are a different kind of risk: they don't add capability you can ignore, they switch off behavior your org may currently depend on. A feature you don't adopt costs you nothing. An enforcement you didn't test can break an integration on upgrade weekend.

3. What to Test First When the Preview Opens

Early Winter '27 coverage from the ecosystem highlights a handful of enforcement-style changes worth putting at the top of your test list. Treat these as the starting point for your own review of the official release notes rather than an exhaustive inventory — but if any of them apply to your org, they apply hard:

Legacy username-password API logins. The retirement of the old OAuth username-password flow has been flagged in preview coverage. Any integration still authenticating with a stored username, password, and security token — common in older middleware and homegrown scripts — needs to move to a modern OAuth flow. Your login history will tell you if you're affected.
Bulk email address updates. Coverage points to Email Change Verification becoming non-optional, with bulk user email updates requiring an Authorized Email Domain or DKIM configuration. If your team ever mass-updates user emails — after a rebrand, a domain migration, or an acquisition — set this up before you need it.
Hardcoded instance URLs. Links that point at "na139.salesforce.com"-style addresses instead of your My Domain — in integrations, email templates, custom buttons, or bookmarked reports — are a long-deprecated pattern that keeps getting riskier with every release. Search for them and replace them.
Automation that filters on profile names. Flows, validation rules, and Apex that branch on a profile's name break the moment someone renames a profile — and this pattern is increasingly constrained by the platform. Custom permissions are the durable replacement.
Accessibility and zoom behavior. Winter '27 coverage notes continued accessibility work, including how pages behave at 200% browser zoom. Spot-check your most-used record pages — dense custom layouts are where surprises hide.
Managed packages. Your AppExchange vendors test against the new release too, but not always on your schedule. Ask your critical vendors — CPQ, marketing automation connectors, document generation — to confirm Winter '27 readiness before the preview opens.

4. A Four-Week Prep Plan That Fits a Real Workload

You don't need a release management office to do this well. You need about an hour a week between now and the preview, spent in the right order:

This week — inventory. List your sandboxes and what each is used for. List every integration touching Salesforce and how it authenticates. List your managed packages. Write down your ten most business-critical processes — the flows, approval chains, and integrations that would generate angry phone calls if they stopped. This list becomes your regression checklist.
Week of August 10 — audit. Pull login history and look for legacy username-password API authentications. Search your metadata for hardcoded instance URLs and profile-name references in automation. Email your critical package vendors and ask for their Winter '27 compatibility statement.
Week of August 17 — position your sandboxes. When the Sandbox Preview Guide is published, confirm which of your sandboxes will receive the preview, and refresh your designated testing sandbox ahead of the cutoff so it lands on a preview instance with reasonably current data. Then stop refreshing it.
Week of August 24 onward — fix and test. Fix what you already know is wrong before the preview even arrives: configure DKIM or Authorized Email Domains, start migrating any legacy OAuth integrations, replace hardcoded URLs. Once your sandbox upgrades to Winter '27, run your ten-process regression checklist against it, log anything that behaves differently, and schedule a short note to end users about anything that will look or work differently in October.

5. Three Mistakes to Skip This Cycle

Don't plan to "deal with it in October." By the time your production org upgrades, the preview window has been open for weeks and every issue you find is already live. The whole value of the preview is finding problems while they're still theoretical.

Don't refresh your only good sandbox at the wrong moment. A refresh in the wrong week can move your sandbox off the preview track or wipe the test data you needed. Check the preview guide first, refresh deliberately, then leave it alone.

Don't confuse reading the release notes with being ready. The notes tell you what Salesforce changed; only testing tells you what breaks in your org. Mid-market orgs are rarely vanilla — years of flows, third-party packages, and quick fixes interact with releases in ways no document predicts. An hour of hands-on regression testing is worth an afternoon of reading.

Get Ahead of Winter '27 Before the Window Opens

Release readiness isn't glamorous work, but it's the difference between a release weekend nobody notices and a Monday spent triaging broken integrations during Q4. An hour a week between now and late August covers it — and most of that hour is inventory and cleanup your org needed anyway. If you'd like a second set of eyes before the preview opens, start with our free 2-minute org health check at 360quantumsolutions.com, or book a consultation about a 5-day org audit — we'll map exactly where Winter '27 touches your setup, with a fixed fee and no surprises. Your Salesforce should be your #1 sales tool going into Q4. Let's make sure the next release keeps it that way.

Salesforce Summer '26: 10 Changes Worth Understanding

Thu, 30 Jul 2026 13:57:05 GMT

Every Salesforce release note runs to hundreds of pages, and most of it won't touch your org. Summer '26 is different in one respect: it contains a small number of changes to default behaviour that can alter how existing code runs, and those deserve attention even from teams who normally skim.

Below are the ten changes we think matter most for mid-market teams, grouped by who needs to care. For each one we've said what it is, why it matters, and what to actually do about it. The full release notes are linked at the end — this is a filter, not a replacement.

The three security changes that can affect running code

These are the ones to read even if you read nothing else. They change defaults, which means code that worked before can behave differently after.

1. Apex now defaults to user mode

In API version 67.0, SOQL, SOSL, DML and Database operations enforce user mode by default. That means object permissions, field-level security and sharing rules are respected unless you explicitly say otherwise.

Why it matters: this is the right default and a genuine security improvement. But if you have Apex that quietly relied on system-level access — reading a field the running user can't see, updating a record they don't own — it may now return less data or throw where it previously succeeded.

What to do: this is a regression-test job, not a reading job. Run your test suite against a sandbox on the new API version and look specifically at anything touching sensitive fields or cross-owner records. Note that the change applies to classes compiled at API 67.0 and above, so existing classes don't shift until you bump them — which gives you control over the timing, if you use it deliberately.

2. Classes without a sharing keyword now default to "with sharing"

Previously, an Apex class that didn't declare with sharing or without sharing ran without sharing. That default has flipped.

Why it matters: for years the safe advice has been "always declare it explicitly." Teams that followed that advice are unaffected. Teams that didn't now have classes whose behaviour changes depending on when they were compiled, which is exactly the kind of thing that produces confusing bugs six months later.

What to do: search your codebase for classes with no sharing declaration and add one deliberately. It's mechanical work and it removes ambiguity permanently.

3. WITH SECURITY_ENFORCED no longer compiles

The WITH SECURITY_ENFORCED clause has been retired and replaced by WITH USER_MODE .

Why it matters: this isn't a deprecation warning — affected code won't compile. If you use it anywhere, that's a blocker rather than a nice-to-have.

What to do: search for it now. WITH USER_MODE is the replacement and is genuinely better: it handles polymorphic fields properly and reports field-level security violations more comprehensively.

For AI leaders: Agentforce grows up

4. Agentforce Builder and Agent Script go GA — and become the default on 13 July 2026

The new builder is generally available and becomes the default from that date, with one-click upgrades for legacy agents and configurable model selection in Agent Script.

Why it matters: the date is the point. If you have agents built in the previous tooling, the platform moves underneath you whether or not you've planned for it.

What to do: upgrade in a sandbox before the date rather than after, and re-run your agent test cases. Salesforce has also open-sourced the Agent Script toolchain — parser, linter, compiler and language server — under Apache 2.0, which matters if you want agent definitions in version control and reviewed like code. For most teams that's the right way to manage them.

5. Multi-agent orchestration arrives in beta

Orchestrator agents can now connect to specialised subagents, with Salesforce describing the pattern as a single front door backed by specialists behind it.

Why it matters: it directly addresses the biggest practical problem with agent design. One agent scoped to do everything performs poorly; several narrow agents perform well but confuse users who don't know which to talk to. Orchestration is the sensible resolution.

What to do: if you already have one working agent, this is how you add a second without degrading the first. If you have none, build one narrow agent well before reaching for orchestration — the pattern solves a problem you don't have yet.

6. Custom Scorers let you grade agent conversations against your own KPIs

In beta, you can score sessions against measures like sentiment, tone, product interest, escalation trigger and politeness, alongside the standard metrics, and deploy them through the Metadata API.

Why it matters: this is the missing piece for anyone running an agent in production. "Did it deflect the case" is easy to measure; "was it any good" has been much harder. Custom scorers make quality something you can actually track over time rather than sample by hand.

What to do: if you have a live agent, define two or three scorers that reflect what you'd tell a new hire to care about, and review them weekly. This is the practical answer to the "who monitors it in month six" question.

7. Agentforce voice extends across digital and mobile channels

Voice capability now spans digital and mobile surfaces, and the mobile SDK adds React Native support with a single TypeScript codebase across iOS and Android.

Why it matters: if you've been treating agents as a web-chat feature, the surface area just widened considerably — and so did the governance question about what an agent is allowed to say when nobody is reading a transcript.

For architects: the platform shifts

8. Salesforce-hosted MCP servers reach GA

There are now pre-built Model Context Protocol servers for SObject CRUD and SOQL, Data 360 queries and Tableau analytics, plus the ability to build custom servers from Apex actions, flows, Apex REST endpoints, prompt templates and Agentforce agents.

Why it matters: this is how external AI tooling talks to your org in a structured, governed way rather than through bespoke integrations. Strategically it's one of the more significant items in the release, even though it will show up on few admins' radar.

What to do: treat it as an access-control question first. An MCP server is a door into your data; decide deliberately what goes through it and who can use it, before someone stands one up because it was easy.

9. SOAP login() retires in Summer '27 — start now

The SOAP login() method retires next summer for API versions 31.0 through 64.0, with migration to OAuth required.

Why it matters: a year sounds like plenty until you discover the integration using it was built by someone who left, and nobody is certain what it connects to. Legacy middleware, data-loading tools and older point-to-point integrations are the usual suspects.

What to do: inventory your integrations this quarter. Finding them is the slow part; migrating to OAuth is usually straightforward once you know what you're dealing with.

10. Data 360 gets code extensions and finer query control

You can now deploy Python scripts for batch transformations, string manipulation, custom computation and chunking logic on isolated containers, and a new SET OPTIONS SOQL clause lets you specify dataspaces and control how empty strings and nulls are handled.

Why it matters: the transformation work that previously forced data out to an external tool can increasingly stay inside the platform. The SET OPTIONS addition looks small but the null-versus-empty-string distinction is a classic source of quietly wrong results.

What we'd actually do this month

If you do nothing else: search your codebase for WITH SECURITY_ENFORCED , because that one stops compiling rather than merely warning. Then audit Apex classes with no sharing declaration , and regression-test anything security-sensitive against API 67.0 in a sandbox .

If you run agents, upgrade to Agentforce Builder in a sandbox before 13 July rather than discovering the switch after the fact.

And whatever your timeline, start the SOAP integration inventory now . It's the only item here with a hard external deadline, and it's the one most likely to be forgotten until it isn't.

The full release notes are published in Salesforce Help, and the developer-focused summary on the Salesforce Developers blog is the best starting point for the technical items above.

If you'd like a view of which of these actually apply to your org rather than to orgs in general, our free Org Health Check runs Salesforce's own diagnostics against your setup — including a security and permissions review — and gives you a written summary of what to address first. No cost, no obligation.

Does Agentforce Require Data Cloud? A Decision Framework

Thu, 30 Jul 2026 13:54:45 GMT

It's one of the most common questions we get asked, and it's usually asked with a sinking feeling: "We want to build an agent. Do we have to buy Data Cloud first?"

The honest answer is that it depends on what your agent needs to know — and for a meaningful share of the use cases that mid-market teams actually want to build, the answer is no. The two products are related, and Salesforce positions them together for good reasons, but they are not inseparable, and treating them as a mandatory bundle can turn a focused six-week project into something considerably larger and slower.

This is the framework we use to work it out. It takes about twenty minutes with the right people in the room, and it will usually give you a clear answer.

The question underneath the question

An agent needs to ground its answers in something. The real question is never "do I need Data Cloud" in the abstract — it's "where does the information my agent needs actually live, and is it already usable where it sits?"

Data Cloud earns its place when the answer involves unifying data from multiple systems into one real-time profile. If your agent only needs things that already sit in your Salesforce org, cleanly, you may be adding a large piece of architecture to solve a problem you don't have.

So work through the following in order. Stop at the first one that clearly describes your situation.

Case 1: Everything the agent needs is already in Salesforce

Your agent answers questions about cases, opportunities, accounts, contacts, orders or knowledge articles — and all of that lives in your org today, reasonably clean and reasonably current.

You probably don't need Data Cloud. An agent can be grounded directly in your Salesforce records and your knowledge base. This covers a lot of genuinely valuable use cases: case deflection on documented topics, internal assistants that help reps find account context, service agents answering from existing knowledge, and drafting help for support and sales staff.

What you do need instead is the unglamorous work: clean records, deduplicated accounts, knowledge articles that are current and written clearly, and a sensible sharing model. That work is the actual prerequisite, and skipping it is what causes agent projects to disappoint — not the absence of Data Cloud.

Case 2: The agent needs one or two things from one other system

Your agent mostly works from Salesforce, but it needs order status from your ERP, or subscription state from your billing platform, or shipping information from a logistics provider.

You probably still don't need Data Cloud. One or two well-scoped integrations will usually be cheaper, faster and easier to reason about than standing up a unification layer. Depending on the system and the freshness you need, that might be an API call at the moment the agent asks, or a straightforward sync into a Salesforce object.

The thing to be careful about here is freshness. If the answer must be accurate to the minute, a nightly sync is not an integration — it's a source of confidently wrong answers. Decide the tolerance before you pick the approach.

Case 3: The agent needs a unified view across many systems

Your customer exists in several places at once — a web analytics profile, an e-commerce record, a marketing platform, a support system, a billing system — and the agent's usefulness depends on seeing them as one person with one history.

This is what Data Cloud is for, and this is where it earns its cost. Identity resolution across sources, a real-time unified profile, and the ability to activate that profile is a genuinely hard problem to solve any other way. If you try to solve it with point-to-point integrations you will end up building something that resembles Data Cloud, only worse and with nobody maintaining it.

Be honest about whether you are actually in this case, though. Wanting a single view of the customer is nearly universal. Needing one, in real time, for the specific agent you are about to build, is much less common.

Case 4: The agent needs to act on behaviour as it happens

You want the agent to respond to what someone is doing right now — browsing a particular product, abandoning a process, hitting a usage threshold — rather than to what is recorded about them.

This also points to Data Cloud , because real-time ingestion and activation is precisely the capability being bought. Batch data cannot do this, and a series of integrations will not do it well.

A test that cuts through most of the debate

Write down the ten questions you most want the agent to answer. For each one, write where the answer lives today.

If eight or nine of them point at Salesforce, build the agent on Salesforce and integrate the exceptions. If they scatter across four or five systems, and the value depends on connecting them, you have your answer the other way.

This sounds almost too simple, but it is remarkable how often a team that was certain they needed a unification project discovers that nine of their ten questions were answerable from data they already had — and how often a team that thought they could get away with a quick build discovers the opposite.

A sequencing point worth more than the licensing decision

Even when Data Cloud is genuinely the right destination, it does not have to be the first step.

There is often a well-scoped agent you can build now on the data already in your org — one that delivers something measurable, teaches your team how these systems behave in production, and builds internal confidence — while the larger data work proceeds on its own timeline. Sequencing that way tends to produce better outcomes than a long build with nothing visible until the end, and it means the data programme has a concrete consumer pulling it forward rather than being a project everyone loses patience with.

The failure mode we see most often isn't picking wrong. It's picking a large architecture first, spending two quarters on it, and never getting to the agent that was supposed to justify it.

What to do with your answer

If you landed in Case 1 or 2, your next move is a data-quality and knowledge review, not a licensing conversation. If you landed in Case 3 or 4, the licensing conversation is real — but you should still ask what can ship in the meantime.

And if you genuinely can't tell which case you're in, that is itself useful information: it usually means the use case isn't specific enough yet, and another hour defining it will save considerably more than an hour of build.

If you'd like help working through it, our free Org Health Check looks directly at your data quality, integration state and AI readiness inside your own org, and gives you a written summary of what to fix first. No cost, no obligation — and if the honest answer is that you're not ready for an agent yet, we'll tell you that too.

Agentforce Readiness Checklist: 25 Questions to Answer First

Thu, 30 Jul 2026 13:53:47 GMT

Most Agentforce projects that stall don't stall on the technology. They stall because something upstream of the agent — the data it reads, the knowledge it cites, the process it hands off to, the person who owns it — wasn't ready, and nobody checked before the budget was committed.

This is the checklist we work through before we quote an Agentforce engagement. It isn't a sales qualifier. It's genuinely the list of things that, in our experience across implementations, determine whether an agent ships and gets used or quietly gets switched off three months later. Some of these questions have uncomfortable answers. That's the point — it is much cheaper to find out now.

Work through it honestly. If you can answer most of these clearly, you're in good shape. If you can't answer several in the first two sections, fix those first; no amount of agent configuration will paper over them.

1. Business case — what is this agent actually for?

Question 1: Can you name the single use case in one sentence? Not "improve customer service." Something like "answer order-status questions from existing customers without a human touching them." Agents that are scoped to one job ship. Agents scoped to "handle support" do not.

Question 2: How many times a month does that job happen? If it's a handful, automation won't pay for itself. If it's thousands, you have a genuine case. Pull the actual number from your case or query volume rather than estimating — the estimate is almost always wrong in one direction or the other.

Question 3: What does it cost you today? Handle time multiplied by volume multiplied by loaded cost. You need this number to know whether the project is worth doing, and you need it again afterwards to know whether it worked.

Question 4: What happens if the agent gets it wrong? An agent that misroutes a support ticket is an inconvenience. An agent that misquotes a price, misstates a policy, or gives incorrect regulated advice is a different category of problem. Be clear which one you're building before you start.

Question 5: How will you measure success, and who agrees with that measure? Deflection rate, handle time, first-contact resolution, CSAT — pick the one or two that matter and get the person who owns that number to agree in advance. Retrofitting a success metric after launch never convinces anybody.

2. Data — can the agent find what it needs?

This is where most readiness assessments fail, and it's the section worth being most honest about. An AI agent is only as good as the data it can reach, and it will confidently answer from bad data exactly as readily as from good data.

Question 6: Is the data the agent needs actually in Salesforce? If order status lives in your ERP and nowhere else, the agent can't see it without an integration. That integration is part of the project, and it is often the larger part.

Question 7: Is it clean? Duplicates, half-filled records, free-text fields where picklists should be. An agent reading three versions of the same account will behave unpredictably, and you will struggle to explain why.

Question 8: Is it current? A nightly sync is fine for some use cases and useless for others. If a customer asks "has my order shipped," yesterday's data is a wrong answer delivered confidently.

Question 9: Do you have a single, trustworthy view of the customer? If the same person exists as three contacts across three objects, decide how the agent should resolve that before it has to.

Question 10: Who owns data quality, by name? Not "the team." A person. If nobody owns it, it degrades, and the agent degrades with it.

3. Knowledge — what will the agent actually say?

Question 11: Do you have written knowledge articles, or is the knowledge in people's heads? Agents ground their answers in documented knowledge. If your best answers live in your most experienced rep's memory, that's a content project before it's an AI project.

Question 12: Is that content accurate and current? Go and read ten of your articles at random. If a meaningful share are out of date, the agent will serve out-of-date answers at scale and much faster than a human ever could.

Question 13: Is it written in a way a machine can use? Clear headings, one topic per article, explicit answers rather than implied ones. Content written for a human who can infer context often confuses a retrieval system.

Question 14: What is deliberately out of scope? Write the list of topics the agent must never attempt — pricing exceptions, legal questions, anything regulated. This list is as important as the in-scope list.

Question 15: Who approves knowledge changes? Once an agent is live, editing an article changes what thousands of customers are told. That deserves a review step.

4. Security and permissions — what should it be allowed to see?

Question 16: Have you reviewed your sharing model recently? An agent inherits access. If your permissions are broader than they should be, the agent surfaces that immediately and at scale — which is how quiet data-access problems become loud ones.

Question 17: Is any of the data in scope personal, financial, or regulated? If so, what are the handling rules, and can you evidence that they're being followed?

Question 18: Do you need an audit trail of what the agent said? For most regulated contexts the answer is yes, and it's far easier to design in than to add later.

Question 19: What can the agent change, as opposed to read? An agent that reads is a lower-risk build than one that updates records, issues refunds, or triggers fulfilment. Be deliberate about which you're authorising.

5. Process and escalation — what happens at the edges?

Question 20: What is the handoff to a human, exactly? Which queue, with what context attached, within what time. A handoff that drops the conversation history is worse than no agent at all, because the customer has now explained themselves twice.

Question 21: How does the agent know it's out of its depth? Confidence thresholds, explicit topic boundaries, customer frustration signals. Decide the triggers before launch.

Question 22: Can a customer always reach a person? Not every use case requires it, but you should make that call consciously rather than discovering it in a complaint.

6. Testing and ownership — who runs this after launch?

Question 23: How will you test it before it meets a customer? Assemble a set of real historical questions — including the awkward ones — and check the answers against what a good human would have said. Testing against invented questions tells you very little.

Question 24: Who monitors it in week one, and in month six? Agents drift as products, policies and data change. Someone needs to read transcripts regularly. Name them.

Question 25: What is the rollback plan? If quality drops, who can switch it off, how quickly, and what happens to in-flight conversations? Knowing the answer makes everyone more willing to launch in the first place.

How to read your answers

If you answered sections 1 and 2 clearly, you're in a strong position — the rest is largely design work. If you struggled through section 2 on data, that's your project right now, and it's worth doing on its own merits whether or not you ever build an agent; clean, connected, trustworthy data improves everything else in the org at the same time.

If section 3 on knowledge is thin, that's usually a content and process problem rather than a Salesforce problem, and it's often quicker to fix than people expect once someone owns it.

And if you got through all twenty-five with clear answers, you're better prepared than most teams we speak to. The build itself is the straightforward part.

Where to start

You don't need to solve all twenty-five before doing anything. You need to know which ones you can't answer, because those are the risks in your project, and they're much cheaper to address now than after a build is underway.

If you'd like a second pair of eyes on your answers, our free Org Health Check covers the data, permissions, automation and adoption questions above directly against your org — we run Salesforce's own diagnostics and give you a prioritised view of what to fix first. No cost, no obligation, and you get a written summary either way.

Agentforce Help Agent: Pay-Per-Resolution AI Comes to Salesforce

Tue, 28 Jul 2026 14:31:20 GMT

For two years, the biggest objection we've heard from mid-market leaders about AI agents hasn't been "does it work?" It's been "what will it actually cost me?" Consumption-based pricing — tokens, credits, conversations — made budgeting feel like guesswork, and guesswork is exactly what a lean B2B operation can't afford. This month, Salesforce answered that objection in the most direct way possible: an AI service agent you only pay for when it finishes the job. Agentforce Help Agent, announced June 25 and generally available as of July 2026, charges per resolution — not per conversation, not per token. If the agent doesn't fully resolve the issue, or the customer asks for a human, you pay nothing. Here's what that means in practice, why it matters more for mid-market companies than almost anyone else, and how to figure out whether your org is actually ready for it.

1. What Agentforce Help Agent Actually Is

Help Agent is a prepackaged, autonomous customer service agent built on the Agentforce 360 Platform. The key word is prepackaged . Until now, getting real value from Agentforce generally meant designing your own agents: defining topics, writing instructions, building actions, and testing behavior — a meaningful project even for well-staffed teams. Help Agent flips that model. It ships with guided setup that Salesforce says takes minutes rather than months, grounds itself automatically on your existing Salesforce Knowledge articles, and comes with prebuilt actions for the workhorses of everyday service: case management, appointment scheduling, and order updates.

It's also channel-agnostic out of the box. One agent, configured from a single control screen, can handle conversations across web, customer portal, messaging, and voice. That's a quiet but important detail for mid-market teams, because deploying a bot per channel — each with its own logic and its own maintenance burden — is precisely the kind of sprawl that turns a promising pilot into an unowned mess eighteen months later.

Salesforce has been running a version of this on its own help portal, and the numbers it reports are worth noting: 4.3 million inquiries handled on help.salesforce.com with roughly a 70% autonomous resolution rate. Vendor-reported figures always deserve healthy skepticism, but as a proof point for "prepackaged agent grounded on a good knowledge base," it's a substantial one.

2. The Pricing Shift: From Credits to Outcomes

To appreciate why pay-per-resolution is a big deal, it helps to remember the road that led here. When Agentforce launched at Dreamforce 2024, pricing was $2 per conversation — whether or not that conversation went anywhere useful. In May 2025, Salesforce moved to Flex Credits, a consumption model that gave customers more granularity but still left many finance teams squinting at usage dashboards trying to forecast spend. One consultant memorably compared it to a 1991 cell phone plan, where every month's bill was an adventure.

Pay-per-resolution is the third act, and it's philosophically different. Under the new model — reported at a flat $2 per resolved issue — you're charged only when Help Agent takes an issue from start to finish on its own. If the customer escalates to a human, no charge. If the customer leaves negative feedback, no charge. Underlying consumption — the Data 360 queries and Agentforce processing behind each interaction — isn't metered separately during those conversations. Salesforce's own product leadership framed the goal plainly: let customers attribute spend to value.

Why outcome pricing favors the mid-market

Enterprises can absorb a fuzzy AI bill as an R&D line item. A 150-person B2B company can't. Outcome-based pricing does three things for a mid-market budget: it makes the unit economics legible (cost per resolved case is a number your CFO already tracks), it shifts risk onto the vendor (a badly performing agent costs you little), and it makes the build-vs-buy conversation honest, because you can compare $2 per resolution directly against your current fully loaded cost per case. For many service teams, that internal number lands somewhere between $8 and $25 once you account for salaries, tooling, and overhead — which is exactly why this pricing model is getting attention.

3. A Timely Signal, Not Just a Product Launch

Help Agent's general availability isn't happening in a vacuum. On July 24, Salesforce announced a $1.6 billion contract with the U.S. Department of Veterans Affairs to modernize veteran services — one of the largest signals to date that agentic AI on the Salesforce platform is moving from demos into large-scale, high-stakes production. When procurement processes that cautious commit at that scale, it usually means the technology has crossed a credibility threshold. And with Dreamforce coming September 15–17 in San Francisco, it's a safe bet that prepackaged agents and outcome-based pricing will be central themes — Help Agent looks like the first of a family, not a one-off.

For mid-market B2B leaders, the takeaway isn't "buy this today." It's that the era of AI agents as a science project is ending, and the era of AI agents as a line item with a measurable ROI is starting. That changes the questions you should be asking.

4. The Honest Caveats

Before anyone gets carried away, a few things deserve clear eyes.

"Resolution" is defined by the vendor. A customer who gives up and closes the chat without escalating or complaining may still count as resolved. Watch your own CSAT and reopen rates, not just the resolution counter.
The agent is only as good as your knowledge base. Help Agent grounds on Salesforce Knowledge. If your articles are thin, outdated, or contradictory, you'll get confident answers to the wrong questions — at $2 apiece.
B2B service is not B2C service. Mid-market B2B cases often involve contracts, entitlements, and relationships. The right early scope is the high-volume, low-complexity tier: order status, scheduling, password and access issues, documentation questions.
Pricing details will evolve. This is the third pricing model in under two years. Build your business case on ranges, not single points, and revisit it after Dreamforce.

5. A 6-Step Readiness Checklist for Mid-Market Teams

Whether you adopt Help Agent this quarter or just want to be ready when outcome-priced agents mature, the preparation work is the same — and none of it is wasted, because every step below also improves your human-powered service today.

Audit your knowledge base first. Pull your top 50 case drivers from the last 12 months. For each, ask: is there a current, accurate Knowledge article a machine could act on? The gap between that list and your article library is your real project plan.
Clean the data the agent will touch. Duplicate accounts, stale contacts, and inconsistent case categorization all degrade agent performance. An agent scheduling an appointment against the wrong account record isn't a productivity gain — it's a new problem.
Map your escalation paths deliberately. The moments Help Agent hands off to a human are where trust is won or lost. Decide who receives escalations, with what context, and how fast, before the agent goes live.
Model the economics honestly. Calculate your current fully loaded cost per resolved case. Compare it to $2 per autonomous resolution at a conservative resolution rate — assume 30–40% for your use cases, not the 70% Salesforce reports for its own portal.
Pilot narrow, measure wide. Start with one channel and two or three case types. But measure everything: resolution rate, CSAT, reopens, escalation quality, and agent-handled volume versus your baseline.
Assign a human owner. Autonomous doesn't mean unmanaged. Someone on your team should review agent conversations weekly in the early months, feeding corrections back into Knowledge. This is the single most predictive factor we see in whether AI service tools compound in value or quietly decay.

Where This Is Heading

Pay-per-resolution pricing is Salesforce betting that its agents are good enough to be paid like employees: for finished work. That confidence will spread — expect prepackaged, outcome-priced agents for sales development, scheduling, and collections to follow. Mid-market companies that spend the next two quarters getting their knowledge, data, and processes agent-ready will be able to adopt each of these in weeks. Companies that don't will keep funding pilots that stall.

The honest first step isn't buying anything — it's knowing whether your org is ready. That's what we do at 360 Quantum Solutions: fixed-fee projects, certified consultants you talk to directly, and a go-live guarantee we put in writing. Start with our free 2-minute org health check at 360quantumsolutions.com , or book a 5-day org audit and we'll tell you exactly where your Salesforce org stands — and what an agent-ready roadmap looks like for your team. Your Salesforce should be your #1 sales tool. Let's make it one.

TrailblazerDX 2026: Ten Years In, and Salesforce Just Changed Everything

Fri, 24 Apr 2026 09:00:00 GMT

Ten years ago, TrailblazerDX was a scrappy developer gathering where Salesforce admins and engineers swapped war stories over coffee and breakout sessions. This year, TDX celebrated its tenth anniversary with the kind of announcements that don't just update a platform — they fundamentally redefine what the platform is .

The theme was blunt: Build the Agentic Enterprise. Not explore it. Not pilot it on a side project. Build it, with production-ready tools, starting now. Salesforce isn't positioning itself as a CRM with AI features bolted on — it's positioning itself as the infrastructure layer that every AI agent, coding tool, and enterprise system plugs into.

Salesforce Goes Headless

If one announcement defined TDX 2026, it was Headless 360 . It means you no longer need a browser to work inside Salesforce — everything on the platform is now accessible as APIs, MCP tools, and CLI commands. Parker Harris put it plainly: "Why should you ever log into Salesforce again?" If your agent, your CI/CD pipeline, or your integration layer can call Salesforce directly without a human navigating the UI, the old click-to-configure model starts to look like a bottleneck.

More than 60 new MCP tools and 30-plus preconfigured coding skills now give coding agents complete, live access to the entire Salesforce platform — data, workflows, and business logic — directly in tools such as Claude Code, Cursor, Codex, and Windsurf. The platform now maps across four layers: Context (Data 360), Work (Customer 360), Agency (Agentforce), and Engagement (Slack).

Agentforce Vibes 2.0: Vibe Coding Gets Serious

Agentforce Vibes 2.0 brings multi-model support — including Claude Sonnet and GPT-5 — and an AI "development partner" that understands your business, not just your syntax. The two things that make this more than a shiny IDE update are full org awareness and Natural Language DevOps : the tool understands your metadata, schema, and existing code patterns from the first prompt, and with the DevOps Center MCP integration you can describe what to deploy and agents execute it — cutting cycle times by as much as 40%.

There's a real tension worth acknowledging. Teams that benefit most already have clear domain ownership and architectural principles. Without that, speed leads to fragmentation faster than it leads to value. Vibe coding amplifies both the good and the messy — and the messy gets louder when the build loop runs this fast.

Agent Script: Controlling What the Agent Actually Does

One of the more underrated announcements was the open-sourcing of Agent Script — a definition language that lets developers specify when agents should use LLM reasoning and when they should follow deterministic logic, with guardrails and transitions defined in structured files. This matters because the hardest part of deploying agents in the enterprise isn't getting them to do something — it's getting them to do the right thing, consistently, across edge cases and approval chains.

The Real-World Proof Point

Engine, the B2B travel management company featured in the keynote, built its customer service agent in 12 days using Agentforce. The agent now handles 50% of customer cases autonomously, with CSAT rising and cost-to-serve falling at the same time. Fast build time, meaningful automation rate, measurable business outcome — that's the story that lands.

The Bottom Line

TDX 2026 wasn't a conference full of roadmap promises. Most of what was announced is available today, for free, in Developer Edition orgs. Salesforce is also shifting from per-seat licensing to consumption-based pricing for Agentforce — a change with real budgeting and ROI implications. If you're in the ecosystem and wondering where to start, the practical path is clear: activate a Developer Edition org, spin up Agentforce Vibes 2.0, and start there.

Ten years in, TDX has never looked more like a technical conference with genuine weight behind its announcements. For anyone building seriously on Salesforce, this was the one to pay attention to.

The Key Benefits of Partnering with a Consultancy for Salesforce Implementation

Thu, 30 Oct 2025 09:00:00 GMT

In today's competitive landscape, organizations are always looking for ways to improve operations, strengthen customer relationships, and foster growth. Salesforce can be a powerful ally in achieving these goals — but successfully implementing it is not a simple task. It takes strategic planning and effective execution. This is where partnering with a consultancy can be transformative.

Access to Expert Knowledge and Tailored Solutions

Partnering with a consultancy gives you access to professionals with deep Salesforce experience across many industries. You don't just gain best practices — you learn the latest strategies and get help pinpointing the features that provide the most value for your organization. By analyzing your existing processes, a good partner suggests tailored solutions that directly address your challenges, so you're not just adopting Salesforce but making the most of it.

Streamlined Implementation and Reduced Risk

Implementing Salesforce can be overwhelming without the right resources or expertise. Consultancies use structured methodologies that keep projects moving and reduce errors at every phase — from initial planning through post-launch support. They're also adept at spotting potential risks early and mitigating them, which protects your investment and improves the likelihood of a successful rollout.

Ongoing Support and Training for Your Team

After go-live, your people need to actually understand how to use the system. Consultancies design training programs tailored to your organization — interactive workshops, online sessions — that empower your team to get the most out of Salesforce. Ongoing support addresses questions as they arise, keeping employees confident and proficient, which ultimately drives better productivity and smoother adoption.

Enhanced Customization to Meet Specific Needs

Every business is different, and a generic CRM rarely fits perfectly. A consultancy configures Salesforce around your existing workflows, processes, and data structures, so the platform integrates cleanly into how you already work. They can also connect Salesforce to your other systems, creating a cohesive view of customer data across departments.

Improved ROI Through Strategic Planning

Salesforce is a real investment, and every organization wants a solid return. A consultancy helps craft a clear roadmap aligned to your business objectives, sets up tracking of key performance indicators, and enables continuous monitoring so you can make informed decisions and keep improving your CRM strategy over time.

From expert knowledge and tailored solutions to streamlined processes and continued support, the advantages of the right partnership are clear: more customization, less risk, and better ROI. As businesses navigate the complexities of the digital age, partnering with a consultancy for Salesforce implementation is a crucial strategy for long-term success.

The AI-Powered Salesforce Org: Moving Beyond Einstein to Custom AI

Sun, 12 Oct 2025 09:00:00 GMT

In today's fast-paced world of customer relationship management, Salesforce stands out for its advanced AI capabilities. While Einstein has played a significant role in transforming businesses, many organizations are now discovering the benefits of custom AI solutions tailored to their specific challenges.

Understanding Einstein and Its Limitations

Salesforce Einstein is an integrated suite of AI technologies — predictive analytics, natural language processing, machine learning — designed to help organizations make smarter decisions. Yet Einstein may not meet every organization's unique needs. Many companies find they require solutions tuned to their specific datasets or problems — a healthcare provider, for example, may need models that analyze patient outcomes by regional demographics.

The Rise of Custom AI Solutions

Custom AI lets organizations apply artificial intelligence in a way specifically aligned with their goals. By developing unique algorithms and models, businesses can build applications for their distinct challenges — improving customer service, refining sales processes, or sharpening marketing. Custom AI also integrates diverse data sources: third-party apps, IoT devices, and proprietary databases.

The Benefits of Custom AI in Salesforce

Enhanced personalization. By analyzing customer behavior and preferences, organizations can create targeted campaigns, suggest relevant products, and offer support aligned to individual needs.

Improved decision-making. Advanced analytics surface insights that inform strategy. Sales teams can use AI-driven forecasts to spot trends and adjust; other teams can flag risks and opportunities earlier for more proactive decisions.

Streamlined operations. Automating repetitive tasks — data entry, lead scoring, follow-ups — frees your team to focus on relationship-building and strategic work.

Implementing Custom AI in Your Org

Start by assessing your needs: identify the specific challenges you face and the goals you want to achieve, and let that evaluation guide the solution. Collaborate with experts who bring skill in data science, machine learning, and Salesforce development. And start small — begin with a focused pilot, validate it, then scale across the organization for broader impact.

Challenges to Consider

Data privacy and security are critical, especially with customer information — solutions must comply with regulations and safeguard sensitive data. Custom AI also takes real investment of time and resources, including ongoing maintenance and updates.

Moving from partial reliance on Einstein to purpose-built custom AI opens real opportunities: better personalization, sharper decisions, and greater operational efficiency. Businesses willing to invest thoughtfully are better equipped to address their industry's unique challenges — and to keep growing in a competitive market. Moving beyond Einstein to custom AI isn't merely a trend; it's an essential evolution for businesses looking to thrive in the digital age.

Navigating the Rise of Agentic AI in Salesforce: Challenges and Use Cases

Wed, 01 Oct 2025 09:00:00 GMT

The rapid evolution of AI is changing how businesses operate, and agentic AI — systems that can act independently to accomplish specific goals — is at the forefront. In Salesforce, this technology is redefining customer interactions, data management, and operational efficiency. The advantages are clear, but there are real challenges to adopting it successfully.

Understanding Agentic AI

Agentic AI systems make decisions and take action autonomously. Unlike traditional AI that often needs human oversight, agentic AI performs tasks, learns from experience, and adapts to new scenarios — which makes it especially valuable in a CRM like Salesforce, where informed, timely decisions matter.

Use Cases in Salesforce

Enhanced customer support. AI agents can handle inquiries and resolve issues independently, improving response times and freeing human agents for the complex, emotionally nuanced cases that need them.

Predictive analytics. Agentic AI examines large volumes of data to uncover trends and forecast customer behavior, helping teams shape targeted strategies and reach the right people at the right time.

Automated workflow management. With predefined rules, agents manage lead scoring, follow-ups, and data entry — reducing manual errors and streamlining operations.

Challenges of Implementation

Data privacy. As organizations rely more on AI to process customer data, compliance with regulations like GDPR and CCPA becomes paramount — and consumer trust is on the line. Integration with existing systems. Fitting agentic AI into existing Salesforce frameworks and older systems takes careful planning. Resistance to change. Employees may fear job loss or feel overwhelmed, so training and change management are essential.

Barriers to Adoption

The cost of implementation — software, training, and ongoing maintenance — adds up, and it's worth weighing those against the long-term benefits of better retention, higher productivity, and stronger revenue. Successful adoption also needs specialized AI and data skills, so investing in training or bringing in experts closes the gap. And because AI makes autonomous decisions around sensitive data, organizations need clear ethical guidelines and accountability.

Agentic AI opens new opportunities in Salesforce, but it introduces real challenges too. Companies that understand the use cases and proactively address the barriers — balancing innovation with ethical responsibility, building an adaptable culture, and investing in the right resources — will be best positioned to harness it for long-term success.

How to Make the Most of Dreamforce — Lessons from 16+ Years in the Ecosystem

Mon, 29 Sep 2025 10:00:00 GMT

Every Fall, Salesforce brings together the brightest minds in business, technology, and innovation for Dreamforce. If you've been there, you know it can be overwhelming, but in the best way possible.

After attending for over 16 years, I can confidently say Dreamforce isn't just an event; it's a transformative experience. It's where ideas meet action, and strategies blend with community. While you might feel swept away by keynotes and sessions, the real rewards come from how you prepare and immerse yourself.

Here's what I've gathered from my years at Dreamforce—and how you can elevate your experience.

Start with a Purpose, Not a Schedule

The most common mistake that first-time attendees make is chasing sessions instead of focusing on outcomes.

Dreamforce offers hundreds of talks, but if you aim to attend them all, you might end up remembering very little. Before you even board your flight to San Francisco, narrow down your goals to three specific outcomes.

For instance:

"I want to learn how to activate data with Salesforce Data Cloud to improve my company's analytics capabilities."
"I need to connect with at least five partners specializing in education or SMB use cases for future collaboration."
"I want to grasp how AI can enhance my customer engagement strategies and increase retention rates by at least 20% over the next year."

By defining your goals upfront, every session, meeting, and conversation you have becomes meaningful. You'll find yourself attending what truly matters.

Pro tip: While it's smart to bookmark sessions in the Dreamforce app, leave some room for unexpected meetings. Many valuable insights come from spontaneous hallway conversations or impromptu expo floor demos.

Network Like a Human (Not a Business Card)

Dreamforce attracts executives, architects, developers, and innovators. However, true networking goes beyond swapping LinkedIn profiles. It's about forming authentic connections.

Instead of simply asking what someone does, try exploring why they are there and what challenges they are tackling. This approach can lead to meaningful insights rather than just surface-level contacts.

After each engaging conversation, make a quick note in your phone to recall the context: "Met Sarah from EduTech — discussing AI impact."

This simple habit can help you keep track of your interactions and allows you to reach out later with thoughtful messages, enhancing your connection.

Embrace the Keynotes

The keynotes at Dreamforce are not to be missed. Featuring industry leaders and innovative thinkers, they offer inspiring stories that can ignite your passion and trigger fresh ideas.

While it might seem tempting to skip the keynotes for smaller sessions, they typically set the stage for the entire event. Keynote speakers share insights on upcoming trends and the future of technology, aligning your goals with the wider Salesforce ecosystem vision.

Make sure to take notes and share your thoughts online or with fellow attendees afterward. Discussing the themes from keynotes can deepen your understanding and allow you to connect with others who share similar interests.

Hands-On Learning

Hands-on learning is one of the most rewarding aspects of Dreamforce.

Diving into workshops, demos, or labs gives you a practical grasp of how to apply new technologies in your work.

Prioritize sessions that focus on hands-on experiences, as they equip you with actionable tools and knowledge that can drive immediate impact once you're back at your organization. For example, you could participate in a workshop that teaches you to automate customer workflows, which can improve response time by over 30%.

Leverage the Community

Beyond sessions and keynotes, Dreamforce is all about community.

Make the most of networking events, meetups, and social gatherings. These informal settings can lead to unexpected connections and future collaborations.

Join groups relevant to your interests or industry. Whether you gravitate towards a Salesforce developers meetup or a gathering for AI enthusiasts, being part of a community enhances your experience and offers ongoing support after the event concludes.

Follow Up and Reflect

Post-Dreamforce, it's easy to feel overwhelmed by the sheer amount of information and connections you've made.

Take time to reflect on your experiences. Write down what you learned and create a follow-up plan for the connections you established. Send personalized messages referencing your conversations to help jog their memories. This practice not only strengthens your network but also solidifies the relationships you nurtured during the event.

Final Thoughts

Dreamforce presents a unique chance to immerse yourself in the Salesforce ecosystem and connect with like-minded individuals.

By approaching the event with intention, focusing on clear goals, and actively engaging in the community, you can transform your experience from overwhelming to empowering.

Remember, it is not just about attending sessions or meeting people; it's about gaining insights and forging lasting relationships.

As you gear up for your next Dreamforce, keep these lessons in mind. With the right mindset and approach, you'll leave the event not only with memories but also with actionable insights and valuable connections that continue well beyond the experience.

How to Successfully Implement Salesforce Without Delaying Your Timeline

Mon, 29 Sep 2025 09:00:00 GMT

Implementing Salesforce can feel overwhelming for small and medium-sized businesses (SMBs). The potential for improved customer relationship management and streamlined operations is enticing, but worries about timelines often cause hesitation. This post provides essential steps to ensure a smooth Salesforce implementation without unnecessary delays, allowing you to harness its benefits sooner rather than later.

Understanding the Salesforce Implementation Timeline

Before you embark on your Salesforce journey, it is essential to grasp the typical implementation timeline. The duration for implementation can vary widely based on your business needs, organization size, and the specific Salesforce products selected.

On average, Salesforce implementations can range from a few weeks to over six months. Nevertheless, a well-structured plan can help cut this timeframe significantly, potentially by up to 30% in some cases.

Define Your Goals and Objectives

The first step for a successful Salesforce rollout is to clearly define your goals. Ask yourself: What do you want to achieve? Whether that's improving customer service response times by 15%, boosting sales by 20%, or enhancing marketing effectiveness, having specific objectives serves as your project's roadmap.

Engaging key stakeholders—like sales managers or customer service leaders—in these discussions can clarify your timeline. Their insights will help ensure everyone is aligned with the overall vision, making the implementation process smoother.

Choose the Right Implementation Strategy

There are several strategies to implement Salesforce, and the right choice can significantly influence how long it takes to set up. Here are a few approaches:

1. Phased Implementation: Roll out Salesforce in stages, focusing on one specific area at a time. For example, you might start with sales, then move on to marketing, which can reduce stress on your team and allow for adjustments based on early feedback.

2. Big Bang Implementation: Launch all features at once. This can be quicker, but it's riskier. Many businesses find themselves overwhelmed and encounter issues that can delay the process.

3. Salesforce Quick Start Implementation: Tailored for SMBs aiming to get started quickly, this involves a predefined set of features and a more rapid timeline. Many businesses using this approach can see results in as little as four weeks.

Selecting the right strategy hinges on your specific business needs and available resources.

Assemble the Right Team

A dedicated team is crucial for successful Salesforce deployment and timely results. Consider including:

Project Manager: Oversees the entire implementation process and ensures that deadlines are met.
Salesforce Administrator: Manages the platform and addresses any technical issues.
Key Users from Different Departments: Involve representatives from sales, marketing, and customer service. Their perspectives will be vital in customizing Salesforce to fit your organization's needs.

A well-rounded team working toward a common goal fosters a more efficient implementation process.

Develop a Comprehensive Project Plan

A detailed project plan can keep your Salesforce implementation on track. It should clearly outline:

Key Milestones: Identify critical dates like data migration completions or training sessions.
Timeline: Create a realistic schedule for all phases of the implementation. Typically, an effective timeline anticipates 10–20% buffer time for unexpected delays.
Resources Needed: List both human and technological resources necessary at each stage of the project.

By having a clear project plan, you can stay organized, focused, and reduce the risk of delays.

Data Migration and Integration

Data migration can be one of the most challenging aspects of implementing Salesforce. This process involves moving existing data from current systems into Salesforce. To simplify this task:

Clean Your Data: Before migration, ensure all data is accurate and relevant. Studies show that organizations save up to 25% of time during migration by having clean data.
Use Data Migration Tools: Familiarize yourself with Salesforce's built-in tools. Effective use can cut migration time in half for some businesses.
Test the Migration: Conduct preliminary test migrations to identify issues beforehand. This proactive step can save you significant time in the long run.

By carefully planning your data migration, you can minimize delays and enhance your Salesforce rollout.

User Training and Support

Training is critical for a successful Salesforce implementation. It ensures your team can effectively use the system. Consider:

Tailored Training Sessions: Offer sessions tailored to specific roles. For instance, sales reps may need different training than marketing team members. This targeted approach can boost user confidence and efficiency.
Ongoing Support: After initial training, provide continuous support to handle questions or problems. Creating a knowledge base can become an invaluable resource.

Investing in user training can speed up the adaptation period, allowing you to see the benefits of Salesforce sooner.

Monitoring and Adjusting as Needed

Once Salesforce is live, it's crucial to keep an eye on its performance. Regularly check if the system meets your business objectives, such as increasing customer satisfaction scores by 10% or improving sales cycle times by 15%.

Gather feedback from users and be willing to make adjustments. Regular evaluation can help you maximize Salesforce's impact, ensuring the implementation remains effective over time.

Final Thoughts

Implementing Salesforce does not have to be a lengthy ordeal. By defining clear goals, selecting the right strategy, assembling a dedicated team, crafting a thorough project plan, managing data migration, providing effective training, and ongoing monitoring, you can successfully implement Salesforce while staying on track.

With thoughtful planning and execution, your organization can unlock the full potential of Salesforce, enhancing customer relationships and streamlining operations. Embrace the journey and watch your business succeed with Salesforce!

Why 360 Quantum Solutions Is the Ideal Partner for Small and Medium Businesses

Mon, 29 Sep 2025 08:00:00 GMT

Small businesses are vital to our economy, yet they face significant hurdles with technology. Many passionate business owners simply lack the technical expertise to implement complex systems like Salesforce — and research indicates that around 60% of small businesses report challenges in technology adoption, often stemming from inadequate support and guidance. This post explains how we built 360 Quantum Solutions to close that gap for small and medium businesses.

Understanding the Struggles of Small Businesses

Customizing Salesforce to meet specific business needs is essential, but without expert support it can quickly lead to overspending and missed deadlines. Off-the-shelf configurations rarely match how a growing team actually sells and serves, and internal staff are usually stretched too thin to close the gap themselves.

That is exactly why partnering with a reliable Salesforce implementation provider matters: the right partner brings the technical depth, so your team can stay focused on running the business.

The Importance of Budget and Timeline

Budgeting and adhering to timelines are two of the biggest concerns small businesses bring to us. We've all heard the stories — a project that spirals due to unexpected costs and delays. Those experiences demonstrate the critical importance of thorough planning and communication.

At 360 Quantum Solutions, transparency and collaboration come first. Our certified Salesforce consultants work with you to establish realistic budgets and timelines before any work begins, and our previous clients have reported meaningfully shorter project timelines — in many cases around 30% — after adopting our planning methodology.

Why Training Matters

Training is a crucial yet frequently overlooked aspect of Salesforce implementation. Businesses often invest in a powerful CRM only to see it underutilized because staff members feel overwhelmed. Research demonstrates that organizations that offer training programs experience up to 40% higher adoption rates of new technology.

To close this gap, our Salesforce Quick Start services include personalized training programs tailored to your specific business needs, empowering your team to maximize the Salesforce investment from day one.

Tailored Solutions for Small Businesses

Each small business has distinct needs, making a one-size-fits-all approach ineffective. We specialize in end-to-end Salesforce implementation, ensuring the solution aligns with how your business actually operates.

Whether you need a first Salesforce setup or ongoing consulting, our team guides you through the process with a deep understanding of small business operations — and the vast majority of our clients report improved workflow efficiencies after implementation.

The Role of Salesforce Go-Live Experts

Launching Salesforce is an exciting yet nerve-wracking moment for many small businesses. This stage sets the tone for the entire Salesforce journey.

Our Go-Live experts ensure a seamless transition, assisting from setup through post-launch support. Clients who use our go-live support consistently report far fewer launch-related issues, which helps maintain productivity through the critical transition period.

Building Long-Term Relationships

At 360 Quantum Solutions, we prioritize lasting relationships with our clients. We function as a growth partner rather than merely a service provider. Our dedication to your success extends beyond implementation, with continuous support and consulting services that help your business adapt as the landscape evolves.

Partnering with us gives you access to extensive resources and knowledge, enabling you to tackle challenges and seize opportunities as they arise.

Final Thoughts

Choosing 360 Quantum Solutions as your Salesforce implementation partner can significantly transform how your business operates. We recognize the challenges small and medium businesses face, and we remain dedicated to providing tailored solutions that respect your budget and your timeline.

With an emphasis on training, customization, and ongoing support, we empower our clients to maximize their Salesforce investment — with a roadmap aligned to your unique business goals and built to drive success.