Salesforce Development Company: Apex, Lightning, Flow and Integrations Built Around the Platform’s Limits

Updated September 2026 · Written and maintained by the Progression Agency strategy team

A Salesforce development company designs, builds and maintains custom functionality on the Salesforce Platform: Apex code, Lightning Web Components, Flow automation, integrations with your other systems, Experience Cloud portals, data migrations and products sold to other Salesforce customers. Progression Agency does this work for operations, sales and service leaders and the CTOs who answer for their systems, and hands over tested, documented metadata in version control that your own admins can maintain. Progression Agency is based in New York City and works with clients across the United States and worldwide.

What does a Salesforce development company do?

It turns the parts of your process that standard Salesforce cannot express into supported software on the platform, delivered with tests and a release process rather than as one-off changes in production. That covers data model, automation, Apex logic, custom screens, integrations, portals, migrations and packaged apps.

The line between configuration and development matters when you buy. An administrator can add fields, page layouts, validation rules and many Flows. A developer is needed when logic must run in bulk against thousands of records, when an integration has to survive errors and retries, when a screen needs behavior no standard component offers, or when code will be installed in other companies’ orgs. Salesforce app development services cover that second list, and a good provider will tell you when the first list is all you need.

What is Salesforce platform development?

Salesforce platform development is building applications on the Salesforce Platform itself, using its data model, security model and interface instead of a separate stack. Apex is the server-side language, and because it runs in a multitenant environment Salesforce enforces strict limits on it (Apex Developer Guide). Lightning Web Components are custom HTML elements built with HTML and JavaScript (LWC Developer Guide), and Flow is the low-code automation layer. Most real projects combine all three with the platform’s APIs.

What is a custom app in Salesforce?

In Salesforce’s own terms, a Lightning app is a branded bundle of objects, tabs, pages and utilities that users open from the App Launcher; Salesforce’s help documentation says Lightning apps contain everything you expect from a custom app, such as custom and standard objects and custom tabs (Salesforce Help: Lightning Apps). Buyers looking for custom app development Salesforce work usually mean more than an App Launcher tile: a new data model, Apex logic, components and integrations that behave like a purpose-built application living inside the org.

Flow, Apex or Lightning Web Components: choosing the right tool

Use Flow when an administrator should be able to read and change the logic, Apex when the work is heavy, transactional or bound to another system, and Lightning Web Components when the screen itself needs custom behavior. Most builds use all three; the skill is in drawing the boundaries.

Flow first, while it stays readable

Salesforce has put its automation investment into Flow Builder. It stopped supporting Workflow Rules and Process Builder on December 31, 2025; existing rules keep running, but they no longer get customer support or bug fixes (Salesforce Help). We migrate old rules with Salesforce’s Migrate to Flow tool where it produces clean results and rebuild them by hand where it does not, consolidating overlapping automations so a single record save does not fire several processes in an order nobody chose.

Apex for bulk, transactional and integration logic

Apex earns its place when logic has to run across many records at once, call an external system, or enforce a rule that must hold even when data arrives through the API rather than the screen. It also brings obligations: unit tests, code review and constant attention to the limits described in the next section.

Lightning Web Components for the screens people use

Salesforce’s guidance is to choose Lightning Web Components over the older Aura model whenever you have the choice, and because the framework is built on web standards, most of the code is standard JavaScript and HTML (Salesforce). We build components for guided data entry, dense editable tables, embedded calculators and anything a standard page layout cannot do, reusing Salesforce’s base components so custom screens still look and behave like the rest of the org.

Governor limits: the constraint every Salesforce build is designed around

Salesforce enforces hard per-transaction limits because Apex shares multitenant infrastructure, and code that exceeds one throws a runtime exception that cannot be handled. Designing inside them is most of what separates code that works in a demo from code that survives a data load.

Figures are quoted from Salesforce’s Execution Governors and Limits page. Limits apply to each Apex transaction, and for Batch Apex they reset with each batch of records.

Bulkify by default

Every trigger and service class we write handles collections rather than single records: queries and DML run once per batch, never inside a loop. A 10,000-row import should consume the same handful of queries as one record saved on screen, which is the difference between a clean load and a failed one.

Move heavy work to asynchronous Apex

When a job needs more CPU time or heap than a synchronous transaction allows, it moves to Batch Apex or queueable jobs, where the higher asynchronous limits apply. Scheduled Apex is the exception worth knowing: Salesforce applies synchronous limits to scheduled jobs even though the feature is asynchronous (Salesforce).

User mode became the default at API version 67.0

Salesforce’s Summer ’26 release shipped API version 67.0 and changed how Apex saved at that version behaves: SOQL, SOSL and DML now default to user mode, enforcing the running user’s object permissions, field-level security and sharing; a class compiled at 67.0 with no sharing keyword now defaults to with sharing; and WITH SECURITY_ENFORCED no longer compiles, replaced by WITH USER_MODE. Triggers are the exception and always run in system mode (Salesforce Developers Blog). We review older classes before raising their API version, because code that quietly relied on system mode can start returning fewer rows or throwing access errors.

Salesforce integrations: REST, Bulk API 2.0, events and middleware

Choose the integration pattern by volume and timing: record-level REST calls for interactive sync, Bulk API 2.0 for large asynchronous loads, event streams for near-real-time change, and middleware when many systems share the same rules. Most real integrations combine two or three of them.

Salesforce’s Bulk API documentation draws the line at 2,000 records: above it a job is a good candidate for Bulk API 2.0, and below it bulkified synchronous REST or SOAP calls are the recommendation (Bulk API 2.0 Developer Guide). Change Data Capture publishes create, update, delete and undelete events so an external system stays current without periodic exports or repeated API calls (Change Data Capture Developer Guide).

MuleSoft or a lighter middleware layer?

MuleSoft’s Anypoint Platform covers the whole API lifecycle, from designing specifications through building, deploying behind policies and monitoring (MuleSoft documentation). It suits organizations running many integrations under shared governance. For two or three connections, a well-built Apex integration or a lighter iPaaS is often easier to own, and our custom API and integration team builds either.

Integration users, logging and retries

Each integration gets its own integration user with the narrowest permissions it needs, a log of every failed record with the reason, and a retry path that cannot create duplicates. When the other system is down, records wait in a queue instead of disappearing.

Experience Cloud portals for customers, partners and members

Experience Cloud is how Salesforce puts your data in front of people outside the company. Salesforce describes it as a way to create branded digital experiences for employees, customers and partners, whether that is a portal, a help center or a mobile app (Salesforce Help: Experience Cloud).

The development work is mostly about three things: the data model and sharing rules that decide what each external user can see, the licenses that decide what they can do, and the interface. Newer sites run on the Lightning Web Runtime (LWR) with Lightning Web Components, and Salesforce publishes separate guidance for moving an older Aura site to LWR, which is best treated as a project in its own right.

Sharing first, pages second

We design external sharing before building pages. A dealer portal that shows one dealer another dealer’s orders is a data breach, not a cosmetic bug, so the sharing model is tested with a test user for every role before launch.

Portals that do real work

Order status, case submission with attachments, warranty registration, quote requests and document libraries are the common builds. Each is a Lightning Web Component or Flow backed by Apex where the logic requires it, and performance-tested in a Full sandbox when traffic justifies it, since Full sandboxes are the only type that supports load testing.

Data migration into Salesforce without losing history

A migration is a mapping exercise first and a loading exercise second: decide which records, fields and relationships survive, clean them, then load them in dependency order and reconcile the counts. The load itself is the short part.

1. Inventory each source system and agree what stays behind: dead records, duplicate contacts, fields nobody uses.
2. Map every field to a Salesforce object and field, including picklist values, record types and record owners.
3. Deduplicate and standardize before loading, not after.
4. Load parents before children (accounts, then contacts, then opportunities and activities), keeping external IDs so any load can be rerun safely.
5. Reconcile record counts and spot-check totals with the business owner of each object.
6. Freeze the old system, run the final delta load and switch users over.

For volume, Salesforce’s Data Loader handles files of up to 150 million records when it runs on Bulk API 2.0 (Data Loader Guide). Scripted loads through the Bulk API are the better choice when a migration will be rehearsed several times before cutover. Choosing what to keep, and cleaning it up with the people who use it, is part of our CRM consulting and implementation work.

Salesforce app development for the AppExchange

Building a product for other Salesforce customers changes the job: the code ships as a managed package, must pass Salesforce’s security review before it can be listed, and has to behave in orgs you will never see. The marketplace is still widely called AppExchange; Salesforce’s partner documentation now calls it AgentExchange.

Salesforce’s partner guide states that managed packages and API solutions distributed on its marketplace must pass the security review, and adds that passing it is not a guarantee of a partner application’s quality or security (ISVforce Guide). Certified packages gain a practical benefit at runtime: managed packages that have passed the review get their own allocation of most per-transaction limits, separate from the installing org’s own code (Apex Developer Guide).

Preparing for the security review

We scan with Salesforce Code Analyzer, which brings several code scanners together behind the Salesforce CLI, VS Code and CI/CD and includes rules written specifically for the security review (Code Analyzer), fix what it finds, and document how the package authenticates, stores data and calls external services.

Designing for orgs you cannot see

A packaged app has to cope with orgs that have different record types, validation rules, sharing models and data volumes. We build with namespaced components, optional features that switch off cleanly when a dependency is missing, and install scripts that fail with a clear message, then test in several scratch orgs shaped like real customers.

The Salesforce software development life cycle we run

The Salesforce software development life cycle we follow keeps version control, not the production org, as the source of truth, moves every change through sandboxes with automated tests, and plans regression testing around Salesforce’s three releases a year. It is what makes an org maintainable by people who did not build it.

Salesforce’s DX tooling is built on that principle: the version control system rather than the org is the source of truth, with the Salesforce CLI and scratch orgs for development and automation (Salesforce DX Developer Guide). Deployment rules are strict: to deploy Apex or package it, unit tests must cover at least 75% of the code and all of them must pass (Testing and Code Coverage). We treat 75% as a floor and write tests that assert behavior, which Salesforce’s own documentation recommends over chasing the percentage. The general phases are covered in our guide to the software development life cycle.

Sandbox definitions follow Salesforce Help: Sandbox Types and Templates.

Three releases a year, planned for

Salesforce ships three major releases a year, Spring, Summer and Winter, and upgrades sandbox instances four to six weeks before a release reaches production (Trailhead). For Summer ’26, the sandbox preview began May 8, 2026 and production upgrades ran between May 15 and June 13 depending on the instance (Salesforce Developers). We run the regression suite in a preview sandbox every cycle and fix what the release breaks before it reaches your users.

A handover your admins can live with

Every project ends with metadata in your repository, an inventory of automations by object, integration runbooks and a short admin guide. Your team should be able to change a Flow or read an Apex class without calling us.

Org health: what we check before writing new code

An org health review tells you what to fix before you build, and it often changes the plan. We look at security settings, automation sprawl, code quality, test coverage, limits and data quality, and report findings in order of business risk.

Salesforce’s Health Check scores an org’s security settings against the Salesforce Baseline Standard or a custom baseline, with up to five custom baselines allowed (Salesforce Help: Health Check); Code Analyzer covers the code. For architecture, Salesforce’s Well-Architected framework groups its guidance into five pillars: trust, reliability, operational excellence, resource and cost optimization, and fairness (Salesforce Architects).

• The Health Check score, and every high-risk setting that fails the baseline.
• Active Workflow Rules and Process Builder processes still waiting for migration to Flow.
• Objects with more than one record-triggered automation and no defined order.
• Apex classes that run close to governor limits in production logs, and tests that assert nothing.
• Classes saved far behind the current API version, and what a version bump would change.
• Integration users holding more permissions than their job needs.
• Duplicate rules, required fields users work around, and fields nobody fills in.
• Storage, API usage and license consumption against what you pay for.

Salesforce Marketing Cloud development

A Salesforce Marketing Cloud developer builds the data model, journeys, templates and integrations behind Salesforce’s marketing products and connects them to Sales and Service data. Deciding who gets which message belongs to our lifecycle marketing automation team; the build and the data work sit here.

Salesforce Marketing Cloud development usually starts with data: which contacts and events flow from Sales Cloud, the website and commerce systems, how consent is stored, and which identifiers tie them together. Templates and journeys come after the data model is right.

How much is Salesforce Marketing Cloud?

Salesforce lists Marketing Cloud Next Growth Edition at $1,500 per org per month and Advanced Edition at $3,250 per org per month, both billed annually, with add-ons such as Salesforce Personalization at $8,000 per org per month (Salesforce pricing, checked September 30, 2026). Implementation and development are separate from the license and depend on data sources, journeys and channels.

HubSpot Marketing Hub or Salesforce Marketing Cloud?

Choose by where your customer data and sales team already live and how complex your journeys are. HubSpot publishes Marketing Hub prices by edition; Enterprise starts at $3,600 a month with five core seats and 10,000 marketing contacts, plus a required one-time $7,000 onboarding fee (HubSpot pricing). Marketing Cloud tends to suit organizations already running Sales or Service Cloud with large data volumes; HubSpot suits teams that want marketing, sales and service in one simpler suite. We compare both against your process before anyone signs.

Industry builds: lead generation, lending and service

The same platform supports very different processes, and the build follows the process rather than a template. Three requests come up again and again from operations teams.

Lead generation with Salesforce

Salesforce’s Web-to-Lead captures up to 500 leads a day from website forms (Salesforce Help: Web-to-Lead). Higher volumes, enrichment, deduplication and routing call for an API-based capture path, assignment logic in Flow or Apex and source tracking that follows each lead to revenue. Our lead generation and marketing analytics teams handle the demand side of the same pipeline.

Loan management software on Salesforce

Salesforce sells Digital Origination, formerly Digital Lending, with prebuilt applications for loans such as auto, HELOC and personal loans and for deposit accounts (Salesforce). Servicing a loan book after origination (payment schedules, accruals, collections) usually lives in a core banking or servicing system, so the development work is the integration and the custom objects, screens and rules around it. Lenders building beyond the platform can start with our fintech software development team.

Service operations and case management

Case routing, entitlements, field handoffs and customer self-service share one pattern: Flow for the routing rules service managers own, Apex for anything that touches an external system, and Experience Cloud where customers help themselves.

Will AI tools make Salesforce developers unnecessary?

No. AI assistants now draft routine Apex, tests and components, and Salesforce ships its own coding agent, but someone still has to design the data model, own security and limits, review what the agent writes and answer for the release.

Salesforce’s Agentforce Vibes coordinates sub-agents for Apex, Lightning Web Components, Jest tests and SOQL, and its plan mode changes no files until a developer approves the plan (Agentforce Vibes Developer Guide). Summer ’26 added Salesforce Hosted MCP Servers, which let MCP-compatible clients such as Claude, ChatGPT and Cursor connect to an org over standard OAuth, with custom MCP servers respecting the org’s sharing and security model (Salesforce Developers Blog). Used well, these tools make a good team faster. They do not remove the need for review, because generated code can still query inside a loop or run in the wrong access mode.

How buyers ask ChatGPT, Claude and Copilot to recommend a Salesforce developer

Operations leaders and CTOs now often start a vendor search by asking an assistant, and they ask in the language of the problem, not the category. The assistants answer by retrieving pages that name specific capabilities, and by leaning on marketplace listings, list articles and question-and-answer threads.

The questions buyers type

Prompts are long and specific, which is exactly why generic service pages rarely get named:

• “Which Salesforce development companies can build an Experience Cloud portal for our distributors?”
• “Who can fix Apex CPU time limit errors in our opportunity triggers?”
• “Recommend a firm that integrates NetSuite and Salesforce with Bulk API 2.0 and error handling.”
• “Best company to migrate Workflow Rules and Process Builder to Flow before our audit.”
• “Freelancer or agency for our first managed package on AppExchange?”
• “Who can prepare our org for the API version 67 user-mode defaults?”

What the assistants cite

ChatGPT search, Perplexity, Claude, Gemini, Copilot and Google’s AI Overviews retrieve live pages, and for this market the evidence they find is uneven. The organic results in our brief for “salesforce app development company” (September 2026) mixed Salesforce’s own product pages, marketplace consultant listings, two list articles ranking development and implementation firms, and a Quora thread. Assistants draw on the same kinds of sources: listings for provider names, list articles for shortlists, Salesforce documentation for technical claims, and provider pages that answer the exact question asked.

What to publish so an assistant names you

For a Salesforce development company, specific and checkable pages beat adjectives. Publish a page per capability (portals, integrations, migrations, packaged apps) with version-specific detail; link each named developer’s certifications to Salesforce’s public certification verification tool; keep company facts identical on your marketplace listing and your site; and answer questions in the first sentence. Let the crawlers in: OpenAI says sites that opt out of OAI-SearchBot are not shown in ChatGPT search answers (OpenAI), and Google says AI Overviews need nothing beyond a page that is indexed and eligible for a snippet (Google Search Central). Our answer engine optimization team runs this program for B2B companies.

How to choose a Salesforce app development company

Ask for evidence you can check. The right Salesforce app development company will show you code, tests, a release process and a handover plan, and will tell you which of your requests need no code at all.

Marketplace consultant listings and independent list articles help build a longlist; the questions above turn it into a shortlist. Whatever badges a Salesforce development company displays, verify the named team yourself.

How much does Salesforce app development cost?

As published planning ranges, a Salesforce customization of Apex, Flow and Lightning components runs $20,000–$100,000 over one to four months, a single integration $15,000–$40,000 over three to six weeks, and an org assessment $5,000–$15,000. A written scope sets the actual price.

These are planning ranges, not quotes; the quote follows a written scope, and Salesforce license fees are separate. Demand for the service is modest but commercial: “salesforce app development company” draws about 390 US searches a month and “salesforce app development” about 320, with advertisers bidding $22.68 and $30.15 a click respectively (Ubersuggest, September 2026).

Process and timeline for a first Salesforce release

We typically plan a focused first release at about twelve weeks from signed scope to production, and each stage has a measure you can hold us to. Larger programs repeat the build and release stages in cycles.

Related Salesforce, CRM and integration services

Salesforce work rarely stands alone. These services share the same data, and each can be added when it earns its place.

• Custom CRM builds: when Salesforce is not the right platform and a standalone CRM fits better.
• CRM consulting and implementation: selection, cleanup, training and adoption.
• APIs and integrations: the connections between Salesforce, your ERP and your data warehouse.
• Lifecycle marketing automation: the strategy and email programs Marketing Cloud runs.
• ERP development and custom web portals for work outside the Salesforce license.
• Dashboard development: reporting that joins Salesforce with finance and operations data.
• AI integration and custom AI agents connected to your org.
• Software consulting: architecture reviews and build-versus-buy decisions.
• Enterprise app development and fintech software for larger programs.
• n8n automation for workflows that span Salesforce and tools outside it.
• Inventory management software that feeds order and stock data back to the org.

Frequently asked questions