The blast radius is the price.

After the free thirty minutes I estimate — in front of you — how many hours it takes to name the cause. That estimate becomes the fixed price.

Pick the one that sounds like yours.

— boundary your problem reaches┄ boundary beyond it where the cause gets named

4–6 hours to name the cause.

The cut crosses 2 of five boundaries. One workflow, one team, one owner. The cause is inside a boundary you can draw.

The estimate is made in front of you on the call, and it becomes the fixed price before any work starts.

8–14 hours to name the cause.

The cut crosses 4 of five boundaries. Two or three functions touch it and each has a different account of what happened.

The estimate is made in front of you on the call, and it becomes the fixed price before any work starts.

16–24 hours to name the cause.

The cut crosses 5 of five boundaries. The symptom is downstream of how decisions get made, not of any one workflow.

The estimate is made in front of you on the call, and it becomes the fixed price before any work starts.

I do not bill discovery as delivery. If thirty minutes is enough to name it, that is the whole engagement and it is free.

The estimate happens on the call, not after it.

You watch the hours get counted. If it turns out smaller than I said, it gets smaller. If thirty minutes settles it, there is nothing to invoice.

Step 1 of 3

Where does the symptom keep returning?

Free 30 minutes. Bring the recurring symptom; we will test whether problem mapping is the right next move.