How AI Agents Are Changing Business Applications

Salesforce and Anthropic recently announced Claudeforce, a partnership that brings Salesforce data and sales workflows into Claude. Its first offering, Salesforce in Claude, gives sellers access to 37 prebuilt skills for tasks such as meeting preparation, deal-health review, pipeline analysis, and CRM updates—without requiring them to begin in Salesforce’s conventional interface. The offering is currently available to select pilot customers, with an open beta expected in September 2026.

Claudeforce also expands Claude’s role within Salesforce, where Salesforce says it supports reasoning across Agentforce products and can be accessed through Amazon Bedrock within the Salesforce Trust Boundary.

A seller preparing for a customer meeting typically opens Salesforce, locates the account, reviews recent activity and opportunities, checks for pipeline changes, and updates relevant records after the conversation. With Salesforce in Claude, however, that work can begin with a task-based request. Claude can then retrieve relevant Salesforce context and use approved workflows to support the task.

This changes the relationship between employees and business applications. While Salesforce still stores customer data, manages permissions, and applies the rules that govern sales processes, its interface is no longer the only place where employees can access those capabilities.

As agents connect to more business systems, applications may increasingly serve as governed sources of data, workflows, and actions that employees can use from outside their native screens.

What changes with Salesforce in Claude

With Claudeforce, Salesforce remains responsible for the account data, opportunity history, sales workflows, user permissions, and activity records that support its CRM. Claude, meanwhile, acts as an additional access layer, allowing sellers to work with Salesforce information and approved actions from within its own interface.

Sellers can begin certain tasks in Claude rather than first navigating to a specific Salesforce record, report, or dashboard. For example, they may ask Claude to surface relevant account context, review pipeline health, prepare follow-up actions, or update an approved record. Salesforce then provides the data, workflows, permissions, and governance that determine what Claude can retrieve or change.

This is helpful because business work rarely happens in just one application. A sales representative may rely on a CRM, but customer context can also be spread across email, a support platform, product analytics, contract documents, and internal messages. The CRM remains central to the sales process, but it’s only one part of the broader set of systems employees use to understand an account and decide what to do next.

Salesforce’s Headless 360 initiative supports this broader access model. It exposes Salesforce capabilities through APIs, Model Context Protocol (MCP) tools, and command-line interfaces, enabling developers and authorized AI agents to interact with Salesforce data, workflows, and business logic beyond the browser interface. According to Salesforce, those capabilities remain governed by the same authentication and security model organizations already manage.

Where agents can reduce application switching

Many business processes struggle not because a team lacks the right systems, but because the information needed to complete one request is distributed across them.

A support escalation, for example, may involve a case-management platform, CRM records, product-usage data, service-level commitments, internal documentation, and communications with other teams. Each system may contain a necessary part of the answer, but the employee handling the issue must determine which records matter, piece together the history, and decide what should happen next.

An agent can help create a working view of that request. It might assemble the relevant case history, account details, recent product activity, applicable service commitments, and internal guidance. It could also identify missing information or flag that the issue meets a defined escalation threshold. The representative remains responsible for evaluating that information, responding to the customer, and involving the appropriate team.

This approach is particularly useful in workflows that follow a repeatable pattern but require information from several sources, such as:

• Reviewing an order when inventory, supplier, and customer-service information must be checked together.
• Determining whether a finance request includes the required documentation and approvals before it enters formal review.
• Coordinating employee onboarding across HR records, IT provisioning requests, training materials, and policy documentation.
• Building a project update from task-management data, internal communications, and reporting systems.

In these scenarios, the agent’s role is to reduce the effort required to establish the current state of work. It can organize the relevant information, identify gaps, and direct a request toward the next approved step without taking responsibility for the underlying decision or process.

The systems behind the agent still matter

An agent’s usefulness depends on the systems it can access. Accurate data, defined workflows, and reliable controls determine whether it can produce useful results and operate safely within a business process.

Each business application continues to serve as the authoritative system for the area it manages: the CRM for customer records and sales activity; the ERP for transactions, financial controls, and approval processes; the HR system for employee records, permissions, and internal workflows; and the support platform for case ownership, escalation paths, and service expectations.

Agents can retrieve information, flag missing details, draft a response, recommend a next step, or initiate an approved workflow. The application behind the agent should continue to enforce access rights, authentication, approval requirements, and the business rules that determine how a process moves forward.

Salesforce in Claude routes actions through Salesforce, allowing the platform’s existing authentication, permissions, and business rules to apply. That approach helps organizations extend access to data and workflows without creating an alternate path around the controls used to protect customer, financial, employee, and internal business information.

The degree of oversight should reflect the consequence of the action. An agent may be able to summarize a customer account, identify missing information in a request, retrieve policy documentation, or prepare a draft for employee review. Actions such as changing pricing, approving a payment, modifying a contract, or making an employment decision may require explicit approval, additional verification, or a purpose-built workflow

Where agents fit—and where they don’t

AI agents are well suited to work that begins with a question, a request, or a need to bring together information from several places. They can help employees find relevant records, understand recent changes, summarize a case, or initiate a defined workflow. However, they’re less suitable as a universal replacement for the interfaces employees use to review and manage business operations.

Dashboards, reports, tables, forms, and administrative screens still remain useful for many tasks. A finance leader may need to review a detailed report before approving a transaction. An operations manager may need to compare performance across locations and time periods. A system administrator needs a structured view of user access, integrations, and workflow rules.

A conversational interface isn’t always the most useful format for that work. In many cases, an agent can provide the starting point, while the application provides the environment for investigation, validation, and decision-making.

For example, an agent can identify accounts with declining activity and create a list for a sales manager to review. The manager may then open the CRM to inspect opportunity details, consider the forecast, and decide how to prioritize the team’s follow-up.

Both interfaces have a role. The agent reduces the effort required to identify the work, while the CRM provides the detail needed to manage it responsibly.

What organizations need before deploying agents

The quality of an agent-assisted workflow depends on more than the model behind it. An agent needs current information, access to relevant systems, clear permissions, and defined boundaries around the actions it can take.

Before deploying an agent in a business process, organizations should consider:

• Data quality: An agent will produce weak results if it relies on incomplete customer records, outdated documentation, or conflicting information across systems.
• System integration: The agent needs secure access to the data and actions required for the workflow, whether through APIs, connectors, MCP servers, or custom integrations.
• Access controls: Employees should not be able to access information or complete actions through an agent that they could not access in the original business application.
• Approval requirements: Organizations need to define which tasks the agent can complete, which require human review, and how the system should handle exceptions.
• Monitoring and auditability: Teams need visibility into what the agent accessed, what it recommended or changed, and whether it performed as intended.

Addressing these requirements early gives organizations a clearer basis for deciding which workflows are appropriate for agent support.

A focused workflow is often the best place to start. An internal knowledge assistant, account-preparation tool, support-triage workflow, or routine reporting use case can help an organization assess data readiness, employee adoption, and governance needs before connecting agents to more consequential processes.

How business applications may change

Salesforce in Claude offers an early example of a broader shift in enterprise software: employees may increasingly begin work with an outcome or request, then access the relevant business data and workflows through an agent.

That could change how organizations design and evaluate applications. A platform’s value will depend not only on its interface, but also on how reliably it exposes useful data, actions, and controls to authorized employees and AI systems.

For employees, this could reduce the time spent locating information across separate tools and make routine work easier to begin. For organizations, it increases the importance of maintaining accurate data, well-defined processes, and controls that continue to apply wherever work begins.

The result is likely to be a more flexible application environment, not a single conversational interface that replaces every dashboard, form, or operational system.

Building agent-ready business software

AI agents are only as effective as the systems, integrations, data, and governance models behind them. Organizations need more than a conversational interface: they need secure, well-designed software that connects the right data and workflows while preserving the controls employees and customers depend on.

FullStack helps companies design, build, and modernize custom software, enterprise integrations, and AI-enabled applications. Whether you are exploring a focused internal assistant or planning a broader agent-enabled workflow, our teams can help you evaluate the technical foundation, define appropriate guardrails, and build solutions around the way your business actually operates.

Contact us today if you’re interested in working with us.