Salesforce evolves: shifts to declarative, AI-first, modular, multi-cloud. Architects align with strategic direction.
Salesforce's strategic direction:
- AI-first — Agentforce, Einstein, prompt-driven.
- Modular — Industry Clouds, packages, smaller deployable units.
- Declarative — more in Flow / Lightning App Builder; less Apex needed.
- Cloud-native — Hyperforce, multi-region.
- Open — Pub/Sub API, Data Cloud, more APIs.
- Vertical — Industries Clouds, vertical-specific features.
Architecting in alignment:
1. AI-ready architecture.
- Data classified for AI use.
- Trust Layer enabled.
- Prompts versioned.
- Human-in-the-loop where needed.
- Plan for AI evolution.
2. Declarative-first.
- Flow first, Apex when needed.
- Custom Metadata for config.
- Lightning App Builder for UI.
- Reduce Apex / Aura / Visualforce footprint.
3. Modular packaging.
- Unlocked Packages.
- Reusable LWC.
- Generic Apex utilities.
- Easier to migrate / replace.
4. Cloud-native readiness.
- Hyperforce-compatible.
- Avoid hardcoded data center references.
- Multi-region capable.
5. API-friendly.
- Standard APIs (REST, Pub/Sub).
- External Id fields.
- Open integration patterns.
6. Industry alignment.
- If in vertical, evaluate Industry Cloud.
- Don't fight industry-specific Salesforce direction.
Anti-patterns:
- Heavy custom Aura — fights the LWC direction.
- Heavy Process Builder — fights the Flow direction.
- Hard-coded customisations — fights the configurability direction.
- Closed architecture — fights the open / API direction.
- Ignoring AI — fights the AI-first direction.
Practical patterns:
- Quarterly Salesforce direction review — what changed strategically?
- Roadmap alignment — adjust internal roadmap to platform direction.
- Beta participation — early access to upcoming features.
- Strategic briefings with Salesforce — understand direction.
Senior architect insight: Salesforce's gravity well pulls architecture toward declarative + AI + modular. Architectures that align ride the wave; those that fight it become technical debt.
The senior framing: Salesforce evolves whether you like it or not. The choice is whether your architecture evolves with it or becomes a relic.
Architects influence Salesforce's direction (via feedback) AND adapt to it (via roadmap alignment). Both at once.