Integrations
Salesforce connected to the ad order system, the ERP, the subscription platform, and the reporting layer, so a deal is entered once.
Read moreSalesforce · Extension
Code, when it earns its place.
Salesforce can be configured further than most orgs are. When configuration runs out, we write Apex, Lightning Web Components, and integration code, in source control, with tests, so the next admin can read it and the next release does not break it.
When this is the right engagement
- A process needs logic Flow cannot express or cannot express safely
- Sellers need data from the ad server or the ERP on the record without a full sync
- A previous developer left Apex with no tests and no documentation
- Release upgrades keep breaking something nobody understands
- A small application belongs inside the CRM
What you get
- Flow automation before code, and a written reason when code is chosen
- Apex triggers, classes, and batch jobs with test coverage well above the minimum
- Lightning Web Components for the screens the standard layouts cannot deliver
- Integration code on the Salesforce APIs
- Source control, deployment pipeline, and documentation your team can maintain
How it runs
- 01
Confirm configuration will not do it
The cheapest code is the code you do not write.
- 02
Specify the behavior and the failure modes
What it does, what it does when the other system is down, and who finds out.
- 03
Build in source control
Your repository, our commits, tests included.
- 04
Test in a sandbox with real records
The advertisers, orders, and edge cases that will actually hit it.
- 05
Deploy, monitor, document
Released through a pipeline, watched, and written up for whoever comes next.
Questions we get
Will custom code lock us in?
Not if it is done properly. Everything we build lives in your source control, uses supported APIs, and comes with documentation. You can hand it to any Salesforce developer.
Work and news
Notes from Salesforce engagements.
Case studies from Salesforce engagements are being prepared for publication. The record above is public in the meantime.
Start with the stuck point
What should Salesforce be doing that it isn’t?
Bring the workflow, handoff, or report that keeps resurfacing. We will tell you whether it is a Salesforce problem, a data problem, or a systems problem, and what to do about it.