In 2026, the architecture question is no longer whether Salesforce will include AI. It is how native agents, Data 360, external models, headless services and the wider cloud estate should work as one accountable system.
The answer is not a single-vendor diagram. It is a small set of durable layers and ownership rules that preserve clarity while capabilities change.
Cloud Group point of view
Keep customer truth, business policy and outcome accountability close to the enterprise. Make models, interfaces and orchestration replaceable within governed boundaries.
A practical playbook
The strongest next step is narrow enough to govern and useful enough to produce evidence. We would structure the work around these moves:
- Experience: design around the customer or employee outcome, not the assistant.
- Orchestration: assign one accountable agent or workflow to each job.
- Context: publish governed Data 360 and domain data products.
- Action: expose permission-aware business capabilities through stable contracts.
- Control: centralize identity, policy, evaluation, observability and economics.
The architecture and operating implication
Use Salesforce as the customer and transaction spine where it holds authority. Let Data 360 unify and activate relevant context without defaulting to unnecessary copies. Use Agentforce for native work and external platforms where they add differentiated capability, connected through a governed tool and API layer. Correlate every material interaction to an outcome and owner.
Measure what changes
Model activity is not a business result. Track a small set of indicators that connect behavior to accountable work:
- Time to launch a governed outcome
- Reuse of data, actions and evaluations
- Quality, risk and cost by value stream
- Custom complexity removed as capability matures
The best architecture is lightweight in the places the market will change and rigorous in the places the business must trust. That balance is how an AI platform becomes operating leverage.
Primary sources
This field note is grounded in the product and market context available at the time of publication.
