Hand your client a map of their Salesforce org in week one
Clientell MCP gives Claude Code, Cursor, Codex or VS Code a map of the Salesforce org: objects, fields, Flows, Process Builders, Workflow Rules, Apex triggers, validation rules and permissions. Ask what touches a field, and check the answer against the org.
No card. The clock starts when you connect your first org. Start with the client’s sandbox. Clientell runs on desktop.
Day one in a client org
Your first hour in a Salesforce org you didn’t build
A worked sequence for a sandbox your client has handed you. Each question is one you can paste into your agent. The field and object names are examples, so swap in your client’s.
- 01
Connect the client sandbox, not production
Sign up for the trial and connect a sandbox the client has given you. Production waits for the client’s sign-off. The trial clock starts when you connect your first org.
- 02
Ask for the shape of the org
Which objects have the most Flows, Apex triggers and validation rules attached to them?
This tells you where the client’s logic lives before you read any of it. Write down the top three objects. Those are where surprises hide.
- 03
Pick the field the client talks about most
What touches Opportunity.StageName? List every Flow, Process Builder, Workflow Rule, Apex trigger, validation rule and permission that reads or writes it.
Swap in the field your client keeps naming. Use the answer as a list of things to open, not as a verdict.
- 04
Check three answers against the org itself
Open three of the items the agent named and confirm each one is real and does what the agent said. For a custom field, the “Where is this used?” button in Setup is a second source. Keep a note of any item one source has and the other lacks.
- 05
Ask what runs when a record is saved
What runs when an Opportunity is saved? List the Apex triggers, record-triggered Flows, Process Builders and Workflow Rules on the object.
Old Process Builders and Workflow Rules often sit beside newer Flows on the same object. Mark which ones are still active, and check the run order against Salesforce’s order of execution.
- 06
Ask who can see and change it
Which profiles and permission sets give edit access to this field?
Compare against what the client believes. Gaps here are usually the first useful finding you hand back.
- 07
Write up what you can prove
Keep the answers you checked. Mark the rest “unverified”. That page is your week-one map, and nothing in it came from a guess.
Before you quote
Know what a change touches before you quote it
A quote that misses one Flow becomes unpaid rework. This checklist turns the map into a dependency and impact read you can finish before you price the change. Run it in the client’s sandbox.
- 01
Write the change in one sentence
Object, field or automation, and what changes. Example: rename the Negotiation stage on Opportunity to Contract Review.
- 02
Ask what touches it
Flows, Process Builders, Workflow Rules, Apex triggers, validation rules and permissions that reference the field or value. One question, in a sandbox.
- 03
Ask what fires on the object
What else runs when that record is saved. A change can be safe for the field and still collide with a trigger on the object.
- 04
Open every hit yourself
Mark each as confirmed, not found, or unsure. Confirmed hits go into the price. Anything you could not resolve goes into the quote as an exclusion, a stated assumption or paid discovery work.
- 05
Check what the map does not cover
Reports, dashboards, outside integrations and managed packages are not in the list above. Check those by hand or ask the client who owns them.
- 06
Sort the hits
Must change, must test, or note only. Price the first two. Keep the third for the client conversation.
- 07
Put your assumptions in the quote
State the sandbox you checked and the date. If the org changes before work starts, run the checklist again.
An example of sorting the hits
Illustrative only, for the change “rename the Negotiation stage on Opportunity”. It is not a customer result.
Must change
A validation rule that tests for the old stage name
Priced as build work
Must test
A record-triggered Flow that branches on stage
Priced as test and review
Note only
A permission set that already grants edit on the field
Listed, not priced
Client data
How your client’s data is handled
- Records are read live under your own Salesforce permissions and are not stored. The graph holds structure, not contents.
- Nothing changes in the org without your approval.
- Start in the client’s sandbox. Connect production only with the client’s sign-off.
- Passed Salesforce’s security review. Listed on AgentExchange. SOC 2 Type II, ISO 27001, GDPR and HIPAA, as stated on our AgentExchange listing.
Details are in the security section of the docs.
The offer
Pricing for consultants
$249 a month for 10 people. One client production org, its sandboxes included. Another client's production org is $200 a month, or talk to us about a multi-client plan.
14-day trial, no card. See pricing or talk to us.
Evidence
Does the map help the agent?
On a metadata-question benchmark, the same model's graded score was 86.5% with Clientell's Context Graph against 44.2% without it: 110 questions × 3 runs, graded by Claude Opus.
Install
Add it to the agent you already use
Clientell MCP works in Claude Code, Cursor, Codex and VS Code. Add the server to your agent’s MCP config, sign in to Clientell, then connect the client’s sandbox. The setup steps cover each client.
Deploys still go through your own Salesforce CLI session. Moving off the Salesforce DX MCP server? Read the end-of-life guide.
Common questions
Short answers
Claude Code and the Salesforce CLI already work for me. Why add this?
Often they do, for one-off queries. The gap is questions about structure: what touches this field, what fires on this object. Try both on one client sandbox during the trial and keep whichever is right more often.
My client’s security team will not allow a third-party tool.
Clientell passed Salesforce’s security review and is listed on AgentExchange. Records are read live under your own Salesforce permissions and are not stored. Start in the client’s sandbox, and connect production only with the client’s sign-off.
I work across many client orgs. How does pricing work?
$249 a month for 10 people. One client production org, its sandboxes included. Another client's production org is $200 a month, or talk to us about a multi-client plan.
I do not want the client to think a tool did the work.
Clientell MCP runs inside your own agent and terminal. Nothing changes in the org without your approval.
Does it replace the Salesforce DX MCP server?
No. It maps the org and tells your agent what a change would touch. Deploys still go through your own Salesforce CLI session. See the DX MCP end-of-life guide for how the two fit together.
More: Clientell MCP · AI for Salesforce consulting partners · Clientell vs Cirra AI · Claude Code for Salesforce admins · Salesforce org documentation
Try it on one client sandbox
Ask three questions, then check the answers against the org. 14-day trial, no card.
Clientell runs on desktop.
Last updated 28 October 2026.