01
Org strategy
Multi-org vs. single-org vs. multi-tenant. The decision tree, with the failure modes for each.
Resource HubTry Clientell free
Resources for Salesforce architects
Patterns, trade-offs, and decision frameworks for the people designing the system.
Salesforce architects make the calls that everyone else lives with for 5 years. Multi-org vs. single-org. Custom objects vs. standard. Data Cloud vs. external warehouse. AI agents vs. workflow rules. These resources are about the trade-offs, the failure modes, and the second-order effects that show up two years after the decision.
05 resources · 04 FAQs
“An architect's job isn't to design the system. It's to design the system you can defend in three years when the people who asked for it have all left.”
Top jobs to be done
What architects actually need help with.
02
Data architecture
Standard vs. custom objects, big objects, external objects, Data Cloud. When to use which.
03
Integration patterns
Sync, async, event-driven, polling. The cost model and the failure model for each.
04
AI agent architecture
Where do agents live, what do they touch, and how do you keep them from turning your org into mush?
05
Governance & access
Sharing, profiles, permission sets, territories. The model that scales and the one that bites.
06
Migration playbooks
Lightning, DX, multi-org consolidation. The migration phases, the rollback plan, the comms plan.
Use cases for architects
Explore by what you're trying to ship.
#01#02#03#04
Org documentation continuous-update
Auto-generate the architecture spec, the field-usage analysis, the flow dependency graph. The handover doc that stays accurate.
Salesforce data operations
Reference architecture for cross-cloud data flow, integration patterns, and the consolidation playbook for multi-org work.
AI flow builder
Generate flows that respect bulk patterns and governor limits from the prompt up. Review at the pattern level, not line by line.
Permission + access governance
Build, audit, and re-baseline the access model. The compliance prep that used to be a 2-week project, automated.
By topic
Deep-dive playbooks for architects.
Curated for architects
Resources, hand-picked for this role.
Cheatsheet
/01
0/100
Score
The
63
Record-level
76
10
89
The
67
Permission Set Spaghetti: The Map Nobody Drew For You
The 4 permission layers and how they really resolve, 10 named anti-patterns, the SOQL query bank, real-world breach stories, and a cleanup sequence that won't break access. Spring '26 current.
Salesforce Security·PDF
Cheatsheet
/02
0/100
Avg readiness
Data quality
82
Automation
64
Adoption
71
Integration
88
AI Readiness in Salesforce Cheat Sheet
A comprehensive checklist to evaluate your Salesforce org's readiness for AI, covering data quality, automation maturity, user adoption, and integration preparedness.
Salesforce AI·PDF
Guide
/03
0min
Read time
/0110
/02Worksheets
/03AI
/0490-day
Fixing Salesforce Technical Debt With AI: A Complete Guide
A 10-chapter guide for admins and the leadership teams who fund them. Worksheets, AI prompts, and a 90-day plan to audit, prioritize, and fix Salesforce technical debt.
Salesforce Technical Debt·PDF
Playbook
/04
0steps
Dev workflow
- Generate Apex
- 02Read inherited code
- 03Generate tests
- Review with AI
The Salesforce Developer's AI Playbook
How working Salesforce developers are using AI to ship Apex, LWC, and integrations 3–5x faster, without giving up code review discipline or production safety.
Salesforce Development·14 min read
Checklist
/05
0/100
Score
15
65
Signal
78
Built
91
Vendor-neutra…
69
15 Salesforce Flows Quietly Tanking Your Org
A 15-minute audit checklist of the 15 most common Flow anti-patterns we find in production Salesforce orgs. Signal, why it tanks, and the rebuild for each. Vendor-neutral, built from 150+ org reviews.
Salesforce Flows·PDF
Adjacent resources
Things architects also look up.
AI Tool Directory · Architects26 tools · 6 jobs
Best AI tools for Salesforce architects.
Ranked directory with workflows, pricing, and pros and cons. Curated stack picks for architects below.
Starter stack for architects
See all →Frequently asked
Questions architects keep asking.
How should architects think about AI agents in their reference architecture?
Treat agents as a new actor class, not a new tool. They have credentials, permissions, audit trails, and rate limits, model them like an integration user, not like a feature. The architectures that fail treat agents as magic; the ones that work treat them as services.
Multi-org or single-org for an enterprise rollout?
Single-org by default. Multi-org by exception, justified by regulatory boundaries (GDPR data residency, HIPAA tenant isolation) or genuinely independent business units with no shared accounts/contacts. Multi-org for org-chart reasons is the most expensive mistake architects make.
When should I use Data Cloud vs. an external warehouse?
Data Cloud if 80%+ of your activation surface is inside Salesforce (Marketing Cloud journeys, Agentforce, Sales Cloud personalization). External warehouse if 80%+ of your activation surface is outside (BI tools, ML models, data products). The hybrid is real but rare.
What's the most under-rated architectural skill in 2026?
Knowing what NOT to build. The architects with the highest leverage in the AI era are the ones who can look at a feature request and route it to the agent instead of the dev backlog. That's a different muscle than designing the agent.
Getting Started
Skip the reading. Ship the work.
Resources only get you so far. Hand the actual architects work to Clientell AI, the agent that builds Flows, cleans data, and manages users on your real Salesforce org.
Unlimited messages · No credit card required
SOC 2
HIPAA
GDPR
Salesforce Partner