1. Home
  2. Services
  3. Salesforce development

Salesforce development in Apex and Lightning Web Components, built to Salesforce's limits

We write the Salesforce code that clicks cannot: Apex for rules and background jobs, and Lightning Web Components for screens. Every line has to fit inside limits Salesforce sets per transaction, and pass tests that cover at least 75% of the code before it can reach production. This page sets out those rules, as we read Salesforce's own guides on 18 November 2026.

Checked 19 November 2026

What a Salesforce developer does, and when you need one

A Salesforce developer writes the code that Salesforce’s setup screens cannot express. You need one when a rule or a screen goes past what setup screens and flows can do.

Trailhead, Salesforce’s learning site, describes the job through its certificate. A Certified Platform Developer can develop and deploy custom business logic and custom interfaces with the platform’s programmatic tools, and can extend the platform with Apex and Visualforce. Salesforce’s Apex guide says something similar: for complex business processes, you build custom features and screens with tools such as Apex.

Four signs that a job needs code rather than clicks:

  • The rule reads a set of records at once. A discount that depends on a customer’s whole order history, say.
  • Another system must answer first. A stock check in your ERP before a quote saves.
  • The screen does something the standard page cannot. A quote builder that groups lines by drawing number, for example.
  • The job runs on a schedule. A nightly clean-up of stale leads, which Salesforce’s Apex Scheduler can run with Batch Apex.

Some jobs need no code at all. Trailhead lists a separate certificate, Platform App Builder, for people who make custom apps with Salesforce’s declarative tools, meaning clicks rather than code. Ask whether clicks will do before paying for code.

Five kinds of Salesforce code

This page covers five kinds of Salesforce code. Each one runs inside your org and follows the same limits.

Scroll the table sideways to see every column.

Kind of code Salesforce tool What it does
Rules on save Apex triggers Custom actions before or after a record is inserted, updated or deleted
Links to other systems Apex callouts and Apex REST Call out to another system, or give it an endpoint to call
Screens Lightning Web Components Custom parts of a page, built with HTML and JavaScript
Big jobs in the background Batch Apex Mass updates of records, Salesforce’s preferred way to stay inside the limits
Agent actions Apex, flows or APIs in Agentforce Builder Give an AI agent a step it can take

Salesforce says Apex can start from web service requests and from triggers on objects. It also says custom public API calls can be built from stored Apex methods. That is how an outside system gets an endpoint of your own design.

For agents, Salesforce says Agentforce Builder connects agents to flows, Apex, MuleSoft APIs and prompt templates. Agent Script is its new language for building agents there. Salesforce says it lets builders set conditions and loops, plus transitions between steps. Our Salesforce AI agents page covers that work in depth.

Apex runs inside limits your code must respect

Salesforce says Apex runs in a multitenant environment, which means companies share the same servers. So Apex is bound by governor limits, caps on what one transaction may do. Salesforce says code that exceeds a limit gets a runtime exception that cannot be handled. Its guide says the runtime guards against runaway code so it cannot hog shared resources.

These are the per-transaction limits from Salesforce’s table. Synchronous code runs while a user waits; asynchronous code, such as batch Apex, runs in the background.

Scroll the table sideways to see every column.

Per transaction Synchronous Asynchronous
SOQL queries 100 200
Records read by SOQL 50,000 50,000
SOSL searches 20 20
DML statements (saves) 150 150
Records saved by DML 10,000 10,000
Callouts to other systems 100 100
Total wait for callouts 120 seconds 120 seconds
Heap (working memory) 10 MB 25 MB
CPU time 10,000 milliseconds 60,000 milliseconds

From Salesforce’s Apex Developer Guide, version 68.0, read 18 November 2026. A single Apex class can be up to 1 million characters long, not counting comments. Salesforce also allows only five active Batch Apex jobs at one time in an org.

Never query or save inside a loop. Our example: one query that reads 200 records costs 1 of the 100 queries, but a query inside a loop over 200 records would break the limit. So a trigger should handle a list of records, never one at a time. Salesforce’s guide asks for the same in its tests, which should cover bulk records as well as single ones.

API calls from outside have their own caps. Salesforce counts API limits for the whole org, not per user. It allows 25 concurrent API requests of 20 seconds or longer in a production org or sandbox. Salesforce stops a REST or SOAP call after 10 minutes, unless it is a query.

Your edition decides whether Apex is there at all

Check the edition before planning any code. Salesforce’s Apex guide lists Apex in Performance, Unlimited, Developer and Enterprise Editions, and Database.com.

Salesforce’s pricing page uses newer names. It says Core replaces Enterprise Edition, Advanced replaces Unlimited Edition, and Max replaces Agentforce 1 Edition. The developer guides we read still use the old names, so read “Enterprise” there as the edition Core replaced.

If your edition is not on that list, ask Salesforce what code your edition allows before you plan a custom build. For license prices by edition, see our Salesforce cost article. The link to another system can sometimes run outside Salesforce instead, through the API, if your edition includes API access.

SOQL is close to SQL, with gaps that matter

SOQL is how Apex reads records. Salesforce says it is like the SELECT statement in SQL, but designed for Salesforce data.

Developers who know SQL pick it up fast, then hit the gaps. Salesforce lists what SOQL cannot do: it cannot run arbitrary joins, use wildcards in field lists or use calculation expressions. Instead, it reads from one object or from objects that are related to one another, such as an Opportunity and its Account. That shapes the data model, because a query that needs two unrelated objects needs a link between them first. By default, a SOQL statement cannot pass 100,000 characters.

SOSL is the other query language. Salesforce says to use it when you do not know which object or field holds the data. One example is a search box that looks across accounts and contacts. One transaction may run 20 SOSL searches.

Lightning Web Components build the screens

Lightning Web Components, or LWC, are how custom parts of a Salesforce page get built. Salesforce says they are custom elements built with HTML and modern JavaScript. Its LWC site adds that they use standard HTML, modern JavaScript and native Web Components.

That matters for hiring and for upkeep. Salesforce’s site says you build these custom elements with HTML, JavaScript and CSS, so a web developer can read the code without learning a private language first. When a component calls Apex, the same governor limits apply behind the screen.

How code reaches production: tests first

Salesforce will not take Apex into production without tests. Before you deploy Apex or package it, Salesforce says unit tests must cover at least 75% of your Apex code, and all of them must pass. Every trigger must have some test coverage. When Apex is deployed to production, every unit test in your org’s namespace runs by default.

Salesforce’s own advice is not to chase the number. Its guide says to cover every use case, including the cases that should fail and bulk saves. Coverage of 75% or more then follows. Unit test methods commit no data to the database and send no emails, so a test run leaves your records and inboxes alone.

There is one more reason to write good tests. Salesforce says it runs all unit tests before any platform upgrade, to check that custom Apex still works. Weak tests leave you blind on upgrade day.

Deploys themselves have size caps. Salesforce says one deploy or retrieve can hold up to 10,000 files, in a .zip file of at most 39 MB. Inbound and outbound change sets can hold up to 10,000 files of metadata.

Scratch orgs, packages and Salesforce CLI

Salesforce DX is Salesforce’s toolset for managing and building apps across their whole life. Its guide says that with DX, your version control system is the source of truth, not the org. So the code and settings live in Git, not only in the org.

Scratch orgs

A scratch org is a temporary Salesforce org for building and testing, deleted once it expires. Salesforce says scratch orgs last at most 30 days. You pick from 1 to 30 days when you create one, and the default is 7. Once a scratch org expires, it cannot be restored. Each one has 500 MB of data storage.

Scratch orgs come from a Dev Hub, which Salesforce says is often your production org. Salesforce says you cannot enable Dev Hub in a sandbox, and once enabled it cannot be turned off.

Scroll the table sideways to see every column.

Dev Hub edition Active scratch orgs New scratch orgs per day
Developer Edition or trial 3 6
Enterprise Edition 40 80
Unlimited Edition 100 200
Performance Edition 100 200

Packages for internal apps

Salesforce says “unlocked packages” are especially suited for internal business apps. Each package version is an immutable artifact that never changes, so a version tested in a sandbox is the same version that reaches production. Salesforce also warns that admins can change packaged metadata directly in production for an emergency. So Salesforce advises that admins tell the development team whenever they edit packaged metadata in production.

Salesforce CLI and tools

Salesforce CLI is a command-line tool that simplifies development and build automation with your org. Salesforce built it on oclif, an open-source framework in Node.js, and publishes weekly release notes for it. It announced sf (v2), the unified CLI, as generally available in July 2023. Salesforce says any code editor works, and recommends Visual Studio Code. For teams that prefer a screen, Salesforce sells Agentforce DevOps Center, which it says lets teams build and test apps and agents, then deploy them.

Dated changes your code must keep up with

Salesforce changes on a fixed beat. Its major release transition happens three times a year. During each release, you can test early in scratch orgs and sandboxes, before your production org is upgraded, so your tests can run there first.

API versions also retire on a schedule:

  • Version support. Each API version gets at least 3 years of support from its first release, Salesforce says. It gives at least 1 year’s notice before support ends.
  • Current version. The REST API guide for the Winter ’27 release covers version 68.0.
  • Old versions. From Summer ’27, versions 31.0 to 40.0 lose support, and from Summer ’28 they are retired. Calls to a retired version come back with a 410:GONE error.
  • SOAP login(). Salesforce plans to retire this sign-in call with the Summer ’27 release. It remains only in API version 64.0 and earlier.
  • Connected apps. Creating new ones is restricted as of Spring ’26. Salesforce recommends external client apps, and outside software must use one of the two with an OAuth 2.0 flow to reach the REST API.

Salesforce saves each Apex class against an API version, and integrations call a version too. So check which versions an org’s classes and links use, and plan moves ahead of each retirement date.

What AI coding tools change for Salesforce developers

Salesforce now sells an AI coding tool, Agentforce Vibes. It says you describe what you need, and Agentforce writes the code, tests it and deploys it. It suggests code inline in the Agentforce Vibes IDE and in VS Code. It works with Salesforce Code Analyzer to find bugs and security holes early. It reaches MCP tools through the Salesforce DX MCP Server.

Salesforce describes the Model Context Protocol (MCP) as an open standard first developed by Anthropic. Salesforce’s DX MCP Server is open source and lets large language models work with Salesforce orgs. An org must be authorized on the developer’s own computer first.

The rules do not change for AI-written code. It still needs tests covering 75% of the Apex. In synchronous code, it still has to fit 100 SOQL queries and 150 DML statements per transaction. Someone still has to decide what the code should do and own the deploy.

Hiring a developer, a freelancer or a team

You can hire a freelance Salesforce developer, make a dedicated hire or bring in a team. The choice comes down to how much of the work you need covered. A single developer writes code. A Salesforce project also needs setup, data, tests, deploys and training.

Trailhead’s certificates show the split of skills:

Scroll the table sideways to see every column.

Trailhead certificate What Trailhead says it covers
Platform App Builder Custom apps built with Salesforce’s declarative tools, meaning clicks
Platform Developer Custom business logic and screens built with code, including Apex
Platform Developer II Advanced coding skills and data modeling for complex logic
Agentforce Specialist Managing and tuning Agentforce

Whoever you hire, ask four questions. Where will you build and test? How do you keep code bulk-safe under the 100-query limit for synchronous code? What does your test plan cover beyond the 75%? How do changes reach production?

Our team’s Salesforce work

Our team has built Salesforce agents both ways: inside Agentforce, and as custom agents that work through Salesforce’s API.

Those agents cover six jobs: lead qualification, follow-up cadence, quote creation and sending, data analytics and reporting, lead enrichment, and quote to cash.

Our team also takes Salesforce implementation end to end, from setting up the org to moving the data in and training the team. See Salesforce implementation for those steps.

Data work on Salesforce is part of our record too, including moving a company’s records into a new org.

For builds outside Salesforce, see custom software development. Four of our builds, each with its system and job, are on the case studies page.

The first call is free.

Questions

What is the job of a Salesforce developer?

A Salesforce developer writes the code that the setup screens cannot express. Trailhead describes a Certified Platform Developer as someone who builds and deploys custom business logic and custom screens with the platform's code tools. In practice that means Apex for rules and links to other systems, and Lightning Web Components for screens. The developer also writes the tests Salesforce demands before any of it reaches production.

Is Salesforce a CRM system?

Yes. Salesforce says CRM stands for customer relationship management, and it sells Salesforce as a CRM. Its records include accounts, opportunities (deals) and cases (customer issues). Developers build on the same platform. Apex code and Lightning Web Components run inside your org, next to those records. If you run an ERP, Salesforce reaches its orders and invoices through its APIs.

Does Salesforce involve coding?

Only when you need it. Much of Salesforce is set up with clicks. Fields and flows need no code at all. Code starts where clicks stop. Apex is Salesforce's own language, with syntax that looks like Java. Lightning Web Components use standard HTML and modern JavaScript. Salesforce's guide also says Apex is not a general purpose language, so other jobs run outside Salesforce.

Is Salesforce hard to learn?

The basics are free to learn. Trailhead, Salesforce's learning site, offers free guided learning, with a self-paced path for the Platform Developer certificate. Apex feels familiar to anyone who knows Java, because Salesforce based it on Java idioms. The hard part is the limits. Code that runs while a user waits gets 100 SOQL queries and 150 DML statements per transaction, so it has to handle records in bulk from day one.

Will AI replace Salesforce developers?

Not on the facts we read. Salesforce sells Agentforce Vibes, which it says writes and tests code from a plain request, then deploys it. Salesforce's own rules still apply to that code. Tests must cover at least 75% of the Apex, and every transaction must fit the governor limits. Someone still decides what the code should do, reviews it and owns the deploy. Salesforce pitches it to developers of any skill level as a way to build faster.

Do you need access to our production org?

Not to build. Code is written and tested in scratch orgs, which are temporary orgs for development, and in sandboxes kept apart from production. It reaches production only through a deploy that runs your tests. If a test needs real records, a sample is enough. We sign your NDA before you share any data, if you ask.

What does Salesforce development cost?

Each build gets its own quote, and we publish no rates. The quote follows the work: how many objects and screens, how many systems the code calls, how many rules, and how much test data the 75% coverage rule needs. Salesforce's licenses come on top, and Apex needs an edition that includes it. For Salesforce's own published prices, see the Salesforce cost article on this site.

Sources

Every source behind a figure or a vendor fact on this page, with the day we read it.

Describe the Salesforce build you need

The first call is free. Bring the rule or screen you want and your Salesforce edition. We talk through how it fits Salesforce's limits.

Describe your Salesforce build