Salesforce MVP Hall of Fame (Shivanath Devinarayanan) · Founded 2022
Claude in Slack
Work that spans documents, tickets and other tools gets passed around in DMs. Claude joins the channel as a shared teammate on one named job, and the whole team sees what it did.
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
Work in Slack, before and after.
Today
With the agent
- Work passed around in DMs
- Claude in the channel on one named job
- Each person pastes into their own chat
- A shared teammate, not a private chat
- Nobody sees what was done
- The channel sees every step it took
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
Team lead at a US professional services firm
Today: Client updates are pieced together from documents and tickets in private messages.
After: Claude drafts the update in the channel from the sources, and the team approves it in the thread.
The job
What has to be true.
Shared teammate
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.
