A CRM that stays
easy to change
We design, build and support setups on the Salesforce platform, with automation in one place, integrations on supported sign-in and access set for each job, so you know what each change will touch.
Thanks, we’ll be in touch soon.
{{ heroStatus }}
You’re in good company
A few of the companies we’ve worked with.
When no one is sure what runs on save
Many companies have run their Salesforce org, the account that holds their records and everything built around them, for years. Each team added fields, automation and integrations as it needed them, one need at a time.
So one object, a kind of record such as an account or a case, can carry an old workflow rule, a process, several flows and a trigger written in Apex, Salesforce’s own programming language. Salesforce documents the order they run in on each save, but few people in the company know it, and a small change can set off something no one expected.
Workflow Rules and Process Builder still run, though Salesforce no longer supports them, and some integrations still sign in with a user’s username and password, a method Salesforce has set a date to retire. So in many orgs, each change takes longer to test than to make.
What we build
Work on the Salesforce platform that fits how your teams sell and serve, linked to the other systems you run, with each change tried in a sandbox, a copy of your org kept apart for building and testing, before it reaches your live org.
Setups designed for how you sell and serve
Standard objects first, such as accounts, contacts, cases and opportunities, Salesforce’s name for deals, then custom objects and fields only where your work needs them, with record types and page layouts so each team works with the fields and steps it uses.
Automation moved to Flow
Workflow Rules and Process Builder rebuilt as flows, the automation Salesforce now recommends, with what runs on each object, and in what order, written down and tested before the old rules are switched off.
Code where configuration stops
Code in the Apex language, Salesforce’s own, and Lightning Web Components for the screens your teams work in, written for the limits the platform sets on each transaction, with the tests Salesforce requires before code can reach production.
Access set for each job
Permission sets, small named bundles of what a person can do, grouped for each job, and sharing set so people see the records their work needs, as the section below shows.
Integrations on supported sign-in
Connections to the systems you run, built as external client apps, which Salesforce recommends for new integrations, each signing in by a method Salesforce supports and running as its own user, with only the access it needs.
Sites for customers and partners
Experience Cloud sites your customers or partners sign in to, built on the same records your teams use, such as a customer’s own cases or the deals a partner works on with you, each visitor with the license their access needs.
Moves onto the Salesforce platform
Accounts, contacts and their history brought in from spreadsheets or another CRM, with duplicates found first, using matching rules, Salesforce’s way of spotting likely duplicates, so each customer arrives once.
Releases tested before they arrive
Each of Salesforce’s releases tried in a preview sandbox before it reaches your live org, release updates turned on early in a sandbox to see what they change, and your own changes moved to production in planned steps, each checked before it ships.
AI agents where they help
Agents built on the Agentforce platform, Salesforce’s own tools for AI agents, for useful tasks on your records, with controlled access and a person approving what matters. For the AI assistants your team already uses, Salesforce’s hosted MCP servers, on Enterprise Edition and above, act as the person signed in, within their own access.
- Connecting any of your systems:Systems & API Integration
- Automation across your tools:Workflow Automation
- Care once it’s live:Support & Maintenance
- Storefronts on the same platform:Storefront development, built on the Agentforce Commerce platform
- Developers in your own team:Hire developers for your Salesforce org
Each person sees what their job needs
In a Salesforce org, what a person can do comes from their profile and from the permission sets they’re given: which objects they can open, and which fields on them they can read or edit. Permission sets are named bundles of access, and several can be grouped into a permission set group for one job.
Which records they see comes from sharing: the org-wide defaults set how much of each other’s records people see, the role hierarchy lets managers see their teams’ records, and sharing rules open records up to the groups who need them.
Salesforce recommends, where possible, a minimum-access profile for each person, with access added through permission sets and permission set groups, by the tasks people do rather than their job title. So we design access around the work, and each integration runs as its own user with only what it needs, instead of one exception at a time.
Permission sets
Account manager
- {{ c.name }}
- {{ c.text }}
Support lead
- {{ c.name }}
- {{ c.text }}
Access comes in small, named sets, each given for the job someone does.
{{ acStatus }}
The platform moves three times a year
Salesforce upgrades every org itself, three times a year, in releases named for Spring, Summer and Winter. There’s no upgrade project to run, but everything built on the platform has to keep working through each one.
A sandbox can get each release a few weeks before your live org does, in Salesforce’s sandbox preview, so your changes and customizations can be tried on it there first. Some changes come as release updates instead, each enforced from a date Salesforce sets, and many can be turned on early in a test run, so you can see what they change before they arrive.
Older methods reach their end on dates Salesforce sets. Workflow Rules and Process Builder have had no support or bug fixes since December 31, 2025. Since the Spring ’26 release, creating new connected apps, the older way to set up how an integration signs in, has been disabled by default, and Salesforce recommends external client apps instead. The OAuth username-password flow, where an integration signs in with a user’s password, is set to be retired for connected apps on February 20, 2027.
So we test each release before it arrives, and move each older method in planned steps, before its date.
Start with a review of your org
The review covers your objects and fields: which are in use, which duplicate each other and which reports depend on them; what runs on each object, in what order, and how much is still Workflow Rules or Process Builder; your Apex and Lightning Web Components, and their tests; each integration, what it reads and writes, how it signs in, whether it’s a connected app or an external client app, which user it runs as and the access it holds; your profiles, permission sets and sharing, and who can export data; your data, its duplicates and where they come from; and your sandboxes, how changes reach production and how release updates are tested.
Starting on the Salesforce platform, or adding an integration? The first step is the data model and one connection, built and tried in a sandbox with real records, then released early, so your team works with it before the rest is built.
Either way, you get a written review and a proposal for the first step.
Questions worth asking
Our org still runs Workflow Rules and Process Builder. Is that a problem?
Not straight away. Salesforce says active rules and processes keep running as they did, but it has given no support or bug fixes for them since December 31, 2025, and recommends moving them to Flow. We list what each one does, rebuild it as a flow in a sandbox, check it does the same work, then switch the old ones off in planned steps.
Will Salesforce’s changes to sign-in affect our integrations?
Only those that use the methods being retired. Salesforce is set to retire the OAuth username-password flow for connected apps on February 20, 2027, after which integrations that still sign in that way can’t, and it names the supported flows to move to. Creating new connected apps is disabled by default, while existing ones keep working, and Salesforce recommends external client apps for new integrations. The review lists how each of yours signs in, and what to move first.
Should we build with Flow, or with code?
Flow where it fits, and Apex where the logic needs it. Salesforce recommends Flow for the automation Workflow Rules and Process Builder used to do, and we use Apex where the logic is complex or has to handle many records at once. We choose for each object, and write down which runs where, so the two don’t work against each other.
Can you tidy an org that’s grown over many years?
Yes. The review comes first: what’s used, what runs on each save and what each integration relies on. Then changes go in planned steps, each tried in a sandbox, so the org keeps working while it’s tidied, and nothing is removed until we know what depends on it.
How do you test before each release?
A sandbox on Salesforce’s preview gets each release a few weeks before your live org, so we run your key processes and tests there first. Where a release update that applies to you has a test run, we turn it on early in a sandbox to see what it changes, and fix anything that needs it before Salesforce enforces it.
Can our AI assistants or agents use our Salesforce data?
Yes, within each person’s access. The Agentforce platform, Salesforce’s own tools for AI agents, works with your records on the platform. For the assistants your team already uses, Salesforce’s hosted MCP servers, generally available on Enterprise Edition and above, let them read and act on your data as the person signed in, with that person’s permissions and sharing applied, and their name on any change they make. We start with read-only access, then add only what the work needs.
Can you build a portal for our customers or partners?
Yes, with Experience Cloud sites, where people outside your company sign in to the same records your teams use: customers can follow their own cases, and partners can work on the deals they share with you, each with the license their access needs. Where a portal needs more than that, we build it in your own product, connected to your Salesforce org.
Web & App DevelopmentDo we need more Salesforce licenses for this?
Sometimes. Some features need certain editions or licenses: Salesforce’s hosted MCP servers need Enterprise Edition or above, and people outside your company who sign in to an Experience Cloud site need licenses of their own. Before anything is bought, we say which the work needs, and where we can, we build on the edition and licenses you already have.
Can you move us onto the Salesforce platform from another CRM or from spreadsheets?
Yes. We map your data to Salesforce’s objects and fields, set matching and duplicate rules so each customer is kept once, and import a sample first, checking it with your team before the full import, history included.
Can you take over our existing setup?
Yes. We begin with a read-only look at the org: its objects, automation, code and integrations, and who holds which permissions. Then the review sets out what to change first, and nothing in your live org changes until you’ve agreed to it.
Can it connect to our ERP, billing and product?
Yes. We agree first which system is in charge of each field, then connect them through Salesforce’s APIs, each connection as its own user with only the access it needs, documented and monitored once it’s live.
Systems & API IntegrationHow do you keep our data secure?
Access is set for each job, and each integration runs as its own user with only the access it needs, signing in by a method Salesforce supports. Every change is tried in a sandbox before it reaches your live org. Our security work adds threat modeling, code review and checks in every build.
Application SecurityWhat does it cost?
The price follows the work: how much the org holds and runs, and whether it’s being set up, tidied or extended. You get a written proposal before any work starts: the scope, the price or rate, and how you pay.
PricingCan your developers join our own team?
Yes. Tell us what your org needs, and we’ll introduce developers who build on the Salesforce platform, matched to it, within 48 hours, working in your time zone. You meet them and decide who joins.
Hire developers for your Salesforce org
Salesforce, Agentforce, Apex, Experience Cloud and Lightning are trademarks of Salesforce, Inc., and the other Salesforce product names on this page may be too. Webair is independent of Salesforce, Inc., and isn’t sponsored by, endorsed by or affiliated with it.
Let’s build it better
Tell us what runs in your org today and what you’d like it to do next. A short call is enough to see where to start.
Thanks, we’ll be in touch soon.
{{ ctaStatus }}