Hiring a Salesforce developer: freelancer, agency or in-house?

If you need a Salesforce developer, the right choice depends on how much work you have and how long it lasts. A freelancer suits a clear, one-off task; a small consultancy suits ongoing work that needs several skills; an in-house developer makes sense once you have a steady backlog for a full year or more. Below is how we would decide if we were on your side of the table.

Do you need a developer or an admin?

Many companies search for a developer when they actually need a good admin. A lot of what used to need code can now be done with configuration and Flow: record-triggered automation, screen flows for guided data entry, approval processes, validation rules and most reports.

You need a developer when the work involves:

• Apex code for complex logic, large data volumes or callouts to other systems
• Lightning Web Components for custom screens that standard layouts cannot handle
• Integrations through the REST or Bulk APIs, platform events or middleware
• Fixing or replacing existing custom code that is slow, untested or hitting governor limits
• Building actions for Agentforce agents that call Apex or external services

If your list is mostly fields, layouts, reports and simple automation, start with an admin or a consultant who does both. It is usually cheaper and the result is easier to maintain.

When is a freelancer the right choice?

A freelance Salesforce developer is a good fit when the task is well defined and has a clear end. Examples: a Lightning Web Component for one page, an integration with a single system, or a fix for a failing trigger.

What works well:

• Fast start, often within days
• You pay for the task, not for a team
• Direct contact with the person writing the code

What to watch:

• One person means one point of failure. If they get busy or disappear, the knowledge goes with them.
• Code review and testing depend entirely on their habits.
• Freelancers rarely cover admin, data, integration and training all at once.

To reduce the risk, ask for the work in your sandbox, insist on test classes and short documentation, and make sure every credential and connected app is in your name, not theirs.

When is an agency or consultancy better?

A small consultancy is usually the best value when the work is ongoing or mixed: some admin changes this month, an integration next month, a data clean-up after that. You get several skills without paying for several full-time salaries.

What works well:

• More than one person knows your org, so holidays and sick days do not stop work
• Built-in review: someone checks the code before it reaches production
• Admin, development, integration and reporting from one team
• Easier to scale up for a project and down afterwards

What to watch:

• Large agencies can sell with a senior architect and deliver with a junior team. Ask who will actually build.
• Fixed-price projects need a clear scope. Vague requirements turn into change requests.
• Make sure you are not locked in. You should own the code, the documentation and every integration account.

Our post on how to choose a Salesforce consultant has ten questions that help here.

When should you hire in-house?

An in-house Salesforce developer makes sense when Salesforce is central to how you run the business and you have a steady backlog of development work for the foreseeable future. Typical signs: several clouds in use, many integrations, frequent releases and a team that depends on new features every few weeks.

What works well:

• Deep knowledge of your business and your data
• Available every day, with no hand-overs
• Can own your release process and long-term architecture

What to watch:

• Hiring takes time, and good Salesforce developers are in demand.
• One person cannot be an expert in everything. You may still need outside help for Marketing Cloud, CPQ or a complex integration.
• Someone has to review their work. A single developer with no peer review can build up technical debt quietly.

Many companies end up with a mix: one in-house admin or developer who owns the org day to day, and a consultancy for larger projects and specialist work.

How do the three options compare?

	Freelancer	Consultancy	In-house
Best for	One clear task	Ongoing or mixed work	A steady, long backlog
Start time	Days	Days to a couple of weeks	Usually months
Skills covered	One person's	Admin, dev, integration, reporting	One person's, growing over time
Continuity risk	High	Low	Medium
Code review	Depends on the person	Usually built in	Needs a process

What skills should a Salesforce developer have in 2026?

Look for current skills, not only years of experience:

• Apex and testing: bulk-safe triggers, a trigger framework, meaningful test classes rather than tests written only to reach coverage.
• Lightning Web Components: not Aura or Visualforce for new work, unless there is a good reason.
• Flow: knowing when Flow is the better tool and when code is. Workflow Rules and Process Builder are retired, so anyone still building with them is out of date.
• Integration: REST and Bulk APIs, named credentials, platform events and handling errors and retries properly.
• Deployment: sandboxes, source control and the Salesforce CLI or a DevOps tool, not changes made directly in production.
• Agentforce: for teams starting with AI agents, experience writing Apex and Flow actions that agents can call safely.

How do you test a Salesforce developer before hiring?

A short paid trial tells you more than an interview. Some ways to do it:

1. Review existing code. Give them a trigger or class from your org (with no sensitive data) and ask what they would change and why.
2. A small real task. Something that takes a few hours, built in a sandbox, with a test class and a short note on how it works.
3. Ask about a failure. "Tell me about an integration that broke in production and what you changed afterwards." Good developers have a specific answer.
4. Check how they explain things. You will work with them for months. If they cannot explain a design choice to a non-developer, that will cost you later.

Whichever route you choose, keep ownership with you: your sandbox, your source control repository, your integration accounts and your documentation.

Summary

Hire a freelancer for a clear, one-off task. Choose a consultancy for ongoing or mixed work where you need several skills and someone reviewing the code. Hire in-house when Salesforce development is a full-time, long-term need, and keep outside help for specialist work. In every case, test with a small real task first and keep ownership of everything that is built.

If you want to see how we work, read about our Salesforce consulting services and Salesforce development work, or book a free call to talk through your project.