Is this a Success Plan brochure?

No. This is how Mindcat runs the program. Named owners and receipts. The delivery sequence lives on the MuleSoft delivery note.

Where do the receipts live?

In the org, the gateway, and the queue. A slide is not a receipt.

Guide · program operations

A claim. A receipt. An owner.

The first week is in the org, reading what already exists. Kick-off names the people. Day-to-day is artifacts, not slides. Escalation is a map, not a thread. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.

Get the written assessment

Certified Partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE and US desks

MuleSoft delivery

Program ops

Every commitment has three parts.

01
Claim
The work, in a sentence. Not a slide title.
02
Receipt
A policy, a trace, a mapping, a reviewer queue. Something that exists when we are gone.
03
Owner
One person who can change it. Written down at kick-off.
04
Escalate
The next named person when the owner is stuck. Not a group chat.

Public operating model for an agent or MuleSoft program. A claim is the commitment. A receipt is the artifact. An owner is the person who can change it. Escalation is who they call when it is stuck.

Mermaid source

flowchart TD
  A["Claim: what we said we would do"] --> B["Receipt: the artifact"]
  B --> C["Owner: who can change it"]
  C --> D["Escalate: named next person"]

Map

What we keep on the map.

Questions

What we actually say.

Is this a Success Plan brochure?: No. This is how Mindcat runs the program. Named owners and receipts. The delivery sequence lives on the MuleSoft delivery note.
Where do the receipts live?: In the org, the gateway, and the queue. A slide is not a receipt.

The brief · one email

Name the owners. Name one claim.

We will tell you whether the receipt already exists, or whether the program is still a slide.