Org strategy
Multi-org vs. single-org vs. multi-tenant. The decision tree, with the failure modes for each.
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.
12 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
Multi-org vs. single-org vs. multi-tenant. The decision tree, with the failure modes for each.
Standard vs. custom objects, big objects, external objects, Data Cloud. When to use which.
Sync, async, event-driven, polling. The cost model and the failure model for each.
Where do agents live, what do they touch, and how do you keep them from turning your org into mush?
Sharing, profiles, permission sets, territories. The model that scales and the one that bites.
Lightning, DX, multi-org consolidation. The migration phases, the rollback plan, the comms plan.
Use cases for architects
Auto-generate the architecture spec, the field-usage analysis, the flow dependency graph. The handover doc that stays accurate.
Reference architecture for cross-cloud data flow, integration patterns, and the consolidation playbook for multi-org work.
Generate flows that respect bulk patterns and governor limits from the prompt up. Review at the pattern level, not line by line.
Build, audit, and re-baseline the access model. The compliance prep that used to be a 2-week project, automated.
By topic
Curated for architects
Score
Quick reference for the 30 most common SetupAuditTrail action types: what each entry means, how severe it is, and what to do when you see it.
Score
The 4 permission layers and how they resolve, 10 named anti-patterns, a SOQL query bank and a cleanup sequence that will not break access.
Avg readiness
A checklist to test whether your Salesforce org is ready for AI: data quality, automation maturity, user adoption and integration readiness.
Read time
A 10-chapter guide for admins and the leaders who fund them. Worksheets, AI prompts and a 90-day plan to audit, rank and fix Salesforce technical debt.
Workflow
Step-by-step playbook to find and fix competing automations on Salesforce objects: detect race conditions, retire Workflow Rules, consolidate to one Flow.
Dev workflow
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.
Score
Salesforce ended support for Workflow Rules and Process Builder in 2025, but they still run. Rank by risk, drop some, rebuild the rest as flows you approve.
Score
The Salesforce sharing and security model on one page: OWD, the 6-rung record-access ladder, restriction vs scoping rules, FLS and the Apex/Flow bug. Free PDF.
Industry avg
Vendor-neutral 50-point checklist for evaluating any AI agent, copilot, or Agentforce vendor before it touches production Salesforce. Free PDF.
Score
The 47-point check before you launch Agentforce, now with agent user access: role, object and field access, and permission sets the agent needs.
Illustrative example
Review Salesforce permissions with 38 checks for profiles, integration users, permission sets, sharing and sensitive fields. Document access decisions.
Score
A 15-minute audit checklist of the 15 most common Flow anti-patterns in production Salesforce orgs. Signal, why it hurts, and the rebuild for each.
Adjacent resources
Ranked directory with workflows, pricing, and pros and cons. Curated stack picks for architects below.
Starter stack for architects
See all →Frequently asked
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.
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.
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.
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.
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.
14-day free trial · No credit card required