Hire an AI Salesforce architect

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A recommended design with the main decision stated first
• A decision record for each big choice, with options, trade-offs and when to look again
• A data model sketch showing objects, links and who can see what
• An integration plan showing how data moves and what happens on failure
• A list of Salesforce limits that touch your design, each marked to check
• A short release plan from sandbox to live

How it does the job well

• Governor limits are non-negotiable. Every design must account for SOQL (100), DML (150), CPU (10s sync/60s async), heap (6MB sync/12MB async). No exceptions, no "we'll optimize later."
• Bulkification is mandatory. Never write trigger logic that processes one record at a time. If the code would fail on 200 records, it's wrong.
• No business logic in triggers. Triggers delegate to handler classes. One trigger per object, always.
• Declarative first, code second. Use Flows, formula fields, and validation rules before Apex. But know when declarative becomes unmaintainable (complex branching, bulkification needs).
• Read the existing code, its conventions and its tests before changing anything. Match the project's patterns.
• Make the smallest change that fully solves the request. Keep unrelated refactors out.
• Reproduce a bug before fixing it, and add a test that fails without the fix.

Mistakes it avoids

• Saying you looked at the org, ran a check or changed a setting.
• Invented usage figures, such as "you have 97 queries left".
• Code before the data model and integration choices are agreed.
• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.
• Changing behaviour outside the request, such as reformatting whole files or renaming public interfaces.

What a good result looks like

An example, not your task: You are adding another cloud, such as Service or Marketing, to an org you already run.

• Recommendation. The main design choice and the reason, up front.
• Data model. Objects, how they link, and who can see each one.
• Integration plan. How each outside system sends data, and what happens when a call fails.
• Automation choices. Which jobs use Flows or formulas and which need code, with reasons.
• Decision records. One short record per big choice, with options, trade-offs and when to review.
• Limits to check. Salesforce limits that touch the design, each marked to check in current documentation.

How the work is checked

• The recommendation comes first and says why.
• Every integration has a failure plan.
• Every limit number is marked to check, or comes from a page the user gave you.
• No claim about the user's org that the user did not tell you.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Understand your org. It maps what exists today, the data volumes and the pain points. Anything missing is asked once, then marked MISSING.
• Shape the data model. It lists objects, links, record types and the sharing rules that decide who can see what.
• Choose integration patterns. For each outside system it picks sync or async, push or pull, and plans for failure and retries.
• Place the logic. It uses Flows, formulas and validation rules first, and moves to code only where those get hard to keep.
• Check limits and security. It tests the design against bulk loads and Salesforce limits, and flags personal data that needs protecting.
• Write decisions and a release plan. Each big choice gets a decision record. A short release plan covers sandbox, testing and rollback.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id specialized-salesforce-architect only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/specialized-salesforce-architect/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The business problem you want Salesforce to solve, in plain words
• Which Salesforce products you use, and your edition if you know it
• Outside systems that must connect, how often data moves and about how many records
• Your current objects, Flows or code, as a list or export with no customer records (optional)
• Rules you must follow, such as privacy or where data may be stored (optional)

Helpful context (optional)

• Your object list from Setup, with no customer records.
• Expected record counts and growth for your biggest objects.
• The current Salesforce limits page for your edition, pasted in.

Tools and access

• Claude, ChatGPT or Gemini in a chat: Good at comparing options across a long brief and writing the decision records.
• Claude Code: Useful when your Salesforce project is in a code folder, so it can read your metadata files.

Functions and deliverables

• Salesforce architect agent: Get a Salesforce architecture plan with a data model, system links, decision records and the platform limits to check before you build.
  • A recommended design with the main decision stated first
  • A decision record for each big choice, with options, trade-offs and when to look again
  • A data model sketch showing objects, links and who can see what
  • An integration plan showing how data moves and what happens on failure
  • A list of Salesforce limits that touch your design, each marked to check
  • A short release plan from sandbox to live
  Source: Michael Sitarzewski and Agency Agents contributors.
• System design planner: Plan your system design before you build. Describe your app and get an architecture pick, a diagram and the trade-offs behind each choice.
  • A recommended architecture
  • A diagram in Mermaid form
  • A dependency check with problems flagged
  • A trade-off summary for each choice
  Source: Alireza Rezvani.
• Decision record writer: Write a decision record for a design or tech choice you made. You get the reasons, the options you passed on and the trade-offs, in a short file.
  • Decision record in your project's format
  • List of rejected options with reasons
  • Stated trade-offs
  • Suggested file name and place
  Source: Addy Osmani.
• Platform growth experiment planner: Share your product link. Test demand for one integration before building a full marketplace listing.
  • A recommendation with its evidence and missing facts
  • A small test with an owner, cost cap and decision rule
  • The next action and what needs approval
• AI project context organiser: Share your project and next task. Get a short rules file, a focused file list and a clear handoff for later sessions.
  • A ready rules file for your project
  • A list of which files to load for each task
  • Rules for when to reset or trim the session
  • A checklist for spotting drifting answers
  Source: Addy Osmani.

Tasks you can use it for

• You are adding another cloud, such as Service or Marketing, to an org you already run.
• A system outside Salesforce, such as your store or billing tool, must sync with it and you must pick how.
• Your org has old workflows and Flows that clash and you need a clean-up plan.
• A developer or partner proposes a design and you want a written second opinion.

Limits to check before starting

• You have one how-do-I question about a field, report or Flow. Ask your Salesforce admin or Salesforce Help.
• You want changes made inside a live org. This agent only proposes, so hand its plan to your admin.
• You want to link two apps with no code, such as Zapier or Make. Use the Zapier and Make automation planner.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Add the pack to your AI as a skill. If you cannot, start a new chat and paste SKILL.md, then references/source-agent.md.
• Describe the business problem first. Then paste your setup, such as a list of objects and automations. Leave out customer records.
• Say what is fixed, such as the products you use, your deadline and who will maintain the build.
• Read the recommendation first. If you disagree, say so early and ask it to rework that choice.
• Check each limit it names against current Salesforce documentation, or ask your admin, before you trust the number.
• Give the decision records to your admin or partner to build from. Nothing in your org changes until a person makes the change.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/specialized-salesforce-architect for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.