Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Salesforce Architect
hard

What's different about architecting for very large enterprises (Fortune 100)?

Large enterprises have characteristics that shape architecture differently from mid-market.

Characteristics:

  • Scale: 50K+ users, M+ records, hundreds of integrations.
  • Complexity: many business units, regions, legacy systems.
  • Regulation: multiple frameworks across jurisdictions.
  • Risk-aversion: changes scrutinised heavily.
  • Slow decision-making: many stakeholders.
  • Existing investments: deep tech stack to integrate with.

Architectural patterns:

1. Multi-org by necessity.

Often regulatory / data residency / business unit autonomy demands.

2. Mulesoft as backbone.

Single integration is rare; many integrations require backbone.

3. Heavy governance.

ARB, CoE, data governance councils, security reviews.

4. Sophisticated DevOps.

Multiple sandboxes, CI/CD platforms (Copado typical), comprehensive testing.

5. Compliance overhead.

Shield typical for regulated industries. Field Audit Trail. Privacy Center. Comprehensive logging.

6. Specialised teams.

Dedicated security architects, integration architects, data architects, business analysts per domain.

7. Vendor management.

Salesforce strategic partner. AppExchange decisions made centrally. Enterprise agreements.

8. Multi-cloud strategy.

Salesforce + Mulesoft + Heroku + AWS + Snowflake + Tableau common.

9. Long timelines.

Programs span years. Phased rollouts. Risk management heavy.

10. Scaled communication.

Regular leadership briefings, stakeholder forums, internal communications.

Differences from mid-market:

  • Decision-making slower — more stakeholders.
  • Investment larger — but expectations higher.
  • Risk aversion higher — innovation slower.
  • Architecture team larger — specialisation.
  • Compliance more demanding.
  • Talent pool deeper internally — but harder to attract externally.

Common pitfalls:

  • Bring mid-market patterns — don't scale.
  • Underestimate governance overhead — bureaucracy.
  • Insufficient discovery — surprises late.
  • Vendor relationships poor — Salesforce account team underutilised.
  • Stakeholder fatigue — too many forums.

Senior architect insight: large enterprise architecture is its own specialty. Architectural patterns from startups / mid-market don't directly translate.

The senior framing: success at scale requires both technical excellence AND organisational maturity. Many architects have one; few have both.

Career path: large enterprise architecture often pays well but moves slowly. Architects who thrive are patient, politically savvy, and enjoy systemic problems.

Why this answer works

Senior. The scale-specific patterns and "own specialty" framing are mature.

Follow-ups to expect

Related dictionary terms