Salesforce MVP Hall of Fame (Shivanath Devinarayanan) · Founded 2022
Marketing campaigns
Journeys on a customer the org already knows. Consent first. Marketing Cloud when the send can stand behind the list.
Founded 2022 · Founder in the Salesforce MVP Hall of Fame · Dubai HQ · Kochi studio
The stack
How we would assemble it.
The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
Before and after
Campaigns, before and after.
Today
With the agent
- Lists merged from several tools before each send
- One customer view before the send
- Consent checked in a spreadsheet
- Consent travels with the record
- Journeys only one person can change
- Journeys the team can edit
Spec, shadow, gate
How the first agent goes live.
One named job. A shadow run before any write.
Week one
The job on one page: inputs, the write, the limit, who approves, and what it may never do.
Before go-live
The agent acts as the person it works for, with their access. Knowledge and permissions checked before it takes a job.
Shadow run
Shadow
The agent runs beside the person and writes nothing. You compare its calls with theirs.
Go-live
Writes go live behind a human approval. The gate loosens only where the shadow run earned it.
Every week
Every run is logged. On the Run plan we read the transcripts every week and fix what went wrong.
For example
One desk, for example.
Example
Marketing head at a Dubai retail group
Today: Each campaign starts with merging lists and checking consent by hand.
After: The send goes to customers the org already knows, with consent on each record. The team edits the journey themselves.
The job
What has to be true.
Campaign desk
The brief
Send the situation.
Name the process. Name the object. 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.