Before you post the job, separate the one-time build from the work that repeats. A Salesforce developer is the right hire for the first and an expensive way to cover the second. In most RIA and law firm orgs, the recurring work is the larger half: imports, bulk updates, deduplication, field mapping, report rebuilds, and the integration glue between Salesforce and everything else. That is the part worth solving differently.
What the role costs in 2026
Sources: ZipRecruiter (July 2026), FoundHQ consultant rate guide, and published partner rate cards.
| Role | Onshore | Nearshore | Offshore |
|---|---|---|---|
| Administrator | $85 to $115/hr | $35 to $55/hr | $30 to $50/hr |
| Developer | $90 to $125/hr | $45 to $70/hr | $45 to $65/hr |
| Architect | $135 to $170/hr | $80 to $95/hr | $70 to $85/hr |
Two numbers matter more than the headline salary. The first is utilization: a firm with one Salesforce-native product and 60 users rarely has 40 hours a week of developer-grade work, so you end up paying developer rates for admin tasks. The second is bus factor. One person holding every automation, every field mapping and every report is a single point of failure the day they take a new job.
The nine jobs firms actually hire for
Pulled from what RIAs and law firms describe when they open the req. Only three of the nine require code.
- Data imports and transformations. Custodian files, e-billing exports, spreadsheets from a prior system. Mapped, cleaned, loaded, checked.
- Bulk updates and mass changes. Reassign a book, restate a fee schedule, retag 4,000 matters after a practice-group change.
- Deduplication and hygiene. Merging households, matching contacts to the right entity, fixing what a form let through.
- Reports and dashboards. The quarterly pack, the origination report, the WIP view partners keep asking for.
- Declarative automation. Flows, validation rules, approval steps, assignment logic.
- Integration glue. Salesforce to Addepar, Black Diamond, a DMS, a billing system, a shared inbox.
- Apex and triggers. Logic the declarative tools cannot express. Code.
- Lightning Web Components. Custom screens for a workflow the standard UI handles badly. Code.
- Custom API integrations. A system with no packaged connector. Code.
The first six repeat. They arrive weekly or monthly, they are deterministic, and they are almost entirely about moving data between systems accurately. That is the distinction the hiring decision should turn on.
Seven ways to cover the work
Ordered by who ends up owning the org, not by preference. Most firms end up with two or three of these at once.
Promote an internal admin
Best for: Firms whose backlog is configuration, not code · Pricing: Certification is about $200 per exam; the person is already on payroll
Strengths
- Knows the firm, the clients and the exceptions
- Covers six of the nine jobs above
- Fastest path to someone owning the org
Trade-offs
- Takes real hours away from their existing role
- Hits a hard ceiling at Apex and custom integrations
- Single point of failure unless a second person shadows them
Certified implementation partner
Best for: A scoped, one-time build or a vertical product rollout · Pricing: Project-based; Litify and FSC builds commonly run three to six months
Strengths
- Deep experience with Litify, Practifi, Salentica and FSC
- Fixed scope and a delivery date you can hold them to
- Brings patterns from firms that look like yours
Trade-offs
- Priced for projects, not for weekly upkeep
- Knowledge leaves with the engagement unless you document it
- Change orders are where budgets actually go
Managed services retainer
Best for: Steady upkeep without a headcount · Pricing: $2,500 to $9,000 a month; Litify-specific admin support runs about $65 to $80 an hour
Strengths
- Predictable monthly cost and a real SLA
- Covers vacations and turnover
- Cheaper than a full-time senior hire
Trade-offs
- Hours are capped, so the backlog still queues
- You are one client among many
- Recurring data work consumes hours you would rather spend on improvements
Nearshore or offshore contractor
Best for: Well-specified builds where rate is the constraint · Pricing: $30 to $70 an hour depending on role and region
Strengths
- Roughly half the onshore rate
- Easy to scale up for a defined project
- Good fit for Apex and LWC work with a clear spec
Trade-offs
- Requires someone internal to write the spec and review the work
- Time-zone lag on work that has to happen today
- Client data access needs a real review before you start
Salesforce's own declarative tools
Best for: Teams who have not yet exhausted what the platform includes · Pricing: Included in your license
Strengths
- Flow, Data Loader, Duplicate Rules and the Import Wizard cover more than most firms use
- Nothing new to buy or vet
- Native audit trail and permissions
Trade-offs
- Someone still has to build and babysit each one
- Weak on unstructured inputs like varied PDFs and shared-inbox email
- Flows accumulate into their own maintenance problem
iPaaS or ETL tooling
Best for: Connecting Salesforce to systems that have clean APIs · Pricing: From roughly $20 a month to enterprise contracts
Strengths
- Purpose-built for moving records between systems
- Large connector libraries
- Handles scheduled syncs well
Trade-offs
- You build and maintain every pipeline
- Struggles where the input is a document rather than a record
- Adds a second platform for someone to own
Caddi
Best for regulated opsBest for: The recurring data work in law and finance back offices · Pricing: Custom; pilots start small and scale with usage
Strengths
- Record the task once; Caddi writes it as deterministic code and runs it
- Reads varied PDFs and shared-inbox email, not just clean records
- Built and maintained for you, so the backlog does not queue behind one person
- SOC 2, audit trails and role-based access
- 70+ integrations across legal and wealth stacks
Trade-offs
- Not a substitute for Apex or a custom Lightning component
- Vertical focus on law and finance, not a general developer bench
- You still need someone who owns Salesforce configuration decisions
When you genuinely should hire
There are cases where the developer is the correct answer and everything else is a detour.
- You are building a product on the platform. Custom objects, packaged logic, an app other firms will use. Hire.
- You already carry significant Apex. Someone has to own it, test it and survive the seasonal releases.
- Salesforce is your system of record for a regulated process and the configuration decisions need a permanent owner inside the firm.
- You are mid-implementation of Litify, Practifi or FSC. These products assume a named administrator. Without one, the build stalls and the reports drift.
Which fits your situation?
Hire a developer
This is developer work. No automation platform substitutes for it.
The honest summary
Where Caddi fits
Caddi is built for the repeating half. You screen-record the task the way you already do it, and Caddi writes it as deterministic code that runs over APIs across your stack: Salesforce plus the DMS, the custodian feed, the billing system and the shared inbox. It handles the document-shaped inputs that break connectors, it logs what it did for audit, and it is maintained for you, so a backlog of small data jobs stops competing with the work you actually hired someone to do.
Related reading: CRM migration, Salesforce for law firms, Salesforce for financial advisors, and CRM data entry automation.
Salesforce, without the headcount
See the recurring work run itself
Caddi builds automations from a screen recording and runs them across Salesforce and the rest of your stack.
Frequently asked questions
How much does it cost to hire a Salesforce developer?
A full-time Salesforce developer in the US averages about $129,000 a year (ZipRecruiter, July 2026). On contract, onshore developers bill roughly $90 to $125 an hour, nearshore $45 to $70, and offshore $45 to $65 (FoundHQ). A retained managed-admin arrangement is typically $2,500 to $9,000 a month depending on hours.
Do I need a developer or an admin?
Most of what RIAs and law firms want is admin work, not developer work: fields, page layouts, validation rules, reports, Flow automations, and imports. You need a developer when you need Apex, Lightning Web Components, or an integration no packaged connector covers. Hiring a developer for admin work is the most common way firms overpay.
Can I run Salesforce without a dedicated admin?
Small orgs can. Salesforce-native vertical products change that: Litify, Practifi, Salentica and Financial Services Cloud all assume a named administrator, and Litify implementations typically run three to six months with outside help. If nobody owns the org, configuration drifts and reports quietly stop being trustworthy.
What is the alternative to hiring a Salesforce developer?
Seven realistic options: promote an internal admin, engage a certified partner for a scoped project, retain a managed-services provider, use a nearshore or offshore contractor, stay inside Salesforce's own declarative tools, buy an iPaaS or ETL tool, or run agents that do the recurring data work. The right answer depends on whether your need is a one-time build or a task that repeats every week.
Is offshore Salesforce development worth it?
For well-specified, one-time builds it often is, at roughly half the onshore rate. It works less well for recurring back-office work in regulated firms, where the cost is in context and review rather than in code, and where every handoff adds latency to work that has to happen the same day.