Industries Clouds = Salesforce verticals with pre-built data models, OmniStudio components, industry-specific features.
Architectural considerations:
1. Vertical fit.
Validate the Industry Cloud's data model genuinely fits before committing. Too much customisation defeats the purpose.
2. OmniStudio integration.
Industries Clouds heavily use OmniStudio (FlexCards, OmniScripts, Integration Procedures, DataRaptors). Architects design with OmniStudio patterns.
3. Hybrid with standard.
Industries Cloud + Sales Cloud + Service Cloud common. Account/Contact shared; vertical objects layered on.
4. Custom code minimised.
Industries Cloud favours declarative + OmniStudio. Custom Apex / LWC reserved for what they can't do.
5. Vertical integrations.
Each Industries Cloud has expected integrations: Health -> EMR systems; Financial Services -> core banking; etc.
6. Compliance.
Industries Clouds often pre-configured for vertical compliance (HIPAA for Health, FINRA/SEC for Financial Services). Architects ensure config is leveraged.
7. Talent.
Industries Cloud talent is specialised. Smaller pool than core Salesforce. Plan accordingly.
8. Roadmap alignment.
Salesforce evolves Industries Clouds with platform releases. Architects track and adopt.
9. Cost.
Industries Cloud licensing significantly higher than core Sales/Service. Justify with vertical features used.
Decision framework:
- Industry Cloud fits 80%+ of needs out of box — adopt.
- Industry Cloud fits 50-80% — case-by-case, may still adopt.
- Industry Cloud fits <50% — custom on standard Salesforce often better.
Common patterns:
- Health Cloud + Service Cloud for provider organisations.
- Financial Services Cloud + Sales Cloud for advisor wealth management.
- Manufacturing Cloud + Sales Cloud for B2B account-based selling.
Architect role: validate fit, design hybrid where appropriate, leverage vertical features, plan for vertical-specific risks.
Senior insight: don't customize Industries Cloud heavily. The value is the standard model; heavy customisation defeats it.