Salesforce Platform
Salesforce Platform. The app that belongs next to the CRM.
The Salesforce Platform is for the app that belongs next to the CRM. Flow first. Apex when the job needs it.
Salesforce consulting partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE, India and US desks
In the org
What this cloud is actually for.
The Salesforce Platform is for the app that belongs next to your CRM, and for the events that let work leave the org without blocking whoever clicked save. Flow first, Apex when the job needs it.
Who this is for
Three apps that belonged next to the CRM.
Flow first. Apex when the job needs it.
Example
Operations manager at an Abu Dhabi equipment-rental firm
Today: Rental contracts, inspections and returns are tracked in a sheet next to Salesforce.
After: Contracts, inspections and returns live on custom objects beside the account, and Flow sends the return reminder.
Example
Salesforce admin at a Dubai insurance broker
Today: A trigger written years ago times out whenever the policy system is slow.
After: The trigger publishes an event and returns, so saving a policy no longer waits on the other system.
Example
IT lead at a Dallas title company
Today: Closings are tracked across email and a legacy desktop tool.
After: A closing app on the platform, with the checklist and documents on one record.
Event fabric
How work leaves the org without blocking a user.
Flow, Apex, platform events, and change data capture are the Salesforce half of the durable plane. Get this wrong and every integration becomes a synchronous callout someone waits on.
On save
Flow
The deterministic step runs declaratively. No model, no code.
When code is needed
Apex publishes an event
Instead of holding the transaction open while another system thinks.
Seconds later
Platform events and Pub/Sub hand the work to an asynchronous consumer.
Continuously
Change data capture feeds memory and analytics, instead of a nightly poll that drifts.
Architecture
Where this cloud sits in your agent architecture.
Flow, Apex, and platform events are how work leaves the org without blocking a user.
Find your week
From one email to a desk that works.
The same path for every cloud. No number before the process is clear.
Today
Send the situation
One email: the cloud, the desk, and the week that hurts. A reply within 24 hours.
Week one
Read the org
Read-only access: the custom objects, Flows and Apex you run, the ones that time out, and the app your desk keeps asking for.
End of week one
The written note
What is worth building, what is worth finishing, and which cloud earns the seat. Often fewer than you were quoted.
Then
A fixed price for one named piece
Scoped after the read. Week one is credited in full when the build is signed within 60 days.
Go-live
Handover to the people who run it. The Run plan if you want someone on it after go-live.
Questions
What we actually say.
- Flow or Apex?
- Flow first. Apex when the job needs it. We will not write Apex to look busy.
- Is this a licence to rebuild the ERP in Salesforce?
- No. If the work is a software factory with a named delivery date, we are the wrong partner.
- Heroku?
- When the customer-facing app must sit outside the org. Not as a default.
The brief
Send the situation.
Name the cloud. Name the week. The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days.