Salesforce architecture consulting
Independent Salesforce architecture support for data models, integrations, security and multi-cloud design, with every significant decision written down and explained.
Architecture decisions in Salesforce are cheap to make and expensive to reverse. Choosing the wrong object for a core entity, letting every integration write directly to Account, or building a sharing model around today's org chart can cost far more later than the original build.
GeekMidst provides Salesforce architect consulting for organisations that want those decisions made carefully, by someone who will explain the trade-offs and write them down. We work on single orgs and multi-cloud estates that combine CRM, Marketing Cloud Engagement, Account Engagement, Data Cloud (now branded Data 360) and external systems.
When to bring in an architect
- Before a large implementation or rebuild, to set the data model, security model and integration approach.
- When adding a new cloud, business unit or region to an existing org.
- When performance, governor limits or data volumes are starting to cause problems.
- When you are deciding between one org and several, or between building in Salesforce and building outside it.
- When an internal team wants an independent review of a design before committing to it.
Areas we design and review
Data model
Standard versus custom objects, relationships, record types, data volumes and archiving.
→Integration architecture
API choice, middleware versus point-to-point, event-driven patterns, error handling and ownership of each data element.
→Security and sharing
Profiles, permission sets, role hierarchy, sharing rules and how external users fit in.
Automation strategy
Where Flow, Apex and platform events belong, order of execution and how to avoid recursive or conflicting automation.
→Customer data and Data Cloud
Ingestion patterns, mapping to the Customer 360 Data Model, identity resolution and activation.
→Environments and release
Sandbox strategy, source control and deployment approach.
→How we document decisions
Every significant choice is captured as a short decision record: the context, the options considered, the option chosen, the reasons, and the consequences you accept by choosing it. These records are written for the people who will maintain the org after us, not for an audit file.
A typical architecture engagement also produces:
- A context diagram showing Salesforce, connected systems and the direction of each data flow.
- A data model diagram and data dictionary for the core objects.
- An integration catalogue listing each interface, its pattern, frequency, owner and error handling approach.
- A security model summary describing who can see and change what, and why.
- A risk register covering limits, data volumes and dependencies that need monitoring.
Where a detail depends on your edition, licences or current platform limits, we say so and confirm it against your org rather than assume. The Salesforce Developer documentation and Salesforce Help remain the reference for current limits.
How an architecture engagement runs
- 01
Frame the question
Agree exactly which decisions are in scope and who will make them.
- 02
Understand the current state
Review metadata, integrations, data volumes and existing documentation, and speak to the people who run the system.
- 03
Explore options
Set out two or three realistic options for each decision, with trade-offs in cost, complexity and future flexibility.
- 04
Decide and record
Work through the options with your team, then write up decision records and diagrams.
- 05
Support the build
Review designs and pull requests during delivery, so the architecture survives contact with real requirements.
Questions we hear
Do you only advise, or do you also build?
Can you review a design produced by another partner?
Should we use one org or several?
Do you work with Data Cloud and Marketing Cloud architecture as well as CRM?
What do you need from us to start?
Get an architecture review
Tell us the decision in front of you and the systems involved. We will suggest how to frame it and who needs to be in the room.
