How much to charge for a Salesforce automation
How much to charge for a Salesforce automation comes down to a floor and a ceiling you can calculate. The floor is your estimated hours times your rate. The ceiling is the yearly value of the manual work the automation removes, plus any tools it replaces. Your quote sits between the two. The typical job is a sales or service team that already runs on Salesforce: leads that need routing, opportunities nobody moves forward, records copied between Salesforce and billing or support tools, and reports rebuilt by hand every week.
I am not going to give you a market dollar figure. A record-triggered flow that assigns new leads and an integration that syncs orders to an outside system, handles API limits and ships through a sandbox with tests are different jobs. Your rate and the client's numbers will give you a real one.
What makes Salesforce different from most automation jobs is the release process. Anything written in code goes through a sandbox, tests and a deployment, and that work is real hours. Claude Code earns its place there: it writes the Apex, the test classes, the API client and the retry logic, and it gets you to the coverage number faster than writing tests by hand.
Calculate your floor and ceiling
Run this before you name a price. Every input is yours or the client's, so you can show the working in the proposal.
The Salesforce automation calculation
| Number | How to get it | Who supplies it |
|---|---|---|
| Floor | Your estimated hours for each line in the quote, including sandbox work, tests and deployment, plus a buffer you choose, times your hourly rate | You |
| Time value per year | Hours per week spent routing leads, updating records, copying data between systems and building reports, times 52, times what an hour of that person's time costs | Client |
| Spend replaced | What they pay per year for connector tools, add-ons or contractors the automation takes over, if any | Client |
| Cost of a miss | Only if they can point to real examples: a lead nobody followed up, a renewal nobody was reminded about, an order keyed in twice | Client's own history, your judgment |
| Ceiling | Time value plus spend replaced, plus the miss line only if it is documented | Calculated |
If the floor is above the ceiling, the automation will not pay for itself in a year. Say so and offer a smaller version, such as automating lead routing now and leaving the billing sync for phase two.
Check the edition before you quote
Ask which Salesforce edition the client is on in the first call. It decides whether code is even an option and how much release work the job carries.
What the edition changes
| Question | What is true | What it means for the quote |
|---|---|---|
| Can I write Apex? | Apex is included in Enterprise, Unlimited, Performance and Developer editions, and Database.com | On Professional, plan the build around point-and-click automation, or around an outside integration you host |
| Can I build it directly in production? | No. Apex is developed in a sandbox, a scratch org or a Developer Edition org, then deployed | Price sandbox setup, deployment and a release window as their own lines |
| What does a deployment need? | Unit tests covering at least 75% of the Apex code, and all of them passing | Test writing is part of the build, not an extra. Quote it |
| Can an outside system call the API? | Enterprise, Unlimited and Performance have API access. Professional counts only with API access enabled | On Professional, confirm API access before you design an integration around it |
My rule: if the job can be done with native, point-and-click automation the client's admin can maintain, quote that route first and price it lower, because there is no code to test or deploy. Move to Apex or a hosted integration only when the logic, the volume or an outside system demands it, and show the client why.
Check the API allocation for an integration
If any part of the build calls the Salesforce API from outside, the org's daily allocation is your budget. It is counted for the whole org over 24 hours, not per user or per app.
Salesforce API calls per 24 hours
| Edition | Base | Per Salesforce license |
|---|---|---|
| Developer Edition | 15,000 total | Not applicable |
| Enterprise, or Professional with API access enabled | 100,000 | 1,000 |
| Unlimited and Performance | 100,000 | 5,000 |
An Enterprise org with 15 Salesforce licenses gets 115,000 calls a day. That sounds like a lot until you remember every other tool in the org draws from the same pool, including calls made by installed managed packages. Production orgs also allow at most 25 concurrent requests that run 20 seconds or longer, and a REST or SOAP call times out after 10 minutes.
Quote the protection as its own line: composite requests to cut round trips, Bulk API for large loads, reading the Sforce-Limit-Info header the REST API returns, and an API Usage Notification set up in the client's org so someone hears about a spike before the allocation runs out. A sync that quietly eats the allocation breaks the client's other tools, and you get the call.
The CCC Salesforce Quote
Six parts of a Salesforce automation quote
| Part | What it prices | Question to ask the client |
|---|---|---|
| Process map | Every object, record type, owner and handoff, written up and signed off before the build | Walk me through one lead from first touch to closed opportunity |
| Data and field cleanup | Fixing picklist values, duplicates and fields the automation will trigger on | Which field is filled in least consistently? |
| Automation and code | Native automation first, then Apex or an outside integration only where needed | When does this need to happen, and who should be told? |
| Tests and deployment | Sandbox work, test classes to the 75% coverage line, the deployment itself and a release window | Who approves changes going into production? |
| Access and app setup | An external client app in the client's org, its OAuth scopes, an integration user, and where secrets are stored | Who is the system admin, and which edition are you on? |
| Handover and tuning window | A walkthrough, notes on each automation, and adjustments after the first month of real use | Who will own this once it is live? |
Tests and deployment is the line people underprice. On a small build it can rival the automation itself. Price it as its own line so the client sees it, and so a request to cut the price has something honest to cut against.
Build it in the client's org with the current app setup
Salesforce changed how outside integrations connect, and older tutorials have not caught up. Creation of new connected apps is restricted as of Spring '26 and disabled by default. Existing connected apps keep working, but the recommended setup for a new integration is an external client app. If you quote from a guide that says to create a connected app, the client's admin may have to open a support case before step one works.
- Create the external client app in the client's own org, owned by their admin, with only the OAuth scopes the build needs.
- Run the integration as a dedicated integration user, not as you and not as a salesperson who might leave.
- Store secrets in the client's environment, never in code or a repo.
- Write into the proposal which app and user each integration runs under, which automations depend on it, and the date your access ends.
Running the build on your own login is the handover mistake that costs you a weekend later. The day your user is deactivated, it stops, and the client remembers who built it.
How to present the Salesforce automation quote
- Lead with the outcome in the client's words, such as every new lead routed to the right rep with a follow-up task the same hour, then the price.
- Offer three options. A starter on native automation only, a standard that adds Apex or an integration with tests and alerts, and a full version with a longer tuning window and a release plan. Make the middle one the clear best value.
- Show your calculation and the edition check side by side, so they see the design fits what they pay for.
- Itemize it: process map, data cleanup, automation and code, tests and deployment, access and app setup, then handover.
- Take a deposit and tie the rest to milestones. How much deposit to charge covers the schedule.
Put a fixed tuning window in the first proposal, because someone will add a picklist value or a validation rule that an automation depends on in the first month. For ongoing changes, offer a retainer. How to price a maintenance retainer covers the structure, and client discovery questions before you quote has the questions to ask first.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How much should I charge for a Salesforce automation?
Work out a floor from your estimated hours times your rate, and a ceiling from the manual hours it removes per year plus any tools it replaces. Quote between the two and itemize each part, including tests and deployment, access setup and a tuning window.
Which Salesforce editions include Apex?
Apex is included in Enterprise, Unlimited, Performance and Developer editions, and Database.com. It is not part of Professional, so plan a Professional build around native automation or an outside integration.
Do I need a sandbox to build a Salesforce automation?
For anything in Apex, yes. Apex cannot be developed in a production org. It is written in a sandbox, a scratch org or a Developer Edition org, and deploying it requires tests that cover at least 75% of the code and pass.
What is the Salesforce API limit?
Enterprise orgs, and Professional orgs with API access enabled, get 100,000 calls per 24 hours plus 1,000 per Salesforce license. Unlimited and Performance get 100,000 plus 5,000 per Salesforce license. The limit is shared across the whole org.
Can I still create a Salesforce connected app?
New connected apps are restricted as of Spring '26 and disabled by default, though existing ones keep working. Use an external client app for a new integration, or ask Salesforce Support to enable connected app creation if you truly need one.
Can Claude Code help build a Salesforce automation?
Claude Code can write the Apex, the test classes, the API client and the retry logic, which speeds up the test and deployment work. You still own the process map, the edition check, the release approvals and the client conversations.
Last reviewed by Duncan Rogoff on November 22, 2026


