Guide · MuleSoft delivery
Foundation. Scale. Then data.
The first week is in the org, reading what already exists. Kick-off is named owners and three goals. Day-to-day is receipts. We will not run a fabric program on a slide. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
Certified Partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE and US desks
Kick-off
How we start a MuleSoft program.
This is Mindcat practice. It is not a Success Plan brochure.
Sequence
Three phases. Aggressive on the first.
01
Foundation
Team MCP servers and non-product model calls through Flex Gateway. No exceptions except the product surface you already sell. Identity on the hop.
02
Scale
Four policy families live: identity, field, row, action. One production worker on a named desk. Slack or Salesforce into Agent Fabric into Agentforce, with a rollback.
03
Data
A small number of systems of record through MuleSoft. Lineage locked. No new sources after the cutoff. Demo only if the receipts exist.
Mermaid source
flowchart TD
P30["Foundation: MCP and model calls through Flex Gateway"] --> P60["Scale: policy families and one production worker"]
P60 --> P90["Data: few systems of record through MuleSoft, lineage named"]Risks
What we manage in the open.
Questions
What we actually say.
- Is this a fixed 90-day package?
- No. The sequence is the model. The calendar depends on whether identity and the gateway already exist. We will not print a day count as a promise.
- Where are the receipts?
- The operating-model note. Every commitment has a claim, an artifact, and an owner.
Next
What to read next.
The brief · one email
Name the owners. Name the first system.
We will tell you whether foundation is a week or a quarter.
