What we do
Tools
Industries
Department
How we workLet's talk →
Home/Salesforce/Freelance Salesforce Developer
Freelance Salesforce Developer

Vetting a Freelance Salesforce Developer Before They Get Admin Access

You've got three freelance Salesforce developers shortlisted, all with good reviews, and one wants System Administrator access to production on day one. Here's which Salesforce jobs suit a freelance engagement, and what to ask before anyone gets a login.

Match the Salesforce job to the hire

The job decides what kind of freelance Salesforce developer you need, and what you check them on.

The Salesforce job Who usually takes it What to check hardest
A few Flows, validation rules, page layouts or reports An admin-level freelancer, often a matter of hours That they build in a sandbox and hand you a list of what changed, so the next person can find it.
An Apex trigger or a batch class A freelance developer with the Platform Developer certification and Apex work they can show Tests that assert results, not just enough lines run to pass the 75% rule. And that the code handles bulk loads.
A custom screen in Lightning Web Components A freelancer with LWC components in production somewhere How the component behaves for users with less access than an admin, and on the mobile app if your reps use it.
An integration with your ERP, billing or support desk that runs every day A freelancer or a firm, as long as someone owns it after launch Where failed records go, who hears about them, and which user the integration runs as. These decide whether it stays working.
Ongoing admin and small changes every month A retained freelancer or an in-house admin A written handover: which automations exist, what each one does, and where the code lives.

Before the first login: six questions for a freelance Salesforce developer

Good freelancers answer these without a pause. They're also fair to ask any firm, including us.

  • "Which Salesforce certifications do you hold? Can I see your Trailhead profile?"

    Certifications show on a person's Trailhead profile. For Apex work, Platform Developer (formerly Platform Developer I) is the usual baseline. It proves they passed an exam, not that they write careful code, so use it as a floor.

  • "Where will you build this, and how does it get to production?"

    The answer should be a sandbox, then a change set, Salesforce CLI or DevOps Center. Edits made straight in production are how orgs end up with automations nobody can trace.

  • "What will your Apex tests cover, and what do they check?"

    Salesforce won't deploy Apex to production unless tests cover at least 75% of your org's code, and every trigger has some coverage. Tests that run lines without asserting outcomes pass that bar and catch nothing.

  • "What happens when 10,000 records get imported at once?"

    Triggers receive records in chunks of up to 200. Code that runs a query for each record hits the limit of 100 queries per transaction and fails the import. A careful developer brings this up before you do.

  • "Which user will the integration run as?"

    If it's their own login, it stops when their access is removed. An integration should run as a dedicated integration user with a permission set that grants only what it needs.

  • "What do we have when the job is done?"

    The code in your org and in a repository you own, a note of every Flow and field they touched, and the credentials for anything external in your name, not theirs.

Hiring a company instead of a freelancer

n-frames is a company, not a freelancer. We build Salesforce integrations, Apex and automation for businesses, including where Salesforce has to share data with another system: an ERP, a billing tool, a support desk. The code and its documentation go into your org and a repository you own, so the work stays readable whoever touches it next.

Whichever way you go, the checklist above is the part that protects your org. A freelancer who answers it well is a sound hire. If you want a second number on the same job to compare against, that's a normal thing to ask for.

Questions people ask

Is an agency more expensive than a freelance Salesforce developer?

Per hour, often yes. Per job, it depends on how the work is scoped and what's included: tests that hold up, a sandbox-first deploy and documentation. Compare quotes for the same written scope rather than comparing day rates, and the gap is usually smaller than it looks.

Is a freelancer the better call for a genuinely small Salesforce fix?

Usually, yes. A validation rule, a report or a page layout is a few hours' work, and a certified freelancer who builds it in a sandbox and tells you what changed is a sensible hire. Ask the same questions from the checklist anyway. Small changes made straight in production add up.

Does a freelancer or an agency make more sense for custom Apex work specifically?

Either can write good Apex. What to look at is whether the code is bulk-safe, whether the tests assert real outcomes, and who will change it when your process changes next year. For Apex that sits inside an integration, n-frames builds the trigger, the error handling and the logging together, because they fail together.

What does a freelance Salesforce developer need access to?

A sandbox first, with a user whose profile or permission sets match the work. Production access only for the deploy, ideally through a change set or the CLI rather than a standing admin login. Remove or downgrade their user when the job ends.

Is the Salesforce quote really free, with no obligation?

Yes. n-frames reads the scope and sends back what it involves and what it costs. What happens next is your call: build it with us, hand it to a freelancer, or neither.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.