Salesforce architecture & engineering
We simplify Salesforce orgs and leave them documented for the next team.
Every org accumulates flows, triggers and fields that each made sense on the day they shipped. We simplify what is there, build what is missing and leave an org the next team can run.
What happens when a record saves
Automations added over the years often fire on the same save and overwrite each other.
What fires when one account saves. Two pairs write the same field, and the order changes from save to save.
Both write the owner Both write the status
One entry point per object. Each step runs once, in a fixed order.
- Set regionFrom the billing country, once
- Assign ownerFrom the routing table, once
- Update statusOne rule, written down
- Sync to other systemsAfter the record is final
Do these sound familiar?
What we deliver
- Org assessmentEvery object, flow, trigger and integration mapped, with dependencies checked against Apex, Flow and dynamic references.
- Automation consolidationRacing before-save flows and legacy workflow rules collapsed into one governed pattern per object.
- Apex & Lightning Web ComponentsBulk-safe, tested code for logic Flow cannot carry: contract assembly, metrics engines, guided pages.
- Security & accessProfiles consolidated, permission sets by role, integration users on least privilege, break-glass recovery.
- Release disciplineSource control, validate-then-quick-deploy and a read-back of what landed in production.
- Reporting cleanupDead reports and dashboards retired on usage evidence, so what remains gets read.
This practice in our case studies
- A decade of org debt, retired without an outageTen years of automations, profiles and stored history had piled up. The org was simplified without an outage or a locked-out user.
- A new sales process for every live deal, in one eveningLeadership wanted five stages with exit criteria. Every open deal moved in one evening, and the reports leadership reads each week kept their history.
Questions before we start
Do you write code or configure?
Both. Flow where it holds up, Apex where the logic needs bulk safety, tests and reuse, and Lightning Web Components where people need a better screen.
Can you work in an org another partner built?
Yes. Most engagements start with an assessment of what is already there, including the parts nobody documented.
How do you deploy safely?
Sandbox first, a validation against production, a quick deploy of the validated set, then a read-back of what landed. A success message on its own is never the test.
Integrations and guides
- Salesforce data storage over the limit: what to delete firstWhen data storage passes 100%, inserts start failing, and integrations usually fail first. The fix is rarely more storage. It is usually years of activity history nobody reads.
- Salesforce record page blank in the mobile appThe record opens on a phone with a header and nothing else, while the same record looks fine on a laptop. If the page uses Dynamic Forms, the cause is usually the phone assignment.
Related practices
- Systems integrationSalesforce connected to your commerce, warehouse, contract, billing and support systems, with one owner for every field and an alert when a sync goes quiet.
- Data unification & migrationOne record per customer across regions and platforms, merged and migrated with a rollback for every change.
- Revenue & contract operationsThe deal, the signed contract and the bill kept in agreement, from the first quote to the renewal.
- AI agents & readinessIdentity, definitions and permissions fixed before any AI agent reads your records, with cost and accuracy measured.
Talk to us about your systems.
Tell us which systems are involved and what is going wrong. We reply within one business day, and new engagements begin in January 2027.
hello@feldtgroup.com