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

Hiring a Salesforce Developer? Start With What the Ticket Is For

A good Salesforce developer asks why before writing any Apex. Often the honest answer is a Flow, a feature Salesforce already has, or a connection to another system, and the trigger on the ticket was never needed. We take the outcome as the job, not the spec.

Flow or Apex: the first call on any Salesforce change

Salesforce lets you build a lot with clicks. Knowing where clicks run out is most of what an experienced developer brings.

Clicks

When Flow will do

  • Flow handles updating related records, sending alerts, routing approvals and scheduled reminders.
  • Guided screens that walk a rep through a process step by step.
  • An admin can read and maintain it later without a developer.
  • Salesforce has ended support for Workflow Rules and Process Builder, so Flow is where that kind of logic lives now.
Code

When it needs Apex or Lightning Web Components

  • Apex for processing large batches of records that would run into platform limits in a Flow.
  • Calling outside systems with proper error handling and retries.
  • Custom screens and components the standard page layouts cannot do.
  • Logic complex enough that it needs real automated tests around it.

Building a Salesforce career? This split is roughly the line between admin and developer job listings, and the strongest developers are fluent on both sides. Hiring? Be wary of anyone who answers every request with code.

Three common Salesforce tickets, and what they're usually asking for

A developer paid to build the ticket as written will build it. The question is whether reps actually stop working around the problem afterwards.

01

"Add an invoice status field to the Account page"

What reps want is to stop leaving Salesforce to check accounting before they call a customer. A field someone types into by hand goes stale within days. A sync from the accounting system through the Salesforce API keeps it true.

A field somebody has to keep updating.Payment status pulled in from accounting.
02

"Write a trigger to block duplicate leads"

Salesforce has its own duplicate and matching rules, and they handle plenty of cases without code. Custom code earns its place only where those rules can't express how your team defines a duplicate.

Custom code rebuilding a standard feature.Built-in rules first, code for what they miss.
03

"Build us a pipeline-by-region dashboard"

The dashboard itself takes clicks. The real issue is usually that region is typed in five different ways, so any chart of it is wrong. Validation rules and a cleaned-up picklist fix the data, then the report is easy.

A chart built on inconsistent data.Consistent data, then the chart.

What goes wrong in Salesforce code nobody looks after

Salesforce ships three major releases a year and your data keeps growing. Code that was fine at launch doesn't stay fine by itself.

Limits start biting as data grows

How you'll know: Users hit errors like "Too many SOQL queries: 101" or "Apex CPU time limit exceeded" on saves that worked last year.

Fix: Rewrite the code to handle records in bulk, querying and updating them together instead of one at a time inside a loop.

A tiny change is blocked from production

How you'll know: A one-line fix fails to deploy because overall Apex test coverage has slipped below 75%.

Fix: Write tests that check real outcomes, not filler written only to lift the percentage.

Record IDs typed straight into the code

How you'll know: It works in the sandbox and fails in production, or breaks after a sandbox refresh.

Fix: Look records up by name or keep the values in custom metadata, so each environment supplies its own.

Unsupported automations still firing

How you'll know: Setup still lists active Process Builder processes or Workflow Rules.

Fix: Salesforce's Migrate to Flow tool handles the simple ones. Rebuild the complicated ones by hand and test them in a sandbox before switching the old version off.

Triggers and Flows on the same object fight each other

How you'll know: A field changes twice on save, or ends up with a value nobody chose.

Fix: Keep one trigger per object and write down the order that automation runs in.

Weighing a freelance Salesforce developer against an agency on price and risk is its own question. Our freelance Salesforce developer comparison covers it head on, and our Salesforce consultant page covers bigger setup and process work.

Let's talk

Send the Salesforce ticket, and the reason behind it

Paste in the request as written and add one line on what's slowing your team down. n-frames builds what the request really needs, a Flow, Apex code or a connection to another system, and quotes it free with no obligation.

Triage my Salesforce ticket →

Questions people ask

What's the difference between hiring "a developer" and hiring an outcome-focused partner?

A developer, freelance or not, usually builds the Salesforce ticket exactly as written, whether or not it fixes the problem behind it. An outcome-focused partner is accountable for the problem itself, which sometimes means telling you the ticket should change before anyone builds it.

What if I just need a small Salesforce fix, not a big project?

Describe it and we'll size it honestly. One validation rule or a field change doesn't need a long engagement, and we won't pad the quote. It only grows when the small fix turns out to be the first sign of a workflow problem underneath.

Do you only do custom Apex development, or also configuration and automation?

Both. n-frames writes Apex and Lightning Web Components when the job needs code, but much of what slows a sales team is fixed with Flow automation, cleaner data, API integrations to other systems, or a better dashboard.

I'm specifically comparing a freelancer against an agency, not just looking for a developer. Where's that?

That's a separate question about cost and risk, and it has its own page: freelance Salesforce developer vs. agency.

What does a Salesforce developer actually do?

Writes and maintains the custom parts of a Salesforce org: Apex classes and triggers, Lightning Web Components, integrations with other systems, and the tests Salesforce requires before code reaches production. Good ones also know when Flow or a standard setting does the job without code.

How do people become Salesforce developers?

Most start on Trailhead, Salesforce's free learning site, with a free developer org to practice in. Learning the admin side first helps, because so much of the job is knowing what the platform already does. Then come Apex, SOQL and Lightning Web Components, and Salesforce's developer certifications.

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.