AI stack

Five layers. Governance on top.

For teams adding AI to Salesforce: models, agents, memory and automation chosen layer by layer, with governance on top. Send the layer that hurts and hear back within 24 hours.

Compare runtimes
  1. 01Models · Claude, Gemini, OpenAI, Bedrock
  2. 02Agentic systems · Agentforce, CrewAI, ADK, A2A
  3. 03Agentic memory · Neo4j, Cognee, IndyKite
  4. 04Automation and voice · n8n, Retell
  5. 05Deployment and governance · identity, evals, policy, audit

One request

How one request moves through the stack.

A customer asks a question on WhatsApp. Five stops later the record is right and someone can see why.

  1. Surface

    The customer writes

    On WhatsApp, Slack, a portal or the phone. The agent acknowledges at once.

  2. Gateway

    Identity and policy checked

    The request runs as that person. The gateway decides which tools and models it may call.

  3. Runtime

    The agent does the step

    Agentforce if the work lives in Salesforce. A code agent if it does not.

  4. Memory

    It grounds on what you know

    The customer profile, the last conversation and the approved articles, with permissions attached.

  5. Write

    The record changes once

    A queued write with retries. A timeout never posts twice. The trace is kept.

The five planes, in the order a request meets them. Each stop links to its plane page.

Which layer hurts

Three desks, three missing layers.

Typical first conversations, each starting from one layer.

  • Example

    CTO, Riyadh consumer lender

    Today: Three teams chose three models from three demos. Nobody can say where customer data is processed.

    After: The candidates run the same set of real cases, and the hosting region is named in writing before the pilot.

    For CTOs
  • Example

    Head of service, Dubai property developer

    Today: The assistant answers buyers well, then forgets what it promised them last week.

    After: Profile, working context and past decisions are kept as memory, with the record’s permissions attached.

    Real estate
  • Example

    Operations lead, Kochi NBFC

    Today: Reminder calls end in a notebook. Salesforce never hears what the borrower said.

    After: A voice workflow writes each outcome to the loan record and hands the unsure calls to a person.

    Automation and voice
Examples of the work, not case studies. Roles and cities are typical of the desks we see.

Tools

What we actually put in.

The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.

The brief

Tell us which layer hurts.

One email starts it. We ask about the layer and the org after. 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.