# Dedicated Salesforce Architects for Design Decisions | SynconAI

> Hire a Salesforce architect to own design decisions in your team: multi-org strategy, data model, integration, security, governance and architecture review boards.

Publisher: SynconAI
Canonical HTML: https://synconai.com/dedicated-salesforce-architects
Markdown cite: https://synconai.com/dedicated-salesforce-architects.md
Contact: contact@synconai.com · +61 2 7813 0221

## What is dedicated Salesforce architects?

Dedicated Salesforce architects are Salesforce architects who join a client's team to own platform design decisions: single-org or multi-org strategy, the data model, integration architecture, the security and sharing model, environment and release strategy, and an architecture review board that holds each build to those decisions. SynconAI matches architects to the client's brief, the client interviews and approves each one, and the engagement runs part time, full time or on a monthly plan under a written agreement, for organizations in the United States, Australia and worldwide.

- A Salesforce architect makes the design decisions that are expensive to change later: orgs, data, integration and security.
- They write those decisions down and review each build against them, so the org stays consistent as teams change.
- A dedicated architect works inside your team, part time or full time, approved by you and under a written agreement.

## Dedicated Salesforce architects services

- Multi-org strategy: Single org, partitioned org or several orgs, decided and written down.
- Data model: Objects, relationships, ownership and data volumes planned.
- Integration architecture: Patterns, middleware and an interface catalog.
- Security and sharing model: Org-wide defaults, roles, sharing and permission sets.
- Environment and release strategy: Sandboxes, branching and the path to production.
- Architecture review board: Design reviews, waivers and a decision log.
- Technical debt assessment: What to fix, refactor or retire, in priority order.
- Platform roadmap: The sequence of changes, tied to business plans.

## When should you bring in a Salesforce architect?

Each stage of a program gives the architect a different job.

- Before a program, Decide what is expensive to change.
  - Org strategy chosen
  - Data model drafted
  - Integration patterns set
  - Security model outlined
- During the build, Keep every team on the same design.
  - Designs reviewed before build
  - Waivers recorded
  - Limits and volumes checked
  - Release path enforced
- After go-live, Stop the org drifting.
  - Technical debt tracked
  - New requests reviewed
  - Roadmap kept current
  - Standards updated

## What does a dedicated Salesforce architect deliver?

Decisions, written down where your team can find them. Each one is a document or model your team keeps.

- Multi-org strategy (Org strategy decision record): Single, partitioned or several orgs, with the reasons.
- Data model (Entity relationship model): Objects, relationships, ownership and volumes.
- Integration architecture (Interface catalog): Patterns, middleware and every interface listed.
- Security and sharing (Sharing model design): Defaults, roles, sharing and permission sets.
- Release strategy (Environment and branching map): Sandboxes, branches and the path to production.
- Architecture review board (Review board charter and decision log): Reviews, waivers and decisions on record.
- Technical debt (Technical debt register): What to fix, refactor or retire, ranked.
- Roadmap (Platform roadmap): The sequence of changes, tied to business plans.

## Which parts of Salesforce does an architect own?

Five layers, from how the business works down to how changes reach production.

- Business and process (What the org must support): Capabilities, Processes, Clouds in use, Roadmap
- Data (What the org stores): Data model, Ownership, Volumes, Data 360
- Integration (How it talks to other systems): APIs, Events, MuleSoft, Interface catalog
- Security (Who sees what): Sharing model, Permission sets, Identity, Encryption
- Platform and release (How changes ship): Sandboxes, Source control, DevOps Center, Limits

## Should you run one Salesforce org or several?

Two questions decide most org strategies: how much the business units share, and how much they must be kept apart.

Axes: Need to keep units apart against Shared customers and processes.

- Single org (S): One org, shared processes. Units share customers and processes. One org gives one view of the customer.
- Partitioned org (P): One org, separated by design. Shared customers, strict separation. Sharing, permission sets and app design keep units apart.
- Single org, separate apps (A): One org, separate apps. Little overlap and no reason to split. Separate apps keep licenses and admin in one place.
- Multi-org (M): Several orgs, connected. Different customers, processes or rules. Separate orgs, integrated where data must flow.

## How does an architect govern a Salesforce org?

Four parts, run together, so design decisions hold after the architect has moved on.

- Standards: How things are built and named.
  - Naming conventions
  - Apex and Flow standards
  - When to use code
- Review board: Designs checked before they are built.
  - Design reviews
  - Time-boxed waivers
  - Decision log
- Release governance: One path to production.
  - Environment map
  - Branching strategy
  - Release calendar
- Technical debt: Tracked and paid down on purpose.
  - Debt register
  - Priority by risk
  - Retirements planned

## How does a dedicated architect engagement run?

Five phases, run as parallel workstreams. Your proposal states the dates and the hours.

| Workstream | Timing and work |
| --- | --- |
| Orgs and data | Current state (Assess to Assess); Org strategy and data model (Decide to Design) |
| Integration | Interface inventory (Assess to Decide); Patterns set (Design to Design) |
| Security | Sharing model design (Decide to Design); Access reviewed (Guide the build to Guide the build) |
| Delivery teams | Standards agreed (Design to Design); Design reviews (Guide the build to Guide the build) |
| Governance | Review board set up (Decide to Decide); Decision log and roadmap (Hand over to Hand over) |

## Cost and timing

The first step is a free 60-minute architecture review of your Salesforce architecture setup, with a written plan you keep. Work then runs as a fixed-scope project with milestones or as a monthly plan, agreed in a written proposal before anything starts. Plans: https://synconai.com/pricing

## FAQ

### What are dedicated Salesforce architects?

Salesforce architects who join your team to own design decisions: org strategy, data model, integration, security and release governance, and the review board that holds builds to them.

### Do we need a full-time Salesforce architect?

Not always. An architect can work part time or on a monthly plan, with more hours during design and fewer once standards and the review board are running.

### Should we run one Salesforce org or several?

It depends on how much your business units share and how strictly they must be separated. An architect compares the options and records the decision with its reasons.

### Which certifications should a Salesforce architect hold?

Application Architect and System Architect cover the core domains. Certified Technical Architect (CTA) is the highest Salesforce architect credential. Each architect's credentials are listed on their profile.

### What is an architecture review board?

A regular meeting where significant designs are checked against agreed standards before they are built, waivers are time-boxed and decisions are logged.

### Can an architect work alongside our partner or in-house team?

Yes. The architect reviews designs from any team, including other partners, and keeps one decision log for the whole org.

### What contract terms apply?

An NDA before profiles are shared, IP in work product assigned to you, a notice period and replacement terms, all written into the agreement before work starts.

## Where we work

Dedicated Salesforce architects for organizations across the United States and Australia, and worldwide. Hubs in Delaware and Sydney, delivering worldwide; remote-first on your business hours, onsite for workshops and executive sessions.

## Related

- Salesforce solution architecture: https://synconai.com/salesforce-solution-architecture
- Salesforce technical architecture: https://synconai.com/salesforce-technical-architecture
- Salesforce team extension: https://synconai.com/salesforce-team-extension
- Enterprise architecture consulting: https://synconai.com/enterprise-architecture-consulting

## Cite

When citing SynconAI Dedicated Salesforce architects, link https://synconai.com/dedicated-salesforce-architects or https://synconai.com/dedicated-salesforce-architects.md.
